OK i did some testing with my pi4b and it correctly powercycles as long as the ilok (2nd gen the one with the blue light) is attached to the top right USB 3 port (next to the ethernet jack)
Note my kernel, eeprom version and "Raspberry Pi 4 Model B Rev 1.1" in the cpuinfo.
Are yours exactly the same?
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux
pi@raspberrypi:~ $ sudo rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)
LATEST: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/default
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
pi@raspberrypi:~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 1
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 2
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 3
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
Hardware : BCM2711
Revision : a03111
Serial : 10000000b4fe30aa
Model : Raspberry Pi 4 Model B Rev 1.1
pi@raspberrypi:~ $
then plug the ilok into the top usb 3 port and try to use it between clients again.
Does that fix the problem? (This new build will wait 3 seconds between powering off the port and powering it back on, whereas the old server just waited 2 seconds, maybe 2 seconds is not enough time for the ilok to fully power off, not sure...)
I have just tried the above (BTW, my info matches yours with the exception of Raspberry Pi 4 Model B Rev 1.2 in my case).
Installed new build and I am getting iLok sharing errors again. Where as it was actually working previously. (all ports)
If I ssh in and run "sudo uhubctl -l 1-1 -a 0" (as per before), it all works again, but I have to run that command after rebooting the Pi
OK i did some testing with my pi4b and it correctly powercycles as long as the ilok (2nd gen the one with the blue light) is attached to the top right USB 3 port (next to the ethernet jack)
Note my kernel, eeprom version and "Raspberry Pi 4 Model B Rev 1.1" in the cpuinfo.
Are yours exactly the same?
Can you try this new build of the server https://www.virtualhere.com/sites/default/files/usbserver/test/vhusbdarm and see if it fixes your issue if you are still having issues:
then plug the ilok into the top usb 3 port and try to use it between clients again.
Does that fix the problem? (This new build will wait 3 seconds between powering off the port and powering it back on, whereas the old server just waited 2 seconds, maybe 2 seconds is not enough time for the ilok to fully power off, not sure...)
I have just tried the above (BTW, my info matches yours with the exception of Raspberry Pi 4 Model B Rev 1.2 in my case).
Installed new build and I am getting iLok sharing errors again. Where as it was actually working previously. (all ports)
If I ssh in and run "sudo uhubctl -l 1-1 -a 0" (as per before), it all works again, but I have to run that command after rebooting the Pi
Interesting " Raspberry Pi 4 Model B Rev 1.2"
so they might have changed something between 1.1 and 1.2 in the pi hardware...
You will need to have a quick look here https://www.raspberrypi.org/documentation/linux/usage/systemd.md and setup a systemd script to run at boot
Cools thanks Michael.
Mmm, I think this systemd script biz is a little beyond my understanding.