You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if I attempt to use "gt load /mnt/some/full/path/my.schema.file" I get an error, but if I cd to that path and just "gt load my.schema.file" it works happily.
example log output:
root@eg-13E128:~# gt load /mnt/kroot/owrt_private_feeds/remake_master/files/etc/remake.d/eth2-acm.gt
Error on import gadget <<<<< note this
Error: USBG_ERROR_NOT_FOUND : Not found (file or directory removed)
root@eg-13E128:~# ls -l /^C
root@eg-13E128:~# cd /mnt/kroot/owrt_private_feeds/remake_master/files/etc/remake.d/
root@eg-13E128:/mnt/kroot/owrt_private_feeds/remake_master/files/etc/remake.d# gt load eth2-acm.gt
[ 9562.708101] using random self ethernet address
[ 9562.712594] using random host ethernet address
[ 9562.718874] usb0: HOST MAC 7e:ed:2b:ac:61:64
[ 9562.722543] etb: port 1(usb0) entered blocking state
[ 9562.723248] usb0: MAC 0a:d4:88:aa:3c:a1
[ 9562.728256] etb: port 1(usb0) entered disabled state
root@eg-13E128:/mnt/kroot/owrt_private_feeds/remake_master/files[ 9562.737566] device usb0 entered promiscuous mode
/etc/remake.d#
I've tried looking at the code for this, and the "Error on import gadget" is after it's loaded the file, so I'm not sure what's happening here?
The text was updated successfully, but these errors were encountered:
pabs3
transferred this issue from linux-usb-gadgets/gt
Dec 8, 2022
I expect that this is actually a bug in libusbgx, because that is where
the USBG_ERROR_NOT_FOUND error comes from. Transferred the issue there.
Would you mind tracing where the error comes from in libusbgx?
if I attempt to use "gt load /mnt/some/full/path/my.schema.file" I get an error, but if I cd to that path and just "gt load my.schema.file" it works happily.
example log output:
I've tried looking at the code for this, and the "Error on import gadget" is after it's loaded the file, so I'm not sure what's happening here?
The text was updated successfully, but these errors were encountered: