[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <200702272059.17644.vinctre@videotron.ca>
Date: Tue, 27 Feb 2007 20:59:17 -0500
From: Veronique & Vincent <vinctre@...eotron.ca>
To: Takashi Iwai <tiwai@...e.de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Sound 2.6.19: Soundcard driver often fail to load?
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists