Messages in this thread | | | Date | Mon, 29 May 2006 10:50:31 -0400 | From | Dave Jones <> | Subject | Re: 2.6.17rc emu10k1 regression. |
| |
On Mon, May 29, 2006 at 11:43:56AM +0200, Takashi Iwai wrote:
> > modprobe.conf has .. > > alias snd-card-0 snd-emu10k1 > > options snd-card-0 index=0 > > options snd-emu10k1 index=0 > > remove snd-emu10k1 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-emu10k1 > > > > What changed ? > > Nothing from ALSA side. Maybe the module loading mechanism (or slot > order) was changed on your system. > > The scenario is: > > intel8x0 driver is first loaded on the first empty slot (index=0) > before snd-emu10k1. Since you set index=0 module option for > snd-emu10k1, it tried to load on the same slot but failed. > > A workaround is to set index=1 option for snd-intel8x0 in addition, > for using emu10k1 as the primary card.
The modprobe.conf also had an index=1 entry already for the intel driver.
Dave -- http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |