Something doesn’t add up. My guess is you’re using a MacBook but don’t want to tell us for obvious reasons.
There’s literally no reason for “specific libraries and kernel modules” when installing Linux on any x86 PC. It makes no sense.
Hah. Nope. There’s a ton of custom features on hardware that need tweaking all over Windows laptops. There are entire forums dedicated to specific brands out there. None of this was much of a surprise, I had put off giving this a try because I had read about the hoops I’d have to jump through and been too lazy to try.
Huh. I’ve installed Linux on anything from an old 32bit netbook to a Fujitsu convertible that both had such a fucked up UEFI implementation they couldn’t even boot a standard Windows ISO without Ventoy in grub mode, as well as a cobbled-together Workstation with Nvidia graphics, and never ran into issues like this.
Something doesn’t add up. My guess is you’re using a MacBook but don’t want to tell us for obvious reasons.
There’s literally no reason for “specific libraries and kernel modules” when installing Linux on any x86 PC. It makes no sense.
If they said that they went “back” to Windows, why would you assume a MacBook?
Hah. Nope. There’s a ton of custom features on hardware that need tweaking all over Windows laptops. There are entire forums dedicated to specific brands out there. None of this was much of a surprise, I had put off giving this a try because I had read about the hoops I’d have to jump through and been too lazy to try.
Huh. I’ve installed Linux on anything from an old 32bit netbook to a Fujitsu convertible that both had such a fucked up UEFI implementation they couldn’t even boot a standard Windows ISO without Ventoy in grub mode, as well as a cobbled-together Workstation with Nvidia graphics, and never ran into issues like this.