What happened to the platform below?

What makes it different in regard to your ADHD?

Don’t worry, all you need is a free ISA slot!

I’ll give it a shot!

It’s on my to-do list, but I haven’t gotten around to it yet.

UPDATE:

I was able to recover my system by re-installing the NVIDIA drivers through, in my case, sudo apt install nvidia-driver-550 since the kernel log indicated a version mismatch, presumably due to the Discover updates. Something’s still janky with the drivers as I experience massive lag and a ghosting cursor, but I’ll figure that out.

I’d really appreciate tips on how to prevent this in the future.

I dug a little deeper and using journalctl --since yesterday I could retrieve a proper log. There are a couple of red and yellow entries, some of the latest ones being:

Feb 16 12:31:28 radium (udev-worker)[471]: event10: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
[…]
Feb 16 12:31:28 radium kernel: nvidia: loading out-of-tree module taints kernel.
Feb 16 12:31:28 radium kernel: nvidia: module license 'NVIDIA' taints kernel.
Feb 16 12:31:28 radium kernel: Disabling lock debugging due to kernel taint
Feb 16 12:31:28 radium kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Feb 16 12:31:28 radium kernel: nvidia: module license taints kernel.
[…]
Feb 16 12:31:37 radium kernel: NVRM: API mismatch: the client has the version 550.144.03, but
NVRM: this kernel module has the version 565.77. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.
Feb 16 12:31:38 radium sddm[1280]: Failed to read display number from pipe
Feb 16 12:31:38 radium sddm[1280]: Display server stopping...
Feb 16 12:31:38 radium sddm[1280]: Attempt 3 starting the Display server on vt 2 failed
Feb 16 12:31:38 radium sddm[1280]: Could not start Display server on vt 2

The NVIDIA API warning appears several times throughout the log actually, which also implies I was wrong about driver version 560 being installed.

Okay, first time I do this. I followed this article, made sure the paths are right, but journalctl -e shows -- No entries --. Any idea where I went wrong? ls -l / and ls -l /home tell me I chrooted into the right directory.

Edit: I ran these commands
kubuntu@kubuntu:~$ sudo mount -t proc proc /mnt/rescue/proc
kubuntu@kubuntu:~$ sudo mount -t sysfs sys /mnt/rescue/sys
kubuntu@kubuntu:~$ sudo mount -o bind /dev /mnt/rescue/dev
kubuntu@kubuntu:~$ sudo mount -t devpts pts /mnt/rescue/dev/pts
kubuntu@kubuntu:~$ sudo chroot /mnt/rescue
root@kubuntu:/# journalctl -e

Yes, I am able to boot Kubuntu 24.04.1 from a USB drive.

I remember setting the memory buttons up, but I don’t actually use them. The KD3005D is probably fine, too. Personally, I’d still prefer fine-adjusting voltage and current via the incremental encoder and pushbutton of the KA3005D. The price difference around here is ~20%.

I recommend the KORAD KA3005D. It’s a reasonably priced, relatively small size unit with great controls.

Edit: Am using it in my home lab as well as my current and previous work environment (among other power supplies).

Thanks for the read, that sent me down an interesting rabbit hole

Yup, is says powered by Avast.

It was certainly the Huawei System UI. How do I tell which engine they’re using?

Can you? I wasn’t aware of that

That’s exactly what made me finally pull the trigger. I would never have guessed how easy the transition would be.

Love the slippers

Dumb me thought the dogger was the one saying “huh?”

Unacceptable! The people demand beans!

That smile. You rarely see that on photos from this time.