OK, I've done a bit more work on this today with various combinations of udev selectors and I think I might have cracked it.
Can you put
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}="usb_device", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="2806", RUN+="/usr/sbin/madfuload -l -3 -f /usr/share/usb/maudio/ma006100.bin -D $ENV{DEVNAME}"
in place of the original Transit line in /lib/udev/rules.d/42-madfuload.rules
I've tested this on a laptop and a netbook in both 32 and 64 bit and it seems to work around the race condition - allowing the firmware to load.
Let me know if that helps.
OK, I've done a bit more work on this today with various combinations of udev selectors and I think I might have cracked it.
Can you put
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE} ="usb_device" , ATTRS{idVendor} =="0763" , ATTRS{idProduct }=="2806" , RUN+="/ usr/sbin/ madfuload -l -3 -f /usr/share/ usb/maudio/ ma006100. bin -D $ENV{DEVNAME}"
in place of the original Transit line in /lib/udev/ rules.d/ 42-madfuload. rules
I've tested this on a laptop and a netbook in both 32 and 64 bit and it seems to work around the race condition - allowing the firmware to load.
Let me know if that helps.