And possible Gnome has issues with eGPUs, or at least on this HP laptop. But Vanilla OS probably isn’t stable for anything.
Ended up putting Debian on the laptop, and tried Gnome first, but installed KDE, I didn’t remove Gnome though.
Easier to debug Debian anyways, not much info on the Vanilla OS site about it. So you mostly have to figure everything out yourself. You can try searching, but you may be searching for eternity, I can get different results every time I search. Sounds like DuckDuckGo isn’t very private.
Hmm Fedora, might have been unstable because of some bug.
amdgpu 0000:6a:00.0: [drm] *ERROR* [CRTC:85:crtc-0] flip_done timed outNot sure if Fedora got that or not, was completely locking up. Good news is, Debian, you can still access a tty on the laptop display.
There’s various workarounds that may or may not work. And may be a problem with VRR in KDE. If you have to use the KWIN things, VRR might not even work anymore. And since VRR is experimental in Gnome, the thing to disable for that, might affect VRR as well, no idea.
But maybe I can go back to Gnome soon.
Currently trying “amdgpu.dcdebugmask=
0x200 amdgpu.runpm=0“.
KWIN_DRM_NO_AMS=1
KWIN_DRM_NO_DIRECT_SCANOUT=1Putting that in /etc/environment, might fix it as well. I put it in there, but commented it out. In case I don’t need it. For Gnome, you only need to change one thing. I’m too lazy to find the info. It was on one of the Git things for something.
Steam hasn’t crapped it out yet, last time I tried opening a game, while doing the shader thing it crapped out. I had to go into a tty and reboot, couldn’t login to KDE, and didn’t say the password was wrong. Well not every time, I kept trying, then I typed it wrong multiple times. But I guess you’d need to rmmod amdgpu, which probably won’t work.
Guild Wars 2 opened, and was able to get in the game, so maybe it’s fine now.
Good luck getting into a tty in Vanilla OS, when it craps out. Pretty sure even when the laptop display was enabled in Gnome, I still couldn’t get in a tty or at least not always. All those buttons do is make it restart the Display Manager, if you are lucky, unlucky and nothing will happen. Perhaps it has no tty. Nice feature, not worth my time to fuck with it anymore.
Well, beginners might like it, they’ll never need a tty. So if it freezes, they can just hold the power button down. And if there data gets corrupted, they can reinstall. Hopefully beginners backup any data they care. The Vanilla OS website says beginners can use it.
I’d prefer to get into a tty, and reboot correctly myself. And check dmesg to see if it says what went wrong. Journalctl may have info, but if it just completely freezes up, maybe not. Not to mention, you might get data corrupted if you reboot or power off incorrectly. So journalctl might be useless.