Re:Technical reasons to choose FreeBSD over GNU/Linux (2020)
by trelane on Saturday August 06, 2022 @09:19PM
(#32373027)
> Personal experience with Ubuntu on a recent Thinkpad:
Well, that's your first problem. How does FreeBSD or OSX do on it? Maybe you should buy a Linux laptop to run Linux instead of slapping Linux on a Windows laptop and expecting it to work correctly.
Re:Technical reasons to choose FreeBSD over GNU/Linux (2020)
by depressedpanda on Sunday August 07, 2022 @01:14AM
(#32374080)
No, I'm pretty sure all his problems are due to Nvidia.
Try Intel or AMD; they are a lot more stable in my experience.
Re:Technical reasons to choose FreeBSD over GNU/Linux (2020)
by ooneeks on Sunday August 07, 2022 @06:46PM
(#32380671)
Don't Nvidia make open-source Linux drivers now?
I honestly have not had graphical driver issues since... Well since a good while before SteamOS and such. I don't doubt you guys at all, but I only have "older" laptops that might have GPU issues in terms of overall Linux compatibility.
Re:Technical reasons to choose FreeBSD over GNU/Linux (2020)
by umanwizard on Sunday August 07, 2022 @09:26PM
(#32381574)
> Don't Nvidia make open-source Linux drivers now?
Yes, but only since very recently — AFAIK, most distros are not using the open-source drivers yet, as they don’t yet have feature parity with the proprietary ones.
* When using Wayland, until VERY recently (latest nvidia drivers), the entire system would freeze when hooking up an external monitor. Okay, no problem I’ll use X.
* Hygrid graphics just completely doesn’t work, loads of glitches, glacially slow framerates on external monitors, etc. Okay, I turn off hybrid graphics in the BIOS, but that absolutely trashes battery life.
* X does not let you run different scale factors concurrently. You can’t set your laptop screen to 2x and your external monitor to 1x. Wayland does let you, but see above.
* I have two 4K monitors hooked up to my laptop. Whenever I resume from sleep, there’s a very good chance that only one or zero of the monitors is detected. They both power on, but only one (or sometimes none) of them actually has a signal. Cycling power on the monitor usually fixes the issue. My coworker has a Thinkpad from the same line but a generation earlier, and it had the exact same problem, so this has apparently been around a while and still isn’t fixed.