Pitstop 2. I copied that floppy.
kbal
joined 1 year ago
If there's anyone whose sexual fetish is exploring previously unseen parts of the uncanny valley, they're in for a hell of a good time in the next few years.
Altman and OpenAI greatly overestimate their ability to control what is done with this technology. The more they tighten their grip, the more open-weights sexbots will slip through their fingers.
Imagine one man having the power to decide such things for all of society. He sure likes to.
Is it t-shirts for sale at a little table off to the side somewhere you'll probably never see unless you go looking? Or is there an advertising billboard behind the stage that lights up after every song?
Oh yeah, I forgot about updating initramfs. Just like I usually do at home. Installing a new kernel would do it automatically though, and I imagine that's somewhat likely to be needed. It has been for both of the new-ish video cards I've had in recent years.
Shouldn't that be "gc_11_0_0_mes_2.bin" — without the double 0? That you could download from git.kernel.org among other places.
That video card came out around the same time as the current version of Debian stable, so it's probably too new to be included in your version of firmware-amd-graphics. It would go in /usr/lib/firmware/amdgpu/ with a bunch of similar-looking files. The other thing you might need to go with that firmware is a newer linux kernel, which you could get from backports.
Is there a c/lostlemmites somewhere?
Even if you are going to do a little bleeding edge development Debian stable can be a good solid base to start from.
I'd use ext4 for that, personally. You might also consider using full-disk encryption (redhat example) if there's going to be any data on there you wouldn't want a burglar to have. Obviously it wouldn't do much good if you don't encrypt the other disk as well, but having a fresh one to try it out on makes things easier.
Ah, Fedora 40 is on kernel version 6.8.9 it seems, the bad one for amdgpu, and it doesn't look like their current build is patched to fix it, so it could be this bug. It's fixed in 6.8.10 and 6.9 if you have the ability to upgrade to those. Otherwise you might want to try reverting to the previous kernel version if that's easy in fedora.
(Edit to add that I didn't see the "im a complete newbie" bit... I'm just very aware of this recent bug because it gave me some trouble. Sorry if you did happen to start with a version that has this problem. It's really bad luck if so. But I don't really know.)