At Mon, 16 Jun 2008 13:13:20 +0200,
Jean Delvare wrote:
Le lundi 16 juin 2008, Takashi Iwai a écrit :
At Mon, 16 Jun 2008 10:32:30 +0200,
Jean Delvare wrote:
Le samedi 14 juin 2008, Andreas Jaeger a écrit :
* hda intel does not work (phonon tells me
it's broken and uses pcspeaker instead),
hda_intel: probe_mask set to 0x1 for device 17aa:20ac
PCI: Setting latency timer of device 0000:00:1b.0 to 64
input: PC Speaker as /devices/platform/pcspkr/input/input8
Taking a blind shot... Could it be that the PC speaker driver registers
as a regular ALSA device now and comes up before hda_intel, becoming
the default audio device? Check if "aplay -l" returns more than one
card. Maybe you have to tell ALSA which "card" is #0 and which one is
#1. I think Yast has an interface to set this.
It's not about YaST but rather auto-loading mechanism.
As a workaround, just add snd-pcsp to /etc/modprobe.d/blacklist.
I mentioned Yast just as an easy way to change the audio device index
values, so that snd-hda-intel remains the main audio device. I guess
that editing /etc/modprobe.d/sound manually the following way would
work as well:
options snd-hda-intel enable=1 index=0
options snd-pcsp enable=1 index=2
(or even enable=0 for snd-pcsp)
On 11.0, it works better with snd slots option. Now YaST sets
options snd slots=snd-hda-intel
which will reserve the first slot for snd-hda-intel driver, so this
problem won't occur.
Maybe the module config of Andreas is from the older version.
I am curious what are the integration plans for the
We certainly want to include this driver in our products, for the
users who want it. But OTOH we have to make sure that it will not be
the default sound device. Does this mean that we blacklist the
snd-pcsp driver if a real sound card is found during installation?
Do we blacklist it by default and let it up to the few interested
users to remove the blacklist statement manually? Or do we just give
the PC speaker a greater index value as I suggested above, so that
other devices take precedence?
I mean to blacklist it forever. It's almost a fun project and not for
serious usage. So, either disabling in the kernel config or addint it
to blacklist would make both users and us happy.
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org