Some USB device no longer detected #3839
Comments
|
Same issue here. Using ODROID M1. 2 of 4 USB-Ports are not working anymore. |
|
@jacknife71 Unfortunately, I can confirm that. It's probably unrelated to the original issue, because there is no kernel message at all when a device is plugged into the USB 3 (blue) ports. It seems to be a stable kernel regression because otherwise nothing much have changed between the version. I have created another issue to track it and will have a closer look. Thanks for reporting the issue and sorry for the inconvenience. The best workaround would be to downgrade to 14.1 ( |
|
@GraemeDBlue Does reverting to 14.1 (using the commands from the previous comment) fix the issue? Have you tried whether a cold boot (unplugging the PC for a while) doesn't fix it? If not, could you please post the complete host logs when it doesn't work? |
|
Downgrade to 14.1 works. |
|
@sairon unfortunately reverting to 14.1 does not seem to solve the issue for me . Coral is just no longer detected |
|
@sairon actually I lie, it does now work again on 14.1, but against all suggestions "Protection mode" needs to be ON for it to work, which previously it was set to OFF |
|
@sairon bumped to 14.2 with above change and it still works, so unsure how that flag can have been changed to now be opposite to suggested setting for using a Coral |
|
Not sure what's going on there with Frigate, but for the device not appearing in the system, that seems to be a different problem - the device wasn't enumerated by the kernel (returning error 71 = protocol error), something that wouldn't be fixed by toggling the protection mode. Possible reasons are a bad USB cable or interference, bit less likely general problem with the hardware or a kernel regression. |
|
@sairon yep makes no sense, but its still working with the protection mode turned on, really makes no sense at all |
Describe the issue you are experiencing
On Upgrading, my USB Coral device for Frigate running on same Generic x86-64 hardware, as an add on is no longer detected and I see this in the Frigate logs on attempted start of the add on
Unplugging the Coral lets the add on boot again , so my guess is driver for Coral on latest OS update?
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
6.6.73-haos
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
2025-01-28 09:17:52.639 ERROR (MainThread) [asyncio] Task exception was never retrieved future: <Task finished name='Task-14299' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1506> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')> Traceback (most recent call last): File "/usr/src/supervisor/supervisor/addons/addon.py", line 1520, in watchdog_container await self._restart_after_problem(event.state) File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 291, in wrapper raise on_condition( supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00 2025-01-28 09:18:55.126 WARNING (MainThread) [supervisor.docker.addon] Frigate (Full Access) running with disabled protected mode!Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Sonoff
Spotify
Additional information
Frigate Logs: Frigate has not been updated and this worked before OS update
The text was updated successfully, but these errors were encountered: