worc
May 8th, 2008, 01:40 PM
Hi people.
I know there are many threads in the forum talking about this. But I guess what I found today might be a little different.
Laptop: Toshiba Satellite P105 S9337
Sound Card: HDA INTEL (Conixant 20549)
Problem:
No sound after resume from a suspend. All info shows the sound card is working properly except I can hear nothing (I've tried all solutions I can find, check alsamixer, edit /etc/modprobe.d/alsa-base, edit /etc/default/acpi-support...). It is interesting that I can get sound back if I in step give it another hibernate( NOT suspend).
By saying everything shows the sound card is working properly, I mean I get no error when trying to play some sound, aplay/mplayer/audacious, the funny part is that I can even see the waveform of the music that audacious is playing.
This is an old problem for me since the first time I use Ubuntu (6.10). It remains in 6.10 all the way along to the current 8.04.
I believed it was an alsa issue.
Somehow, my earphone doesn't work in 8.04 (that's not true in 7.04 and 7.10), so I tried to downloaded and installed latest free OSS. Boom, earphone works perfect with OSS. Then, I tried a suspend. After resume, I lost my sound again.
What? OSS performs the same as ALSA on the part?
I tried to play some music in the shell with OSS's ossplay, it says something like "/dev/dsp: Input/output error". What? Does that mean the problem is actually not caused by the driver but the suspend action itself? Then I tried a couple of times to reproduce it and get the same result.
Here is my conclusion (but BASED ON GUESS, cause I'm just a user instead of a pro):
I tried years to fix the problem of losing sound after resume from suspend but all failed. There are so many solutions on the internet but none of them works for me. But, if the problem is not on the driver side, that all make sense to me.
What if something happend during suspend/resume and cause the sound card 'dead' but the system doesn't realize it?
I spend hours to check files in /etc/acpi but found nothing really suspicious.
That's really beyond my scope. If anyone is interested, please, you got someone to save.:)
I know there are many threads in the forum talking about this. But I guess what I found today might be a little different.
Laptop: Toshiba Satellite P105 S9337
Sound Card: HDA INTEL (Conixant 20549)
Problem:
No sound after resume from a suspend. All info shows the sound card is working properly except I can hear nothing (I've tried all solutions I can find, check alsamixer, edit /etc/modprobe.d/alsa-base, edit /etc/default/acpi-support...). It is interesting that I can get sound back if I in step give it another hibernate( NOT suspend).
By saying everything shows the sound card is working properly, I mean I get no error when trying to play some sound, aplay/mplayer/audacious, the funny part is that I can even see the waveform of the music that audacious is playing.
This is an old problem for me since the first time I use Ubuntu (6.10). It remains in 6.10 all the way along to the current 8.04.
I believed it was an alsa issue.
Somehow, my earphone doesn't work in 8.04 (that's not true in 7.04 and 7.10), so I tried to downloaded and installed latest free OSS. Boom, earphone works perfect with OSS. Then, I tried a suspend. After resume, I lost my sound again.
What? OSS performs the same as ALSA on the part?
I tried to play some music in the shell with OSS's ossplay, it says something like "/dev/dsp: Input/output error". What? Does that mean the problem is actually not caused by the driver but the suspend action itself? Then I tried a couple of times to reproduce it and get the same result.
Here is my conclusion (but BASED ON GUESS, cause I'm just a user instead of a pro):
I tried years to fix the problem of losing sound after resume from suspend but all failed. There are so many solutions on the internet but none of them works for me. But, if the problem is not on the driver side, that all make sense to me.
What if something happend during suspend/resume and cause the sound card 'dead' but the system doesn't realize it?
I spend hours to check files in /etc/acpi but found nothing really suspicious.
That's really beyond my scope. If anyone is interested, please, you got someone to save.:)