Newb here, help needed w/ Bazzite

just_another_person@lemmy.world on 06 Jun 00:03 next collapse

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

Stop listening to AI.

bastion@feddit.nl on 06 Jun 01:54 next collapse

The best advice was gratuitous.

wuphysics87@lemmy.ml on 06 Jun 02:44 next collapse

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…

Xuntari@programming.dev on 06 Jun 11:25 collapse

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.

Necroscope0@lemm.ee on 06 Jun 14:43 next collapse

What would that command do? Not obvious to this newb. Format everything?

AngryCommieKender@lemmy.world on 06 Jun 16:02 next collapse

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.

lagoon8622@sh.itjust.works on 07 Jun 15:15 collapse

It wouldn’t remove /.

®e(m)ove

-®ecusively

(f)orce

~ /home/thisuser

/ just reinforces that we are referring to the ~ directory itself

AngryCommieKender@lemmy.world on 07 Jun 16:43 collapse

Thanks! It’s been a while since I’ve used Linux terminal commands.

Xuntari@programming.dev on 06 Jun 23:34 collapse

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

wuphysics87@lemmy.ml on 06 Jun 21:55 collapse

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

Valencia@sh.itjust.works on 06 Jun 18:18 collapse

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.

savvywolf@pawb.social on 06 Jun 00:14 next collapse

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

Necroscope0@lemm.ee on 06 Jun 04:14 collapse

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

savvywolf@pawb.social on 06 Jun 11:08 collapse

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?

Necroscope0@lemm.ee on 06 Jun 14:14 collapse

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

noxypaws@pawb.social on 06 Jun 00:27 next collapse

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!

Necroscope0@lemm.ee on 06 Jun 04:01 next collapse

Solid green, have to hard reboot.

Necroscope0@lemm.ee on 06 Jun 04:13 collapse

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.

crates@lemmy.world on 06 Jun 12:32 next collapse

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

Necroscope0@lemm.ee on 06 Jun 15:32 collapse

There is no cursor

crates@lemmy.world on 06 Jun 21:56 collapse

Oh, scratch that, then

counterspell@lemmy.world on 06 Jun 15:48 collapse

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

Necroscope0@lemm.ee on 06 Jun 16:07 collapse

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

Necroscope0@lemm.ee on 06 Jun 23:45 collapse

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.

princessnorah@lemmy.blahaj.zone on 07 Jun 02:04 next collapse

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.

MangoPenguin@lemmy.blahaj.zone on 07 Jun 12:50 collapse

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

Lemmchen@feddit.org on 06 Jun 00:35 next collapse

Which version of bazzite did you download? Do you get the installer to boot?

Necroscope0@lemm.ee on 06 Jun 04:09 collapse

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.

unskilled5117@feddit.org on 06 Jun 06:39 next collapse

Honestly that sounds more like a hardware issue than software

Necroscope0@lemm.ee on 06 Jun 15:32 collapse

Yeah starting to come to that conclusion as well.

Lemmchen@feddit.org on 06 Jun 13:37 collapse

And which version of bazzite did you install?

Necroscope0@lemm.ee on 06 Jun 14:03 collapse

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

calamityjanitor@lemmy.world on 06 Jun 01:05 next collapse

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…

Hawke@lemmy.world on 06 Jun 03:39 next collapse

It’s definitely an AMD graphics card crash.

Necroscope0@lemm.ee on 06 Jun 04:07 collapse

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

calamityjanitor@lemmy.world on 06 Jun 06:51 collapse

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.

Necroscope0@lemm.ee on 06 Jun 14:12 collapse

Thank you for this resource, now I have a couple more things to try before busting open the case and messing with hardware

GregorGizeh@lemmy.zip on 06 Jun 01:33 next collapse

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.

Necroscope0@lemm.ee on 06 Jun 04:04 collapse

I already tried redownloading and reinstalling Bazzite, yeah. Followed install instructions on Bazzites page pretty sure it had me verify the ISO

Botzo@lemmy.world on 06 Jun 01:47 next collapse

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.

FooBarrington@lemmy.world on 06 Jun 06:52 next collapse

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.

Necroscope0@lemm.ee on 06 Jun 16:55 collapse

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)

FooBarrington@lemmy.world on 06 Jun 17:01 collapse

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

Necroscope0@lemm.ee on 06 Jun 17:24 collapse

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

FooBarrington@lemmy.world on 06 Jun 18:01 collapse

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: www.memtest.org

Necroscope0@lemm.ee on 06 Jun 18:29 collapse

Yeah I ran that first thing after the crash

FooBarrington@lemmy.world on 06 Jun 19:43 collapse

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

Necroscope0@lemm.ee on 07 Jun 01:13 collapse

No I have not tried to run the memtest yet

dRLY@lemmy.ml on 07 Jun 03:12 collapse

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

Necroscope0@lemm.ee on 06 Jun 14:23 next collapse

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

Necroscope0@lemm.ee on 06 Jun 16:54 collapse

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)

geneva_convenience@lemmy.ml on 06 Jun 08:34 next collapse

Can you install slightly older drivers? Also maybe reseat the GPU (plug out and in)

Necroscope0@lemm.ee on 06 Jun 14:04 collapse

I will try reseating it, this is the second set of drivers I have tried already though

cmo@lemmy.world on 06 Jun 12:46 next collapse

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.

Necroscope0@lemm.ee on 06 Jun 14:21 collapse

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.

WilfordGrimley@linux.community on 06 Jun 13:48 collapse

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?

Necroscope0@lemm.ee on 06 Jun 14:17 collapse

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?

WilfordGrimley@linux.community on 06 Jun 15:04 collapse

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.

Necroscope0@lemm.ee on 06 Jun 15:31 collapse

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.

WilfordGrimley@linux.community on 07 Jun 11:17 collapse

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.