Back to Linux - Ep 07: Not again, Nvidia!
This article is a transcript of a video that you can watch by clicking the thumbnail below. Hence, certain statements may not make sense in this text form, and watching the video instead is recommended.
This video is a part of my series Back to Linux in which I covered my transition from my Apple MacBook Pro to a ThinkPad a few months back. Though this video isn't really about a transition, as I'm still looking for that "perfect" setup, I consider this video to be a part of the series.
Previously we've seen that I was about to enter the Void, so let's continue from there.
If you haven't watched the previous videos in the series yet, you might feel a little lost in this one. I would highly recommend watching at least a couple of previous videos to get in sync with the state of the machine we'll be talking about for the rest of this video.
Updates till now
As I've mentioned in my previous videos, I'm moving slowly with the migration from Debian to Void, taking one step at a time. I've moved my secondary computer, my Dell Precision desktop to Void and it's working great. What I've been worried about since the start is how my ThinkPad will behave with Void.
I had planned a systematic, step-by-step migration for the ThinkPad, exactly the way I did for Debian. In fact, I executed almost all the steps, learned a lot more things this time, one of those things being runit, which is awesome by the way.
Two unexpected issues
The two unexpected places where I spent time fixing things were the audio and the touchpad.
For the touchpad, I've already had a configuration that worked through xinput to configure libinput for the touchpad, but this time around, because Synaptics was also present with the meta-package for Xorg, it was taking precedence. After hours of trying and also seeking help from Reddit, I learned that I could either install
xorg-minimal (which doesn't come with Synaptics by default) or have both Synaptics and libinput installed along with
xorg and force X to use libinput. I learned that one can create a config file overriding all other configurations, which is exactly what I did and my touchpad now worked exactly as it did with Arch and Debian.
So that should've taken care of everything, right? Sadly, it didn't, and I got stuck with the same thing as I did for Arch. Xorg worked great with the open-source driver
nouveau, which is pretty unusable for my use-case, but as soon as I installed the closed-source proprietary driver, it kept crashing with no way to recover the session, even through the other TTYs.
Xorg configuration being as complicated as it is, I even tried to create a configuration file for my machine by referring to several examples online and none of them worked, not that I expected it to. The best result I could get is the same and familiar "no screens found" error, which is at least something you can recover from instead of being left with a stuck session needing a hard-reset using the hardware power key.
Wayland could have been an option
As a result of my desperation to get this thing to work, I even started looking at Wayland once again after years. I learned that there is plenty of help to find alternatives for Xorg-based graphical environments that you can run on Wayland.
sway being the closest alternative for my
i3wm, I spent some time with it and found it to be snappy as advertised and the response times were noticeably low, not to say that i3wm has ever been slow for me. In fact, the instant it started (and picked up i3wm configs automatically), it confused me to think that what I had on screen was i3wm, which couldn't have been true, but then I realized that I had read this about sway that it can also work with i3wm configs.
I liked the fact that I didn't need a
startx, and I could launch a graphical session just by typing
sway. But even with all this ease and luxury, I had the following major issues:
- Steam, which is the standard test I run while testing the graphical capabilities of a Linux setup, didn't launch at all.
- Scaling on my high-resolution 4K screen was awful. I know that I could fix it eventually, but it didn't work by default, proving that support for HiDPI isn't great for Wayland compositors either, the way it hasn't been great for Xorg.
- There were many things on the screen that couldn't be clicked. Some of them were the menus in the Thunar file manager.
- I also noticed a few glitches while using the touchscreen and dragging things around. I usually almost never use the touchscreen on my machine, and I had opted for it as it was the only option coming with a 4K HDR screen, but regardless, knowing that there would be issues here as well I lost my remaining hope with Wayland.
With this, I concluded that it wasn't the time for me to jump into Wayland yet, so I kept this thing aside for the time being.
I spent way more money on this machine than I had originally planned for, so I guess I'll have to be living with Nvidia and its issues for at least a decade.
And, if Xorg won't work with Nvidia and even Wayland isn't an option, it feels that I may not be able to use Void on my ThinkPad X1 Extreme for the very same reason I couldn't use Arch. I wish I could combine the "just works" feature from Debian with the "newness" that comes with Void.
Speaking of combining two Linux distros, the only thing that comes to my mind is Bedrock Linux as that is exactly what it offers. So next up, I'll evaluate Bedrock Linux and play with a few combinations of Linux distros, mostly with one of them being Debian (or Devuan) for those packages that need to be older including core graphical packages, and probably Void for everything else?
Stay tuned for updates, and I hope to get back with a positive result from my research.
That's all that I have for this video, and if you found it helpful, you know what to do. Just be a little kind in the comments. As always, a subscribe will be helpful too. Thanks for watching it till the end, may the maker watch over you, see you in the next video!