no sound since upgrade to gutsy with pci id 10b9:5461

Bug #139892 reported by feanor
12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Ubuntu Audio Team

Bug Description

After an upgrade to gutsy, sound works at first but fails after an additional update.
I have added output as requested in "debugging sound problems" as a text file.
Thanks a lot for taking care of this :-)

greetings,

Manuel Gaus

Tags: cft-2.6.27
Revision history for this message
feanor (manuel-gaus) wrote :
Revision history for this message
feanor (manuel-gaus) wrote :

I have resolved this bug for me by downgrading to feisty. Sound definitively works in feisty.

Revision history for this message
Cob @FPGLaurent (c-o-b) wrote :

Same probleme. Dont know how fix it.
Will try to find / re-install the correct driver.

Revision history for this message
Cob @FPGLaurent (c-o-b) wrote :

Alsa propose only 5451 (http://www-old.alsa-project.org/alsa-doc/index.php?vendor=vendor-ALi#matrix) ... doesn't work.
Bug fixed by "Method E: Patch to add support for Realtek ALC268 Codec to Alsa 1.0.14" (https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller)

Revision history for this message
JV (ziri01) wrote :

I have also had the same problem. I have two soundcards. In feisty, the sound worked, in gutsy not.

 aplay returned following:
ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'defaults.pcm.dmix.device'
ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM default

So I decided to delete my configuration files:
rm .asoundrc .asoundrc.asoundconf

The sound immediatelly started working! But I would prefer if the files were deleted by the upgrade script rather than struggling myself to find the reason.

Just to give you more information, here is the diff between my correctly working gutsy (left) and the original feisty configuration file. In the older alsa version, the definitions like "defaults.pcm.device" were probably not yet mandatory:
15,21c15,17
< defaults.pcm.dmix.max_periods 0
< defaults.pcm.dmix.rate 48000
< defaults.pcm.dmix.format S16_LE
< defaults.pcm.dmix.card defaults.pcm.card
< defaults.pcm.dmix.device defaults.pcm.device
< defaults.pcm.dsnoop.card defaults.pcm.card
< defaults.pcm.dsnoop.device defaults.pcm.device
---
> defaults.pcm.dmix_max_periods 0
> defaults.pcm.dmix_rate 48000
> defaults.pcm.dmix_format S16
54,56d49
< defaults.namehint.showall off
< defaults.namehint.basic on
< defaults.namehint.extended off

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

It unfortunately appears that this bug is not yet resolved. Does this issue still exist in the Hardy Heron 8.04 LTS release? If so, the Intrepid Ibex 8.10 Alpha2 is also scheduled for release today. It will appear at the following when available: http://www.ubuntu.com/testing/intrepid/alpha2 . It contains the actively developed 2.6.26 Ubuntu kernel. It would be great if you could test this upcoming release via a LiveCD and verify if the issue still exists. If so, please include the appropriate debugging information as outlined at https://wiki.ubuntu.com/DebuggingSoundProblems . Thanks in advance.

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 139892

Changed in linux-source-2.6.22 (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
Eric Miao (eric.y.miao) wrote :

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.