This year I'm finally putting into action something that I've been wanting to do for some time: fortifying my home's network, improving privacy for my father and me, and laying the foundation for a smart home. (You guys took the time to help me out with that here, which, btw, thanks again!)

The network and privacy fortification is well underway and working. I set up Pi-hole with Unbound on one of my Raspberry Pis that also acts as a Tailscale exit node, got a new router that can connect my devices to ProtonVPN, have my Synology server working as storage, and... you know what, let's save this for another post. I'm still figuring some things out and want to let the dust settle first.

Anyway, back to gaming and PC'ing.

I'm no stranger to Linux; I've been using it on and off for over a decade on older PCs. But I've never committed to it on my main rig. As I said in another post, "It's the little things that make me not jump to Linux". While "these little things" didn't completely go away, I guess rolling up my sleeves to reconfigure my network, becoming more privacy-conscious, and reading about the ongoing issues with Windows 11 tipped the scales.

I debated between EndeavourOS and Fedora KDE. Fedora won.

EOS is a solid choice and I'd recommend it to anyone who wants to try out an Arch-based distro. But Fedora is undeniably more popular, which means if there's a Linux app, it's almost guaranteed the devs will have a Fedora version with dedicated documentation and installation commands. In other words, the potential for more convenience won out.

And convenient it was, mostly thanks to this website: https://nattdf.streamlit.app/. It helped a ton. It installed codecs, SSH, enabled Flathub and RPM Fusion, etc. It even provides a script to install Nvidia drivers.

But drivers weren't my real worry. My real worry was something else entirely.

You see, I lied to you guys by omission. I actually tried to install Fedora a few months ago, but I had severe issues with my TV. My PC is connected to both a monitor and a TV. The monitor worked without problems, but the TV was a different story. The image quality was terrible. You know those photos taken with the very first camera phones? That's how the colors looked. I remember trying everything: switching to X11, installing different driver versions, messing around with Nvidia settings, display settings, color profiles, even the TV's internal settings. Nothing worked. So I gave up and went back to Windows.

But today, while trying to fix an issue with my TV, I noticed two things:

1. I found out that my TV's HDMI ports are not all equal. Port 4 is HDMI 2.1, while all the others are 2.0.
2. My PC was connected to Port 3.

This was the problem. It's what caused my Windows to randomly lose sound, and it's what made the image quality terrible on Fedora, and it's what caused issues I mentioned in my old post. I don't know how or why Windows could "deal with it" and output 4K 120Hz without apparent image quality loss, but somehow it did.

Regardless, after moving the cable to Port 4, installing Fedora, and getting the drivers running... it works just fine and dandy. Great image quality, 4K, and 120Hz. My PC still works flawlessly as a gaming machine.

The moral of the story? Don't be like me. Before blaming Wayland, Nvidia, drivers, or Linux... check the back of the TV.

This also brings a much-needed sense of standardization to my setup. Now that everything is under the same Linux umbrella, I can manage it all via SSH with total consistency. I’m already eyeing my Raspberry Pi’s Telegram bot as a way to remotely wake the PC for heavy tasks and shut it down afterward. The potential of this setup has me feeling pretty euphoric.

Now that the biggest hurdle is cleared, Steam is running perfectly and Proton is handling my game library like a champ. I'm finally daily-driving Linux on my main rig, and this time, I think it's for good.

I'm info dumping some links about open-source robotics. The rabbit hole runs deep and this barely scratches the surface.

Disclaimer: I haven't tried any of these yet. Based on a cursory search and following links from the great Open-source robotics Wikipedia page.

Robotics simulation on Godot

• https://github.com/flynneva/godot_ros - Proof-of-concept integrating ROS2 (Robot Operating System) with Godot, for a 3D robot simulation environment. (Updated 8 months ago)

• https://github.com/nordstream3/Godot-4-ROS2-integration - A fork(?) of the above. The readme is clearer with visual examples of what it's meant for. (Updated 12 months ago)

• https://github.com/plaans/gobot-sim - A top-down 2D factory simulation of packages being processed by machines. (Updated 3 months ago)

• https://lab.nexedi.com/nexedi/godot-modbus-demo - Exposing a modbus interface to control simulated industrial components. (Updated 5 years ago.) Comes with a blog post which might be more recent (a year ago?).

• https://arxiv.org/abs/2412.18408 - "Exploring Flexible Scenario Generation in Godot Simulator" about generating simulated physical scenes for testing computer-controlled cars. Write-up only with no code. (Submitted 9 months ago)

