So I have been getting green screen of death on this new computer build of mine. This new computer is the first time I have run linux as I am NOT paying Microsoft any more of my money. The green screens started happening immediately I had originally thought it was due to old drivers at first but I updated every last thing I could find and it is still happening. AI told me that it could be a corrupted file system and suggested a command but it did not seem to do anything and I do not know why. Please help with this and any other suggestions on why I may be greenscreening. It is very intermittent, if I am online for 17 hours it will happen once or twice. Anyway, here is the command the AI gave me and its results…
fsck / btrfs --check --repair fsck from util-linux 2.40.4 If you wish to check the consistency of a BTRFS filesystem or repair a damaged filesystem, see btrfs(8) subcommand ‘check’.
Probably a super newb question but I am a super newb here in Linux lol
X870 RX9070 XT Ryzen 9800X3D
Thanks in advance
Run a LiveUSB of anything else. If it works, install that instead.
Stop listening to AI.
The best advice was gratuitous.
If ai gives you something to try it’s better than nothing. But I was going to suggest another distro if someone else hadn’t. Thanks ai…
Doing nothing is way better than running random commands suggested by AI, or anyone for that matter, if you don’t know what it does. I’ve seen AI suggest to run
rm -rf ~/, which is obviously never a good idea.What would that command do? Not obvious to this newb. Format everything?
I think there may be some safeguards in place so that it doesn’t, but yeah. It reads something like (rm) remove/delete, (-rf) remove/delete the folder, (~/) do this recursively until you hit root (Unix equivalent of C:).
I may have some of that parsed incorrectly, I haven’t taken the plunge into Linux quite yet. As soon as I figure out what I did wrong in my current hardware build I will install Linux. Probably Mint.
It wouldn’t remove /.
®e(m)ove
-®ecusively
(f)orce
~ /home/thisuser
/ just reinforces that we are referring to the ~ directory itself
Thanks! It’s been a while since I’ve used Linux terminal commands.
Yeah, sorry for assuming it’s obvious. Maybe I’ve been around Linux people too much xD
AngryCommieKender is mostly right. It would delete every file and directory in your home directory, which is the Linux equivalent of the Users/<username> folder on Windows. It’s where all of your Documents, Pictures, Downloads, config files, and the likes are stored.
I’m not sure it’s a protected action, since it’s not the actual root of the computer. But, I’ve never tried, so I don’t know :P
I should have phrased that better. I agree copy and pasting commands off of the internet is a terrible idea. Be they from ai or from a forum or wiki. By ‘try’ I meant look into. As in explore that path. To you and I ‘try’ means something different than a new user. I will be more careful in the future
I get ai being an existential threat to most of the denizens of lemmy (overwhelmingly techy and left leaning) but ai vastly simplified the Linux install process for me. I took a c++ class 10 years ago that I failed and that was about the extent of my programming knowledge so without AI it would’ve been a nightmare trying to get everything set up. Gemini remembered what distro I was installing, my drives and their /dev/ name or whatever, how I should insert those into fstab, why grub wasn’t picking up my nobara install, etc. AI might be useless in other situations but computer commands and troubleshooting I think it’s the one place it excels.
Tell us more about what’s happening, is the whole monitor turning green or just parts of it?
Does it stay green until you do something, or does it go away on its own?
Does it happen only with certain games or applications, or does it happen regardless of what’s running?
And please for the love of fuck do not run any commands you don’t personally understand, especially if it came from an “ai”. Don’t poison your brain (and the planet) with “ai” bullshit, please!
Solid green screen across the whole thing. The speaker starts humming the mouse and keyboard do not do anything and it does not resolve on its own (not within five minutes or so anyway). I have to do a hard reboot, then it works fine for the next 7-14 hours and then it happens again. Does not matter what I am doing. I have had it go green when I was reading plain text and not even touching the inputs.
Is the sound coming from the motherboard speaker or through a sound card or display?
From the MB to the external box speaker on the desk.
So I was wrong, sound was wired through the display via HDMI to the MB. I switched the speaker over to the MB directly and plugged the monitor into the GFX card instead of the MB, see if this changes anything.
Your monitor always needs to be plugged into the graphics card. If you plug it in via the motherboard, then your GPU is doing nothing, as it can’t backfeed to that motherboard connector. CPUs often have their own graphics built-in, and that’s what yours would have been using instead.
You’re going to get much better performance now too if the monitor was plugged into the motherboard before
This sounds to me like a hard drive/ file system issue. Don’t know how to fix it but if the mouse cursor doesn’t move, it’s usually a storage device issue
There is no cursor
Oh, scratch that, then
Solid green, have to hard reboot.
Your motherboard wouldn’t happen to be an AsRock? There’s been reports of ASRock mobos in particular causing problems with 9000 series AMD chips, especially the X3D. Mate of mine running windows has been having it crash especially when idle at desktop.
I’m not familiar with a green Linux equivalent to the BSOD. Is it completely green? In that case it may be a graphics problem…
It’s definitely an AMD graphics card crash.
Hrm, no MB is MSI. Graphics card is AsRock though, were there compatibility issues with them too? And yes, completely solid green screen. Speaker also humming and nothing to be done, a hard reboot is required
Like Hawke said it seems like the graphics card or driver crashing. Very hard to troubleshoot, especially when it’s random. Bazzite probably already has very recent drivers, there’s this post on the bad website listing some things to try. This stuff can lead to superstitious thinking, with people changing something, rebooting to have it work fine for a while then they post that change as if it fixed it.
God speed.
Thank you for this resource, now I have a couple more things to try before busting open the case and messing with hardware
I’m a bazzite user for a good year now, and also a first time Linux user. My hardware is amd as well, and for me the experience has been great, the most annoying issues having been compatibility workarounds for windows software. I would definitely recommend you to join their discord for support.
A green screen of death does not sound healthy, even crashes or hard reboots have never produced something similar for me. To rule out hardware issues, can you install a windows copy and/or create a USB with a live Linux OS such as mint to compare? (For reference, some Linux distros are able to run entirely off a USB stick, albeit much slower due to the obvious bottleneck).
If all this checks out I would suggest either reinstalling bazzite off a verified iso (there is a function before installing to make sure there are no errors) or using another distro.
I already tried redownloading and reinstalling Bazzite, yeah. Followed install instructions on Bazzites page pretty sure it had me verify the ISO
What do you mean by “green screen of death”? Is there any text or something you can transcribe or screenshot for us?
No text or screen shot possible, screen is just solid green mouse and keyboard do nothing. Have to do a hard reboot.
Ah. If this is a new build that suggests a hardware issue. Can you try running with only one stick of RAM and/or xmp disabled to see if that fixes things?
Yeah I was going to try messing with hardware next to see if it helps but I want to try all the software based stuff first, I hate fiddling with the hardware. I am just about there though, lol. Not much left software wise I don’t think
Which bazzite build did you install?
Are you able to switch to a secondary or tertiary TTY with Ctrl-Alt-F2 or Ctrl-Alt-F3?
I have not tried what you are asking in the second line because I have no clue what a secondary TTY even is, let alone the shortcuts or commands to do it. You were wondering if I tried this while the green screen is up or while everything is working normally?
While the green screen is up. I listed the shortcuts in the above comment. If there is an issue in the graphics pipeline you may be able to troubleshoot from a terminal only session using Ctrl+Alt+F2.
Login to that text only eesison with the username a password you used when creating the image.
Do you know which bazzite image you used? I think for your configuration it should have been bazzite-desktop. You might be having a green screen graphical issue if you accidentally downloaded a flashed bazzite-deck or bazzite-nvidia with an AMD graphics card.
It was desktop KDE I can not remember if it was the one with gaming mode or not. I think it was not but I could be misremembering. I used one of the first install and the other on the second.
Where you able to log in to a TTY session?
All bazzite images support ‘gaming mode’. The deck images boot into it straight away which could cause problems with desktop hardware.
Consider joining the ublue discord group and troubleshooting with the creators of bazzite in the bazzte channel. They are very knowledgeable and if your issue is reproducible they would be able to implement a fix in future images.
Off the top of my head, I think
sudo journalctl -xeb -1should give you some useful error output for the previous boot (after rebooting from a failure).There’s a
--list-bootsoption if you’ve rebooted a couple times since but aren’t entirely sure.OP, do this - it’s the best way to figure out what’s happening. It could be any number of issues, e.g. faulty RAM. With the output of the command above people can tell you what to test for.
sudo journalctl -xeb -1 [sudo] password for Necroscope:
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:39:09 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f>
Jun 06 09:39:22 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f>
Jun 06 09:41:58 bazzite steam[3399]: ERROR: ld.so: object ‘/usr/lib/extest/libextest.so’ from LD_PRELOAD canno>
Jun 06 09:41:58 bazzite steam[3399]: ERROR: ld.so: object ‘/usr/lib/extest/libextest.so’ from LD_PRELOAD canno>
Jun 06 09:45:56 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f>
Jun 06 09:45:56 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f>
Jun 06 09:46:03 bazzite plasmashell[2860]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtra>
lines 1091-1114/1114 (END)
That’s unfortunately a bit cut off. Could you run this again with the following command?
sudo journalctl -xeb -1 --no-pagerJun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49
Jun 06 09:39:09 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such file or directory
Jun 06 09:39:22 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such file or directory
Jun 06 09:41:58 bazzite steam[3399]: ERROR: ld.so: object ‘/usr/lib/extest/libextest.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jun 06 09:41:58 bazzite steam[3399]: ERROR: ld.so: object ‘/usr/lib/extest/libextest.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Jun 06 09:45:56 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such file or directory
Jun 06 09:45:56 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such file or directory
Jun 06 09:46:03 bazzite plasmashell[2860]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:24: TypeError: Cannot read
property ‘toolTipMainText’ of null
Hm, unfortunately nothing obvious. And your last boot ended with a crash?
Nevertheless you could try running a Memtest (this can take a while) - it will check whether any of your RAM modules are faulty: https://www.memtest.org/
Yeah I ran that first thing after the crash
Oh, you should have mentioned that - or do you think that fsck is Memtest? It is not.
I will give this a try next time it happens! Good looking out
Alright so it finally happened again, here is the output of that command:
sudo journalctl -xeb -1 [sudo] password for Necroscope: Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:39:09 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f> Jun 06 09:39:22 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f> Jun 06 09:41:58 bazzite steam[3399]: ERROR: ld.so: object ‘/usr/lib/extest/libextest.so’ from LD_PRELOAD canno> Jun 06 09:41:58 bazzite steam[3399]: ERROR: ld.so: object ‘/usr/lib/extest/libextest.so’ from LD_PRELOAD canno> Jun 06 09:45:56 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f> Jun 06 09:45:56 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f> Jun 06 09:46:03 bazzite plasmashell[2860]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtra> lines 1091-1114/1114 (END)
I have a 9070xt and a 7600x. I was getting game crashes for a solid week. Although no green screens. Check which version of Mesa you are on, if it’s not the latest, do the upgrade from the terminal. I think you want 25.0.x. This solved my issues it’s been solid since. 9070XT support improved a lot over the last month. I don’t recall the commands to check Mesa version, etc. but that’s something AI should be able to give you. For whatever reason, updating via the GUI did not work for me.
I tried this one already, saw it when I was googling possible solutions. I am also starting to figure it is a hardware issue. I was very uncertain being new to Linux I wanted some software input but it is not looking good for an easy software fix.
Can you install slightly older drivers? Also maybe reseat the GPU (plug out and in)
I will try reseating it, this is the second set of drivers I have tried already though
Which version of bazzite did you download? Do you get the installer to boot?
Yeah everything boots and is installed and works great. Games, discord, everything works. It’s just that randomly the screen goes solid green and I have to hard reboot. It happens about once every 7 or so hours usually I would say.
Honestly that sounds more like a hardware issue than software
Yeah starting to come to that conclusion as well.
And which version of bazzite did you install?
These are the system and build details in the system info, this includes the version right?
Operating System: Bazzite 42 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 Kernel Version: 6.14.4-104.bazzite.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor Memory: 30.4 GiB of RAM Graphics Processor 1: AMD Radeon Graphics Graphics Processor 2: AMD Radeon Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7E51 System Version: 1.0
