From: Takashi Iwai <tiwai@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: alsa-devel@alsa-project.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17rc emu10k1 regression.
Date: Mon, 29 May 2006 11:43:56 +0200 [thread overview]
Message-ID: <s5hejydtbc3.wl%tiwai@suse.de> (raw)
In-Reply-To: <20060528164015.GA13499@redhat.com>
At Sun, 28 May 2006 12:40:15 -0400,
Dave Jones wrote:
>
> $ lspci | grep audio
> 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
> 06:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 04)
>
> (That's 06:0d.1 0980: 1102:7002 (rev 01))
>
> This worked fine in 2.6.16, however when I try a .17rc kernel I get this..
>
> cannot find the slot for index 0 (range 0-1)
>
> EMU10K1_Audigy: probe of 0000:06:0d.0 failed with error -12
>
> (Unremarkable, considering it *isn't* an Audigy)
>
>
> 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.
Takashi
next prev parent reply other threads:[~2006-05-29 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 16:40 2.6.17rc emu10k1 regression Dave Jones
2006-05-28 16:51 ` [Alsa-devel] " James Courtier-Dutton
2006-05-28 16:53 ` James Courtier-Dutton
2006-05-28 16:53 ` Dave Jones
2006-05-29 9:43 ` Takashi Iwai [this message]
2006-05-29 14:50 ` Dave Jones
2006-05-29 14:53 ` Takashi Iwai
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=s5hejydtbc3.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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