dontvisitmyintentions wrote on June 19, 2021 at 2:28 AM

Printing is easy. ACPI is hard. People who try Linux might be put off by shitty sleep or audio support in their new or niche hardware.

I put up with having to reboot to have audio because I got this machine cheap and it's really neat, and I'm too lazy to figure out if it can be fixed in software.

Other people won't put up with that. That's why they wouldn't stick with Linux: because it doesn't solve itself. Never mind that neither does Windows.

Most people never try.

Wahaha OP wrote on June 19, 2021 at 9:13 AM

If you run Linux and have audio trouble, chances are you run pulseaudio, whose troubles can be fixed by running "puleaudio -k", which restarts it. For me, for some reason pulseaudio decided to select the wrong devices upon each restart, so I wrote a script that selects the correct ones which runs at startup.

dontvisitmyintentions wrote on June 19, 2021 at 7:34 PM

It's at a lower level. Re-logging in also doesn't fix sound, though it does show missing batteries and sensors. The script that parses function key presses seems to get confused, and I think that's related to the machine's general ACPI spam. That might be fixable, if I can identify sequences to ignore instead of letting it build errors over time.

Thanks for the suggestion, though.