On Mon, Aug 11, 2003 at 04:47:08PM -0600, Jamin W. Collins wrote:
> On Mon, Aug 11, 2003 at 11:05:43PM +0100, Antony Gelberg wrote:
> > On Mon, Aug 11, 2003 at 03:22:23PM -0600, Jamin W. Collins wrote:
> > >
> > > You can try using the i810 alsa module inplace of the nvaudio module
> > > (at least it works here).
> >
> > That's interesting. My friend has an nforce2 mobo, and the alsa i810
> > module doesn't want to load. See:
> > http://lists.debian.org/debian-user/2003/debian-user-200308/msg01696.html
> >
> > The OSS i810 in 2.4.21 loaded, but kept locking up. How did you get
> > the alsa driver to load?
>
> Just grabbed the alsa-source package (v0.9.2 is what I have installed),
> extracted it and used make-kpkg to build it for my kernel (2.4.20 with a
> few patches). Then installed the resulting debs, which created the
> needed /etc/modutils/alsa file. From there it's just worked.
>
> $ lspci | grep audio
> 00:05.0 Multimedia audio controller: nVidia Corporation nForce
> MultiMedia audio [Via VT82C686B] (rev a2)
> 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97
> Audio Controler (MCP) (rev a1)
I tried this already on his machine. The device was listed as "unknown
device". I don't have the exact text to hand. I wonder if he has a
variant of that chip with a different PCI ID? In which case, do I need
to hack the kernel source, or one of the various pci.ids files lying
around?
A