I've been an IT professional for 20 years now, but I've mainly dealt with Windows. I've worked with Linux servers through out the years, but never had Linux as a daily driver. And I decided it was time to change. I only had 2 requirements. One, I need to be able to use my Nvidia 3080 ti for local LLM and I need to be able to RDP with multiple screens to my work laptop running Windows 10.
My hope was to be able to get this all working and create some articles on how I did it to hopefully inspire/guide others. Unfortunately, I was not successful.
I started out with Ubuntu 22.04 and I could not get the live CD to boot. After some searching, I figured out I had to go in a turn off ACPI in boot loader. After that I was able to install Ubuntu side by side with Windows 11, but the boot loader errored out at the end of the install and Ubuntu would not boot.
Okay, back into Windows to download the boot loader fixer and boot to that. Alright, I'm finally able to get into Ubuntu, but I only have 1 of my 4 monitors working. Install the NVIDIA-SMI and reboot. All my monitors work now, but my network card is now broken.
Follow instructions on my phone to reinstall the linux-modules-extra package. Back into Windows to download that because, you know, no network connections. Reinstall the package, it doesn't work. Go into advanced recovery, try restoring packages, nothing is working. I can either get my monitors to work or my network card. Never both at the same time.
I give up and decide it's time to try out Fedora. The install process is much smoother. I boot up 3 of 4 monitors work. I find a great post on installing Nvidia drivers and CUDA. After doing that and rebooting, I have all 4 monitors and networking, woohoo!
Now, let's test RDP. Install FreeRDP run with /multimon, and the screen for each remote window is shifted 1/3 of the way to the left. Strange. Do a little looking online, find an Issue on GitHub about how it is based on the primary monitor. Long story short, I can't use multiple monitor RDP because I have different resolution monitors and they are stacked 2x2 instead of all in a row. Trust me I tried every combination I could think of.
Someone suggested using the nightly build because they have been working on this issue. Okay, I try that out and it fails to install because of a missing dependency. Apparently, there is a pull request from December to fix this on Fedora installs, but it hasn't been merged. So, I would need to compile that specific branch myself.
At this point, I'm just so sick of every little thing being a huge struggle, I reboot and go back into Windows. I still have Fedora on there, but who would have thought something that sounds as simple as wanting to RDP across 4 monitors would be so damn difficult.
I'm not saying any of this to bag on Linux. It's more of a discussion topic on, yes, I agree that there needs to be more adoption on Linux, but if someone with 20 years of IT experience gets this feed up with it, imagine how your average user would feel.
Of course if anyone has any recommendation on getting my RDP working, I'm all ears on that too.
I like Arch, but a first-time install of Arch for a beginner who doesn't have a lot of patience for reading documentation and troubleshooting is not good advice.
EndeavourOS would be good
There's also the easy archinstall script
He said he's an IT professional for 20 years. That's like the epitome of patience for reading documentations and troubleshooting
The bigger problem when running Arch is that there's a very high gap between "the bootloader makes the kernel run" and "functional desktop system". The installation guide will get you to the first one. For someone who's used to Windows, even as an IT pro, learning Arch is a firehose that's hard to drink from.
Once you've pacstrap'd and set up a user you reboot and start your new OS. Except you have no internet because you didn't know you had to install dhcpcd. Fine, install that--except your user isn't in sudoers, so you have to figure out how to get back to being root to edit the sudoers file. With visudo. Ten minutes later you've figured out how to find and edit the right line. Another ten to get out of vi. Then once that's sorted you're sitting at a terminal you don't know any commands for with no idea how to get to a graphical environment.
You look on your phone and find a recommendation for XFCE4 as a lightweight and simple DE. Great, install that. Try to launch it, and...a bunch of arcane errors. Another hour of troubleshooting and you learn that you missed xorg, which for some reason isn't a dependency of XFCE4. O...kay. You don't want to have to launch it every time you boot, so you go digging and find out you need a desktop manager. Takes some time, but you finally install one and enable the service in systemd, which you have to do manually for some reason.
Finally you get to a graphical environment, and...the fonts are all weird, and unicode symbols are just placeholders. Wait, fonts. You have to install fonts. More research, but you get there. Finally you launch a browser and are delighted to find something familiar. It all works the same. Great! Let's watch a video to make sure playback is working, and...no sound.
Okay, more research, and turns out you missed pulseaudio. Install that, start the daemon aaaand...no audio. Fine, how do you check the audio level? Ah, there's an XFCE4 plugin for pulseaudio. Find that, install it, put it on your panel, click it and...pavucontrol isn't installed. Whatever that is. Okay, install it and try again. Great! So, for some reason the default audio level when you install is 0. Turn that up and you finally hear sound! Hours after starting the process.
And every. little. thing. is like that. For weeks. Especially with Nvidia, and especially if you make the mistake of following a recent guide that shunts you into a Wayland environment. Every time you need to do something there are 20 options, five of which are well-documented but deprecated, the first three you try don't work for reasons you don't understand, then you finally find something that works well enough. Rinse, repeat, for every little thing.
And this is coming from a complete Arch stan. I love Arch. It's my only distro these days. I'm on Hyprland, my neovim is tricked out, everything is slick, responsive, just takes a couple keystrokes to accomplish anything I want to do, and I have everything set up exactly how I want it. It took a long time to get there, though, and I've been using Linux off and on for over 20 years, maining it for the last 10.
With arch based flavored desktop installers (arco endeavour manjaro ..) you get some GBs of stuff that is probably going to ask 1-2GB of upgrades, and then you end up dumping half the crap they came with.
On one you start from bottom up, the rest you start from top towards the ?bottom?.
You only learn when you start with the least needed to boot a system, have net access, and a pkg.mngr.
@Squiddles @hactar42 @Jean_Lurk_Picard @Zak
Some people learn that way, but most don't. It's usually better to start with a working environment and work on one thing at a time until you learn enough that you're ready to dig down another layer. Start with little mysteries and learn the structure of things and how to troubleshoot before jumping in the deep end. Having a system that's hopelessly broken and you don't know why or how to fix it is just likely to turn people away from Linux entirely. People don't win extra points for suffering needlessly.
There is an advantage in arch (and all pacman based distros) that the pkg mgr is friendly and vocal.
Say you want your system to run with vtwm you try and you get many dependencies installed, then try starting it. If it doesn't start it will tell you what is missing still.
Usually with X is either xorg-xinit or a display manager (avoid) and adding exec vtwm into your ~/.xinitrc gets you going.
@Squiddles @hactar42 @Jean_Lurk_Picard @Zak
Yeah, in Windows. Windows and Arch are two completely different beasts.
I get the sentiment (Arch has provided the least friction for me when I needed something niche/specific) but putting OP on Arch is still pushing them into the deep end IMO. If OP is open to trying Arch however, I'd throw out a recommendation for EndeavourOS which is just a pre-made Arch setup.
Or following scripts and copy-pasting the first result from Google.
The problem there is that what people come to learn about the Windows OS becomes ingrained into them as "how to use a computer".
Almost all of that goes out the fucking window when you jump to a non-Windows OS, but especially Arch.