Ubuntu
linux package

  1. Bug #1834771
  2. Comment #72

Comment 72 for bug 1834771

Revision history for this message
Uriel Tunn (u2n) wrote (last edit ):

Hmm, I'm running bone stock LM 20.1 and the kernel is 5.4.0-80 (auto-updated a few days ago). In the last several months, the bug has been triggered a few times -- not often, only infrequently after resume from suspend. On reboot, everything works.

Hate to say I spent days working on a fix for this, and only managed to get a workaround going. So feeling your pain. But the workaround did function reliably. (Not sure why no joy with your setup.)

Choice of distro is very personal; a user should not be forced into one because hardware won't work with any other. ... Possibly consider a cheap video card?

EDIT
Near the bottom of my (lengthy) startup script I found '$HOME/bin/fixHDMIaudio &' so contrary to the above, the fix IS still in use.

EDIT2
To test whether the workaround is still actually fixing the problem (and if there is one), I commented it out and rebooted. Sure enough, no sound. Run manually, sound back.

EDIT 3
To check if any differences in 20.2, I did the upgrade. (It still uses k5.4.0-80.) Exact same results.

So the post 53 workaround IS still fixing the hardware-kernel-driver incompatibility bug, at least with my rig. Apologies for forgetting it was still in use; don't we all move on when an issue is resolved? (Still bugs the CRAP outa me this bug has been around for years -- probably just a few lines of code needed to totally resolve! But wait, I've moved on. Ha!)