• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle














  • So, major caveat here: I’m a linux gamer and don’t have windows [subsystem for linux] available to test.

    This actually works shockingly well for steam-steam gaming, but I’d call these steps proof-of-concept success versus “finished product”.

    I’ll assume if you’re going this deep, you know how desktop mode works and you’re reasonably comfortable with the terminal. Otherwise, don’t follow random guides on the internet, and you understand that you could break things.

    Obvious prerequisite: enable sudo by creating a password for the deck user

    Enable installing packages via pacman: I borrowed from this guide, but didn’t follow it exactly.

    # disable the deck's read-only mode
    sudo steamos-readonly disable
    # init the pacman keyring
    sudo pacman-key --init
    # populate the keyring with archlinux
    sudo pacman-key --populate archlinux
    

    Install, start, and bind the usbip service on the steamdeck (steps from the “Server” portion of archwiki linked in my original comment above)

    # install usbip
    sudo pacman -S usbip
    # enable/start the usbip daemon
    sudo systemctl enable usbip.service
    sudo systemctl start usbip.service
    # enable the kernel module
    sudo modprobe usbip-host
    # list the available usb devices
    usbip list --local
    # bind the Valve usb device (check the output of the above for the right bus id, mine happens to be 3-3)
    sudo usbip bind --busid=3-3
    

    Install start and attach to the steamdeck (steps from the “Client” portion of archwiki listed above)

    # install usbip
    sudo pacman -Sy usbip
    # enable the requisite kernel module
    sudo modprobe vhci-hcd
    # list the remote devices (use your steam desk's ip address, this assumes you're on the same network and have addressed any firewall/configuration issues)
    usbip list --remote 192.168.88.207
    # attach to it
    sudo usbip attach --remote 192.168.88.207 --busid=3-3
    

    Now you can be shocked when it works instantly. Go play a game!






  • I just went through this decision. I landed on Garuda with Nobara a close second. I was coming from Manjaro which was almost completely stable for the last 3.5 yrs. I was only moving because I picked up a new SSD and wanted to see what else was out there.

    I chose Garuda not because of the better gaming or perf, but for the preconfigured BTRFS with auto snapshots on upgrade and the presence of a distributed team reduces the “bus factor” problem that Nobara has for future updates and support.

    I’ve been caught out a few times from upgrades on rolling distributions, so the simplified approach to rollbacks is greatly appreciated.

    Now for the caveats:

    You won’t get Wayland with Garuda and Nvidia by default (at least with their “stock” dr460gonized edition on KDE). And if you have more than one screen, I’d say that’s probably for the best right now (especially if they vary in resolution, refresh rate, or orientation).

    I’ve found that there’s a few little polish things that leave me a bit wanting, but they’re by no means deal breakers: one of my USB hubs won’t reinitialize after waking from suspend (which worked just fine in Manjaro) and color codes (but not full escape sequences) are printed in terminal applications (eg man journalctl prints 1mDescription0m and the like). They’re both probably issues with the Garuda customizations, so I figure debugging them will help me understand things a bit better.

    If you’re willing/able to hop between distro for a bit, I’d suggest trying at least a couple on for size and seeing how they fit you!