Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB Devices Not Recognized After Reboot on Nightly Community Build #1

Open
egigoka opened this issue May 9, 2024 · 2 comments
Open

Comments

@egigoka
Copy link

egigoka commented May 9, 2024

Issue Description:

After flashing the latest nightly community build, USB devices such as mice and card readers initially work as expected. However, after a system reboot, these USB devices are no longer recognized or functional. This issue persists across multiple reboots and occurs with various types of USB-C to USB adapters, including simple converters, OTG cables, and multi-port docks like the Satechi USB-C travel dock.

Steps to Reproduce:

  1. Flash the latest nightly community build onto the device.
  2. Connect a USB device (e.g., mouse, card reader) using a USB-C to USB adapter.
  3. Verify that the USB device is recognized and functioning correctly.
  4. Reboot the device using systemctl reboot.
  5. After reboot, reconnect the USB device using the same adapter.

Expected Behavior:

USB devices should continue to be recognized and function correctly after a system reboot, just as they do immediately after flashing the build.

Actual Behavior:

After rebooting, the USB devices are no longer recognized. No additional changes or updates were made between the initial flash and after the reboot that could affect USB functionality.

Environment:

  • Nightly Build Version: 20240424
  • Device Model: Xiaomi Redmi Note 9S (global) - miatoll, curtana

Troubleshooting Steps Attempted:

  • Tried multiple USB-C to USB adapters, including:
    • Basic 1-port converters
    • OTG cables
    • Satechi USB-C travel dock
  • Repeated the process with different USB devices and adapters to rule out hardware-specific issues.

Additional Information:

  • No similar issues were observed in the stable builds prior to using the nightly.
  • The initial functionality suggests drivers and hardware are initially compatible.

Issue text was corrected with ChatGPT, English is not my first language, so I think that made it more coherent.

@egigoka
Copy link
Author

egigoka commented May 9, 2024

I'm ready to send any additional information such as logs. Feel free to ask.

@egigoka
Copy link
Author

egigoka commented May 9, 2024

Here's journalctl logs and screenshot of working mouse until first reboot:

journalctl-2024-05-09-10-12-53.log
journalctl-2024-05-09-10-13-06.log
journalctl-2024-05-09-10-19-33.log
mouse-works

@egigoka egigoka closed this as completed May 9, 2024
@egigoka egigoka reopened this May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant