HyperHDR as LXC on Proxmox with HyperSerialPico

[jhofker]

I'm running v21.0.0.0 HyperHDR in an LXC on Proxmox, installed with this script
I have two Pimoroni 2040 Plasmas that I flashed with HyperSerialPico

I can see the devices passed through in the LXC:

root@hyperhdr:~# lsusb
...
Bus 001 Device 006: ID 2e8a:000a Raspberry Pi Pico
Bus 001 Device 007: ID 2e8a:000a Raspberry Pi Pico
...

However, HyperHDR doesn't seem to pick them up:

What device mapping does HyperHDR look for when generating the list of outputs? I feel like I'm missing something relatively simple. Thanks!

[awawa-dev]

Switch to Output to Auto, save it and look into logs. Search for 2e8a:000a. Serial ports are provided by QT libraries.

[jhofker]

Thanks, tried that and I don't see any results for 2e8a:000a in the logs.

I copied them to a gist here: https://gist.github.com/jhofker/a0c1d28154fbbc4147e03d1e26b074be

Current settings:

[awawa-dev]

VID: 0x0, PID: 0x0

unless its a some internal device its invalid, some time ago there was a bug with udev, try to force detection on one of these ports. #561 (reply in thread)

[jhofker]

I unplugged one of the devices to limit what I'm trying to debug at once. Then I selected "Force HyperSerial detection (ignore board ProductId/VendorId)" for the remaining device.

This shows in the logs:

2025-03-12T18:26:50.409Z [LEDDEVICE0_ADALIGHT] Device 'adalight' is disabled due to an error: 'Timeout writing data to ttyACM1'

In the container, dmesg shows:

[3449954.322464] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[3450412.715025] usb 1-1.3: new full-speed USB device number 7 using xhci_hcd
[3450412.825063] usb 1-1.3: New USB device found, idVendor=2e8a, idProduct=000a, bcdDevice= 1.00
[3450412.825074] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[3450412.825076] usb 1-1.3: Product: Pico
[3450412.825078] usb 1-1.3: Manufacturer: Raspberry Pi
[3450412.825080] usb 1-1.3: SerialNumber: E6614104030A4B32
[3450412.842718] cdc_acm 1-1.3:1.0: ttyACM1: USB ACM device

Which is a good sign.

In case it's useful to you or others, I tried to get info with device manager.

From the container (lxc):

root@hyperhdr:~# udevadm info -n /dev/ttyACM1
P: /devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.3/1-1.3:1.0/tty/ttyACM1
M: ttyACM1
R: 1
U: tty
D: c 166:1
N: ttyACM1
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.3/1-1.3:1.0/tty/ttyACM1
E: DEVNAME=/dev/ttyACM1
E: MAJOR=166
E: MINOR=1
E: SUBSYSTEM=tty

From the host:

root@pve-tynan:~# udevadm info -n /dev/ttyACM1
P: /devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.3/1-1.3:1.0/tty/ttyACM1
M: ttyACM1
R: 1
U: tty
D: c 166:1
N: ttyACM1
L: 0
S: serial/by-id/usb-Raspberry_Pi_Pico_E6614104030A4B32-if00
S: serial/by-path/pci-0000:00:15.0-usb-0:1.3:1.0
E: DEVPATH=/devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.3/1-1.3:1.0/tty/ttyACM1
E: DEVNAME=/dev/ttyACM1
E: MAJOR=166
E: MINOR=1
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=3450443569068
E: ID_BUS=usb
E: ID_MODEL=Pico
E: ID_MODEL_ENC=Pico
E: ID_MODEL_ID=000a
E: ID_SERIAL=Raspberry_Pi_Pico_E6614104030A4B32
E: ID_SERIAL_SHORT=E6614104030A4B32
E: ID_VENDOR=Raspberry_Pi
E: ID_VENDOR_ENC=Raspberry\x20Pi
E: ID_VENDOR_ID=2e8a
E: ID_REVISION=0100
E: ID_TYPE=generic
E: ID_USB_MODEL=Pico
E: ID_USB_MODEL_ENC=Pico
E: ID_USB_MODEL_ID=000a
E: ID_USB_SERIAL=Raspberry_Pi_Pico_E6614104030A4B32
E: ID_USB_SERIAL_SHORT=E6614104030A4B32
E: ID_USB_VENDOR=Raspberry_Pi
E: ID_USB_VENDOR_ENC=Raspberry\x20Pi
E: ID_USB_VENDOR_ID=2e8a
E: ID_USB_REVISION=0100
E: ID_USB_TYPE=generic
E: ID_USB_INTERFACES=:020200:0a0000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=cdc_acm
E: ID_USB_CLASS_FROM_DATABASE=Miscellaneous Device
E: ID_USB_PROTOCOL_FROM_DATABASE=Interface Association
E: ID_PATH=pci-0000:00:15.0-usb-0:1.3:1.0
E: ID_PATH_TAG=pci-0000_00_15_0-usb-0_1_3_1_0
E: DEVLINKS=/dev/serial/by-id/usb-Raspberry_Pi_Pico_E6614104030A4B32-if00 /dev/serial/by-path/pci-0000:00:15.0-usb-0:1.3:1>
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

I'm wondering if it could be a permissions issue somehow, given that the host sees more information than the container. I'll keep looking, thank you.

[awawa-dev]

I would try to forward USB device, not already attached serial device:

DEVLINKS=/dev/serial/by-id/usb-Raspberry_Pi_Pico_E6614104030A4B32-if00 /dev/serial/by-path/pci-0000:00:15.0-usb-0:1.3:1>

such approach may work for stantard slow serial connection. But I dont use LXC.

[jhofker]

I tried a VM, too, and couldn't get it working properly. Not sure why the devices didn't go through correctly. Moved to a spare Windows machine and it's working great.