No sound - Ubuntu 10.4 x86 - ATI SBx00 Azalia (Intel HDA) (rev 40)

[Drew]

Fresh install on Compaq Presario CQ62-209WM, alongside a fully working Win7 install.

All appears well, install apparently went smoothly. Noticed no sound, verified using a few apps. Volume is maxed on master and pcm. Following is output of "aplay -l":
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: HDA Generic [HDA Generic]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Following is output of "lspci -v" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/601347/+attachment/2996160/+files/lspci%20-v

+ Comprehensive sound problem solutions guide at Ubuntu support forums reports that when running "alsamixer", a green box will be displayed underneath the selected channel slider if the channel is unmuted. Unless this refers to the portion of the slider which is green (~ lower 50%), I do not have this. Also, pressing "M" while in alsamixer does not appear to change mute state.

[Drew (kornesque-gmx)]

UPDATE: Upon purchasing this laptop, I immediately wiped the HD and installed a fresh version of Win7, which worked fine. I then proceeded to install Ubuntu 10.4, and haven't booted back to Win7 since. After posting this bug report, I decided to investigate the audio hardware further using SiSoft Sandra on the Win7 install. It was reported as an ATI IXP SB600 chipset (not found on the ALSA soundcard matrix). Upon booting back into Ubuntu to report this finding, the startup audio came blaring thru the speakers.

I have bounced many times since first T/Sing audio, included a few powerdowns, and have not had this occur. In the absence of any other apparent information, I have to presume that [ridiculous] something about booting into Win7 fixed this issue.[/ridiculous] "aplay -l" reports the same driver in use.

The matter is now bittersweet - audio works, solution is unknown. I will be more than happy to do more digging in an attempt to discover more about the matter if the developers wish.

[Drew (kornesque-gmx)]

After some more use of the machine, it appears that the sound will randomly fail after machine enters sleep state (lid close). This is not consistent, however. Once the sound fails, reboots will not result in restoration of sound. Booting into Win7 install, then back to Ubuntu fixes the issue, albeit temporarily until next random fail. I will try a full power-off next time it fails to see if the sound hardware is retaining it's messed up state somehow. Any thoughts/hints/ideas on this one folks? I'm fine with the temp fix for now, just like seeing a good wacky problem come to resolution, or at least find an explanation

[Drew (kornesque-gmx)]

Afterthought: powerdown does not neccesarily resolve issue as noted in second post - thanks to myself for jogging my own memory. Mind is reeling now. I'll confirm.

[penalvch (penalvch)]

Cut from the Bug Description.

[penalvch (penalvch)]

Drew, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]