zlacker

>>tonyst+(OP)
Yeah, no. Maybe with old laptops, but newer laptops still have their fair share of issues. When I bought my thinkpad A485 kernels wouldn't boot without additional parameters, the graphics would freeze at times and cause a hardlock, sleep and hibernation have been fixed and broken again intermittently over several kernel versions, the wifi card's AP mode started causing segfaults in kernel 5.2 due to the driver's rewrite but has since been fixed, the fnlock key LED didn't update properly, which I spent a while debugging and submitted a kernel patch for, and while over the years the fingerprint scanner has been implemented, it's a pain to install and support for fingerprint scanning in linux is still in a very sorry state. Oh and bluetooth still can't connect more than one device at a time, so I had to buy a dongle to connect two joycon controllers.

Granted, I've always had these kinds of issues with new laptops, especially when it came to proprietary nvidia or AMD graphics (before AMDGPU) and I agree it's improved a lot, but I still need to tell people that there's caveats with some (especially newer) laptops.

>>mid-ki+H5
It's always a gamble with new laptops.

I've had multiple Thinkpad T-generations from T410 to the latest. Sometimes it does works flawlessly out of the factory at purchase.

This time, it did not. The 12th gen Intel CPUs have a heterogeneous design with traditional "P-cores" and low-power "E-cores". I'm suspecting the reason I see terrible performance is that the CPU scheduler does not handle this efficiently and assigns the wrong task to the E-cores.

Also the Intel WiFi does not even get detected. Have not dug deeper into that yet.

Anything > ~6(Intel) ~12(AMD/Realtek) months old tend to work smoothly out of the box, IME.