EnglishMobster
EnglishMobster
UBUniversal Blue
Created by EnglishMobster on 9/4/2024 in #🛟bazzite-help
Random hard reboots every 8-10 hours after installing Bazzite, not a problem on Ubuntu or Windows
Hey ho - Every 8-10 hours I'm getting a random hard reboot. Like, both monitors suddenly go completely black and then 20 seconds later I'm staring at my BIOS. In the kernel logs, I see this every time:
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: Machine check events logged
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: CPU 4: Machine Check: 0 Bank 5: bea0000000000108
Sep 02 13:41:02 bazzite kernel: fbcon: Taking over console
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: TSC 0 ADDR eaaa31ee MISC d012000100000000 SYND 4d000000 IPID 500b000000000
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1725309657 SOCKET 0 APIC a microcode 8701013
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: Machine check events logged
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: CPU 7: Machine Check: 0 Bank 5: bea0000000000108
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff8209f80e MISC d012000100000000 SYND 4d000000 IPID 500b000000000
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1725309657 SOCKET 0 APIC 3 microcode 8701013
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: Machine check events logged
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: CPU 4: Machine Check: 0 Bank 5: bea0000000000108
Sep 02 13:41:02 bazzite kernel: fbcon: Taking over console
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: TSC 0 ADDR eaaa31ee MISC d012000100000000 SYND 4d000000 IPID 500b000000000
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1725309657 SOCKET 0 APIC a microcode 8701013
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: Machine check events logged
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: CPU 7: Machine Check: 0 Bank 5: bea0000000000108
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff8209f80e MISC d012000100000000 SYND 4d000000 IPID 500b000000000
Sep 02 13:41:02 bazzite kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1725309657 SOCKET 0 APIC 3 microcode 8701013
I believe I have ruled out hardware problems. MemTest86 found no errors over 3 different runs. Windows does not have this issue. KDE Neon (my previous distro before Bazzite) does not have this issue. The CPU is an AMD Ryzen 5 3600X. I am running stock clocks. The issue happens at idle (it has happened when it is just at the desktop while I am out of the room). The only thing I have found which matches my problem is this: https://wiki.archlinux.org/title/Ryzen#Random_reboots However, that explicitly mentions the Ryzen 5000 series, and I don't have the option for the AMD Curve Optimizer on my BIOS as it is not supported by the 3000 series. Further, that's the 5.11 kernel, and we're a full major version ahead of that now. Given that the only thing which has changed is that I am running Bazzite instead of something else, I am under the impression that Bazzite is at fault here. Is there anything I can do to fix it, or maybe change my kernel version to the one Neon is running (which worked fine)?
19 replies
UBUniversal Blue
Created by EnglishMobster on 9/1/2024 in #🛟bazzite-help
Setting up Razer Nari headset - "read-only file system"
Hello hello again. I have a Razer Nari headset, which has 2 channels for audio. By default, this doesn't work on Linux - however, this kind person has set up some PipeWire/PulseAudio rules to make it work: https://github.com/imustafin/razer-nari-pulseaudio-profile The script is super duper simple - it copy-pastes the .conf files into /usr/share/alsa-card-profile/mixer/paths/. ...Except it can't, because that's part of the read-only file system. I'm new to Fedora in general, so I've seen things like "add it to rpm-ostree" but I don't actually understand how to do that. Any tips?
14 replies
UBUniversal Blue
Created by EnglishMobster on 9/1/2024 in #🛟bazzite-help
Zoom screen share always shares all monitors on Bazzite
Hello! So I just came over from KDE Neon (Ubuntu-based). This was an issue there, too - specifically it started with Plasma 6.1. Basically, when you try to share your screen on Zoom, it will always share all available monitors. This means that your screen will be ultrawide for no good reason. I share my screen quite a lot, and it's super annoying when it's so wide! On Neon, I had to do a 2-part workaround: 1. Downgrade Zoom to one from earlier this year, before they changed their UI 2. Downgrade xdg-desktop-portal from latest to xdg-desktop-portal=1.14.3-0ubuntu2 (Kubuntu LTS version). As stated, this is still a problem on Bazzite - but I don't know how to do the workaround! Alternatively, I think I can just swap to an X Session... except there's no option for an X Session in the login screen. Running rpm-ostree install plasma-workspace-x11 gives me a black screen when I try to load an X Session in Bazzite, without even a cursor nor the ability to enter a TTY. Any help would be appreciated!
5 replies