Seriously, you guys need to stop trying to troubleshoot Linux’s shortcomings at people. I know. Everybody knows. If you don’t, that’s the first thing any tutorial will tell you. I’m not looking for technical help, just sharing an anecdote.
If you’re curious, no, I couldn’t do Pop because I needed some specific libraries and kernel modules to support this particular device’s power management and I/O quirks and those were only officially supported in a handful of distros, so I picked one of the ones with better documentation, and even that wasn’t meant for my specific hardware.
Not that it matters, because it’s a laptop with a iGPU and a dGPU, and the Intel iGPU was just fine out of the box, so getting the Nvidia dGPU to work well was way down my priority list for this exercise, since the device was meant mostly for web browsing and media consumption. Instead, I had issues with sleep mode, since that was related to those specific modifications, and I coudn’t figure out a way to make it wake from boot without locking up, which is a pretty big dealbreaker for a device on a battery. Plus the embedded audio controls had some issues, the touchpad was flaky and eventually trying to go through the process of getting that dGPU running exposed other compatibility troubles.
I was ready to roll back to Windows once I noticed the touchpad acceleration was messy out of the gate, honestly, that’s my bar for troubleshooting tolerance. So no, I didn’t fail to do a cursory Google search in 2020 and find out that Nvidia support is messy. I knew that my slightly nonstandard device was going to be a bit of a challenge, but was hoping to get lucky. Didn’t get lucky and went back to what works on it. It’s not a call for help, it’s just a thing that happened last time I tried to switch a device to Linux.
Believe what you want. I actually would like to move some (more) of my devices over. I’m just not so married to any one OS to try super hard. I just use whatever works.
It’s kinda nuts to me that not everybody is on the same page with that.
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.
Because I know that nvidia is not really good on linux, you can try using pop os because they have pre-installed nvidia drivers
Seriously, you guys need to stop trying to troubleshoot Linux’s shortcomings at people. I know. Everybody knows. If you don’t, that’s the first thing any tutorial will tell you. I’m not looking for technical help, just sharing an anecdote.
If you’re curious, no, I couldn’t do Pop because I needed some specific libraries and kernel modules to support this particular device’s power management and I/O quirks and those were only officially supported in a handful of distros, so I picked one of the ones with better documentation, and even that wasn’t meant for my specific hardware.
Not that it matters, because it’s a laptop with a iGPU and a dGPU, and the Intel iGPU was just fine out of the box, so getting the Nvidia dGPU to work well was way down my priority list for this exercise, since the device was meant mostly for web browsing and media consumption. Instead, I had issues with sleep mode, since that was related to those specific modifications, and I coudn’t figure out a way to make it wake from boot without locking up, which is a pretty big dealbreaker for a device on a battery. Plus the embedded audio controls had some issues, the touchpad was flaky and eventually trying to go through the process of getting that dGPU running exposed other compatibility troubles.
I was ready to roll back to Windows once I noticed the touchpad acceleration was messy out of the gate, honestly, that’s my bar for troubleshooting tolerance. So no, I didn’t fail to do a cursory Google search in 2020 and find out that Nvidia support is messy. I knew that my slightly nonstandard device was going to be a bit of a challenge, but was hoping to get lucky. Didn’t get lucky and went back to what works on it. It’s not a call for help, it’s just a thing that happened last time I tried to switch a device to Linux.
obvious troll is obvious.
Believe what you want. I actually would like to move some (more) of my devices over. I’m just not so married to any one OS to try super hard. I just use whatever works.
It’s kinda nuts to me that not everybody is on the same page with that.
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.
To each their own, but I can tell you I found people flagging all the issues I encountered online.
What is this mysterious device that requires specific libraries and kernel modules? So I can state the fuck away from the device and the brand