Only side effect I've noticed is you lose the ability to manually adjust resolution of external disp
Only side effect I've noticed is you lose the ability to manually adjust resolution of external displays while in gamemode
Zthat's quite the side effect :(
BYeah, it automatically sets the native/max res of the external monitor which can be good/bad depending what you want it for. Res can still be adjusted for desktop mode
D(Fix Steam Download Speed)
DThis Can be a problem ? Can I leave it ON ?
Cbefore I install bazzite proper on my SD, can I update it using the button in steamos settings, like on SteamOS? Or only via CLI?
Zyou can, but it's not as smooth sailing at times and the changelog isn't visible
Mall that download speed fix does is apply this for you https://www.reddit.com/r/linux_gaming/comments/16e1l4h/slow_steam_downloads_try_this/
Reddit
Explore this post and more from the linux_gaming community
Mhighly unlikely to be what caused your issue
Mif itโs magically better now, it may have been Steam server maintenance since it was a Tuesday
Kuhh, I hope itโs not my deck dying
VI mean, considering you're on an emulator my first guess wouldn't be hardware
Ki was playing P3R and suddenly I had mid-30s fps, so I just kept playing and now even Mk8 is not smooth, like it was always upper 50s. Frametime all over the place
Ddid the bazzite startup movie stop working for anyone else?
Di switched to desktop mode, then back to gamemode, steam defaulted back to the og one, and trying to set up bazzite startup video again results in a black screen
Dmissingno, my old friend!
FProbably throttling due to high CPU or GPU temperature
TAnyone having decky issues after update?
ยฉThat is the way your device communicates urgent attention, like pain in your body you can continue disregarding it but you will get more problems at the long run at the end...
It's better to take a break in those situations and let your device cool down a bit...
OR....use lower graphics settings if you can.
It's better to take a break in those situations and let your device cool down a bit...
OR....use lower graphics settings if you can.
ยฉ
JKDE Community
The KDE community proudly presents Plasma 6, Frameworks 6 and Gear 24.02
JLet's go!
KFor info, when playing I never gone higher than 80ยฐC which for me, seems safe
Dreally wish GE named ULWGL something else, i keep accidentally finding docs/guides to the java 3d engine instead of his tool
DGloriousLauncher maybe
Dhas anyone tried it out?
XHey guys, another question from me 
I'm really enjoying Bazzite for its working TDP settings, and nice scaling options, I think I can never go back to windows. Most of the time I'm using Moonlight to stream from my (wired) desktop (AMD 7800x3d + 4090) to my Legion Go, but I'm experiencing stuttering (and overlay info from moonlight detecting slow connection) roughly for 10 seconds every 5 minutes. Before and after the stuttering the stream is smooth. I tested HEVC/H.264 and bandwith options, tried several settings on the win11 host without any change in this behavior. I then installed Moonlight under Windows on the Legion Go, and the problem is not existent there. To further debug, I let a iPerf3 stream (with 10MBit/s, UDP) running in parallel to the moonlight stream in Bazzite, and when moonlight complains about bandwith, the network errors in iperf3 are peaking as well. Long story short: is the network driver that is used in Fedora/Bazzite the problem? Always thought, that Linux is especially bullet-proof when it comes to networking
I'm really enjoying Bazzite for its working TDP settings, and nice scaling options, I think I can never go back to windows. Most of the time I'm using Moonlight to stream from my (wired) desktop (AMD 7800x3d + 4090) to my Legion Go, but I'm experiencing stuttering (and overlay info from moonlight detecting slow connection) roughly for 10 seconds every 5 minutes. Before and after the stuttering the stream is smooth. I tested HEVC/H.264 and bandwith options, tried several settings on the win11 host without any change in this behavior. I then installed Moonlight under Windows on the Legion Go, and the problem is not existent there. To further debug, I let a iPerf3 stream (with 10MBit/s, UDP) running in parallel to the moonlight stream in Bazzite, and when moonlight complains about bandwith, the network errors in iperf3 are peaking as well. Long story short: is the network driver that is used in Fedora/Bazzite the problem? Always thought, that Linux is especially bullet-proof when it comes to networking 
KOkay itโs now hardlocking in P3R loading screen
Kwill try to rollback or bootup a live usb
Kthe only thing I did is update to pre-beta steam channel
Dcould be a number of things, if you are suspecting its the linux driver, may look into dmesg output logs anything regarding the wireless driver. I'm not too familiar with the legion go, do you know what kind of wireless device its using?
I also wouldn't call it bullet proof, its about as bullet proof as any other piece of software, bugs come up, and sometimes gotta wait for kernel patches to fix them.
I also wouldn't call it bullet proof, its about as bullet proof as any other piece of software, bugs come up, and sometimes gotta wait for kernel patches to fix them.
Dmy strategy for debugging any hardware issues is look for dmesg logs, and then google for lines i find in my dmesg logs, excluding any information that is unique to me (timestamps, hostname, etc.) and hit up all linux forums, arch forums are most useful since they tend to get hit by these kind of bugs first and they will link you to threads about ongoing bug investigations and PRs
Dlastly, reason i asked if you know what kind of wireless device, is because idk if it will show up under
lspcilsusbthx for responding @DevilFish303 , will dig deeper. Maybe someone has the feedback that he has the same experience with the Legion Go under Bazzite - or the opposite. lspci gives:
01:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
01:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
Dah that's it, try looking for anything relating to this in dmesg, see what is coming up
Dalso recommend in an ssh session run
sudo dmesg -wgood advice, will check that
๏ฟฝhello all
๏ฟฝloki max its compatible with this distro?
Xno messages in dmesg -w coming up during the moonlight stream and stuttering; is there a way to get more logging for the wlp1s0 device? I'm not very experienced with linux unfortunately.
Dwell on the brightside its not a driver issue
Dactually i shouldn't say that, let me think of what else to check for
Dso the next thing is monitor traffic with eBPF tool, i found a useful guide by redhat that can walk you through how to set this up: https://developers.redhat.com/articles/2023/07/19/how-retrieve-packet-drop-reasons-linux-kernel#using_tools_to_retrieve_drop_reasons though do note the warning at the bottom that not all reasons for dropped packets are covered
Red Hat Developer
This article discusses reasons why packets drop in the Linux kernel and how to retrieve them.
Djw though, you mentioned you do not see these issues on windows at all, which makes me suspect if firewall is getting in the way, what's your network setup?
Xfirewall on Bazzite-side? My network setup is implemented with UniFi, I'm using 2 different APs in the house, the desktop is 1Gbps wired to a UniFi switch. There is no traffic shaping or internal network traffic filtering in place (which would affect windows then as well). I don't see roaming/hopping between the two different Access Points.
XWill now take a closer look to the eBPF tool
Dnot necessarily bazzite side, the default rules are pretty permissive out of the box, the ports required by moonlight are already open by default
XWhats weird is, that the problem occures to frequently, almost every 5-7min for only 5-10seconds. Is Bazzite doing something periodically in the background?
Dthis is what it looks like for me on the bazzite side
Dbut on the other hand, i also run a network wide firewall, so i can control how devices in my house can talk to each other
Dmake sure wlp1s0 is set to the same zone and the ports are open like this, i have absolutely no issues with these default rules
