T19:57:56.205157Z INFO permission_broker: DenċlaimedUsbDeviceRule: DENY T19:57:56.176615Z INFO permission_broker: Found claimed interface with driver: cdc_acm T19:57:56.176138Z INFO permission_broker: Found claimed interface with driver: cdc_acm T19:57:56.174006Z INFO permission_broker: AllowTtyDeviceRule: IGNORE T19:57:56.173914Z INFO permission_broker: AllowUsbDeviceRule: ALLOW T19:57:55.843935Z INFO kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 T19:57:55.678800Z INFO kernel: usb 1-2: new full-speed USB device number 12 using xhci_hcd So, digging around I found where ChromeOS seems to print its own logs (separate from the Linux container, its own /var/log/messages), and this is what it prints out when the Teensy is connected: And as I said, the Teensy doesn't even show up there a valid device. I suspect that the issue is at the ChromeOS level since there is a setting for the Linux container to allow usb devices. ![]() Yes, I did install the udev rules, and when the Teensyduino installer ran in the linux container, it found them successfully installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |