I did find out that rebasing to *bazzite-deck* on an NVidia laptop definitely does **not** work.
I did find out that rebasing to bazzite-deck on an NVidia laptop definitely does not work.
KKeep an eye on nvk, that should be your ticket to gamescope on Nvidia
JI'm just trying to move an existing Silverblue installation over to a Steam Deck. I don't think I'll need anything NVidia after this.
Pfor anyone else waiting, fedora 39 support just got merged in for sunshine 
CNice!
Cbtw @KyleGospo apologies in advance for pinging - it turns out to be a btrfs issue (or at least a formatting issue) ext4 seems to work well, installed 800gb worth of stuff
C^ that’s regarding the “storage full” issue I reported yesterday even though there’s 400gb left
KFeel free to ping me anytime for good news like this
KShame you can't use btrfs but I'll take it
KJust for my curiosity, what hardware is this?
KThe SD card I mean, not the handheld
C>egs: early access 
Dis there any status of the bluez bug where bluetooth devices won't pair?
KI was not able to reproduce this, if you're having errors please report them upstream
KI am happy to backport patches as they are made
Cit s a sandisk extreme pro 1tb on a legion go
Creally curious why this happened tho, wish I saved some logs
KSame here because I have the same SD card
ESame card here too. No issues with it and BTRFS
Jbazzite doesn't allow layering
etckeeperdnf/usr/bin/dnfHow do other bazzite users version control their
/etc
Twe're supposed to version control it?
DI don't think most of us do. I only manage my home directory and dev tools with home-manager/nix
ENo need to version control it
Pi have wondered how it would be done, but i personally don't have a need. my edits in /etc are very minimal.
CYeah I don't version control it, I have maybe one or two context specific files added and one fstab edit
JWell, I generally do it with
etckeeperi've just layered it without issues. no idea how to configure/test/use but it's on my system.
JHmmm, I'm on bazzite-deck-gnome.
Pi'm on
bazzitecd /etc && sudo etckeeper initsudo etckeeper commit "initial commit"/etcdone, seemed to work fine.
JI like to version control it because
rpm-ostree lets me go back in time, except for /etcwell, we've confirmed it can work. issue lies either in adding gnome, or something deck related.
Pi have no clue of either since i do not use gnome, and have no reason to ever install a deck image
Ptime for some digging 
JI'm checking the ublue repos on github to see if I can find where that script is coming from.
Pafter rereading this, dnf shouldn't even exist... it's an ostree system. there was no
/usr/bin/dnfetckeeperThere's a shell script on my system that just wraps
rpm-ostree.Pweird. i would guess at it being some weird compatibility fix for something with gnome. (big stab in the dark)
JI'll investigate tomorrow when I'm more awake. Still happy to have finally gotten it installed on working on my steam deck, so now it's just figuring out the little things to make using it in Desktop mode better for me.
IIs there somewhere I can easily follow the status of bazzite on steam deck oled? I'd like to install it when it's fully functional
Pthe
:testing branch has many OLED fixes/changesPthere's no curated document or anything if that's what you were after.
Iyeah I was looking for like a list of known oled specific issues
Iguess I can check back in a month or so to see if stable branch is working well
MNobara and Bazzite have 100% OLED functionality. Nobara does for sure and the new fsync kernel today that will get put on :testing should have the last fix needed for Bazzite, related to refresh rate changes.
MWiFi and Bluetooth got figured out a couple weeks ago while audio for Linux 6.6 finally got solved last week
JDigging through the ublue-os repos on GitHub, I found this: https://github.com/ublue-os/akmods/blob/main/build-prep.sh
I think the -deck images are built with
I think the -deck images are built with
KERNEL_FLAVOR=fsync, which triggers running rpm-ostree cliwrap ... which I think installs scripts in /usr/bin/dnf/usr/bin/rpm.GitHub
A caching layer for pre-built Fedora akmod RPMs. Contribute to ublue-os/akmods development by creating an account on GitHub.
JI'm trying to understand why
rpm-ostree cliwrap needs to be called in that script.
Hthe fsync kernel should only be in :testing atm i believe, since it will not work with secure boot, are you on
other than that i dont know anything else about it
:testing?other than that i dont know anything else about it
