mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

15K
active users

#restart

1 post1 participant0 posts today

🤣 at Microsoft today...

Replacing the Blue Screen of Death with a new Black Screen of Death, which now no longer contains *any* information about the problem that caused the system to crash and need to restart.

For the average user, it's now impossible to have even a hint as to what the problem is. Great job, everybody!

For power users, geez, I hope something made it into the event logs and onto disk before the system died. No? Oh well, you didn't really need to know, just reset and wonder how long you've got until it happens again.

EDIT / UPDATE: I've now seen a second article about this change. The first didn't include an image, and described the removal of all information related to the specific error. This second one shows a copy, and it still appears to include the filename containing the code that crashed the kernel and whatever Windows calls an errno value. It appears the first article is mistaken, and they've just removed the QR code that has been present for a few years?

Maybe someone here can help, because I'm slowly running out of solutions to solve my server problem.

The server (running Linux Mint, Ryzen 1800X, GTX 970, 32GB Kingston Fury Beast 3200 (at most, running at 2400 now)) crashes randomly, mostly at idle only with some background applications running (Jellyfin (without encodes), JDownloader,...) sometimes after hours sometimes after days or even weeks without any issues in between.

At first, I thought it was the high-clocked RAM since I recall 1st Gen Ryzen having issues with that, and that was the only part that I upgraded before the issues started, so I clocked it down to 3000, 2666 and now 2400 and ran RAM tests. The tests brought up no problems. (I had one run on 3200 that failed after 45 minutes, but the error never happened again, not even after 24 hours of continuous testing on none of the frequencies.)

ChatGPT is a bit helpful, so I sent my logs to it, but it doesn't change anything about the problem. It told me to run RAM tests, clock down, check for overheating, and all that stuff. The only thing it found is that I sometimes have MCEs (Machine Check Events) on different CPUs and Banks, but that doesn't give an immediate hint to what's wrong exactly. I also had one single machine crash, where it didn't restart and I had to force reboot it.

So if anyone can help me with what I could still try, I would be really grateful!

#Linux#Mint#PC

Link below is for step by step instructions for installing #reticulum #meshchat on #RaspberryPi using #commandline ( e.g. with #remote #headless #ssh ) with automatic #restart of #radio #rnode #service on pi power-on or #reboot . Suitable for restart of pi+rnode after #brownout of #SolarNode following period of little sun, or for rnode in car #carnode to start automatically when car starts, or battery powered node --->
loramesh.org/subpages/pi_insta

#reticulummeshchat
#nodes like #meshtastic nodes

Ukraine Daily summary - Wednesday, February 5 2025

Russian soldiers face execution threats to retake lost ground near Kupiansk -- Ukraine’s EuroMaidan was not a coup, despite Russian disinfo pushed by Musk -- Ukraine’s robotic army is bringing the fight to Russia -- Europe must act on Russian LNG before Trump makes it impossible -- What to expect from Ukraine’s defense innovation in 2025 -- and more

writeworks.uk/~/UkraineDaily/U

writeworks.ukUkraine Daily summary - Wednesday, February 5 2025Russian soldiers face execution threats to retake lost ground near Kupiansk -- Ukraine’s EuroMaidan was not a coup, despite Russian disinfo pushed by Musk -- Ukraine’s robotic army is bringing the fight to Russia -- Europe must act on Russian LNG before Trump makes it impossible -- What to expect from Ukraine’s defense innovation in 2025 -- and more
#Musk#lng#missiles

TIL that FreeBSD supports soft reboot via sudo reboot -r :dragnaww:

This is necessary when I want just to reboot all machinery from init levels 1 to 3 (restart daemons, userspace programs, remount all filesystems, etc) and don't want to do power cycle, restart libreboot and kernel.

#freebsd#til#reboot

After toying around in #gamemaker and trying to make the game idea work with the gameplay loop I had in mind, I decided that it wouldn't work.
So I killed off almost all code written so far to start with a "blank" project. (No, I'm not quite ready to reveal it yet).