Let’s be honest: I don’t love Windows. I don’t like the bloatware, the telemetry, or the way it feels like it’s fighting me for control. As a Network and Server Engineer, I live in terminals and SSH sessions. Naturally, I decided it was time to move my physical machine to the environment I manage: Linux.
I didn’t just use a Virtual Machine. I grabbed a USB stick, backed up my configs, and went for a physical installation on my laptop. I went head-to-head with Linux Mint and Fedora on bare metal. Here is the funny, weird, and brutal reality of a Network Engineer in the “wild.”
1. The “NVIDIA One-Click” Win
On physical hardware, Linux Mint was a dream. Since I’m not here to play games, I just needed my dual-monitor setup and my UI to be snappy.
- The NVIDIA Success: My NVIDIA GPU worked perfectly. Mint’s Driver Manager gave me a “one-click” suggestion for the proprietary driver. One click, and it was settled. Voom! High-resolution terminal windows everywhere.
2. Fedora: The “Upstream” Rush
Then came Fedora. It’s fast, it’s sleek, and it makes you feel like you’re working on a NASA terminal.
- The Addiction: I found myself running
sudo dnfupdate every few hours just for that hit of new kernel dopamine. - The Reality: For a Server Engineer, Fedora is amazing because it’s so close to RHEL, but on a laptop, it can be a “learning experience” when a new update changes how your hardware behaves.
3. The Headache: The Keyboard Backlight
Here is the part they don’t tell you in the tutorials. My gaming-grade laptop has a specific Keyboard Backlight controller. On Windows, it’s a simple app. On Linux? It was a nightmare. I spent more time digging through GitHub repos and trying to find the right kernel modules to just turn the lights on than I did setting up my web server. On Mint its working but on Fedora i didnt know why.
4. The Secure Boot Trap
If you’re running an NVIDIA card, Secure Boot is your worst enemy. Linux on a modern laptop takes it to a new level. If you have Secure Boot enabled in your BIOS, you can’t just “install” a driver; you have to prove it’s trusted.The Linux Mint Win: I have to give credit where it’s due—Linux Mint makes Secure Boot easy. During the installation, it asks you to set a temporary password. When you reboot, you just enroll the key (MOK), enter that password, and you’re done. It’s a “one-and-done” process that felt almost as smooth as Windows.
The Fedora/Manual Struggle: In contrast, other distros often leave you in the cold. You find yourself manually generating RSA keys and using mokutil in the terminal just to get your NVIDIA GPU to wake up.
The Conflict: The Linux kernel is locked down. When you install the proprietary NVIDIA drivers, the kernel sees them as “untrusted” code.
The Fix: You either have to disable Secure Boot in the BIOS (which feels like a step backward for security) or go through the “ritual” of creating a MOK (Machine Owner Key) to sign the drivers yourself.
The Symptom: You install the driver, reboot, and… nothing. You’re back to a laggy screen because the kernel refused to load the driver.
The Headache: When you install the proprietary NVIDIA drivers, Linux tries to load a kernel module that isn’t “signed.” If Secure Boot is on, your OS will simply refuse to load the driver, leaving you with a black screen or low resolution.
The Final Boss: The “Working Environment”
This is where the dream hit the wall. As a Network Engineer, my “office” is a mix of customer environments and secure tunnels.
- The VPN Gauntlet: My day-to-day requires FortiClient IPSec and GlobalProtect. On Windows, these are stable, “set-it-and-forget-it” tools.
- The Linux Struggle: On Linux, getting these specific VPNs to behave with physical hardware—while maintaining split-tunneling and DNS stability—became a second job. I spent more time troubleshooting my own connectivity than I did troubleshooting my customers’ servers.
- The Productivity Wall: I quickly realized that Microsoft Excel is a non-negotiable. While LibreOffice is great for basic sheets, my work involves Excel Macros (VBA) for reporting and audits. On Linux, Macros are essentially broken. There is no workaround; if you need VBA, you need native Windows.
The Plot Twist: Moving Back to Windows
I’ll be honest: I’ve moved back to Windows. I don’t love it, but in my line of work, the OS is a tool. When I’m in a high-pressure “Network Down” situation, I can’t be fighting with a VPN client or a keyboard backlight. I need my tools to work 100% of the time.
Final Thoughts
I don’t play games, and I still don’t love Windows, but I’ve learned that for a Network Engineer, the “best” OS is the one that stays out of your way during an outage. Linux is my passion, but Windows is currently my most reliable multi-tool.
Few links i refer for guide during my testing. Yeah, i waste my time for my fun because everything i already backup in cloud before change of OS is being run.
Backlight Keyboard : https://novacustom.com/clevo-keyboard-backlight-control-for-linux/
Nvidia installation guide : https://github.com/Comprehensive-Wall28/Nvidia-Fedora-Guide