4 ms·

It’s much better than PC, there’s many more standards to chose from! /s > Getting the necessary kernels and software together isn't even all that difficult mos

It’s much better than PC, there’s many more standards to chose from! /s > Getting the necessary kernels and software together isn't even all that difficult most of the time, the problem is that you need someone to set up an appropriate distribution Guess what? On PC there’s a ton of people who have set up a distribution and they are all appropriate for all PCs. That makes it a whole lot easier to find such a person for your PC.

moondev 3y ago
This works the same way for arm64 "system ready" uefi hardware https://cdimage.ubuntu.com/daily-live/current/mantic-desktop-arm64.iso https://cdimage.ubuntu.com/daily-live/current/mantic-desktop...
- tinus_hn 3y ago
  Great! Perhaps one day all ARM64 systems will be ‘system ready’ uefi hardware, just like pretty much all x64 systems are PC systems. But today is not that day and that is why the author of the blog post is running into these problems.
jeroenhd 3y ago
The basic boot process is easier, but it has the same "this board doesn't boot sorry try these steps" problem. Try disabling the splash screen and watch all the ACPI bugs and workarounds jump onto the screen during early boot. It wasn't that long ago that you needed to download five different distros to brute force a working combination if you had a laptop with an Nvidia chip. Even today you need to pass special boot options on some AMD boards because motherboard vendors can't be bothered to release microcode updates. Linux 5.8+ refused to boot with 12th gen Intel graphics if you had a DisplayPort to HDMI adapter installed. I believe it took at least half a year before a fix was released (in a later version of the kernel, that wasn't backported). I remember this vividly because I showed off some dumb Gnome extension and he wanted it too, so he upgraded from a lower LTS to the then-current LTS and after a reboot he could no longer boot. My laptop didn't have sound unless I passed some kind of special parameter in the boot config somewhere. It sometimes freezes on boot while loading GDM. The display flickers and jumps around if you have a maximized application. The Nvidia driver+WM combo doesn't recognize external displays on Wayland. I've even run into one instance where the amd64 version of the distro shipped tons of applications requiring a certain instruction set, so installing the outdated (and now abandoned) x86 versions of the distro was the only solution. Linux Mostly Works on Most Systems. The only reason you can get anything done on it is that there are more people using it and fixing the mess that hardware vendors have left behind. I would say that most people will be able to run Linux smoothly on their hardware if they pick a user friendly distro, but random failure modes are everywhere.

moondev 3y ago

This works the same way for arm64 "system ready" uefi hardware https://cdimage.ubuntu.com/daily-live/current/mantic-desktop-arm64.iso https://cdimage.ubuntu.com/daily-live/current/mantic-desktop...

tinus_hn 3y ago
Great! Perhaps one day all ARM64 systems will be ‘system ready’ uefi hardware, just like pretty much all x64 systems are PC systems. But today is not that day and that is why the author of the blog post is running into these problems.

jeroenhd 3y ago

The basic boot process is easier, but it has the same "this board doesn't boot sorry try these steps" problem. Try disabling the splash screen and watch all the ACPI bugs and workarounds jump onto the screen during early boot. It wasn't that long ago that you needed to download five different distros to brute force a working combination if you had a laptop with an Nvidia chip. Even today you need to pass special boot options on some AMD boards because motherboard vendors can't be bothered to release microcode updates. Linux 5.8+ refused to boot with 12th gen Intel graphics if you had a DisplayPort to HDMI adapter installed. I believe it took at least half a year before a fix was released (in a later version of the kernel, that wasn't backported). I remember this vividly because I showed off some dumb Gnome extension and he wanted it too, so he upgraded from a lower LTS to the then-current LTS and after a reboot he could no longer boot. My laptop didn't have sound unless I passed some kind of special parameter in the boot config somewhere. It sometimes freezes on boot while loading GDM. The display flickers and jumps around if you have a maximized application. The Nvidia driver+WM combo doesn't recognize external displays on Wayland. I've even run into one instance where the amd64 version of the distro shipped tons of applications requiring a certain instruction set, so installing the outdated (and now abandoned) x86 versions of the distro was the only solution. Linux Mostly Works on Most Systems. The only reason you can get anything done on it is that there are more people using it and fixing the mess that hardware vendors have left behind. I would say that most people will be able to run Linux smoothly on their hardware if they pick a user friendly distro, but random failure modes are everywhere.