FS#8807 - kernel26-2.6.23.9-1 snd-hda-intel ad1984 no sound
Attached to Project:
Arch Linux
Opened by Javeed Shaikh (syscrash) - Saturday, 01 December 2007, 03:28 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 March 2008, 06:52 GMT
Opened by Javeed Shaikh (syscrash) - Saturday, 01 December 2007, 03:28 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 March 2008, 06:52 GMT
|
Details
Sound does not work on kernel26-2.6.23.9-1 using the
following card:
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) (on a Lenovo Thinkpad R61i.) The relevant driver is snd-hda-intel. It seems as if the driver does not fully pick up the card. aplay would refuse to play; Deleting everything except soundcore.ko from /lib/modules/2.6.23-ARCH/kernel/sound/ and manually compiling and installing alsa-driver-1.0.15 (ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.15.tar.bz2) fixes the issue. With the arch kernel's driver, dmesg says hda_intel: probe_mask set to 0x1 for device 17aa:20ac PCI: Setting latency timer of device 0000:00:1b.0 to 64 With the manually compiled driver, dmesg says ALSA /home/syscrash/downloads/alsa-driver-1.0.15/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:576: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x009f000c Perhaps this is just a kernel issue and will be fixed magically when they integrate a newer version of alsa? Note, however, that the version that comes with the kernel claims to be 1.0.15 (at least according to /proc/asound/version.) |
This task depends upon
hda module is the worst in alsa and breaks things from time to time.
model= parameter is a nice thing to play with.
also check /etc/modprobe.conf on alsaconf entries and variables that might not fit anymore
I tried other models, also with no effect.
(The messages in dmesg were identical.)
I agree that the hda-intel module seems a
little weird... in fact sound did work at
some point in the past using an arch kernel.
"Deleting everything except soundcore.ko from /lib/modules/2.6.23-ARCH/kernel/sound/
and manually compiling and installing alsa-driver-1.0.15 (ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.15.tar.bz2)
fixes the issue." [then restarted computer to make sure]
I get nothing from dmesg about intel or snd or alsa. But my module is recognized:
$ lsmod | grep snd
snd_seq_dummy 4100 0
snd_seq_oss 34944 0
snd_seq_midi_event 7936 1 snd_seq_oss
snd_seq 56832 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 8212 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_hda_intel 372264 0
snd_hwdep 9224 1 snd_hda_intel
snd_pcm_oss 42528 0
snd_pcm 82696 2 snd_hda_intel,snd_pcm_oss
snd_timer 22920 2 snd_seq,snd_pcm
snd_page_alloc 9872 2 snd_hda_intel,snd_pcm
snd_mixer_oss 17024 1 snd_pcm_oss
snd 58728 10 snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 7968 1 snd
Any more suggestions?
echo up > /proc/acpi/ibm/volume
Turns out this was semi-hardware muted.