So far I’ve gotten it to work in desktop mode, but booting to the regular gaming mode kills it.

It didn’t work by simply installing via git as it does on my desktop computer. I’ve followed this video guide so far: https://youtu.be/YVPtVB0DWUg

But either my reading comprehension is failing me or I’m missing something because per the description and comments, the method still works as of last month.

But I noticed in the video that he mentions running a second command in the terminal and potentially having to change the Neptune number (the video was made for 65, but the deck is on 611 now) on that second command to reflect the current version number.

But he doesn’t have the second command listed on that page he links to (https://monroeworld.com/steamdeck/xbox.html), and it’s only partially visible for a moment on the video, so I don’t know what that 2nd command does.

I was able to get the controller to pair just fine, navigate big picture mode with it, started a game, and was able to control the game using the big picture interface, however.

The first command does make the icons for the script he mentions (in the video he says to use the debug version, and that is shown) appear, and I do get the work he shows initially (xone module not loaded or something like that) that he says is normal for the process before you paste the second command in the terminal. But I don’t know what the second command is to finish the process, and I’m assuming that part is the one that gets it working in gaming mode.

I have no issues with the controller or the dongle on my desktop machine, and it works in desktop mode, so I’m sure they’re fine. I’m just missing a step to get it working in gaming mode specifically.

  • Fubarberry@sopuli.xyzMEnglish
    4·
    7 days ago

    But I noticed in the video that he mentions running a second command in the terminal and potentially having to change the Neptune number (the video was made for 65, but the deck is on 611 now) on that second command to reflect the current version number.

    You might want to check the GitHub itself, specifically this issue.

    It has the commands to run to fix kernel mismatch errors during install

    • oopsgodisdeadmybad@lemmy.zipOP
      3·
      5 days ago

      Update: The error on that issue wasn’t the one I had, but the command was the one that ended in Neptune 611, so I did use it.

      Ran the debug install again and no dice.

      Rebooted and reinstalled, then back to gaming mode, and now it’s working. I knew from several mentions that it might take a couple reboots, so even though it felt weird to need to do it more than once, I still did, and it seems to have paid off.

      Now I’ll still have to switch the dongle back and forth from my PC for now (until I get my hands on the new steam controller), but I can live with that.

      Although as soon as I get it paired and working, I see a new steam os update, so I’ll probably need to do it all again anyway. But at least I can trust the process now.

    • oopsgodisdeadmybad@lemmy.zipOP
      2·
      7 days ago

      I didn’t see that. I stepped on my glasses last week and I was using the deck screen itself working on this. I’m using backups from like 15 years ago lol.

      I’ll look at that tonight when I get a moment. Thanks