I have to start with this question, is the sound card attached to the motherboard?

Peronally i don't believe that the nvidia2 chipset was packaged with an intel sound card (i could be wrong here, i've never used that chipset). A good way to detect the sound card would be to boot up with a knoppix CD and see what it finds( i use that on all foriegn hardware computers so i know what i'm dealing with).

If i'm totally wrong, and you do have an intel sound card, please feel free to tar & feather me... i've earned it.

bryce

Leandro Monk wrote: > Hi: > > I 've try to use the alsa driver for my nforce2... when i try load the > module snd-intel8x0, the system say me: > > /lib/modules/2.4.26-1-386/alsa/snd-intel8x0.o: init_module: No such > device > Hint: insmod errors can be caused by incorrect module parameters, > including invalid IO or IRQ parameters. > You may find more information in syslog or the output from dmesg > /lib/modules/2.4.26-1-386/alsa/snd-intel8x0.o: insmod > /lib/modules/2.4.26-1-386/alsa/snd-intel8x0.o failed > /lib/modules/2.4.26-1-386/alsa/snd-intel8x0.o: insmod snd-intel8x0 > failed > > My /proc/pci is: > > Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio > Controler (MCP) (rev 161). > IRQ 5. > Master Capable. No bursts. Min Gnt=2.Max Lat=5. > I/O at 0xd800 [0xd8ff]. > I/O at 0xdc00 [0xdc7f]. > Non-prefetchable 32 bit memory at 0xec002000 [0xec002fff]. > Bus 0, device 8, function 0: > > I use Debian sarge, and instal this packages: > > alsa-base, alsa-modules, alsa-utils. alsa-lib > > ¿Any idea to fix this problem? >

I use Knoppix 3.3 whit alsa parameter and load succefuly whit snd-intel8x0 module El mar, 21-09-2004 a las 18:45, Leandro Monk escribió:

Remember those words... We will probably see this problem a lot in the future. To resume: discover loads the OSS drivers when "discovering" the sound devices. Obviously, if a user installs alsa, the logical thing would be to blacklist the OSS drivers in the /etc/discover.conf automatically. But the problem is that, Debian policy, the alsa package is not allowed to change the configuration of another package. So the user has to add the blacklist to /etc/discover.conf himself. As for as I understand, the solution would be to change discover configuration from a single file to a directory, where alsa can add it's blacklist during installation. A similar mechanism is already being used with hotplug)