this post was submitted on 11 Dec 2023
61 points (90.7% liked)
PC Gaming
8664 readers
438 users here now
For PC gaming news and discussion.
PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
I had a restart on shutdown quirk with a dell machine, the fix was adding a kernel quirk number in grub line. You might want to try it. Solved it competely for me. add xhci_hcd.quirks=262144 to grub line or try xhci_hcd.quirks=8192 or you may need both so you add the numbers together for 270336.
Thanks for the suggestion! I tried all three but to no avail. It's not the worst behavior, I just resort to a less graceful shutdown holding the power button down at the grub menu. Suspend works fine now that I've disabled bluetooth wakeup, at least, so I just plug in for a while each day to keep things going.
Bummer. As for sound there, if it is a separate amplifier that runs the audio there was a package that let you manually reassign hardware speaker pins to the corresponding outputs, but it is trial and error unless you find someone's notes on which pins worked for them. it is HDAjackRetasker might separate package or be part of alsa-tools-gui. when you run hdajackretask you get a dialog box, try the various overrides, or if that doesn't work then turn on show unconnected pins and advanced override, then it is trying various pin overrides to components and seeing what works. There ia some limited documentation in the gui, and probably more online.
Yep, I messed with hdajackretasker for several hours a few months ago. There was no combination of pins configurations that fixed it that I could find.
It is the amplifier causing the sound problems, but from my research on this and similar issues with other Lenovo laptops like the Legion, it seems to be the way that Lenovo's bios identifies the hardware and its pins to the OS. It's likely possible to write a patch to fix it, but that's over my head and I got the sense from others who have tried that there isn't enough information to write the patch without more details from Lenovo, who have been entirely unresponsive to support requests.
They're fantastic speakers in Windows, so it's a shame, but I can work this way. In another year or two I'll upgrade to a laptop with hardware that I know plays nice with Linux.
Yeah, unfortunate. I have same issue with an HP zbook and the Bang& Olufson sound. Regular LR is fine but the boost is not. When it is upgrade time I'll be choosey.