61
Windows 12 is likely to debut in the second half of 2024 with AI-focused features (www.gizmochina.com)
submitted 2 years ago by to c/pcgaming@lemmy.ca
78 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 years ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago* (last edited 2 years ago) (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •