Version 1.05 of the script is available. You can
download it from AlGrenadine's AxeFX Archive. Once again, many thanks to AlGrenadine for hosting the package file.
If the Axe-Fx II has been powered up and connected via USB during the installation process, the script now takes care that the Axe-Fx II will immediately work as a USB audio and midi interface as soon as the script
finishes. So you will not have to reboot the Axe-Fx II or dis- and reconnect the USB cable after the installation process has finished.
As explained in post 104 the Axe-Fx specific udev rule will get triggered everytime the Axe-Fx II appears on one of the USB ports of your computer which happens
- when Linux is starting up (of course only if the Axe-Fx II is powered up conncected via USB...),
- when you plug in the USB cable connected to an already running Axe-Fx II and also
- when you start or reboot an Axe-Fx II connected via USB.
In the past the udev rule did not get triggered if the Axe-Fx II has already been running and connected to a USB port when the script was executed, because there was no triggering event (i.e. Axe-Fx II appearing at a USB port). That's the reason why the Axe-Fx II had to be rebooted (or alternatively the USB cable had to be unplugged and plugged in again) in that specific situation.
Now the script itself triggers the udev rule made for the Axe-Fx II if it detects an Axe-Fx II on one of the USB ports. Hence the Axe-Fx II gets loaded with the USB firmware hex file (enabling the Axe-Fx II to work as a USB audio and midi interface) without rebooting respectively dis-reconnecting the USB cable.
All this does not affect users who already have run the script successfully. It is not necessary to run the script again. Once the script has created the udev rule file for the Axe-Fx II you are done.