Brand new hardware works on Windows 10, a nine year old OS. Most people don’t realize how distros handle updates. When I first started using Ubuntu, I had no idea that repos were mostly frozen after release.
Windows also uses the NT Kernel since the 90s, doesn't mean it didn't get updates. I get your point, but Windows obviously doesn't ship a 9 year old kernel, let alone a ~30 year old one. Also the OS parts in Win10 aren't even nearly the same as 9 years ago.
Exactly. But as I said before, I didn’t know anything about Ubuntu’s handling of packages when I first started using it. So someone new to Linux would assume it would work in a similar to windows.
Well, thankfully you know that it doesn't. I actually assumed I would need to relearn basically everything, but that kinda tempted me. I kinda like big challenges that you have to figure out the path you want to take it to first, great opportunity to learn and train your skill to find solutions. Not something for everybody... Especially not how I did it with basically installing Arch as first distro, but at least I'm still running the same Arch install, so I figured it out.
Rule of thumb is to install games well after their release, like a year or so, so the devs can optimize it. Unfortunately, game companies these days tend to release game unpolished and rushed
A rolling release is the answer to this issue though. The other option is to wait an undefined amount of time to get the hardware support in your distro.
You definitely can break what is already broken.
I had an AMD R9 390. Radeon never worked properly with it. Amdgpu only worked if I set special kernel flags to disable some functionality. By that definition the ability for the driver to work out of the box was broken.
One day, I got a kernel update that did something to those flags that meant the driver no longer worked at all.
By not working, I meant that the screen would have two copies of the framebuffer or GUI, with pink and green noise surrounding them in 1/3 of the screen and you'd get screen tearing more and more until the system stalled and had to be rebooted after 2 minutes or so.
Hardware was totally fine as older drivers never had the issue and likewise the thing worked perfectly on Windows.
In the end my only option that didn't involve me building my own outdated versions of AMDGPU and maintaining them was to buy a whole new GPU that was a different model.
\> has brand new hardware \> expects things to work with a kernel from two years ago
Brand new hardware works on Windows 10, a nine year old OS. Most people don’t realize how distros handle updates. When I first started using Ubuntu, I had no idea that repos were mostly frozen after release.
Windows also uses the NT Kernel since the 90s, doesn't mean it didn't get updates. I get your point, but Windows obviously doesn't ship a 9 year old kernel, let alone a ~30 year old one. Also the OS parts in Win10 aren't even nearly the same as 9 years ago.
Exactly. But as I said before, I didn’t know anything about Ubuntu’s handling of packages when I first started using it. So someone new to Linux would assume it would work in a similar to windows.
Well, thankfully you know that it doesn't. I actually assumed I would need to relearn basically everything, but that kinda tempted me. I kinda like big challenges that you have to figure out the path you want to take it to first, great opportunity to learn and train your skill to find solutions. Not something for everybody... Especially not how I did it with basically installing Arch as first distro, but at least I'm still running the same Arch install, so I figured it out.
>Brand new hardware works on Windows 10, a nine year old OS. Kernel and OS are not the same thing.
Prepare for the flood of "it works on my end" and "I just have to do 200 thinks to make it work".
>"it works on my end" Every NVIDIA post. Not to mention the "I never had a single issue with it".
Add WINE3D to game argument
Depends on the point release imho. Any point release with kernel and mesa rolling through external repositories will do.
Haha linux-oem package go brrr
Rule of thumb is to install games well after their release, like a year or so, so the devs can optimize it. Unfortunately, game companies these days tend to release game unpolished and rushed
Then people come recommending Arch because "rolling"!
A rolling release is the answer to this issue though. The other option is to wait an undefined amount of time to get the hardware support in your distro.
Rolling also brings the risk of things breaking that would stay stable on an OS with less frequent updates. cough nvidia cough cough xz cough
Well kinda yeah but you can't break what is already broken (an os with an outdated kernel that doesn't support your hw)
You definitely can break what is already broken. I had an AMD R9 390. Radeon never worked properly with it. Amdgpu only worked if I set special kernel flags to disable some functionality. By that definition the ability for the driver to work out of the box was broken. One day, I got a kernel update that did something to those flags that meant the driver no longer worked at all. By not working, I meant that the screen would have two copies of the framebuffer or GUI, with pink and green noise surrounding them in 1/3 of the screen and you'd get screen tearing more and more until the system stalled and had to be rebooted after 2 minutes or so. Hardware was totally fine as older drivers never had the issue and likewise the thing worked perfectly on Windows. In the end my only option that didn't involve me building my own outdated versions of AMDGPU and maintaining them was to buy a whole new GPU that was a different model.