Newb here, help needed w/ Bazzite

Necroscope0@lemm.ee · 7 months ago

Newb here, help needed w/ Bazzite

just_another_person@lemmy.world · 7 months ago

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

Stop listening to AI.

mystic-macaroni@lemmy.ml · 7 months ago

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 · 7 months ago

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 · 7 months ago

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

Xuntari@programming.dev · 7 months ago

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

AngryCommieKender@lemmy.world · edit-2 7 months ago

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 · 7 months ago

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 · 7 months ago

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

mystic-macaroni@lemmy.ml · 7 months ago

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

calamityjanitor@lemmy.world · 7 months ago

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 · 7 months ago

It’s definitely an AMD graphics card crash.

Necroscope0@lemm.ee · 7 months ago

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 · 7 months ago

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 · 7 months ago

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

Botzo@lemmy.world · 7 months ago

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 · 7 months ago

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 · 7 months ago

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 · 7 months ago

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 · 7 months ago

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 · 7 months ago

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/

Necroscope0@lemm.ee · 7 months ago

Yeah I ran that first thing after the crash

FooBarrington@lemmy.world · 7 months ago

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

Necroscope0@lemm.ee · 7 months ago

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

Necroscope0@lemm.ee · 7 months 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)

cmo@lemmy.world · 7 months ago

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

geneva_convenience@lemmy.ml · 7 months ago

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

Necroscope0@lemm.ee · 7 months ago

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