Robotic car simulation on Unreal Engine and Unity

• https://github.com/carla-simulator/carla - "CARLA is an open-source simulator for autonomous driving research." They mostly target Unreal Engine. Regularly updated and popular with 13k stars on GitHub.

• https://github.com/microsoft/AirSim - Microsoft and IAMAI collaborated (plus DARPA funding?) to create an open source simulation platform for both flying drones and autonomous cars. Targets Unreal Engine and experimentally Unity also. Soon being sunset and replaced with a new project confusingly named "Project AirSim."

• https://github.com/iamaisim/ProjectAirSim - The successor to AirSim. The GitHub shows it's only at version 0.1.1 though.

Robot Operating System (ROS2)

• https://github.com/ros2/ros2

• https://docs.ros.org/en/kilted/Tutorials.html - Tutorials beginning with TurtleSim, a top-down 2D turtle scene where you control turtles. Looks like ROS2 uses familiar network messaging patterns like Publish-Subscribe.

• https://vimeo.com/osrfoundation/videos/sort:date - Presentation videos. Looks like the Open Robotics foundation just completed a developers' conference in Japan two days ago. The presentations from ROSCon JP are Japanese-language-only. Next one is coming very soon this October in Singapore.

How to get started?

That's a lot of links. I'd first figure out what I want to do. Humanoid robots seem popular lately—like the Berkeley 3d printed robot—so it'd be interesting to start there, although it doesn't map cleanly onto the projects I linked. So maybe if I imagined a robot with a human torso and arms, but with wheels and car-like locomotion. Then I could use a combination of the car simulators and probably ROS2 to deal with the upper body components? Or maybe there is another solution for the torso and arms that is a more direct fit than ROS2? Maybe iRobot/Roomba has a better solution for the car-like locomotion at this small scale?

Anyone used these before and have a story to share? Anyone curious to try one out and report back? I plan to, but no idea on my schedule.

This isn’t really meant to be a hate post or “linux sucks” kind of thing, in fact I like Linux (EndeavourOS being my distro of choice). This post is more about the little things that nobody really talks about when comparing OS’s, but then you face them and they can be a dealbreaker or a pain in the neck.

This weekend I decided to try running CachyOS in my gaming desktop. For quick context, my desktop is dedicated to gaming, everything else I do on my laptop. The desktop is plugged to a 1080p 60hz monitor and a 4k 120hz TV (hz relevant for later), uses sunshine for streaming, and also Virtual Desktop for my meta quest.

So, I grab the USB and plug it into the PC. Turn it on and here comes the first issue: the background image appears and nothing else.

Well, my first suspicion due to a similar issue I had with ubuntu a decade ago, must be the Nvidia GPU causing issues. Without investigating further, I restarted the PC and used the legacy mode. The resolution was extremely low in my monitor, but it was manageable. Installed the thing and restarted.

Once the PC is back on, the login screen appears. I input the pass, enter and…. Exact same issue. Background image, no UI whatsoever.

I spent an embarrassing amount of time here, investigating the error. Checking the drivers, etc.

But long story short: the actual problem was that my monitor was the second screen, the TV was the primary. The desktop was outputting to both screens. The UI was on the TV.

I curse myself for not remembering that this may have been it, but in my defense:
1- the terminal commands that appear when turning on the OS appeared in my monitor
2- the legacy mode worked on my monitor
3- on windows, the OS is smart enough to figure out which screen is turned on, so I was used to it automatically outputting to the correct screen

Well, once I fixed that, here came the second (small) issue:
Scaling is broken.

Windows used to have this problem but nowadays, when you change screen Windows does a good job scaling things, despite some issues with some apps. At the very least, you won’t get blurry windows.

On KDE… Yeah. Blurry all around. I don’t have a habit of swapping screens mid session, so I could live with it.

Then came the third issue:
KDE is limited by the lower highest possible framerate in both screens. Meaning, on my TV, I was stuck with the 60hz because of my monitor

From what I found out, this is not exclusive to KDE and seems to be a problem with Nvidia. Regardless, for me it was a dealbreaker. In my case, Windows can use the respective framerate of each screen, while Linux can’t.

As I said, this is where I threw the towel and went back to windows. Which is really a pity because I really don’t like where Windows 11 is going, but it’s something I can live with as long it doesn’t get in the way between me and gaming.

Meanwhile Linux, because of these little things, introduced more issues than rewards for my use case, thus why I can’t jump to it on my desktop.