Hello everyone,
i'm having a strange issue with an usb3 UVC video acquisition dongle.
I found out the issue using the dongle inside a debian 12 lxc. The first acquisition (with ffmpeg) is working. As soon as i stop the task, the dongle can't acquire anymore until i reset the uvcvideo module on the proxmox host.
1) i thought it could be a matter of passing the dongle to the lxc, so i tried installing ffmpeg also on the host. Same issue: i can carry out only a single acquisition and then i need to modprobe -r the uvcvideo module
2) At this point i thought it could be the dongle itself to be misfunctioning, so i tried creating a proper vm (debian 13 in this case) and passing the dongle. IT WORKS consistently. I can start stop and restart the acquisition
3) i thought it could be a debian 12 vs debian 13 issue, so i updated the lxc to trixie and tried again. Fail, same issue and same need to reset the module on the host
4) so i thought it could be a kernel issue (honestly i had been thinking to this for a while) since i'm still on proxmox 8 (6.8.12.15) and the VM was far ahead (in the 6.12 branch). So why don't give a try to test kernel? and let 6.14.8.3 be. No luck, still same issue.
5) no more ideas.
Thanks for any help or hint or idea..
My system is a N100 homelab, no subscription, on proxmox 8.4.14
i'm having a strange issue with an usb3 UVC video acquisition dongle.
I found out the issue using the dongle inside a debian 12 lxc. The first acquisition (with ffmpeg) is working. As soon as i stop the task, the dongle can't acquire anymore until i reset the uvcvideo module on the proxmox host.
1) i thought it could be a matter of passing the dongle to the lxc, so i tried installing ffmpeg also on the host. Same issue: i can carry out only a single acquisition and then i need to modprobe -r the uvcvideo module
2) At this point i thought it could be the dongle itself to be misfunctioning, so i tried creating a proper vm (debian 13 in this case) and passing the dongle. IT WORKS consistently. I can start stop and restart the acquisition
3) i thought it could be a debian 12 vs debian 13 issue, so i updated the lxc to trixie and tried again. Fail, same issue and same need to reset the module on the host
4) so i thought it could be a kernel issue (honestly i had been thinking to this for a while) since i'm still on proxmox 8 (6.8.12.15) and the VM was far ahead (in the 6.12 branch). So why don't give a try to test kernel? and let 6.14.8.3 be. No luck, still same issue.
5) no more ideas.
Thanks for any help or hint or idea..
My system is a N100 homelab, no subscription, on proxmox 8.4.14