No sound after wake up, sound card disappeared from pavucontrol #1

Open
opened 1 month ago by taha · 1 comments
taha commented 1 month ago
Owner

After the second or third hibernation/wakeup cycle (not the first time, weirdly enough) there was no sound after wakeup.

Looking at pavucontrol indicated that the sound card which the speakers are connected to had disappeared completely (only the GFX HDMI sound card was listed).

It was enough to issue

pulseaudio --kill

to immediately get the sound card back in pavucontrol and the sound working as normal again (note, had to be run as user, not root).

Let's wait and see if this issue recurs on every wakeup.

After the second or third hibernation/wakeup cycle (not the first time, weirdly enough) there was no sound after wakeup. Looking at `pavucontrol` indicated that the sound card which the speakers are connected to had disappeared completely (only the GFX HDMI sound card was listed). It was enough to issue ``` pulseaudio --kill ``` to immediately get the sound card back in `pavucontrol` and the sound working as normal again (note, had to be run as user, not root). Let's wait and see if this issue recurs on every wakeup. + https://www.linuxquestions.org/questions/linux-hardware-18/ubuntu-18-04-dummy-output-and-sound-disappeared-4175659386/ + https://askubuntu.com/questions/970744/hdmi-sound-disappears-after-suspend-on-ubuntu-16-04
Poster
Owner

Only turning on the speakers after the Linux desktop is up and running seems to work around this problem.

Hibernation seems to be sensitive to the state of connected IO devices at the moment of wake-up.

For example, I have noticed that waking the computer before powering the monitors causes the computer to wake-up without rendering anything on the monitors (wake-up appears to have occurred, but the monitors behave as if the computer is not even connected to them). Had to reboot to get back to working state (the power-down sequence kicked the monitors back to life, though, so we got to watch Linux shut down...).

Only turning on the speakers *after* the Linux desktop is up and running seems to work around this problem. Hibernation seems to be sensitive to the state of connected IO devices at the moment of wake-up. For example, I have noticed that waking the computer *before* powering the monitors causes the computer to wake-up without rendering anything on the monitors (wake-up appears to have occurred, but the monitors behave as if the computer is not even connected to them). Had to reboot to get back to working state (the power-down sequence kicked the monitors back to life, though, so we got to watch Linux shut down...).
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.