The following advice worked for OSS modules on my A7V600; don't know about ALSA: > the sound works well in 2.4 kernel but you have to plug the audio > output were the microfone usualy goes because of the 5.1 chanells of > the sound card and turn the microfone volume to mute. I didn't figure > it out how to switch them to normal. Zach ----- Original Message ----- From: "Don Levey" <fedora-list@xxxxxxxxxxxxx> To: <fedora-list@xxxxxxxxxx> Sent: Monday, January 05, 2004 9:32 PM Subject: ALSA question in FC1 (VIA VT8233/A/8235) > I've checked the archives and not found anything relating to this problem, > so please excuse the interruption if I am in error. > > I've put together my new machine, using an ASUS A7V8X-X motherboard, and > installed FC1. The on-board sound module is detected (accurately, it seems) > as a VIA VT8233/A/8235 AC97 chipset. This is consistent with the board > manufacturer, who says it's got an ADI 1980 (which the ALSA webpage says > uses the 8233/35 chipset and the AC97 CODEC). All well and good, but I > don't get any sound... > > I installed and built ALSA from their sourcem following the instructions at > http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Analog+Dev > ices&card=AD1980&chip=AD1980&module=via82xx (http://tinyurl.com/ywu3e). > This builds 4 modules: > snd-via82xx > snd-pcm-oss > snd-mixer-oss > snd-seq-oss > > Running the install line (modprobe on each of those), I get a few errors on > the first and last module: > [root@dauphin sysconfig]# modprobe snd-via82xx;modprobe snd-pcm-oss;modprobe > snd-mixer-oss;modprobe snd-seq-oss > /lib/modules/2.4.22-1.2115.nptl/kernel/sound/pci/snd-via82xx.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.22-1.2115.nptl/kernel/sound/pci/snd-via82xx.o: insmod > /lib/modules/2.4.22-1.2115.nptl/kernel/sound/pci/snd-via82xx.o failed > /lib/modules/2.4.22-1.2115.nptl/kernel/sound/pci/snd-via82xx.o: insmod > snd-via82xx failed > /lib/modules/2.4.22-1.2115.nptl/kernel/sound/acore/seq/oss/snd-seq-oss.o: > init_module: Device or resource busy > 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.22-1.2115.nptl/kernel/sound/acore/seq/oss/snd-seq-oss.o: > insmod > /lib/modules/2.4.22-1.2115.nptl/kernel/sound/acore/seq/oss/snd-seq-oss.o > failed > /lib/modules/2.4.22-1.2115.nptl/kernel/sound/acore/seq/oss/snd-seq-oss.o: > insmod snd-seq-oss failed > > The output from dmesg suggests that there is an IRQ conflict, though it's > unclear to me which way it goes (something about IRQs 3&4). Windows (it's a > dual-boot) says the sound module is using IRQ-22, which is of no help. Is > there a utility that will help me truly detect the IRQ of the device? Once > I do, does anyone know where I can specify the correct IRQ when loading the > modules? > > Thanks for your help, and patience, > -Don > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list >
