Newb here, help needed w/ Bazzite : linux

[–] [email protected] 6 points 6 days ago (1 children)

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?

[–] [email protected] 5 points 6 days ago (1 children)

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?

[–] [email protected] 5 points 6 days ago (1 children)

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.

[–] [email protected] 4 points 6 days ago (1 children)

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.

[–] [email protected] 2 points 6 days ago* (last edited 6 days ago)

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.

[–] [email protected] 5 points 6 days ago (1 children)

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.

[–] [email protected] 4 points 6 days ago

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.

[–] [email protected] 53 points 1 week ago* (last edited 1 week ago) (10 children)

Run a LiveUSB of anything else. If it works, install that instead.

Stop listening to AI.

[–] [email protected] -4 points 6 days ago

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.

[–] [email protected] 8 points 1 week ago

The best advice was gratuitous.

load more comments (8 replies)

[–] [email protected] 18 points 1 week ago (2 children)

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!

[–] [email protected] 5 points 1 week ago (4 children)

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.

[–] [email protected] 3 points 6 days ago (1 children)

Is the sound coming from the motherboard speaker or through a sound card or display?

[–] [email protected] 3 points 6 days ago (1 children)

From the MB to the external box speaker on the desk.

[–] [email protected] 1 points 6 days ago (2 children)

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.

[–] [email protected] 3 points 6 days ago

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.

[–] [email protected] 2 points 5 days ago

You're going to get much better performance now too if the monitor was plugged into the motherboard before

load more comments (3 replies)

load more comments (1 replies)

[–] [email protected] 6 points 1 week ago* (last edited 1 week ago) (1 children)

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.

load more comments (1 replies)

[–] [email protected] 6 points 1 week ago (4 children)

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...

[–] [email protected] 5 points 1 week ago

It’s definitely an AMD graphics card crash.

load more comments (3 replies)

[–] [email protected] 6 points 1 week ago (3 children)

Off the top of my head, I think sudo journalctl -xeb -1 should give you some useful error output for the previous boot (after rebooting from a failure).

There's a --list-boots option if you've rebooted a couple times since but aren't entirely sure.

[–] [email protected] 3 points 6 days ago

I will give this a try next time it happens! Good looking out

[–] [email protected] 2 points 6 days ago

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)

[–] [email protected] 5 points 1 week ago (1 children)

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.

[–] [email protected] 1 points 6 days ago (1 children)

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: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: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)

[–] [email protected] 3 points 6 days ago (1 children)

That's unfortunately a bit cut off. Could you run this again with the following command? sudo journalctl -xeb -1 --no-pager

[–] [email protected] 1 points 6 days ago (1 children)

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: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

[–] [email protected] 2 points 6 days ago (1 children)

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/

[–] [email protected] 1 points 6 days ago (1 children)

Yeah I ran that first thing after the crash

[–] [email protected] 1 points 6 days ago (1 children)

Oh, you should have mentioned that - or do you think that fsck is Memtest? It is not.

[–] [email protected] 1 points 6 days ago (1 children)

No I have not tried to run the memtest yet

[–] [email protected] 1 points 6 days ago

Do you have DOCP/XMP/Expo (whichever your board may call it) turned on? If so, you might want to try turning it off and see if the crashes stop (or at least get reduced). RAM could be fine but just not stable, which a BIOS update might help. Also might help in the event that your board is one of those that have had issues recently with the X3D CPUs. There is always a chance that the GPU might be faulty. Which I don't know how to best test for that short of just trying an old one (or a friend's if they have their old one).

[–] [email protected] 5 points 1 week ago (1 children)

What do you mean by "green screen of death"? Is there any text or something you can transcribe or screenshot for us?

[–] [email protected] 4 points 1 week ago (2 children)

No text or screen shot possible, screen is just solid green mouse and keyboard do nothing. Have to do a hard reboot.

load more comments (2 replies)

Linux

Rules

Related Communities