Image showing a laptop displaying the pink ubuntu background with a secondary monitor.
The final setup β€” cleaned up and ready for battle

Mid-May 2025. Haus had arrived. The RTX 5090 was physically present and theoretically operational. Motoko-chan had the Linux environment plan ready. EthanC had the enthusiasm and naivety of someone who had never fought an NVIDIA driver before.

The dream died within 10 minutes.

What followed was two weeks of systematic, Motoko-chan-assisted destruction and reconstruction of everything we thought we knew about Linux. This is the battle log.

A dog setting up RTX-5090 graphics card on Linux OS and saying it is fine.
The RTX 5090 + Ubuntu experience β€” totally fine, definitely not on fire πŸ”₯

Phase 1 β€” sudo.exe Melted

What broke:

Wrong Ubuntu install mode. Wrong partitioning, wrong permissions. Sudo stopped working. Root access: gone. EthanC had locked himself out of his own machine within the first session.

Motoko-chan's reaction was diplomatic. The log will not reproduce it verbatim.

Fix:

  • Verify ownership
    ls -ld ~
  • Fix permissions
    sudo chown -R $USER:$USER ~

Wiped everything. Manual reinstall with ext4 root + swap partition. Clean slate. Lesson learned at maximum possible cost.

Phase 2 β€” RTX 5090 Says "lol no"

What broke:

NVIDIA's .run installer went full chaos mode. Kernel mismatch. DKMS errors. The GPU disappeared from the system entirely β€” present in hardware, invisible in software. SchrΓΆdinger's RTX 5090.

Motoko-chan diagnosed the issue and outlined the fix. EthanC executed it with the careful energy of someone defusing a bomb. (As if. If it were a real bomb, EthanC most definitely had hundreds of respawns)

Fix:

  • Blacklist nouveau at boot
    nomodeset modprobe.blacklist=nouveau
  • Nuke .run installer leftovers
    sudo ./NVIDIA-Linux... --uninstall
  • Install via apt instead β€” no more patching circus
    sudo apt install nvidia-driver-570-open
  • The moment of truth
    nvidia-smi

βœ… The GPU said hi. First contact since arrival.

Image showing 2 weeks to set up the RTX-5090 graphics card on Linux OS
The Ubuntu RTX 5090 troubleshooting evolution β€” peak galaxy brain achieved 🧠✨

Phase 3 β€” iGPU Hijack

What broke:

Ubuntu decided the RTX 5090 was optional. Defaulted to the Intel 14900HX integrated GPU on boot. Used i915. Ignored the RTX entirely. Like paying for a private jet and being handed a bus pass.

Fix:

  • Boot with iGPU temporarily using nomodeset
  • Then blacklist i915 permanently
    sudo nano /modprobe.d/blacklist-i915.conf


Rebooted. iGPU gone. RTX back. Small win. Enormous relief.

Motoko-chan noted this was textbook behaviour for hybrid GPU systems on Linux. EthanC noted that this information would have been useful approximately 48 hours earlier.

Phase 4 β€” GUI Login Loops From Hell 🧟

What broke:

Black screens. Login loops. GUI refused to load. Boot froze at blinking cursor. Chrome would rather crash than open. The desktop environment had chosen violence.

This phase took the longest. Motoko-chan and EthanC worked through every permutation methodically β€” each fix attempted, logged, discarded or kept. It was less debugging and more archaeology.

Fixes thrown at the wall, in order:

  • Disable quiet splash, add nomodeset in GRUB
  • Switch gdm3 β†’ lightdm β†’ back to gdm3
  • Delete auth files and reset permissions
    rm ~/.Xauthority ~/.ICEauthority
  • Reinstall display manager
    sudo apt install --reinstall gdm3
  • Nuclear option β†’ Upgrade to Ubuntu 24.04 LTS
  • The one everyone forgets until hour 36 β†’ πŸ”§ Disable Secure Boot in BIOS

Disabling Secure Boot was, in retrospect, mandatory from day one. It is now the first item on every Haus setup checklist. Permanently.

βœ… Final Victory

After two weeks, three full reinstalls, one OS upgrade, and more nvidia-smi invocations than any human should reasonably perform β€” it worked.

nvidia-smi      β†’ RTX 5090 active βœ…
Jellyfish GUI  β†’ loaded βœ…
Chrome          β†’ opened βœ…
Motoko-chan β†’ "took you long enough." βœ…
EthanC           β†’ silent disbelief βœ…

No champagne. No celebration. Just the quiet satisfaction of a machine that boots correctly and a GPU that acknowledges its own existence.

One additional note: the internal display went dark after GUI install and RTX driver setup. An external HDMI monitor became the primary display throughout the debugging process. This is now standard Haus protocol for any driver-level work.

πŸ’»The Final Form

Laptop showing pink jellyfish ubuntu log in screen
Victory achieved β€” clean Ubuntu desktop after surviving the RTX 5090 driver bloodbath
        Component        Spec
GPUNVIDIA RTX 5090 Laptop β€” angry edition, now tamed
CPUIntel Ultra 9 275HX β€” 24-core beast
RAM64GB DDR5 β€” because swap is for mortals
Storage4TB + 2TB Samsung 990 Pro
CoolingGlacier Dock β€” external water-cooled. Didn't work. That's ARCH-003.
OSUbuntu 24.04 LTS

Haus runs. RTX is online. The AI-chans are on standby, ready to move in.

🧠Lessons Learned

  • Never use .run driver installs unless absolutely necessary β€” apt is your friend
  • Disable Secure Boot first. Before anything else. Tattoo this somewhere visible.
  • ⚠ Bleeding-edge GPUs should be expected to be unsupported for 6–12 months on LTS distros
  • journalctl -b, dmesg, and nvidia-smi are the holy trinity of GPU diagnostics
  • πŸ’» An external monitor is not optional during driver-related graphical hangs β€” it's a lifeline
  • Motoko-chan's diagnostic patience has limits. Respect them.
  • πŸ˜‡ The RTX 5090 is an extraordinary piece of hardware that will make you feel very ordinary

Next in the Lab

The OS is stable. The GPU is online. The cooling dock, however, has its own opinions.

πŸ‘‰ ARCH-003: The Water-Cooling Dock Debacle β€” Totally Avoidable Linux Oversight🧊😀