Yeah I'm on bios install so that would make sense. Odd that it would notify me about that then...
Yeah I'm on bios install so that would make sense. Odd that it would notify me about that then...
Hit notifies you about it since bios install is really not expected as far as i know, it is not an expected install due to it being deprecated many years ago so there is no check in place if you are on a bios install or not.
Hbut yes @pure you can ignore the message since its only needed for secure boot
KOut of an abundance of caution it's notifying everyone
KWhen the next update launches next weekend that message will disappear for you and everyone else
KIt was the best way to make sure everyone was aware of it
KI suppose in your case it's also useful because you should not be using the bios mode regardless
M@Kyle Gospo is your Gamescope still built from source or did you also transition over to Chimera’s Gamescope-plus?
KChimera is slightly behind so I made a patch from their commits and applied it against the latest tagged upstream
KAnd that's what we build
Mgot it, thanks. using it as one final testing sample.
MI’m getting close to filing a Gamescope issue for this HDR nits issue totally separate from our refresh rate findings. Going to try one more Neptune kernel build and see if it makes a difference.
Vanilla Neptune seemed promising at first but then after one or two reboots my HDR metadata nits went back to half of what it should’ve been, leading me to believe it’s getting conflicting drm info somehow and then writing that as the new normal. I’m going to double check Bazzite’s output one more time to see if I overlooked anything.
Vanilla Neptune seemed promising at first but then after one or two reboots my HDR metadata nits went back to half of what it should’ve been, leading me to believe it’s getting conflicting drm info somehow and then writing that as the new normal. I’m going to double check Bazzite’s output one more time to see if I overlooked anything.
Munlike refresh rate if this one isn’t kernel dependent it seems in-scope of Valve issue reports
LI have a question about rebasing? Can I rebase without losing files?
Pyou'd want to
systemd should have a target for that, though, I think? every time a user logs in, execstart a script
that, or I just use cron, or monitor for filesystem changes--I have plenty of options, just have to see what the least overkill method would be
find -type dsystemd should have a target for that, though, I think? every time a user logs in, execstart a script
that, or I just use cron, or monitor for filesystem changes--I have plenty of options, just have to see what the least overkill method would be
Hrebasing does not touch your $HOME folder (other than creating config files for new applications when you run the progam for the first time)
however it is strongly discouraged to change between KDE and Gnome due to the 2 separate desktop environments having conflicting configs so you risk getting an unusable userprofile
however it is strongly discouraged to change between KDE and Gnome due to the 2 separate desktop environments having conflicting configs so you risk getting an unusable userprofile
LThank you. I'm just putting my 1tb drive from my LCD onto my OLED. I'll be keeping KDE. I just wanna be on the testing branch for OLED & HDR.
Hthe stuff in testing is getting merged into main/stable next week btw
Bwhy would i need the
findno one else uses my computer but now im interested in setting this up 
FThere is:
if [ -d /sys/firmware/efi ]; then
if [ -d /sys/firmware/efi ]; then
FFor checking if you have UEFI
Felse
BIOS thing
BIOS thing
Fthis is used for Hide GRUB script
Hwhat i meant is the terminal message he got does not check for it
FOh, my bad
Hi didnt say there was no way to check for it 
LOh, then I'll just wait. Thanks.
WPart List - AMD Ryzen 7 7800X3D, Radeon RX 7800 XT, Fractal Design Terra Mini ITX Desktop
KFans are way overpriced, you can get Noctua for that
KI'm open to making that exit our setup scripts so you're switched with no changes
KLeave it as an advanced user option
KAnd not advertise it heavily
KSince you're almost certainly going to suffer issues and need to know what you're doing
Mjust as an fyi, have not been able to replicate this issue on nobara. been trying for a little while now.
Yyou got nobara working on steam deck?
MBazzite/Nobara got them working alongside each other. We’re in basically the same exact spot with some minor differences.
MThis apparently being one of them
Yhey do you know if it will update bios? and does it start in game mode on deck?
M1: yes, theoretically. they haven’t released any BIOS versions in awhile for me to test but I got the last one working.
2: yes, you can choose between which session you start in
2: yes, you can choose between which session you start in
Msame with controller firmware, that should theoretically work for future updates
Ydo i pick from the display manager/lockscreen?
Mit’s dynamically based off what session you reboot or shut down from. reboot from game mode and you’ll boot back into game mode. reboot from desktop and you’ll boot back into desktop.
Yokay last question did you use rufus or something else for the usb?
Mbalena etcher
Yand ill need m and k right?
Muhhh probably just a keyboard. the Nobara ISO has wifi, Bluetooth, etc. working on the live iso already though
Mso that makes things a bit easier
Ythanks,,,,,, oksy this is really my last question. do you update with the desktop app or in game mode?
Mdesktop app
Mnow that I think about it I could probably hook it up to game mode relatively easily…
