Run "sudo dmesg -w", put it to sleep and then look what the kernel tells you why he could not sleep.
simonmicro
joined 2 years ago
Most common issue would be something with your system memory. I could imagine that this caused the timeout of your cpu, which waited for the startup code, which never arrived.
In case you want to test that, swap your memory sticks around. Or tell the kernel to ignore that cpu (see command line arguments of the kernel).
Just use xca as a simple GUI - it can do it all.
Instant thought: "Ausgefressen - Moritz Matthies". Good stuff.
Yes, the expidition was certainly fun... But...
My coop friend started it, which lead to my game crashing instantly. After restarting I was able to play, but to never return to my primary save, as it was bugged - including the terminal.
I thought that finishing it could help (as the terminal mentioned "Unable to pause, complete expidition first"). Nope. 9hrs later same problem. In the end I had to merge the expidition-savegame with my primary save using the NMS savegame editor. With some help from a known good save I was even able to reconstruct the final terminal state (stating that I finished the expidition).
What a mess.
For a university project I've scraped a shitload of stuff from dndbeyond.com (primarly the homebrew section) - are you interested in that? I would have to dig if I still have the raw data available (were processed with some ai-model later).
Oh yes, I also played a lot of Star Trek Elite Force back then - I think I liked the first title more, likely because I'm more into VOY. I liked solving the riddles on the levels and trying for hours to find the secrets... What a good time!
The location permission is needed to activate BLE and scan for other devices using low energy. Android things...
Indeed. IIRC this feature was also part of the Reddit version. Also the view option to hide read was there...
Does someone know what this mini-thing in front of the cats is?