

@ProdigalFrog Interesting, also yes. Now if only I could read the bug report to see the details to see if I can resolve it without creating an account on their gitlab instance :/
Occasional rants, swearing, #Linux tips, #Gaming on Linux, general tech, and the occasional #Ohio local rant.
Systems admin & developer in central Ohio suffering through Windows at day job & run Linux or BSD anytime other.
Run this community instance (open to the public) and help with Veracious Network game servers and network.
VN on Discord - https://discord.gg/9CWsDncg7w
Bits & Bytes on Youtube: https://www.youtube.com/channel/UCLOuiL0JQoIos5C-zEgerqw
tootfinder searchable
@ProdigalFrog Interesting, also yes. Now if only I could read the bug report to see the details to see if I can resolve it without creating an account on their gitlab instance :/
@harrys_balzac Is it complaining that /media/ext_EXT4_drive isn’t mounting? If your root drive (/) is mounting and you have access to /etc/fstab, you can just edit that file with the new UUID of the drive.
ls -lha /dev/disk/by-uuid/
To see what the new UUID is, (assuming you know the device path).
@ProdigalFrog
> When this happens, the kernel literally doesn’t allow the compositor to present to the screen anymore, so the screen is completely frozen forever
Yup, that sounds awfully familiar! Also the log reports from that seem quite familiar too, (Gnome/Wayland + 6.12.2 kernel over here). The 7900XTX seems less prone to the issue however so it doesn’t happen to me _too_ terribly often.
I’ve noticed it happens more often when I’m spawning / closing full screen 3d applications such as games, ie when working on mods.
Unfortunately they don’t seem to have a solid plan on how to resolve performing a reliable reset on the driver and the work-arounds don’t seem to reliably work. Guess I’ll just have to be patient and save frequently.