Skip to content

Instantly share code, notes, and snippets.

@Kethen

Kethen/readme.md

Last active November 1, 2024 19:53
Show Gist options
  • Save Kethen/698cfa8cf387e131ebd36fbfbfe9272e to your computer and use it in GitHub Desktop.
Save Kethen/698cfa8cf387e131ebd36fbfbfe9272e to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. Kethen revised this gist Mar 7, 2022. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -280,8 +280,8 @@ $ sudo pacman -S extra/mesa extra/vulkan-intel multilib/lib32-mesa multilib/lib3
    Now you can revert boot to Plasma and boot into gamescope steam


    ### Gamescope steam resolution
    Look for `-w 1280 -h 800` in `/usr/bin/gamescope-session`, it is a bit finicky but you can probably change your resolution there. If that does not work, you can force scale it with `-W <screen width> -H <screen height>`
    ### Gamescope Steam resolution
    Look for `-w 1280 -h 800` in `/usr/bin/gamescope-session`, it is a bit finicky but you can probably change your resolution there changing it to `-w <screen width> -h <screen height>`. If that does not work, you can force scale it with `-W <screen width> -H <screen height>`

    If scaling is involved, you might want to remove `--max-scale 2`

  2. Kethen revised this gist Mar 7, 2022. 1 changed file with 6 additions and 0 deletions.
    6 changes: 6 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -279,6 +279,12 @@ $ sudo pacman -S extra/mesa extra/vulkan-intel multilib/lib32-mesa multilib/lib3

    Now you can revert boot to Plasma and boot into gamescope steam


    ### Gamescope steam resolution
    Look for `-w 1280 -h 800` in `/usr/bin/gamescope-session`, it is a bit finicky but you can probably change your resolution there. If that does not work, you can force scale it with `-W <screen width> -H <screen height>`

    If scaling is involved, you might want to remove `--max-scale 2`

    ### Enable ssh connection

    First read the boot to Plasma section, or go to desktop mode from Steam, then fire up konsole
  3. Kethen revised this gist Mar 7, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -236,7 +236,7 @@ $ sudo mount -o remount,rw /
    $ sudo btrfs property set -t subvol / ro false
    ```

    #### NOTE THAT UPDATES REMOVE ALL MODIFICATIONS INVOLVING PACKAGES
    #### NOTE THAT UPDATES REMOVE ALL MODIFICATIONS INVOLVING PACKAGES/ROOTFS, YOU WILL HAVE TO REDO THEM AFTER UPDATE

    ### Plasma orientation

  4. Kethen revised this gist Mar 7, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -236,7 +236,7 @@ $ sudo mount -o remount,rw /
    $ sudo btrfs property set -t subvol / ro false
    ```

    #### NOTE THAT UPDATES REMOVE ALL MODIFICATIONS
    #### NOTE THAT UPDATES REMOVE ALL MODIFICATIONS INVOLVING PACKAGES

    ### Plasma orientation

  5. Kethen revised this gist Mar 6, 2022. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -4,6 +4,8 @@ https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3

    SteamOS runs a custom grub to cater it's needs for it's A/B partition design. So far the said custom grub does not boot for me on ovmf/intel uefi (maybe it boots on amd? some said they managed to just rufus the image and boot it)

    skip to https://gist.github.com/Kethen/698cfa8cf387e131ebd36fbfbfe9272e#gamescope-and-non-amd-gpu if it just boots for you

    Upon closer inspection the official bootloader does load some kind of amd firmware before booting the kernel

    Let's boot it anyway with our own grub with the following template grub config. One way to utilize this config is to prepare a livecd of fedora, then swap out the grub config with the template
  6. Kethen revised this gist Mar 6, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -2,7 +2,7 @@

    https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3

    SteamOS runs a custom grub to cater it's needs for it's A/B partition design. So far the said custom grub does not boot on ovmf/intel uefi (maybe it boots on amd? some said they managed to just rufus the image and boot it)
    SteamOS runs a custom grub to cater it's needs for it's A/B partition design. So far the said custom grub does not boot for me on ovmf/intel uefi (maybe it boots on amd? some said they managed to just rufus the image and boot it)

    Upon closer inspection the official bootloader does load some kind of amd firmware before booting the kernel

  7. Kethen revised this gist Mar 6, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -106,7 +106,7 @@ Now boot using the `SteamOS Installer` entry. If that does not work and a recove
    ```
    Then mount the partition labeled efi-A, then let the boot process continue
    ```
    # sudo mount -o ro /dev/sdc2 /var/mnt
    # mount -o ro /dev/sdc2 /var/mnt
    # exit
    ```

  8. Kethen revised this gist Mar 6, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -296,7 +296,7 @@ $ ssh deck@steam_deck_ip_address

    ### Intel GPU (i915) with buggy wayland

    There's a chance that it can still start gamescope under xorg, to do so, after installing the install drivers and downgrading gamescope, first install the xorg drivers for intel
    If downgrading game scope and adding intel mesa did not work, there's a chance that it can still start gamescope under xorg. To do so, first install xorg drivers for intel

    ```
    $ sudo pacman -S xf86-video-intel
  9. Kethen revised this gist Mar 6, 2022. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -16,6 +16,7 @@ Or just wait for the official release to drop, it's a bit of a tinker, and you c
    ![image](https://user-images.githubusercontent.com/22017945/156887722-02b218ce-d971-4714-9a17-8aa1d4857701.png)
    ![image](https://user-images.githubusercontent.com/22017945/156887966-4e56e95b-f22d-4db2-8226-4d9134387fa7.png)
    ![image](https://user-images.githubusercontent.com/22017945/156889714-83b8b246-b853-489b-83f8-b656a2ce0afc.png)
    ![image](https://user-images.githubusercontent.com/22017945/156917337-952222b0-91ab-46bf-9944-118b79209dcc.png)



  10. Kethen revised this gist Mar 6, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -183,7 +183,7 @@ Now the `SteamOS A` entry should boot into SteamOS. However, please read the nex

    Successfully booting into SteamOS UI, once internet connection is configured, it'll attempt an update. The update will be installed onto B if you're booting A, vice versa. Once an update happen, STEAMOS_ROOT_A or STEAM_ROOT_B has to be updated in grub before booting. Updates will also appear to have failed. Disregard the failure, update the ROOTFS uuid and boot it.

    The rule of thumb is to boot STEAMOS_ROOT_B after updating from STEAMOS_ROOT_A, and vice versa. Updates are installed to the alternative root partition.
    The rule of thumb is to update STEAMOS_ROOT_B in grub then boot B after updating from STEAMOS_ROOT_A, and vice versa. Updates are installed to the alternative root partition.

    ### Gamescope and non AMD GPU

  11. Kethen revised this gist Mar 6, 2022. 1 changed file with 12 additions and 0 deletions.
    12 changes: 12 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -18,6 +18,7 @@ Or just wait for the official release to drop, it's a bit of a tinker, and you c
    ![image](https://user-images.githubusercontent.com/22017945/156889714-83b8b246-b853-489b-83f8-b656a2ce0afc.png)



    ```
    set default="0"
    @@ -310,11 +311,22 @@ Then set sddm to launch the xorg session by changing `/etc/sddm.conf.d/steamos.c
    Session=gamescope-xorg.desktop
    ...
    ```
    Change gamescope-wayland.desktop to gamescope-xorg.desktop in `/usr/bin/steamos-session-select`
    ```
    ...
    gamescope)
    #session_launcher="gamescope-wayland.desktop"
    session_launcher="gamescope-xorg.desktop"
    ;;
    ...
    ```

    There's a chance that such hardware is really slow, so change `/usr/bin/gamescope-session` so that it does not fail launching
    ```
    ...
    gamescope -w ...
    gamescope_pid="$!"
    sleep 5
    if read -r -t 3 response_x_display response_wl_display <> "$socket"; then
    ...
    ```
  12. Kethen revised this gist Mar 5, 2022. 1 changed file with 9 additions and 1 deletion.
    10 changes: 9 additions & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -303,10 +303,18 @@ After that make a xorg session from the wayland session
    ```
    $ sudo cp /usr/share/wayland-sessions/gamescope-wayland.desktop /usr/share/xsessions/gamescope-xorg.desktop
    ```
    Then set sddm to launch the xorg session by changing /etc/sddm.conf.d/steamos.conf
    Then set sddm to launch the xorg session by changing `/etc/sddm.conf.d/steamos.conf`
    ```
    ...
    #Session=gamescope-wayland.desktop
    Session=gamescope-xorg.desktop
    ...
    ```
    There's a chance that such hardware is really slow, so change `/usr/bin/gamescope-session` so that it does not fail launching
    ```
    ...
    gamescope -w ...
    gamescope_pid="$!"
    sleep 5
    if read -r -t 3 response_x_display response_wl_display <> "$socket"; then
    ```
  13. Kethen revised this gist Mar 5, 2022. 1 changed file with 19 additions and 0 deletions.
    19 changes: 19 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -290,4 +290,23 @@ $ passwd
    On another machine
    ```
    $ ssh deck@steam_deck_ip_address
    ```

    ### Intel GPU (i915) with buggy wayland

    There's a chance that it can still start gamescope under xorg, to do so, after installing the install drivers and downgrading gamescope, first install the xorg drivers for intel

    ```
    $ sudo pacman -S xf86-video-intel
    ```
    After that make a xorg session from the wayland session
    ```
    $ sudo cp /usr/share/wayland-sessions/gamescope-wayland.desktop /usr/share/xsessions/gamescope-xorg.desktop
    ```
    Then set sddm to launch the xorg session by changing /etc/sddm.conf.d/steamos.conf
    ```
    ...
    #Session=gamescope-wayland.desktop
    Session=gamescope-xorg.desktop
    ...
    ```
  14. Kethen revised this gist Mar 5, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -270,7 +270,7 @@ SigLevel = Never
    Then downgrade gamescope and install Intel mesa

    ```
    $ pacman -S extra/mesa extra/vulkan-intel multilib/lib32-mesa multilib/lib32-vulkan-intel holo/gamescope
    $ sudo pacman -S extra/mesa extra/vulkan-intel multilib/lib32-mesa multilib/lib32-vulkan-intel holo/gamescope
    ```

    Now you can revert boot to Plasma and boot into gamescope steam
  15. Kethen revised this gist Mar 5, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -270,7 +270,7 @@ SigLevel = Never
    Then downgrade gamescope and install Intel mesa

    ```
    pacman -S extra/mesa extra/vulkan-intel multilib/lib32-mesa multilib/lib32-vulkan-intel holo/gamescope
    $ pacman -S extra/mesa extra/vulkan-intel multilib/lib32-mesa multilib/lib32-vulkan-intel holo/gamescope
    ```

    Now you can revert boot to Plasma and boot into gamescope steam
  16. Kethen revised this gist Mar 5, 2022. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -277,12 +277,12 @@ Now you can revert boot to Plasma and boot into gamescope steam

    ### Enable ssh connection

    First read the boot to plasma section, then fire up konsole
    First read the boot to Plasma section, or go to desktop mode from Steam, then fire up konsole
    ```
    $ sudo systemctl enable sshd
    ```

    The deck user needs a password for remote login
    The deck user needs a password for remote login, as well as sudo
    ```
    $ passwd
    ```
  17. Kethen revised this gist Mar 5, 2022. 1 changed file with 6 additions and 6 deletions.
    12 changes: 6 additions & 6 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    ### Booting the steam deck recovery image
    ### Booting the Steam Deck recovery image

    https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3

    @@ -10,7 +10,7 @@ Let's boot it anyway with our own grub with the following template grub config.

    Or just wait for the official release to drop, it's a bit of a tinker, and you can lose data if you do something wrong

    #### DO NOT BOTHER ANYONE AT VALVE FOR ANYTHING BREAKING, THEY MADE IT CLEAR THAT THE RECOVERY IMAGE IS ONLY FOR STEAMDECK
    #### DO NOT BOTHER ANYONE AT VALVE FOR ANYTHING BREAKING, THEY MADE IT CLEAR THAT THE RECOVERY IMAGE IS ONLY FOR STEAM DECK

    ![image](https://user-images.githubusercontent.com/22017945/156887392-d94aaead-f160-4a49-bff8-7f8fdbd1d8a3.png)
    ![image](https://user-images.githubusercontent.com/22017945/156887722-02b218ce-d971-4714-9a17-8aa1d4857701.png)
    @@ -108,9 +108,9 @@ Then mount the partition labeled efi-A, then let the boot process continue
    # exit
    ```

    Once booted into the recovery image, you'll get a KDE plasma desktop
    Once booted into the recovery image, you'll get a KDE Plasma desktop

    ### Imaging steam os using the recovery image
    ### Imaging SteamOS using the recovery image

    Now we can use the official repair script to image steamos onto another drive

    @@ -195,7 +195,7 @@ Gamescope currently has issues with Intel GPUs due to driver problems. You'll ha

    Gamescope currently does not work on Nvidia propietary drivers, see https://github.com/Plagman/gamescope/issues/151

    Read the following sections regarding modifying the rootfs partition, as well as booting directly into plasma instead of Steam
    Read the following sections regarding modifying the rootfs partition, as well as booting directly into Plasma instead of Steam


    ### Boot to Plasma, modifying rootfs partitions
    @@ -273,7 +273,7 @@ Then downgrade gamescope and install Intel mesa
    pacman -S extra/mesa extra/vulkan-intel multilib/lib32-mesa multilib/lib32-vulkan-intel holo/gamescope
    ```

    Now you can revert boot to plasma and boot into gamescope steam
    Now you can revert boot to Plasma and boot into gamescope steam

    ### Enable ssh connection

  18. Kethen revised this gist Mar 5, 2022. 1 changed file with 3 additions and 2 deletions.
    5 changes: 3 additions & 2 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -197,9 +197,10 @@ Gamescope currently does not work on Nvidia propietary drivers, see https://gith

    Read the following sections regarding modifying the rootfs partition, as well as booting directly into plasma instead of Steam

    ### Boot to plasma, modifying rootfs partition

    To boot directly to plasma, you'll have to modify the SteamOS install from another linux install. The SteamOS recovery image will do just fine for that
    ### Boot to Plasma, modifying rootfs partitions

    To boot directly to Plasma, you'll have to modify the SteamOS install from another linux install. The SteamOS recovery image will do just fine for that

    First mount the rootfs you would like to boot to writable, for example, rootfs-A

  19. Kethen revised this gist Mar 5, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -191,7 +191,7 @@ https://github.com/Plagman/gamescope

    If gamescope cannot start, one would just get a black screen

    Gamescope currently has issues with Intel GPUs due to driver problems. You'll have to install older mesa packages and downgrade gamescope.
    Gamescope currently has issues with Intel GPUs due to driver problems. You'll have to install older mesa packages and downgrade gamescope. See https://github.com/Plagman/gamescope/issues/392

    Gamescope currently does not work on Nvidia propietary drivers, see https://github.com/Plagman/gamescope/issues/151

  20. Kethen revised this gist Mar 5, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -182,7 +182,7 @@ Now the `SteamOS A` entry should boot into SteamOS. However, please read the nex

    Successfully booting into SteamOS UI, once internet connection is configured, it'll attempt an update. The update will be installed onto B if you're booting A, vice versa. Once an update happen, STEAMOS_ROOT_A or STEAM_ROOT_B has to be updated in grub before booting. Updates will also appear to have failed. Disregard the failure, update the ROOTFS uuid and boot it.

    The rule of thumb is to update STEAMOS_ROOT_B after updating from STEAMOS_ROOT_A, and vice versa. Updates are installed to the alternative root partition.
    The rule of thumb is to boot STEAMOS_ROOT_B after updating from STEAMOS_ROOT_A, and vice versa. Updates are installed to the alternative root partition.

    ### Gamescope and non AMD GPU

  21. Kethen revised this gist Mar 5, 2022. 1 changed file with 1 addition and 2 deletions.
    3 changes: 1 addition & 2 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -15,8 +15,7 @@ Or just wait for the official release to drop, it's a bit of a tinker, and you c
    ![image](https://user-images.githubusercontent.com/22017945/156887392-d94aaead-f160-4a49-bff8-7f8fdbd1d8a3.png)
    ![image](https://user-images.githubusercontent.com/22017945/156887722-02b218ce-d971-4714-9a17-8aa1d4857701.png)
    ![image](https://user-images.githubusercontent.com/22017945/156887966-4e56e95b-f22d-4db2-8226-4d9134387fa7.png)
    ![image](https://user-images.githubusercontent.com/22017945/156889645-550d334e-5179-4f11-81fd-be54aa37def4.png)

    ![image](https://user-images.githubusercontent.com/22017945/156889714-83b8b246-b853-489b-83f8-b656a2ce0afc.png)


    ```
  22. Kethen revised this gist Mar 5, 2022. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -15,6 +15,8 @@ Or just wait for the official release to drop, it's a bit of a tinker, and you c
    ![image](https://user-images.githubusercontent.com/22017945/156887392-d94aaead-f160-4a49-bff8-7f8fdbd1d8a3.png)
    ![image](https://user-images.githubusercontent.com/22017945/156887722-02b218ce-d971-4714-9a17-8aa1d4857701.png)
    ![image](https://user-images.githubusercontent.com/22017945/156887966-4e56e95b-f22d-4db2-8226-4d9134387fa7.png)
    ![image](https://user-images.githubusercontent.com/22017945/156889645-550d334e-5179-4f11-81fd-be54aa37def4.png)



    ```
  23. Kethen revised this gist Mar 5, 2022. 1 changed file with 5 additions and 0 deletions.
    5 changes: 5 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -185,6 +185,11 @@ The rule of thumb is to update STEAMOS_ROOT_B after updating from STEAMOS_ROOT_A

    ### Gamescope and non AMD GPU

    Gamescope is used as a compositor in game console UI
    https://github.com/Plagman/gamescope

    If gamescope cannot start, one would just get a black screen

    Gamescope currently has issues with Intel GPUs due to driver problems. You'll have to install older mesa packages and downgrade gamescope.

    Gamescope currently does not work on Nvidia propietary drivers, see https://github.com/Plagman/gamescope/issues/151
  24. Kethen revised this gist Mar 5, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -8,7 +8,7 @@ Upon closer inspection the official bootloader does load some kind of amd firmwa

    Let's boot it anyway with our own grub with the following template grub config. One way to utilize this config is to prepare a livecd of fedora, then swap out the grub config with the template

    Or just wait for the official release to drop, it's a bit of a tinker, and you can loose data if you do something wrong
    Or just wait for the official release to drop, it's a bit of a tinker, and you can lose data if you do something wrong

    #### DO NOT BOTHER ANYONE AT VALVE FOR ANYTHING BREAKING, THEY MADE IT CLEAR THAT THE RECOVERY IMAGE IS ONLY FOR STEAMDECK

  25. Kethen revised this gist Mar 5, 2022. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -14,6 +14,8 @@ Or just wait for the official release to drop, it's a bit of a tinker, and you c

    ![image](https://user-images.githubusercontent.com/22017945/156887392-d94aaead-f160-4a49-bff8-7f8fdbd1d8a3.png)
    ![image](https://user-images.githubusercontent.com/22017945/156887722-02b218ce-d971-4714-9a17-8aa1d4857701.png)
    ![image](https://user-images.githubusercontent.com/22017945/156887966-4e56e95b-f22d-4db2-8226-4d9134387fa7.png)


    ```
    set default="0"
  26. Kethen revised this gist Mar 5, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -13,7 +13,7 @@ Or just wait for the official release to drop, it's a bit of a tinker, and you c
    #### DO NOT BOTHER ANYONE AT VALVE FOR ANYTHING BREAKING, THEY MADE IT CLEAR THAT THE RECOVERY IMAGE IS ONLY FOR STEAMDECK

    ![image](https://user-images.githubusercontent.com/22017945/156887392-d94aaead-f160-4a49-bff8-7f8fdbd1d8a3.png)

    ![image](https://user-images.githubusercontent.com/22017945/156887722-02b218ce-d971-4714-9a17-8aa1d4857701.png)

    ```
    set default="0"
  27. Kethen revised this gist Mar 5, 2022. 1 changed file with 3 additions and 0 deletions.
    3 changes: 3 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -12,6 +12,9 @@ Or just wait for the official release to drop, it's a bit of a tinker, and you c

    #### DO NOT BOTHER ANYONE AT VALVE FOR ANYTHING BREAKING, THEY MADE IT CLEAR THAT THE RECOVERY IMAGE IS ONLY FOR STEAMDECK

    ![image](https://user-images.githubusercontent.com/22017945/156887392-d94aaead-f160-4a49-bff8-7f8fdbd1d8a3.png)


    ```
    set default="0"
  28. Kethen revised this gist Mar 5, 2022. 1 changed file with 5 additions and 0 deletions.
    5 changes: 5 additions & 0 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -273,4 +273,9 @@ $ sudo systemctl enable sshd
    The deck user needs a password for remote login
    ```
    $ passwd
    ```

    On another machine
    ```
    $ ssh deck@steam_deck_ip_address
    ```
  29. Kethen revised this gist Mar 5, 2022. 1 changed file with 5 additions and 3 deletions.
    8 changes: 5 additions & 3 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -4,6 +4,8 @@ https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3

    SteamOS runs a custom grub to cater it's needs for it's A/B partition design. So far the said custom grub does not boot on ovmf/intel uefi (maybe it boots on amd? some said they managed to just rufus the image and boot it)

    Upon closer inspection the official bootloader does load some kind of amd firmware before booting the kernel

    Let's boot it anyway with our own grub with the following template grub config. One way to utilize this config is to prepare a livecd of fedora, then swap out the grub config with the template

    Or just wait for the official release to drop, it's a bit of a tinker, and you can loose data if you do something wrong
    @@ -117,7 +119,7 @@ DISK_SUFFIX=p

    The above section was intended for imaging SteamOS onto /dev/nvme0n1, with partitions named /dev/nvme0n1p1, /dev/nvme0n1p2...

    First of all, check `sudo blkid` and `lsblk`
    First of all, check `sudo blkid` and `lsblk` to locate your drive

    If you plan to image on your first nvme device, you can likely keep that section unchanged.

    @@ -153,7 +155,7 @@ $ sudo blkid | grep sdb | sort
    /dev/sdb8: LABEL="home" UUID="40adf72c-90f7-43fb-8f2f-982bdacbd546" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="home" PARTUUID="704e1316-750c-3848-b020-13fd563b655e"
    ```

    You'll have to update the grub config template to cater the UUID. Look for the partition labeled `rootfs-A` on the disk, copy the UUID field
    You'll have to update the grub config template to the radom UUID. Look for the partition labeled `rootfs-A` on the disk, copy the UUID field

    ```
    ...
    @@ -174,7 +176,7 @@ Now the `SteamOS A` entry should boot into SteamOS. However, please read the nex

    Successfully booting into SteamOS UI, once internet connection is configured, it'll attempt an update. The update will be installed onto B if you're booting A, vice versa. Once an update happen, STEAMOS_ROOT_A or STEAM_ROOT_B has to be updated in grub before booting. Updates will also appear to have failed. Disregard the failure, update the ROOTFS uuid and boot it.

    The rule of thumb is to update STEAMOS_ROOT_B after updating from STEAMOS_ROOT_A, and vice versa. Updates installs to the alternative root partition.
    The rule of thumb is to update STEAMOS_ROOT_B after updating from STEAMOS_ROOT_A, and vice versa. Updates are installed to the alternative root partition.

    ### Gamescope and non AMD GPU

  30. Kethen revised this gist Mar 5, 2022. 1 changed file with 19 additions and 5 deletions.
    24 changes: 19 additions & 5 deletions readme.md
    View file
    Original file line number Diff line number Diff line change
    @@ -4,9 +4,9 @@ https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3

    SteamOS runs a custom grub to cater it's needs for it's A/B partition design. So far the said custom grub does not boot on ovmf/intel uefi (maybe it boots on amd? some said they managed to just rufus the image and boot it)

    Let's boot it anyway with our own grub with the following template grub config. one way to utilize this config is to prepare a livecd of fedora, then swap out the grub config with the template
    Let's boot it anyway with our own grub with the following template grub config. One way to utilize this config is to prepare a livecd of fedora, then swap out the grub config with the template

    or just wait for the official release to drop, it's a bit of a tinker, and you can loose data if you do something wrong
    Or just wait for the official release to drop, it's a bit of a tinker, and you can loose data if you do something wrong

    #### DO NOT BOTHER ANYONE AT VALVE FOR ANYTHING BREAKING, THEY MADE IT CLEAR THAT THE RECOVERY IMAGE IS ONLY FOR STEAMDECK

    @@ -61,7 +61,7 @@ menuentry 'SteamOS installer' {
    initrdefi /boot/initramfs-linux-neptune.img
    }
    ```
    ### booting the recovery image itself
    ### Booting the recovery image itself

    During SteamOS boot process, a uuid partition map is loaded from it's EFI partition. The said partition has to be supplied by boot arg `rd.steamos.efi=`

    @@ -172,7 +172,9 @@ Now the `SteamOS A` entry should boot into SteamOS. However, please read the nex

    ### Updates

    Successfully booting into SteamOS UI, once internet connection is configured, it'll attempt an update. The update will be installed onto B if you're booting A, vice versa. Once an update happen, STEAMOS_ROOT_A or STEAM_ROOT_B has to be updated in grub before booting. Updates will also appear to have failed.
    Successfully booting into SteamOS UI, once internet connection is configured, it'll attempt an update. The update will be installed onto B if you're booting A, vice versa. Once an update happen, STEAMOS_ROOT_A or STEAM_ROOT_B has to be updated in grub before booting. Updates will also appear to have failed. Disregard the failure, update the ROOTFS uuid and boot it.

    The rule of thumb is to update STEAMOS_ROOT_B after updating from STEAMOS_ROOT_A, and vice versa. Updates installs to the alternative root partition.

    ### Gamescope and non AMD GPU

    @@ -257,4 +259,16 @@ Then downgrade gamescope and install Intel mesa
    pacman -S extra/mesa extra/vulkan-intel multilib/lib32-mesa multilib/lib32-vulkan-intel holo/gamescope
    ```

    Now you can revert boot to plasma and boot into gamescope steam
    Now you can revert boot to plasma and boot into gamescope steam

    ### Enable ssh connection

    First read the boot to plasma section, then fire up konsole
    ```
    $ sudo systemctl enable sshd
    ```

    The deck user needs a password for remote login
    ```
    $ passwd
    ```