Lenovo Legion Go 2 Gyro / IMU sensor regression on SteamOS Beta (July 29 update)

Your system information

• Steam client version (build number or date): Latest Beta Client Preview
• Distribution (e.g. Ubuntu): SteamOS (Holo)
• Opted into Steam client beta?: Yes
• Have you checked for system updates?: Yes
• Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
• GPU: Lenovo Legion Go 2 AMD (Integrated / Handheld APU)

Please describe your issue in as much detail as possible:

After updating to the latest SteamOS Beta branch, internal hardware gyro/IMU sensors fail to register any movement on the Lenovo Legion Go 2, resulting in flat 0.0°/S values during Steam Controller calibration. While InputPlumber runs and the service shows active, IIO motion sensor nodes fail to bind to active target devices, leaving only standard keyboard, mouse, and deck targets.

Expected behavior: Gyro data should automatically map to the virtual controller target and allow normal motion control functionality.
Actual behavior: Gyro input is completely unresponsive due to a broken or altered kernel-level sensor path / IIO device node exposure in the current beta build.

Steps for reproducing this issue:

1. Opt into the SteamOS Beta update channel on a Lenovo Legion Go 2.
2. Navigate to Controller Settings -> Gyro Calibration.
3. Observe that pitch, roll, and yaw values remain unresponsive at 0.0°/S because the underlying motion sensor hardware nodes are not binding.

Start with the SteamOS Beta update and the InputPlumber service while reproducing the issue on a Lenovo Legion Go 2. Inspect whether the IIO motion sensor nodes bind to active target devices, and compare the available targets with the gyro calibration screen. Done means pitch, roll, and yaw respond instead of remaining at 0.0°/S and gyro data maps to the virtual controller target.