i810 problem with sound after coumputer sleeping or using headphones

Bug #126511 reported by Emil Österlund
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Ubuntu Audio Team

Bug Description

After i plug in headphones in my HP Compaq nc6000 i get not sound anymore from my internal speakers after unplugging again.
Also after the computer has been sleeping i get no sound anymore from the internal speakers.

I have tried both
sudo /etc/init.d/alsta-utils restart
and
sudo invoke-rc.d alsa-utils restart 0

without any results.

i also tried closing all sound apps and then did
rmmod i810 and modprobe i810. nothing.

larsemil@aragorn:~$ lspci | grep audio
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)

also: i did not have this problem under edgy but from the beginning of feisty.

Revision history for this message
Emil Österlund (larsemil) wrote :

oh! after rebooting the sound works fine again...

Revision history for this message
Emil Österlund (larsemil) wrote :

haha that was a bad comment.
after rebooting the sound works fine until i plug something in or make the computer sleep that is. :)

Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

 Hi Emil,

You might want to add some more debugging information. Please look at https://help.ubuntu.com/community/DebuggingSoundProblems and attach those files as separate files.

Thanks, /N

Revision history for this message
Emil Österlund (larsemil) wrote :

Ok here we go. See attached files.

also i get this:
larsemil@aragorn:~$ ls .asoundrc*
ls: .asoundrc*: Filen eller katalogen finns inte

(cant find the file)

Revision history for this message
Emil Österlund (larsemil) wrote :
Revision history for this message
Emil Österlund (larsemil) wrote :
Revision history for this message
Emil Österlund (larsemil) wrote :
Revision history for this message
Emil Österlund (larsemil) wrote :
Revision history for this message
Emil Österlund (larsemil) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

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
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
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.