KKThis shows it found your display
Kunlike your other logs
KI see no errors here
KSame here, found your display
KKpatched edid w/ right values
KKterminated naturally
Kthe one bad log I saw never detected an eDP-1 display
D
Klikely home
Knothing stands out to me here regarding steam or gamescope specifically
DI am probably gonna do a
sudo rm -rf /var/home/deck/* ; cp -R /etc/skel/* /var/home/deckwould j0rge know more about this or possibly @EyeCantCU
EI've never had this happen before
EIt does sound like something going on in home
Dcould it be a full
/boot
Kthat is weird, my boot is 727MB and only 32% full
Didk how to clean it. I might try removing my 10 pinned deployments
Dis it normal for GPU id in distrobox to not match what you see on the host?
KHow are you testing that?
KCan double check on my end
Dvulkaninfo | grep 'GPU id'it comes up as NAVI32 on the host, but GLFX11 in distrobox
K
Doh hmmm... im on 7800 XT, i wonder if that's why
Kif it's working I wouldn't sweat it imo
Kcould be down to different system libraries
Kor even versions
Kbetween the host and the box
Klike lemme try in debian or something, hold on
K
Kmint behaves more like my host
Doh what did you install a few lines above?
Kvulkaninfo
Kwasn't in my container
Dmaybe i missed something besides mesa-utils
Di had to reinstall to be sure, this is an ubuntu box:
Dill ignore it for now, so weird lol
Doh hmmm as soon as this update is done, i will try arch, is your debian based on bookworm or sid?
Kmy debian example was mint based on debian
Knot sure what they base on specifically
KI'd wager it's closer to unstable
Dohhhh interesting, it definitely depends what container to use, the result with bazzite-arch shows my GPU
D
Dim guessing bleeding/cutting edge distros like arch and debian sid containers are better suited for passing over devices when its newish hardware*
Dremoving those deployments did reduce the size and the error shows up less. Is there a way for systemd to show an error instead of the ?
