Treimage iso
Cand what pros does it have over steam deck os?
Oyou probably wont need to but yeah you can just reinstall steamos
NI'm hard pressed to believe it would be the hard drive causing it.
NIt installs fine, it just crashes when you're trying to log in to the desktop mode?
Apretty much. I'm okay now I've rebased to a older version
AState: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-20240427
Digest: sha256:67bb1f9dd52a420f080fd67e71a60bb6f732c12bacab7d27476dfbdca601c757
Version: 40.20240427.0 (2024-04-27T22:36:59Z)
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:f5374c4d16989cdcb013fc843eb67c481f3ef4409bfb742e916165c9829833cd
Version: 40.20240521.0 (2024-05-22T06:03:10Z)
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-20240427
Digest: sha256:67bb1f9dd52a420f080fd67e71a60bb6f732c12bacab7d27476dfbdca601c757
Version: 40.20240427.0 (2024-04-27T22:36:59Z)
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:f5374c4d16989cdcb013fc843eb67c481f3ef4409bfb742e916165c9829833cd
Version: 40.20240521.0 (2024-05-22T06:03:10Z)
NInteresting, so it's only on the latest update?
Tnot the best place for it but installation guide has that info
AI'm seeing the issue on 40.20240521.0 and 40.20240517.0
Arpm-ostree status taken when in broken desktop:
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-20240427
Digest: sha256:67bb1f9dd52a420f080fd67e71a60bb6f732c12bacab7d27476dfbdca601c757
Version: 40.20240427.0 (2024-04-27T22:36:59Z)
Diff: 451 downgraded, 119 removed, 31 added
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:f5374c4d16989cdcb013fc843eb67c481f3ef4409bfb742e916165c9829833cd
Version: 40.20240521.0 (2024-05-22T06:03:10Z)
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-20240517
Digest: sha256:f15f2dfeb61a526aab8a3e7c6072699e84e2eaca5c2932fb725ba778a243daef
Version: 40.20240517.0 (2024-05-17T17:08:59Z)
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-20240427
Digest: sha256:67bb1f9dd52a420f080fd67e71a60bb6f732c12bacab7d27476dfbdca601c757
Version: 40.20240427.0 (2024-04-27T22:36:59Z)
Diff: 451 downgraded, 119 removed, 31 added
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:f5374c4d16989cdcb013fc843eb67c481f3ef4409bfb742e916165c9829833cd
Version: 40.20240521.0 (2024-05-22T06:03:10Z)
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-20240517
Digest: sha256:f15f2dfeb61a526aab8a3e7c6072699e84e2eaca5c2932fb725ba778a243daef
Version: 40.20240517.0 (2024-05-17T17:08:59Z)
OAs far as the Steam Deck goes, faster updates and expanded peripheral compatibility, as well as being able to layer packages on top of the system without them being wiped every update (see Waydroid)
NWould it be feasible to make a dummy account to see if that account has the same issues on the latest version?
ASure
NIt will help to narrow it down to being a profile issue or not.
NI would try it a couple of ways. If the dummy account doesn't work when you make it in the 0427 image, try making it from the command line on the bad image and log into that one.
N@Kyle Gospo TBH, I'm not sure if Gamescope supports multiple profiles or not?
Kit does not
NIs it possible if the dummy account does work that he could migrate his user data over to that account?
Kcrash appears to be in kde w/ libc
Kwhich is odd
OHey, Vulkan is completely borked for me on the asus-nvidia image. Not sure what to do. It's specifically Vulkan, the GPU is detected afaik and Vulkan games crash at launch
NJust trying to narrow it down to what it could be.
Knot that they have any
Hregarding 1080p/HD streaming, i wonder if a windows VM with HW passthrough would work as a server for sunshine (or even to just use to watch on) . if so, is there an instruction guide to setting up passthrough on Fedora/Bazzite? I am not confident my current old HW will work as a Sunshine Server, and besides, if this passthrough would work, is a bit more convenient
Ksudo dmesg | grep nvidia
SI'm seeing this whenever I run
export-gpupcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted
O
Kdid you run it as sudo?
Smight that have something to do with the Intel GPU not being seen?
Sno, but it says the same thing when I do
SAokay this is going to sound weird, but rebasing to stable from 0427 has resolved the issue? Not sure what changed same user
Khow about rebasing to just
:stable?KI expect the latest build to have this fixed
Athats what I did 
Klol, good
K
NIt doesn't need to be more complicated.
NI'm happy it's working lol
Kseems like it loaded, not sure what's up with the crash
Knvidia driver hasn't changed recently
NI still need to get my weird sound issues on the OLED GitHub issue open @Kyle Gospo Not sure it's anything we can do anything about.
NJust hate the Russian roulette of picking up my OLED and sometimes sound will bug out lol
Ovkcube returns a segmentation fault. It CAN see the GPU, for what it's worth. TF2 crashes at launch, a more modern Source game specifically says "D3D11: Failed to create swapchain! (FL: 11.1, HRESULT: 2147467259)". This is isolated ONLY to Vulkan.
OForcing vkcube onto my integrated graphics works fine, but it defaults to discreet (which is ideal, obviously), resulting in a crash
OWhat's weird is that
vulkaninfo --summary still reports the nvidia GPU properlySI'm going to create a forum post, as that is far easier to track than the madness that is Discord https://universal-blue.discourse.group/t/attempting-gpd-wm-2023-with-oculink-arc-a580-egpu/1845/2
Universal Blue
When booting up, the GPD boots up fine with the Oculink-connected eGPU, however it doesn’t see it. When running export-gpu I also see a recurring error here: pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted
OSolved! It was remnants of system76-power setting my GPU to compute mode by default for some reason
