On 10 November 2016 at 10:54, Jaime T <enopatch@xxxxxxxxx> wrote: > Could anyone please tell me why usx2yloader is (silently) failing when > it's called during boot-up, or how I can debug this further? After some debugging, I think I have found both the cause of the problem, and a solution. The debian "alsa-firmware-loaders" package ships a udev rules file (/lib/udev/rules.d/60-alsa-firmware-loaders.rules) which is essentially the same as that suggested in the unofficial wiki (http://alsa.opensrc.org/Tascam_US-122). It contains the line: SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8007", RUN+="/lib/udev/tascam_fpga" But this line triggers the "Phase 2" firmware loader, usx2yloader, BEFORE the "hardware dependent interface" (on which it depends) is up-and-running (see alsa-tools/usx2yloader/README for more info). After stumbling around with "udevadm monitor" for a bit, I replaced that line with: SUBSYSTEM=="sound", ACTION=="add", KERNEL=="hwC2D0", RUN+="/lib/udev/tascam_fpga" and then rebooted. Now: 1) If I boot with my us-122 disconnected and then connect it, it initialises correctly. 2) If I disconnect it and re-connect it, it initialises correctly. 3) If I boot with my us-122 connected, it initialises correctly. (My udev-fu is very limited, and there may be a much better rules line - all suggestions gratefuly received!) Now to change the alsa wiki and log a bug against debian's "alsa-firmware-loaders" package... J :-) ------------------------------------------------------------------------------ _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
