I just installed EndeavorOS on an HP Spectre360 that’s roughly 2 years old. I am honestly surprised at how easy it went. If you google it, you’ll get a lot of “lol good luck installing linux on that” type posts - so I was ready for a battle.
Turned off secure boot and tpm. Booted off a usb stick. Live environment, check. Start installer and wipe drive. Few minutes later I’m in. Ok let’s find out what’s not working…
WiFi check. Bluetooth check. Sound check (although a little quiet). Keyboard check. Screen resolution check. Hibernates correctly? Check. WTF I can’t believe this all works out the box. The touchscreen? Check. The stylus pen check. Flipping the screen over to a tablet check. Jesus H.
Ok, everything just works. Huh. Who’d have thunk?
Install programs, log into accounts, jeez this laptop is snappier than on windows. Make things pretty for my wife and install some fun games and stuff.
Finished. Ez. Why did I wait so long? Google was wrong - it was cake.
Yes, if you don’t have a computer that literally came out this year, don’t have 2 separate graphics cards and don’t need HDR, or specific Windows-only software, Linux generally just works.
And sometimes the Windows only software is more “Windows only” and works with Wine
Windows 3D Builder though is firmly in the Windows Only category though. Which is a bummer because in my experience it’s the best at repairing 3D models for 3D printing that have errors like holes, redundant geometry, inverted faces, etc.
However, some older programs may actually behave better in Wine than say on Windows 11.
Oh, it also supports ancient 16 bit programs which Windows doesn’t anymore.
Lychee Slicer (slicer used for resin printing) is usually pretty good but sometimes it’ll still fail
Which basically means I’d have 2 choices, go in there manually with Blender or fire up Windows 3D Builder and let it work it’s magic
I haven’t fully given up on trying to find a way to get it to work on Linux but I’ve had to take a break from trying purely due to frustration
The dual GPU problem has actually for the most part also been solved; Optimus rarely poses a problem these days
It looks like it works in KDE 6, albeit a bit janky. Might be worth seeing if it works now, and if not come back in a year or so. https://wiki.archlinux.org/title/HDR_monitor_support
You probably won’t be able to run an LTS kernel on a brand new PC that just hit the market. But using the most recent kernel for arch or a derivative like endevorOS should work after like a week maximum.
I did have an issue like this on Ubuntu and its what made me actually start distro hopping since it worked fine on fedora and Arch using the latest kernels.
I experienced this when installing my AMD Radeon RX 7600XT, it was released two weeks prior to me installing it, back then, and Linux Mint and games in it were clearly running off software rendering. Turns out LM uses a more tried and true LTS kernel by default, luckily ot easily allows you to switch or manage kernels through the GUI updater, so I got that fixed easily.
There’s plenty of laptops with 2 separate graphics cards (mine included) and I’d say it’s the ideal experience if you need an NVIDIA card. Everything related to your system is done in the integrated Intel/AMD GPU (which works perfectly) and games and GPU intensive work (like CUDA) gets done in the NVIDIA one.
And HDR has been working for me for over 6 months with Plasma 6. I wish people wouldn’t upvote this stuff that gives the wrong idea.
Pretty sure HDR is “working” in the sense that KDE went ahead and implemented unfinished specs, so that the very few apps that also went ahead with it can do HDR, but only on Wayland which breaks other things that are behind, and also often requires very recent versions and specific obscure parameters to be passed to enable HDR support?
Yeah, it’s a great step forwards and great for enthusiasts, but unless I’m very behind on the state of HDR myself, it’s still something I’d consider “coming soon” and not proclaim it’s just “working for me”. It certainly feels like a “year from now” kind of thing - something to anticipate, not try to force just yet.
“Generally” is the key word. I’m a linux user since slackware on diskettes. My daily driver is Mint, because lazy. I have 2 VMs with kali and kinoite.
A couple of days ago a kernel update borked my install. A problem with the Ryzen graphics driver.
For me it was trivial. Boot into the previous kernel, timeshift roll back, and back in business, but I can see how a newbie woul go into panic.
A satisfied “customer” will recommend you to a friend. A pissed off one will tell 10.
My issue is family control. I haven’t found a way to get Microsoft family type control yet on Linux, since my sibling uses my computer. The syncing time allowed across devices is the hard part.
If you follow general newbie advice and install Mint, the kernel is older than your laptop and may not support everything.
Fedora, EndeavorOS or Manjaro would be a better choice then.
You can always install a newer kernel, or move to something Fedora or Arch based. My son has ZorinOS on 6.8
Or a Mac ime. I tried to run mint OS on a 2016 intel MBPro and it was a disaster. I got it up and running but the Touch Bar didn’t work, the Wi-Fi didn’t work, all kinds of issues.
I got it up and running but the Touch Bar didn’t work, the Wi-Fi didn’t work, all kinds of issues.
That’s because Apple doesn’t release drivers for all those components.
Running anything but a Mac OS on a Mac is a nice pet project, but you can’t expect Linux to work.
It depends. I installed mint on a 2011 MBP a couple of years ago and it was a breeze. I installed arch on it recently and the only snag was having to install the proprietary Broadcom driver to get wireless. It runs great though — which is just as well because it would actually be more difficult to install OSX on the bloody thing, seeing as they no longer support it.
A 2016 MBP is still a bit recent, but, as a general rule of thumb, by the time a Mac stops getting software updates, Linux will be ready for it.
The 2016-2017 MBP are unusually bad. Devices on either side of that? You’re fine. But the 2016-2017 devices? No wifi (except in some extremely unusual cases) is the big problem. Even then, it amazes me how much does work, with zero configuration, with a simple graphical install. The problem with this vintage MBP isn’t that it’s hard to get running–it’s that it’s (almost) impossible, but the parts that aren’t impossible are as smooth as they can be.
Yes, that’s cold comfort. But I’m speaking from the POV of an owner of a 2017 MBP who desperately wanted to keep it going.
The coda to the story is that my wife used it for a while with her business but it fell victim to an absolutely bizarre heat issue where the heat sink vents hot air directly across the controller cable for the display, leading to inevitable failure. Again: not an issue on either side of this model year. It’s sad because it could’ve served for another 4-5 years, making the initial purchase price substantially more tolerable.
Surprisingly it was really easy to install fedora on my wife’s MacBook Pro from 2012.
The only thing I had to do for everything to work perfectly was to install the RPM fusion repository and accept that the @ is gonna be mapped to the wrong key.
It’s the easiest device I’ve had for installing Linux in quite a while…
