From: Veronique & Vincent <vinctre@videotron.ca>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sound 2.6.19: Soundcard driver often fail to load?
Date: Tue, 27 Feb 2007 20:59:17 -0500 [thread overview]
Message-ID: <200702272059.17644.vinctre@videotron.ca> (raw)
In-Reply-To: <s5hk5y95da1.wl%tiwai@suse.de>
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
next prev parent reply other threads:[~2007-02-28 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 10:50 Veronique & Vincent
2007-02-23 11:22 ` Takashi Iwai
2007-02-28 1:59 ` Veronique & Vincent [this message]
2007-02-28 14:34 ` Lee Revell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200702272059.17644.vinctre@videotron.ca \
--to=vinctre@videotron.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®