[jaunty regression] No sound with HDA intel

Bug #320798 reported by Stefan Krause
This bug report is a duplicate of:  Bug #316125: [Jaunty] HDA-Intel - no sound. Edit Remove
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Sound used to work with 8.04 and 8.10 (usually after unmuting a channel), but I can't get jaunty alpha 3 to play any sound.
The hardware is a hp hdx9480 laptop with a Intel HDA chipset. (tIntel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog])

[Also confirmed on Thinkpad T61p with Intel HDA. Used to work with 2.6.28-3 and 2.6.28-4, even when broken in 2.6.28-5 and 2.6.28-6, but a recent update have broke it there, too.]

I checked all channels with alsamixer and alsamixer -D hw:0 and I can't find any muted channel.

Other information:

stef@hape:~$ cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xec004000 irq 23

I tried to check whether sound works with aplay /usr/share/sounds/alsa/Noise.wav. It reports no errors and the volume bar in pavucontrol shows that music is playing.

 stef@hape:~$ ps ux | grep pulse
stef 5807 2.9 0.1 366408 7572 ? Ssl 12:14 0:30 /usr/bin/pulseaudio --start
stef 5808 0.0 0.0 65972 3040 ? S 12:14 0:00 /usr/lib/pulseaudio/pulse/gconf-helper
stef 7090 0.0 0.0 7488 904 pts/1 S+ 12:31 0:00 grep pulse

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-5-generic 2.6.28-5.15
ProcCmdLine: root=UUID=664a01ac-b4a2-473b-b9b1-20664b3cb8f3 ro quiet nosplash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-5.15-generic
SourcePackage: linux

Revision history for this message
Stefan Krause (stefan-krause) wrote :
Revision history for this message
Noel J. Bergman (noeljb) wrote :

Same here.

T61p 6457-7WU.

 # cat /proc/asound/cards
  0 [Intel ]: HDA-Intel - HDA Intel
                       HDA Intel at 0xfe220000 irq 17
 # aplay /usr/share/sounds/alsa/Noise.wav
 Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono

This is a new regression, since I was playing audio Jaunty previously.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Not sure, but it may have appeared after the fixes for Bug 316430.

Noel J. Bergman (noeljb)
description: updated
Revision history for this message
Noel J. Bergman (noeljb) wrote : Re: [jaunty regression] No sound with HDA intel with 2.6.28-5 and later (worked up through 2.6.28-4)

