Summary
On a Lenovo Legion Go 2 running SteamOS, after reboot the integrated controllers power on and the RGB lights are active, but the controller buttons do not respond. The right touchpad continues to work.
Restarting inputplumber.service immediately restores the controller buttons.
Device
- Lenovo Legion Go 2 / 8ASP2
- SteamOS 3.8.28
Steps to reproduce
- Reboot the Legion Go 2.
- Wait for Steam Gaming Mode to load.
- The controllers have RGB lighting, but the buttons do not respond.
- The right touchpad still works.
- Run:
sudo systemctl restart inputplumber.service
- The controller buttons immediately start working again.
Controller notifications during startup
Steam shows this sequence:
Xbox One Elite 2 Controller connected
SteamOS Handheld Controller connected
Xbox One Elite 2 Controller disconnected
Workaround
I created a temporary systemd oneshot service that waits 20 seconds after boot and then restarts InputPlumber:
ExecStart=/usr/bin/sleep 20
ExecStart=/usr/bin/systemctl restart inputplumber.service
With this workaround, the integrated controller works correctly after reboot.
Expected behavior
The Legion Go 2 integrated controller should initialize correctly during boot without requiring InputPlumber to be restarted.
Additional information
The issue started after a recent SteamOS/Steam update.
A SteamOS System Report has also been generated and submitted to Valve.
This may be related to #649, where the emulated controller changes back to xbox-elite after reboot.
Summary
On a Lenovo Legion Go 2 running SteamOS, after reboot the integrated controllers power on and the RGB lights are active, but the controller buttons do not respond. The right touchpad continues to work.
Restarting
inputplumber.serviceimmediately restores the controller buttons.Device
Steps to reproduce
sudo systemctl restart inputplumber.service
Controller notifications during startup
Steam shows this sequence:
Xbox One Elite 2 Controller connected
SteamOS Handheld Controller connected
Xbox One Elite 2 Controller disconnected
Workaround
I created a temporary systemd oneshot service that waits 20 seconds after boot and then restarts InputPlumber:
ExecStart=/usr/bin/sleep 20
ExecStart=/usr/bin/systemctl restart inputplumber.service
With this workaround, the integrated controller works correctly after reboot.
Expected behavior
The Legion Go 2 integrated controller should initialize correctly during boot without requiring InputPlumber to be restarted.
Additional information
The issue started after a recent SteamOS/Steam update.
A SteamOS System Report has also been generated and submitted to Valve.
This may be related to #649, where the emulated controller changes back to
xbox-eliteafter reboot.