Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Thanks for your time and let me know if I can help troubleshoot further!
I updated the firmware on the controller.
I'm using Beta channel on the Deck.
Hamdog's workaround works for me as well.
This setup was working for me a couple of weeks ago. I was travelling without the controller and discovered this problem when I got home.
will there be fix soon?
or is it already fixed in beta/preview, tested this anybody?
Seems to be in a similar state where you probably can try to turn on the controller before the Steam Deck fully boots and it might work.
One thing I noticed that I think is different is that, say you let the Deck boot up (in my case to the passcode screen) and then turn it on like normal, it doesn't work like before - but if I hold the Xbox button down to turn off the controller and then turn it on again it seems to work normally on the second connection.
I also noticed this behavior when initially pairing it fwiw.
Not sure what's going on but I dont have the issue on my desktop running Arch Linux and I believe the xpadneo dkms driver. Been a while but willing to help test things if we get any assistance. Hope one of these workarounds works for you too in the meantime 👍
However, I don't think SteamOS is using that driver but the fix was in /etc/bluetooth/main.conf config file so I tried that on the Deck but no difference. Different issue anyways.
I started up the OLED and went strait to desktop mode (not connecting the controller in gaming mode, if you do then it might work right away in desktop) and ran "sudo dmesg --follow" and turned on the controller. The logs there seemed OK and the controller was recognized. Then I ran "btmon" to check the Bluetooth, which it recognized button presses and things I think which is great.
The controller was not working on the desktop at all, though.
I then closed steam in desktop mode and reopened it and then the controller started working again on the desktop. So maybe this is more likely an issue with steam or steam input in my opinion. These symptoms are telling me that the controller needs to be connected to the Deck before Steam starts for some reason, but I'm unsure why after it's started that turning the controller off and connecting again will work.
So, to sum up workarounds for others in the meantime:
- Can try to turn on the controller shortly before the Deck boots up.
- Can try to turn the controller off by holding the Xbox button down (after you first turn it on and have no input) and then turn it back on.
- Can try to restart steam itself (after you first turn it on and have no input). I have successfully done this both in desktop mode like mentioned, and also at the PIN screen when booting the deck etc. That requires you to hold down the power button on the deck and select "Restart Steam". At least we know this works, but that's not too great when the deck is docked and you're chilling back.
Hope it helps!