We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
During multi-gadget.sh the last line of that script fails:
ls /sys/class/udc > $GADGET_PATH/UDC results in: ls: write error: Device or resource busy
ls /sys/class/udc > $GADGET_PATH/UDC
ls: write error: Device or resource busy
in dmesg I see: [ 80.470962] UDC core: pi4: couldn't find an available UDC or it's busy
[ 80.470962] UDC core: pi4: couldn't find an available UDC or it's busy
that eventually leads to:
DEVICE_UVC: Device open failed: No such file or directory (2).
It does work with showmewebcam (which uses an older 5.10.11 kernel) and it fails with raspbian bullseye with kernel 6.1.21+ (6.1.34+ also fails).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
During multi-gadget.sh the last line of that script fails:
ls /sys/class/udc > $GADGET_PATH/UDC
results in:ls: write error: Device or resource busy
in dmesg I see:
[ 80.470962] UDC core: pi4: couldn't find an available UDC or it's busy
that eventually leads to:
It does work with showmewebcam (which uses an older 5.10.11 kernel) and it fails with raspbian bullseye with kernel 6.1.21+ (6.1.34+ also fails).
The text was updated successfully, but these errors were encountered: