No sound with ALSA after dist-update

Bug #70944 reported by tutuca
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi. I have this hardware listed here http://hwdb.ubuntu.com/?xml=46cd1265887cc11cda3b8c3820970c3e

Specifically the problem is with my sound card: an integrated Nforce2, after the update to edgy all the system sound stopped working. If i test the sound with the alsa driver it gives me this output
[code]audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: No se pudo abrir el recurso para escritura.[/code]

"Can't open resource for writing".

With OSS it works but very noisy, but still no system sound, (no alerts or greeting, etc).

Please let me know what can I do to workaround it or if I missed some info.
Thanks in advance.

Matías.
PD: Let me know if you don't understand, because English is not my first language and may be I didn't make myself clear. Thanks again

Revision history for this message
tutuca (tutuca) wrote :

Workaround to solve it:
On a terminal type: asoundconf reset-default-card

Still I don't know what caused it.

Revision history for this message
towsonu2003 (towsonu2003) wrote :

Thanks for your bug report. how was the system upgraded apt-get/synaptic/adept/update-manager -c)? Could you please include the logs from /var/log/dist-upgrade/

Revision history for this message
tutuca (tutuca) wrote :

I've upgraded trough gksudo "update-manager -c", I haven't got other problem than this. Here are my logs. Thanks for the feedback

Changed in update-manager:
status: Needs Info → Unconfirmed
Revision history for this message
Adam Niedling (krychek) wrote :

What version of Alsa caused the problem? Is it still a problem with Alsa 1.0.16?

Changed in linux-source-2.6.17:
status: New → Incomplete
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Changed in linux-source-2.6.17:
status: Incomplete → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

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
Markus Korn (thekorn) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,
Markus

Changed in linux:
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.