No sound on Intel DQ965GF motherboard

Bug #162410 reported by Eric S. Raymond
2
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

No sound from Intel DQ965GF motherboard. The motherboard uses an 8201H ICH8 audio chip identical to the one actually working in the Lenovo Thinkpad X61 sitting next to it; both are running Gutsy. both load the sound_hda_intel module which is correct for the chip.

The difference is that on the DQ965GF motherboard Gutsy loads a second sound module, snd_usb_audio, and uses that as the default.

aplay -l on the Thinkpad lists "card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]". On the DQ965GF it lists no playback devices.

Revision history for this message
Eric S. Raymond (esr-thyrsus) wrote :
Revision history for this message
Eric S. Raymond (esr-thyrsus) wrote :

The device has PCI ID [8086:284b] (rev 02).

This appears to be an Ubuntu-specific error. At
http://www.linuxquestions.org/questions/linux-hardware-18/intel-dq965gf-mobo-front-sound-jacks-not-working-510302/
I found a post implying that at least the rear jacks on the mobo are
active under Fedora Core 6.

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) that works just fine. 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 laptop 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.

Revision history for this message
Luke Faraone (lfaraone) wrote :

ESR,

Can you try this again in Ubuntu 8.04?

Revision history for this message
Daniel T Chen (crimsun) wrote :

Eric, to further diagnose this symptom, I need additional information, namely output from `grep snd-usb-audio /etc/modprobe.d*/* /etc/modules'.

Also, please note that you can migrate which PulseAudio stream is routed to which audio device using the `pavucontrol' program.

Changed in pulseaudio:
status: New → Incomplete
Revision history for this message
Daniel T Chen (crimsun) wrote :

To triagers: do *not* mark this bug as Invalid if Launchpad has marked it for expiration.

Revision history for this message
Eric S. Raymond (esr-thyrsus) wrote :

Doesn't reproduce on 9.04. I think you can mark this Fixed.

Luke Faraone (lfaraone)
Changed in pulseaudio (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.