JesterEE Posted May 2 Share Posted May 2 Quick little pro-tip for forum posterity. I force updated the LaaC image today because I was doing some system maintenance (don't ask, I didn't need to do it, but I did), and afterward I was getting this error in the LaaC docker log on container start: ERROR: no device matches available drivers and selection criteria Thinking I messed the image up, I deleted my template and reinstalled from Community Apps, though I was met with the same error. The device was still recognized on the host in the /sys/bus/usb/devices/X-Y and /dev/bus/usb/XXX/YYY locations (I use the former in my template) so it wasn't an availability issue. On a lark, I thought that the device might not have been let go correctly by docker when I force updated the image and the device is now bound to an invalid endpoint (or something like that). So I stopped the running LaaC container, and ran these commands in a su terminal: echo 'X-Y' | tee /sys/bus/usb/drivers/usb/unbind echo 'X-Y' | tee /sys/bus/usb/drivers/usb/bind Upon restarting the LaaC container, my Corsair Commander was once again able to be seen by liquidctl. Hope this helps someone in the future! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.