I remember when you had to use this newfangled “kernel module” business if you had two Ethernet cards using the same driver, because a non-module driver would only detect one …
I think the main trouble makers for consumers are the odd network or bluetooth controllers, especially in laptops, which often come with some exotic bullshit.
I have a lot of trouble with Bluetooth on laptops so I tend to run 2.4GHz wireless peripherals instead of Bluetooth. That’s my only complaint these days.
Some builds can get really tetchy about laptop hardware, but that’s almost always older hardware.
Though I will say it took entirely too long for most builds to have a “change what closing the lid” does menu option rather than making you modify a .conf file.
And don’t get me started on resolution switching when hot swapping display inputs.
Wha? Even a bleeping potato can run Linux nowadays, with zero issues at day 1.
t. Got a Orange pi zero 3, and the lil’ bastard is rocking solid – even with (near zero) support.
Imagine not having all your drivers baked in into your kernel
Imagine not knowing about kernel modules 🤣
I remember when you had to use this newfangled “kernel module” business if you had two Ethernet cards using the same driver, because a non-module driver would only detect one …
I think the main trouble makers for consumers are the odd network or bluetooth controllers, especially in laptops, which often come with some exotic bullshit.
I have a lot of trouble with Bluetooth on laptops so I tend to run 2.4GHz wireless peripherals instead of Bluetooth. That’s my only complaint these days.
Imagine being in the orange forum and thinking everybody’s using Mac…
Some builds can get really tetchy about laptop hardware, but that’s almost always older hardware.
Though I will say it took entirely too long for most builds to have a “change what closing the lid” does menu option rather than making you modify a .conf file.
And don’t get me started on resolution switching when hot swapping display inputs.