Open normanr opened 4 years ago
Hi @normanr If this is for a blink(1) mk1 (the one the with silver top and a single LED), then it may be an issue with the mk1. If you'd like a blink(1) mk3 to test with, send us an email at blink1 at thingm.com with your shipping address and we'll mail one off to you at no cost.
Thank you for the offer. I've sent you an email.
I've received the mk3, and the issue reported also applies to it too.
It seems that this is a 'well known' issue, eg: https://skyboo.net/2018/10/binding-unbinding-usb-drivers-a-k-a-who-stole-my-hidraw1-device-file/. I can't figure out if it's libusb or the kernel usb driver that's unbinding the hidraw driver, but I don't think it matters too much. I think it's still worth calling out in the 2.1.0 release notes where hidraw
is mentioned.
I thought that the 2.1.0 release can't find mk1 devices:
The 2.0.5 release shows it fine:
but if I re-plug the device then the 2.1.0 release works fine:
The device appears as:
but after running the v2.0.5 binary (nothing extra appears in dmesg):
Re-plugging the device is fine if you have one or two of them, not if you have many. Luckily it looks like the device can be re-bound to re-create the hidraw devices:
I assume there's not much the blink1-tool could do about this (particularly if running as a non-root user), but the documentation could call this out, and maybe the
no blink(1) devices found
error message could be updated to suggest running the above command (the hard part is figuring out the device id to rebind)?