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

Device name etc is not recognized by host until a machine restart #11

Open
skywhale opened this issue Dec 22, 2020 · 1 comment
Open

Comments

@skywhale
Copy link
Member

For the first time I plugged in a panel controller using native USB connection, the device was recognized as a generic USB ACM device. Manufacturer, SerialNumber, and Product name were not communicated during the handshake.

[1927774.628446] usb 11-1: new full-speed USB device number 5 using xhci_hcd
[1927774.797719] usb 11-1: string descriptor 0 read error: -71
[1927774.797724] usb 11-1: New USB device found, idVendor=16c0, idProduct=27dd, bcdDevice= 0.10
[1927774.797726] usb 11-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1927774.992697] cdc_acm 11-1:1.0: ttyACM1: USB ACM device

I unplugged and re-plugged the USB cable, and this time Manufacturer and SerialNumber were communicated but not the Product name, resulting in a by-id path of /dev/serial/by-id/usb-tonari_27dd_tonari-dashboard-controller-v1-if00

[1928282.322129] usb 11-1: USB disconnect, device number 5
[1928284.288426] usb 11-1: new full-speed USB device number 6 using xhci_hcd
[1928284.462846] usb 11-1: New USB device found, idVendor=16c0, idProduct=27dd, bcdDevice= 0.10
[1928284.462849] usb 11-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1928284.462851] usb 11-1: Manufacturer: tonari
[1928284.462853] usb 11-1: SerialNumber: tonari-dashboard-controller-v1

I rebooted the host machine, and all of Manufacturer, SerialNumber and Product name were communicated and the device was recognized as /dev/serial/by-id/usb-tonari_tonari_dashboard_controller_tonari-dashboard-controller-v1-if00

@skywhale
Copy link
Member Author

The exact same thing happened with frontier-tokyo and frontier-osaka, so it was not something specific to a state of a machine.

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