Closed salamanders closed 4 months ago
if you have a SuzyQ cable/adapter, can connect to the EC console and see what's happening there when the webcam gets plugged in. Or try a USB-C to A adapter and see if it works on a regular USB3 port?
Or try a USB-C to A adapter and see if it works on a regular USB3 port?
It does! I found a USB-C to A cable (blue, so I'm hoping it is USB 3.0), and it worked fine. So it isn't like a short in the camera is suddenly grabbing all the power. TBD if the speed is enough, but the camera runs fine, so the usb A power is sufficient to run the camera. Yay!
If there isn't a standard log file I can upload, I'm guessing this is too rare a condition to be worth chasing down - given that it crashes as soon as I plug in the C-to-C cable, it makes it very hard to diagnose.
given that the only real way to debug it would be with a SuzyQ cable, which also occupies the USB-C port, this would be a difficult issue to debug without a servo debug interface
(Unsure if this would be a firmware issue or not! Might just be damaged hardware)
themachine@chromebox:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Fully up to date with latest 2024-05 firmware script.
Any chance it sees a new thing being plugged in, and says "oh, cool, now I'm getting power from USB-C instead of from the dedicated power barrel plug, I'll switch over" - and then it keels over? It sounds like the fan turns off when I plug in the USB-C cam.