![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://sopuli.xyz/pictrs/image/8167d883-d9f5-4066-8ae7-80e8b3506722.webp)
I always use it when docked. Important to note that the LCD version does not support Bluetooth wake though.
I always use it when docked. Important to note that the LCD version does not support Bluetooth wake though.
You seem to have a misunderstanding of how Bazzite works. It’s just a custom Fedora Atomic spin that includes things like the deck firmware updates, drivers, and gamescope. It does not run SteamOS in a container.
Bazzite uses rpm-ostree. It’s a very different system under the hood.
SteamOS updates can also be done by Discover now. But I would assume his problem is the flatpak updates.
To fix flatpak issues, there is a flatpak repair
command.
I was thinking of using Bazzite. I use Arch for my work install and have been using Arch for personal use since 2015 with Windows dual boot for gaming. Bazzite/UBlue has really surprised me and if I didn’t have an Nvidia GPU I think I would’ve already migrated completely away from Windows with Bazzite. Container based OSes with immutable root are the future IMO.
It’s usually not unencrypted though. You need a special device to defeat the encryption (HDCP).
The local transfer compresses it with the same format the CDN would use, so if the local PC turns off, it just continues via Valve’s servers. The downside is that the compression is quite aggressive. My PC with a 5950X can only go like 300Mbps on local transfer, so the CDN ends up being faster for me since I have gigabit internet and the Deck can get 600 Mbps even over WiFi.
For people with slow Internet speeds, it’s obviously a great feature though.
Bottles lets you easily add games installed in it to your steam library
Have you tried with the newer Mesas (like in SteamOS 3.5)? Apparently it shouldn’t be a problem anymore with the new shader compiler.
Mine arrived today. But I’m on vacation and won’t get back for a week. My roommate brought it inside, so I’ll have it when I’m back home.
512GB model ordered ~25 minutes in. Currently shipping, but UPS status is just “Label Created” at the moment.
The df
command only shows mounted devices and filesystems. You can use lsblk
to show all block devices and their partitions. To format it more nicely to show the labels for each partition, you can use these options: lsblk -o name,mountpoint,partlabel,size
.
This is the output from my deck without the microsd card:
deck@steamdeck ~> lsblk -o name,mountpoint,partlabel,size
NAME MOUNT PARTLABEL SIZE
nvme0n1 476.9G
├─nvme0n1p1 esp 64M
├─nvme0n1p2 efi-A 32M
├─nvme0n1p3 efi-B 32M
├─nvme0n1p4 / rootfs-A 5G
├─nvme0n1p5 rootfs-B 5G
├─nvme0n1p6 /var var-A 256M
├─nvme0n1p7 var-B 256M
└─nvme0n1p8 /home home 466.3G
Amazon is the only seller of the Select cards. For the Plus, anyone can be a seller, so there could be fakes being sold as well. If the Plus is being sold directly by Amazon, then yes, it should be a legit card and there should be no difference.
Why shouldn’t they buy the select? Isn’t the whole purpose of it being exclusive to prevent people from getting fake cards?
It should be noted that the way you listed the partitions misses the dual (A/B) install method that the deck uses. There are 2 identical size partitions for root, var, and EFI. When an update occurs. The system installs the new update on the inactive set of partitions and then tells the UEFI to use the other set on the next boot. That doesn’t matter too much for 512GB models like your’s, but the extra ~5.5GB for the redundant partition layout can be significant for 64GB models.
IIRC, it was 20GB of OS at launch, but they shrunk it. Now it’s a little over 10GB.
I’ve seen a couple short articles where it had 0% savings, but this is the first time I’ve seen it get longer.
HDR is basically unsupported on desktop Linux, though a lot of work has been done recently. Valve meanwhile decided to do their own userspace implementation for their UI and supporting HDR in Proton.
Wake via Bluetooth isn’t new, the OLED model has always supported it (the LCD doesn’t due to hardware). This just lets you disable it for specific devices that you don’t want to wake the Deck.