[alsa-devel] No sound on Intel DQ965GF motherboard
Thank you, alsa developers, for the prompt resolution of my previous sound issue with the Thinkpad X61. Unfortunately, I've now turned up an apparently different problem on very similar hardware.
Sound doesn't work on my DQ965GF motherboard under Ubuntu 7.10. Here's what I've found out about it. I'm writing in hope that someone on the ALSA devel list can suggest diagnostics to pin down the problem exactly.
The device has PCI ID [8086:284b] (rev 02). It is an Intel 82801H.
This appears to be an Ubuntu-specific error. At http://www.linuxquestions.org/questions/linux-hardware-18/intel-dq965gf-mobo... I found a post implying that at least the rear jacks on the mobo are active under Fedora Core 6. I have therefore filed an Ubuntu bug at https://bugs.launchpad.net/ubuntu/+bug/162410 but seen no response.
This also appears to be a very hardware-configuration-specific error. I have an Intel HDA audio device on my X61 laptop with PCI ID [8086:284b] (rev 03), another 82801H, that works just fine under Ubuntu 7.10 (the alsa version is nominally 1.0.14 but some 1.10.15 fixes, including the right one, were backported). Note the 03 as opposed to 02 subrev.
aplay -l, which is supposed to list sound playback devices, returns no listing on the DQ965GF. As a check, on the X61 where it works it returns this:
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0
lsmod also returns suggestively different results. On the laptop, its output includes this line.
snd_hda_intel 337192 1
On the DQ965GF, here are the sound device lines:
snd_hda_intel 337192 0 snd_usb_audio 96640 1 snd_pcm_oss 50048 0 snd_mixer_oss 20096 1 snd_pcm_oss snd_pcm 94344 3 snd_hda_intel,snd_usb_audio,snd_pcm_oss snd_usb_lib 20352 1 snd_usb_audio snd_seq_dummy 5380 0 snd_seq_oss 36864 0 snd_seq_midi 11008 0 snd_seq_midi_event 9984 2 snd_seq_oss,snd_seq_midi snd_seq 62496 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 27272 2 snd_pcm,snd_seq snd_rawmidi 29824 2 snd_usb_lib,snd_seq_midi snd_seq_device 10260 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi snd_hwdep 12168 1 snd_usb_audio snd 69288 13 snd_hda_intel,snd_usb_audio,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_seq,snd_timer,snd_rawmidi,snd_seq_device,snd_hwdep soundcore 10272 1 snd snd_page_alloc 12560 2 snd_hda_intel,snd_pcm usbcore 161584 8 usbhid,snd_usb_audio,snd_usb_lib,xpad,gspca,ehci_hcd,uhci_hcd
Note that snd_hda_intel has no users and that snd_usb_audio has 1.
On the DQ965GF, the Sound Preferences tab on my Gnome toolbar thinks the sound device is "USB Device 0x46d:0x8ad (ALsa mixer)". I don't know what tool GNOME is running to determine this.
This arch-linux thread gave me some insight: http://bugs.archlinux.org/task/6617
It appears the snd_usb_audio driver is a red herring, or at least a separate bug. I checked, and my dmesg log does indeed say "hda-intel: no codecs found!" on boot, which suggests that snd_hda_intel is loading and then failing to initialize properly, accounting for the usage count of 0.
I tried reverting the kernel patch mentioned in the arch thread (e.g. recompiling the snd_hda_intel driver with #define AZX_MAX_CODECS 4) but this did *not* solve the problem.
Any suggestions would be appreciated. I need my music back!
At Fri, 16 Nov 2007 01:10:42 -0500 (EST), Eric S. Raymond wrote:
It appears the snd_usb_audio driver is a red herring, or at least a separate bug. I checked, and my dmesg log does indeed say "hda-intel: no codecs found!" on boot, which suggests that snd_hda_intel is loading and then failing to initialize properly, accounting for the usage count of 0.
If you're using 2.6.24-rc* kernel (or did 1.0.15 backports), make sure that you enabled all CONFIG_SND_HDA_CODEC_* configs. Some people tend to reduce options as much as possible although they are suggested as default=y.
Takashi
Takashi Iwai tiwai@suse.de:
If you're using 2.6.24-rc* kernel (or did 1.0.15 backports), make sure that you enabled all CONFIG_SND_HDA_CODEC_* configs. Some people tend to reduce options as much as possible although they are suggested as default=y.
I'm using 2.6.22, which is the level of the stock Ubuntu 7.10 kernel. It has only one config symbol matching SND_HDA: CONFIG_SND_HDA_INTEL. I rebuilt the snd_hda_module from those sources.
At Fri, 16 Nov 2007 10:21:17 -0500, Eric S. Raymond wrote:
Takashi Iwai tiwai@suse.de:
If you're using 2.6.24-rc* kernel (or did 1.0.15 backports), make sure that you enabled all CONFIG_SND_HDA_CODEC_* configs. Some people tend to reduce options as much as possible although they are suggested as default=y.
I'm using 2.6.22, which is the level of the stock Ubuntu 7.10 kernel. It has only one config symbol matching SND_HDA: CONFIG_SND_HDA_INTEL. I rebuilt the snd_hda_module from those sources.
OK, 2.6.22 should be fine. But how did you build at all? Did you copy alsa-driver 1.0.15 code to 2.6.22 kernel tree, or built properly from alsa-driver tree (configure, make)?
The former case won't work (unless you do very carefully).
Takashi
Takashi Iwai tiwai@suse.de:
OK, 2.6.22 should be fine. But how did you build at all? Did you copy alsa-driver 1.0.15 code to 2.6.22 kernel tree, or built properly from alsa-driver tree (configure, make)?
I did the latter, this morning.
Eric S. Raymond wrote:
Takashi Iwai tiwai@suse.de:
If you're using 2.6.24-rc* kernel (or did 1.0.15 backports), make sure that you enabled all CONFIG_SND_HDA_CODEC_* configs. Some people tend to reduce options as much as possible although they are suggested as default=y.
I'm using 2.6.22, which is the level of the stock Ubuntu 7.10 kernel. It has only one config symbol matching SND_HDA: CONFIG_SND_HDA_INTEL. I rebuilt the snd_hda_module from those sources.
I'm working on getting linux-backports-modules-2.6.22_2.6.22-14.11 uploaded today which will update your Ubuntu 7.10 ALSA drivers to 1.0.15. Look for it to appear in the repo sometime over the weekend (if all goes well).
Tim Gardner tim.gardner@canonical.com:
I'm working on getting linux-backports-modules-2.6.22_2.6.22-14.11 uploaded today which will update your Ubuntu 7.10 ALSA drivers to 1.0.15. Look for it to appear in the repo sometime over the weekend (if all goes well).
Thanks. I do have backports enabled; if this solves the problem I'll so inform the list.
Tim Gardner wrote:
Eric S. Raymond wrote:
Takashi Iwai tiwai@suse.de:
If you're using 2.6.24-rc* kernel (or did 1.0.15 backports), make sure that you enabled all CONFIG_SND_HDA_CODEC_* configs. Some people tend to reduce options as much as possible although they are suggested as default=y.
I'm using 2.6.22, which is the level of the stock Ubuntu 7.10 kernel. It has only one config symbol matching SND_HDA: CONFIG_SND_HDA_INTEL. I rebuilt the snd_hda_module from those sources.
I'm working on getting linux-backports-modules-2.6.22_2.6.22-14.11 uploaded today which will update your Ubuntu 7.10 ALSA drivers to 1.0.15. Look for it to appear in the repo sometime over the weekend (if all goes well).
The build didn't happen over the weekend as I promised. In the meantime one of our sales force guys has an X61. He said he was able to solve his issues from the info in http://ubuntuforums.org/showthread.php?t=587394
I hope I'm correct in remembering you have an X61.
rtg
Interesting that you would post a link to one of my responses on linuxquestions.org.
I still have my DP965LT, and I usually update my audio driver whenever there is a significant change to the tip for my specific audio codec. Couple of things to check. First, is the audio disabled in bios? Does audio work if you use the latest daily snapshot of alsa-driver from ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ ?
If either of these fixes the issue, then it is definitely an Ubuntu issue. This doesn't surprise me, as they have pre-production patches in their sound driver from Intel. These patches may be contributing to the issue (I haven't verified yet).
Also, if this doesn't fix the problem, can you send a link generated from running http://bulletproof.servebeer.com/alsa/scripts/alsa-info.sh It has a lot of detailed information about your audio configuration.
I looked at the driver code, and your specific system is listed (I should know - I added it 8/2006).
Tobin
On Fri, 2007-11-16 at 01:10 -0500, Eric S. Raymond wrote:
Thank you, alsa developers, for the prompt resolution of my previous sound issue with the Thinkpad X61. Unfortunately, I've now turned up an apparently different problem on very similar hardware.
Sound doesn't work on my DQ965GF motherboard under Ubuntu 7.10. Here's what I've found out about it. I'm writing in hope that someone on the ALSA devel list can suggest diagnostics to pin down the problem exactly.
The device has PCI ID [8086:284b] (rev 02). It is an Intel 82801H.
This appears to be an Ubuntu-specific error. At http://www.linuxquestions.org/questions/linux-hardware-18/intel-dq965gf-mobo... I found a post implying that at least the rear jacks on the mobo are active under Fedora Core 6. I have therefore filed an Ubuntu bug at https://bugs.launchpad.net/ubuntu/+bug/162410 but seen no response.
This also appears to be a very hardware-configuration-specific error. I have an Intel HDA audio device on my X61 laptop with PCI ID [8086:284b] (rev 03), another 82801H, that works just fine under Ubuntu 7.10 (the alsa version is nominally 1.0.14 but some 1.10.15 fixes, including the right one, were backported). Note the 03 as opposed to 02 subrev.
aplay -l, which is supposed to list sound playback devices, returns no listing on the DQ965GF. As a check, on the X61 where it works it returns this:
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0lsmod also returns suggestively different results. On the laptop, its output includes this line.
snd_hda_intel 337192 1On the DQ965GF, here are the sound device lines:
snd_hda_intel 337192 0 snd_usb_audio 96640 1 snd_pcm_oss 50048 0 snd_mixer_oss 20096 1 snd_pcm_oss snd_pcm 94344 3 snd_hda_intel,snd_usb_audio,snd_pcm_oss snd_usb_lib 20352 1 snd_usb_audio snd_seq_dummy 5380 0 snd_seq_oss 36864 0 snd_seq_midi 11008 0 snd_seq_midi_event 9984 2 snd_seq_oss,snd_seq_midi snd_seq 62496 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 27272 2 snd_pcm,snd_seq snd_rawmidi 29824 2 snd_usb_lib,snd_seq_midi snd_seq_device 10260 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi snd_hwdep 12168 1 snd_usb_audio snd 69288 13 snd_hda_intel,snd_usb_audio,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_seq,snd_timer,snd_rawmidi,snd_seq_device,snd_hwdep soundcore 10272 1 snd snd_page_alloc 12560 2 snd_hda_intel,snd_pcm usbcore 161584 8 usbhid,snd_usb_audio,snd_usb_lib,xpad,gspca,ehci_hcd,uhci_hcdNote that snd_hda_intel has no users and that snd_usb_audio has 1.
On the DQ965GF, the Sound Preferences tab on my Gnome toolbar thinks the sound device is "USB Device 0x46d:0x8ad (ALsa mixer)". I don't know what tool GNOME is running to determine this.
This arch-linux thread gave me some insight: http://bugs.archlinux.org/task/6617
It appears the snd_usb_audio driver is a red herring, or at least a separate bug. I checked, and my dmesg log does indeed say "hda-intel: no codecs found!" on boot, which suggests that snd_hda_intel is loading and then failing to initialize properly, accounting for the usage count of 0.
I tried reverting the kernel patch mentioned in the arch thread (e.g. recompiling the snd_hda_intel driver with #define AZX_MAX_CODECS 4) but this did *not* solve the problem.
Any suggestions would be appreciated. I need my music back!
Tobin Davis tdavis@dsl-only.net:
Interesting that you would post a link to one of my responses on linuxquestions.org.
Ah, you must be GrueMaster, then.
I still have my DP965LT, and I usually update my audio driver whenever there is a significant change to the tip for my specific audio codec. Couple of things to check. First, is the audio disabled in bios?
No. I checked, audio is enabled.
Doesaudio work if you use the latest daily snapshot of alsa-driver from ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ ?
No. Installing these changes the problem; the "no codecs" message goes away, but snd_hda_intel no longer appears in the output of lsmod. Grepping the dmesg output yields these messages:
[ 37.951029] snd_hda_intel: disagrees about version of symbol snd_ctl_add [ 37.951033] snd_hda_intel: Unknown symbol snd_ctl_add [ 37.951070] snd_hda_intel: disagrees about version of symbol snd_pcm_new [ 37.951073] snd_hda_intel: Unknown symbol snd_pcm_new [ 37.951110] snd_hda_intel: disagrees about version of symbol snd_pcm_limit_hw_rates [ 37.951113] snd_hda_intel: Unknown symbol snd_pcm_limit_hw_rates [ 37.951146] snd_hda_intel: disagrees about version of symbol snd_card_register [ 37.951148] snd_hda_intel: Unknown symbol snd_card_register [ 37.951187] snd_hda_intel: disagrees about version of symbol snd_card_free [ 37.951188] snd_hda_intel: Unknown symbol snd_card_free [ 37.951209] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_preallocate_pages_for_all [ 37.951211] snd_hda_intel: Unknown symbol snd_pcm_lib_preallocate_pages_for_all [ 37.951234] snd_hda_intel: disagrees about version of symbol snd_card_proc_new [ 37.951235] snd_hda_intel: Unknown symbol snd_card_proc_new [ 37.951315] snd_hda_intel: disagrees about version of symbol snd_ctl_find_id [ 37.951317] snd_hda_intel: Unknown symbol snd_ctl_find_id [ 37.951375] snd_hda_intel: disagrees about version of symbol snd_ctl_new1 [ 37.951376] snd_hda_intel: Unknown symbol snd_ctl_new1 [ 37.951424] snd_hda_intel: disagrees about version of symbol snd_component_add [ 37.951426] snd_hda_intel: Unknown symbol snd_component_add [ 37.951452] snd_hda_intel: disagrees about version of symbol snd_card_new [ 37.951454] snd_hda_intel: Unknown symbol snd_card_new [ 37.951500] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_malloc_pages [ 37.951502] snd_hda_intel: Unknown symbol snd_pcm_lib_malloc_pages [ 37.951530] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_ioctl [ 37.951532] snd_hda_intel: Unknown symbol snd_pcm_lib_ioctl [ 37.951555] snd_hda_intel: disagrees about version of symbol snd_pcm_lib_free_pages [ 37.951557] snd_hda_intel: Unknown symbol snd_pcm_lib_free_pages [ 37.951591] snd_hda_intel: Unknown symbol snd_ctl_elem_read [ 37.951622] snd_hda_intel: Unknown symbol snd_ctl_elem_write [ 37.951641] snd_hda_intel: disagrees about version of symbol snd_pcm_set_ops [ 37.951643] snd_hda_intel: Unknown symbol snd_pcm_set_ops [ 37.951669] snd_hda_intel: disagrees about version of symbol snd_pcm_hw_constraint_list [ 37.951671] snd_hda_intel: Unknown symbol snd_pcm_hw_constraint_list [ 37.951700] snd_hda_intel: disagrees about version of symbol snd_device_new [ 37.951702] snd_hda_intel: Unknown symbol snd_device_new [ 37.951735] snd_hda_intel: disagrees about version of symbol snd_pcm_suspend_all [ 37.951736] snd_hda_intel: Unknown symbol snd_pcm_suspend_all [ 37.951767] snd_hda_intel: disagrees about version of symbol snd_card_disconnect [ 37.951769] snd_hda_intel: Unknown symbol snd_card_disconnect [ 37.951789] snd_hda_intel: disagrees about version of symbol snd_pcm_hw_constraint_integer [ 37.951791] snd_hda_intel: Unknown symbol snd_pcm_hw_constraint_integer [ 37.951897] snd_hda_intel: disagrees about version of symbol snd_pcm_period_elapsed [ 37.951898] snd_hda_intel: Unknown symbol snd_pcm_period_elapsed [ 37.951917] snd_hda_intel: disagrees about version of symbol snd_pcm_hw_constraint_step [ 37.951919] snd_hda_intel: Unknown symbol snd_pcm_hw_constraint_step
This may just mean I fluffed the installation, but there is nothing in the install file to clue me in about how.
Also, if this doesn't fix the problem, can you send a link generated from running http://bulletproof.servebeer.com/alsa/scripts/alsa-info.sh It has a lot of detailed information about your audio configuration.
I looked at the driver code, and your specific system is listed (I should know - I added it 8/2006).
If it would help, I'd be willing to create a guest account on the machine for you and work with you in real-time to resolve the problem. You can't hear my speakers, of course, but I strongly suspect that if we could get the driver and its codecs to load properly the rest would just be a matter of making sure they're plugged in.
At Fri, 16 Nov 2007 11:16:19 -0500, Eric S. Raymond wrote:
Doesaudio work if you use the latest daily snapshot of alsa-driver from ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ ?
No. Installing these changes the problem; the "no codecs" message goes away, but snd_hda_intel no longer appears in the output of lsmod. Grepping the dmesg output yields these messages:
[ 37.951029] snd_hda_intel: disagrees about version of symbol snd_ctl_add [ 37.951033] snd_hda_intel: Unknown symbol snd_ctl_add
In most cases, the problem will be gone after unloading all snd* modules and ac97* modules once, then reload the again. alsasound init script sometimes doesn't do that correctly (depending on distro).
Takashi
Takashi Iwai tiwai@suse.de:
In most cases, the problem will be gone after unloading all snd* modules and ac97* modules once, then reload the again. alsasound init script sometimes doesn't do that correctly (depending on distro).
I'll try again when the Ubuntu backports packages get updated, thanks.
On 11/16/07, Eric S. Raymond esr@snark.thyrsus.com wrote:
Thank you, alsa developers, for the prompt resolution of my previous sound issue with the Thinkpad X61. Unfortunately, I've now turned up an apparently different problem on very similar hardware.
Sound doesn't work on my DQ965GF motherboard under Ubuntu 7.10. Here's what I've found out about it. I'm writing in hope that someone on the ALSA devel list can suggest diagnostics to pin down the problem exactly.
The device has PCI ID [8086:284b] (rev 02). It is an Intel 82801H.
According to intel site this board has a STAC9227 the same audio codec I have on my intel DG965RY
Does 2.6.23 work for you?
Accidentally I introduced a error in this driver thus very similar to yours issue was present on few systems. It is fixed in 2.6.24-rc1 So, what kernel fails?
Can you try 2.6.24-rc2
Best regards, Maxim Levitsky
PS: I don't have the DG965RY motherboard temporarely since it decided to break, thus I am waiting for replacement board, and can't use my new PC :-(
Maxim Levitsky maximlevitsky@gmail.com:
Can you try 2.6.24-rc2
That may be the next step, but since 2.6.22 is known to work with this audio chip on my X61 I'd rather not introduce another variable yet. Let's see if my diagnostic sequence with Tobin Davis gets us anywhere, first.
participants (6)
-
Eric S. Raymond -
Eric S. Raymond -
Maxim Levitsky -
Takashi Iwai -
Tim Gardner -
Tobin Davis