I upgraded two devices from balenaOS 2.29.0+rev1 to balenaOS 2.38.3+rev4 and now my USB serial adapter is no longer detected.
A USB device is detected but the USB tree does no longer show the ttyUSB endpoint.
Did you remove any drivers? Changes to the udev system?
When I plugin the USB device on a device with the old BalenaOS, dmesg says:
[22067.664660] usb 1-7: new full-speed USB device number 7 using xhci_hcd
[22067.791853] ch341 1-7:1.0: ch341-uart converter detected
[22067.792125] usb 1-7: ch341-uart converter now attached to ttyUSB1
But when I plugin the USB device on a device with the new BalenaOS, dmesg says:
[ 966.292273] usb 1-7: new full-speed USB device number 5 using xhci_hcd
And I can’t downgrade the BalenaOS! Ouchh!
So do I have to backup the persistent data, reinstall, and restore persistent data, transfer all Balena settings from the old to the new device and delete the old device and … ???
Thanks for this information. Also, can you share the device type you’re using? Not the USB dongle, but if the main device is RPi 3, Intel NUC, Odroid, … Thanks!
It seems that the issue with this kernel module cannot be blamed on the Balena folks.
It turns out that our system worked with balenaOS 2.29.0+rev1 only because we ourselves had compiled the kernel module for our USB device.
So when we updated to balenaOS 2.38.3+rev4, the compiled module did no longer match the kernel.
And I wrongly assumed the balenaOS 2.38.3+rev4 had a regression that broke our system. Sorry about that, and thanks for the support.