Subject: Issues with sound on physical machines

From: Michael Libredove <[email-masked]>
Date: Sat, 10 Feb 2024 18:11:41 +0000

Dear List,

How can I fix the annoying problem of the sound being automatically
muted on my fairly recent ThinkPad L390? Under a virtual machine this
problem doesn't exist. I am stumped. Please help me in any way you
can.

-- Michael

---

From: Steffen Nurpmeso <[email-masked]>
Date: Sat, 10 Feb 2024 20:26:03 +0100

Michael Libredove wrote in
 <FIfx0sbdK0g8VcapT39mJIXSx2NTjN1W__cYYzV5sxz2EEGhlfpgXZO-tg4Rni5yZsCftfp\
 jaxFflOkkcho42TIETV5RnNQZHraccWK-380=@proton.me>:
 |Dear List,
 |
 |How can I fix the annoying problem of the sound being automatically
 |muted on my fairly recent ThinkPad L390? Under a virtual machine this
 |problem doesn't exist. I am stumped. Please help me in any way you
 |can.

You mean after resume?

I have such problem sometimes with v6.1* since some years.
Not that alone, it is also about brigthness settings, in fact one
or two years or so ago i opened a bug report that things like
 echo bla > /sys/class/backlight/$VDEV/brightness
have no effect until some time after resume.
Ditto sound volume is reported as "0" for some time.

It seems to me they have race conditions in the kernel, knew that
before my bug report, and try to do something about it.
Ie, i once saw an interesting commit message which was created
months before my bug report stating something like this.
No healing, though.  Brightness that is.

My script around LID close now sleeps a bit before it
restores/adjusts brigthness and volume, but even a second sleep
does not always get around the problem.

Hope that helps,

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)