Something just changed, and broke audio back to 2.6.28-3. :-( So now I have no sound in Jaunty with any recent kernel, instead of just the most recent ones being broken.

Noel J. Bergman (noeljb)
description: updated
Revision history for this message
matt (bradbury-matthew) wrote :

Found a tempory fix. Restart PulseAudio by typing in terminal:

pulseaudio -k

This command will have to be typed in every time you log in if you want sound from applications.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

That doesn't do it for me. After running it, I still have no sound (and no pulseadio process running). If I try to run pulseaudo after killing it, then:

$ pulseaudio -k
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root privileges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.

$ ps auxwww | grep pulse
noel 4908 0.0 0.0 7484 904 pts/0 S+ 20:56 0:00 grep pulse

$ pulseaudio
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root privileges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
E: alsa-util.c: Error opening PCM device hw:0: Device or resource busy
E: module.c: Failed to load module "module-alsa-sink" (argument: "device_id=0 sink_name=alsa_output.pci_8086_284b_sound_card_0_alsa_playback_0 tsched=1"): initialization failed.

Adding myself to the pulse-rt group did not appear to make any difference. Still no audio under Jaunty anymore.

Revision history for this message
Stefan Krause (stefan-krause) wrote :

pulseaudio -k doesn't change anything for me (Neither does disabling all system sounds as some voices suggest). Even after yesterday's updates I still have no sound.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

For me, it turns out that of the myriad audio problems people have reported, Bug 315971 is what I had to address (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/315971/comments/15). Basically, the speakers were disabled and needed to be re-enabled.

Revision history for this message
Don Spaulding II (donspauldingii) wrote :

I've been bitten by this bug as well (Intel x3100 on Thinkpad T61), and the error message Noel pasted was what I saw when trying to run 'pulseaudio -k' too. I took the hint from the error and ran:

sudo adduser <my_username> pulse-rt

After logging out/back in, audio works fine. Does this sound like a usable solution or a hackish workaround?

Revision history for this message
Stefan Krause (stefan-krause) wrote :
Revision history for this message
Stefan Krause (stefan-krause) wrote :

I've attached the alsa-info output for my Fedora 10 copy. Sound works perfectly fine on that distro. And I decided to do a fresh install for Januty Alpha 4. Some channels were muted, but even after unmuting I get no sound.

I tried to diff the alsa-info output between F10 and Jaunty, but I can't make any sense of the differences.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

> Some channels were muted, but even after unmuting I get no sound.

With Jaunty, even though I have internal speakers working, I cannot get sound out of the headphone jack. It works fine with Hardy, Intrepid and Fedora 10.

Revision history for this message
Stefan Krause (stefan-krause) wrote :

Thanks to https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4262 (Click on "Guest login (view only) is also available" to actually view the issue) I have sound back. The solution was to set the model in /etc/modprobe.d/options:
options snd-hda-intel model=5stack

Now the question is: Close the bug or leave it open (because sound should work after a standard installation)?

Revision history for this message
Noel J. Bergman (noeljb) wrote :

> With Jaunty, even though I have internal speakers working, I cannot get sound out of the headphone jack.

Working now, so for me everything is fixed.

Revision history for this message
Steve Beattie (sbeattie) wrote :

Based on my read of the followup comments, marking as fixed. If that's incorrect and there are still people with sound issues with this chipset, please re-open (set status back to New) or file a new bug. Thanks for your report!

Changed in linux:
status: New → Fix Released
Revision history for this message
neo (tkolodziejski) wrote :

It still doesn't work for me and I hear only silent noise.

Matt's "temporary fix" works. But as I see it's rather ugly since it just kills pulseaudio.

What is more - as far as I remember in Hardy I was also using the testing version and the sound was broken as well. And I was only able to hear that noise.

Revision history for this message
neo (tkolodziejski) wrote :

Yeah, it's working now. I don't know why, but today my jaunty started with sound.

Revision history for this message
panton41 (panton41) wrote :

Still broken after trying everything here:

colinritter@Raoul-Duke:~$ cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xf4600000 irq 22

Revision history for this message
panton41 (panton41) wrote :

Let me also add:

colinritter@Raoul-Duke:~$ cat /proc/asound/card0/codec#* | grep Codec
Codec: LSI ID 1040
Codec: IDT 92HD71B8X

Revision history for this message
panton41 (panton41) wrote :

Turns out headphones work, but main speakers don't.

Revision history for this message
AshBelan (ant1mony) wrote :

I only have headphones, and they don't work. I have an Intel 82801JI HD Audio Controller, which worked perfectly in Intrepid. I've tried a few things, and nothing appears to work. Please patch this, Canonical.

Revision history for this message
Markus Kienast (elias1884) wrote :

Same problem here!! Regression.
HP Pavilion dv3060

ruth@elise:~$ cat /proc/asound/card0/codec#* | grep Codec
Codec: IDT 92HD71B7X
Codec: LSI ID 1040

ruth@elise:~$ cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xd9300000 irq 22

Revision history for this message
Markus Kienast (elias1884) wrote :

Also interesting is, that I really had PERFECT sound in intrepid without any modifications to the pulseaudio config. Now, when I use intrepid kernel on jaunty, so I can hear sound again, the sound is cracky suddenly. And it does not matter if I turn tsched on or off. Actually the sound even sucks, when I run pure alsa!

Revision history for this message
Markus Kienast (elias1884) wrote :

00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
 Subsystem: Hewlett-Packard Company Device 1505
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 22
 Region 0: Memory at d9300000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: HDA Intel
 Kernel modules: snd-hda-intel

Revision history for this message
Stefan Krause (stefan-krause) wrote :

As I'm the original reporter I think I should add some information to this bug and I think it's not a duplicate.

My first problem is that I need to choose model=5stack-no-fp instead of 5stack with newer kernel versions. After that I get some sound back, but my second problem is that I have to set the "Line jack mode" to "line out" after each reboot.
And it even seems that after some time after sound has stopped I have to set the line jack mode again (I'm not sure if I'm clear: aplay test.wav, stop it, wait for a minute, aplay test.wav => no sound until line jack mode is set).
(Maybe powersaving related?)

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.