Sound 2.6.19: Soundcard driver often fail to load?

Sound 2.6.19: Soundcard driver often fail to load?

[Veronique & Vincent]

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]


Hi,

I'm currently running a 2.6.19 kernel and 2 times out of 3 the sound driver fails to load hence probing me a no sound device available in KDE.

Once I reload the driver this output goes into the dmesg:
usbcore: deregistering interface driver snd-usb-audio
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:04.0 to 64
intel8x0_measure_ac97_clock: measured 51418 usecs
intel8x0: clocking to 46862

I've attached the dmesg and the lspci -vvv.

Could the snd-usb-audio interfere with the on-board sound driver?

- vin

[-- Attachment #2: dmesg-2.6.19-NoSound.zip --]
[-- Type: application/x-zip, Size: 7890 bytes --]

[-- Attachment #3: lspci-vvv.txt.zip --]
[-- Type: application/x-zip, Size: 3088 bytes --]

Re: Sound 2.6.19: Soundcard driver often fail to load?

[Takashi Iwai]

At Wed, 21 Feb 2007 05:50:48 -0500,
Veronique & Vincent wrote:
> 
> Hi,
> 
> I'm currently running a 2.6.19 kernel and 2 times out of 3 the sound driver fails to load hence probing me a no sound device available in KDE.
> 
> Once I reload the driver this output goes into the dmesg:
> usbcore: deregistering interface driver snd-usb-audio
> ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
> ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 22
> PCI: Setting latency timer of device 0000:00:04.0 to 64
> intel8x0_measure_ac97_clock: measured 51418 usecs
> intel8x0: clocking to 46862
> 
> I've attached the dmesg and the lspci -vvv.
> 
> Could the snd-usb-audio interfere with the on-board sound driver?

Yes, if you set index=0 module option to snd-intel8x0 driver and
nothing to snd-usb-audio, they may conflict according to the order of
loaded modules.  Pass index=1 (or index=-2) to snd-usb-audio module
option to make the index order consistent.


Takashi

Re: Sound 2.6.19: Soundcard driver often fail to load?

[Veronique & Vincent]

Le vendredi 23 février 2007, vous avez écrit :
> At Wed, 21 Feb 2007 05:50:48 -0500,
> Veronique & Vincent wrote:
> > 
> > Hi,
> > 
> > I'm currently running a 2.6.19 kernel and 2 times out of 3 the sound driver fails to load hence probing me a no sound device available in KDE.
> > ....
> > Could the snd-usb-audio interfere with the on-board sound driver?
> 
> Yes, if you set index=0 module option to snd-intel8x0 driver and
> nothing to snd-usb-audio, they may conflict according to the order of
> loaded modules.  Pass index=1 (or index=-2) to snd-usb-audio module
> option to make the index order consistent.
> 

Now there is a bug opened up at redhat:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229227

I've ran into this info:
http://www.lavrsen.dk/twiki/bin/view/PWC/FrequentlyAskedQuestionsPWC#modprobe_fails_with_FATAL_Error
and did removed the index=X line associated with the pwc driver.  This still create a problem from time to time.

Seems like the index=X option is broken in the alsa driver (or maybie deprecated, remove, buggy, duno?). There is another way to fix the problem by using a /etc/asound.conf file (see http://alsa.opensrc.org/FAQ026) and removing the index=X entries from your mdoprobe.conf file

Maybie the Fedora team should use the asound.conf configuration instead?

> Takashi

thnx!

- vin

Re: Sound 2.6.19: Soundcard driver often fail to load?

[Lee Revell]

On 2/27/07, Veronique & Vincent <vinctre@videotron.ca> wrote:
> Maybie the Fedora team should use the asound.conf configuration instead?

This doesn't work for apps that use the deprecated /dev/dsp API.

Of course, a modern distro should be trying to purge these anyway...

Lee