0 Followers
0 Following
1 Posts

Transferring SSD from LCD to OLED Dual Boot - My Experience

https://lemmy.world/post/8700477

Transferring SSD from LCD to OLED Dual Boot - My Experience - Lemmy.World

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 [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.

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 - emudeck.github.io/…/third-party-emulation/?h=dist…

Hope this helps some stranger out there figure things out

Third Party Emulation (Decompilations and Games) - EmuDeck Wiki

Weird Issue with SteamOS Beta and Distrobox

https://lemmy.world/post/7252268

Weird Issue with SteamOS Beta and Distrobox - Lemmy.World

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