• 2 Posts
  • 8 Comments
Joined 1Y ago
cake
Cake day: Jul 06, 2023

help-circle
rss

Bought the 512gb LCD via preorder, got a 2tb for it, upgraded/skinned it with personalizations, then got the LE OLED when it went live.

For me, personally, I thought it was well worth it. However I use it daily. I have a fully functional rig with 3080, but just find myself constantly tinkering with my deck and like being able to take it on work trips constantly with minimal impact to my carry on weight. Beyond the screen, the battery life is the real winner here in combination with the enhancements. But I also had the money to spend on it. If you’re tight for cash, then it’s probably best to wait. Or you could try selling to offset cost. Just really depends on what you want to do for extra battery life and the like.


Transferring SSD from LCD to OLED Dual Boot - My Experience
Wanted to post my experience so far for others that are in the same niche as me, as I didn’t find much on it looking around. - Prior to moving my SSD to OLED, I made sure I was current on updates with SteamOS, specifically I was in the Beta branch. - I also made sure to download the new APU/SD card drivers on my windows partition. Someone managed to find a wifi driver that works for Windows here - https://oemdrivers.com/network-qualcomm-qcnfa765 - Haven’t found a working Bluetooth driver yet for windows, so be forewarned on that - After the above, I just plucked out the SSD from the LCD over to the LE OLED model - as others have mentioned, be careful of the ribbon cable. I managed to bend back the protective plate enough to get at the screw holding the SSD in place, it was easier getting out than putting back in, but after about 5 minutes of carefully keeping the protective plate peeled back and making sure SSD was properly seated, was able to get screw back in - After initial boot with my 2tb SSD, selected the SteamOS boot, got into it, immediately ran another update, restart, and boot straight back to SteamOS. - I use Clover as my boot manager, so went into desktop mode and ran the tool, made sure to re-enable the efi partitions again and changed the theme. - Restart now brings me to the boot manager, selected my Windows 10 partition - On boot, it was oriented in portrait mode (sideways), super easy fix by changing back to landscape - Ran APU, SD card, WiFi drivers, everything with those are more operational - Windows still missing audio and Bluetooth drivers, but is otherwise functional Figured to post this to make sure others know what to expect, overall much easier than I thought it was going to be.
fedilink

So I wanted to follow up on this with what I did, and think I found the solution. This way if someone like me trawls the internet looking for something that is the same problem, they might have resolution.

Basically I isolated the problem to podman. What it looks like is I had an existing podman directory pre-3.5.1 update and it had issues with distrobox. So what I did;

Went to .local\podman - deleted the contents of that folder.

Then followed the emudeck distrobox guide to reinstall podman to .local\bin\

Made sure to rename the podman launcher to simply “podman”.

I also edited the .bashrc in home\deck which looks like it had leftovers from the previous podman to have the following (per guide)

Uncomment the xhost line below if you know that you are using xhost

#xhost +si:localuser:$USER export PATH=$HOME/.local/bin:$PATH

I only re-installed podman, and left distrobox alone. You may also have to use the following commands, as I did;

sudo touch /etc/subuid /etc/subgid sudo usermod --add-subuid 100000-165535 --add-subgid 100000-165535 $USER

For reference, this is the guide - https://emudeck.github.io/community-creations/steamos/third-party-emulation/?h=distrobox#how-to-set-up-distrobox

Hope this helps some stranger out there figure things out


Weird Issue with SteamOS Beta and Distrobox
So I recently moved from Stable to Beta to capitalize on Distrobox being added natively to the deck. I used Distrobox a lot late last year, then after I upgraded to a new SSD, went entirely fresh and stayed in Stable channel. The problem I’m encountering, I can create a container (created 2 Debian containers and a Fedora container), but I can’t enter any of them. I tried removing and creating new ones to no avail. This is the output I get below. Wondering if anyone has encountered this or if it’s just me, or if there are recommendations on how to troubleshoot. deck@steamdeck ~)$ distrobox enter debian Container debian is not running. Starting container debian run this command to follow along: podman logs -f debian [conmon:e] Include journald in compilation path to log to systemd journal Error: unable to start container "0abddd5ce95420fcfa7b670862258704a724fb270c18176d6e3602a2d99018c6": exit status 1
fedilink

No - strictly because I gutted windows update via a Windows Lite tutorial. Basically it’s an evergreen Windows OS that I’m using, so I never have to worry about Windows messing the boot. SteamOS will sometimes bork it, but I use Clover as my dual boot solution and it’s fairly easy to recover.

The trouble with a stock Windows OS is the frequent updates, to the point of your question. I do believe there are ways to mitigate it, but does require a bit of prep and being aware of windows And its updates.


I have 0 regrets upgrading to 2tb. I now have a dual boot setup with windows taking 1tb and SteamOS taking the other 1tb, and then a 1tb SD card for the SteamOS side. Makes life sooooooo much easier, no longer having to play musical games for what I want on my deck. Can have a modded FO new Vegas list, modded morrowind list, and another couple dozen games with space to spare (ranging from Cyberpunk to terraria). And on the windows side, plenty of room there to play with my different server emulators, VMs and the like. It’s truly ideal and will give you substantially more freedom.


I would say wait for a sale, but easy for me to say since I already have my deck since over a year ago. If you’re strapped for cash or just working within a budget for the year, then yeah you can easily save at least 50 or more bucks on one. If money isn’t really an object and you got upcoming travel plans where you can capitalize on the steam deck’s mobility, then it’s worth it at current price too. I have easily spent over a grand on the steam deck from the actual unit (512 version at 650), 2tb SSD, 1tb SD card, case, dock, skins, back pad accessories, 1tb usb flash drive with usb c/usb a, etc.

So all to say, if you like tinkering/making it your own, and are trying not to blow out your budget entirely, may be worth to save. I am glad I got the anti glare screen as I’m still not up for replacing the screen myself, but if the lowest model had the same screen, would have gotten that one and just swapped the SSD.


I had a similar issue with my Apple TV and projector. I switched the HDMI cord, and haven’t had the noise since (that I can recall). Try that route first if you have another HDMI cord. If that doesn’t solve it, then not sure honestly.


Most likely that. Assuming they want to find a way to prevent the boot manager from getting borked on updates for both sides of the fence. If they roll it out half-baked they’ll probably get flooded with tech tickets which would eat bandwidth for other issues. Basically preventing them from getting dragged down the support rabbit hole. In current state, if you muck up your install it’s on you to fix/troubleshoot.

For those that are more familiar with this process like you and me, it’s not a real hassle. But when you push out a new “feature”, they have to resolve for the lowest common denominator, which would consist of the more “casual” users. Bearing that in mind, you can probably see why they want to flesh it out a bit more.


Although not a direct answer, just wanted to give my experience.

Originally used a dedicated SD card for Windows, it worked fine but was warned that the constant read/write on the card could cause it to fail quicker than its normal lifespan. Since I didn’t want to fiddle with it in another year or two, I ended up getting a bigger internal drive (2tb nvme) and dedicated 1tb to SteamOS and the other TB to windows. Then have a 1tb SD card for the majority of games on my SteamOS side of the house.

I personally use a custom windows 10 install for that side, which helps prevent Windows from overriding the REFInd boot. However I did notice that when I updated SteamOS to the main branch, it borked REFInd and had to select SteamOS boot file through the file manager on boot, then reinstall REFInd via the normal script on desktop mode.

Just some considerations for you as your journey through your dual boot adventure.