Ubuntu
madfuload package

  1. Bug #330573
  2. Comment #6

Comment 6 for bug 330573

Revision history for this message
oudalrich (uhkeller) wrote : Re: madfuload doesn't work on Jaunty

On my system, udev does not even try to run madfuload when I plug in my Transit, at least madfuload does not show up in udev's debug output to /var/log/syslog. I have tried various changes to the udev rules (from comments 1 and 3, among others), but no rule seems to match the device, though the device ID is correct. Here's the line I currently use (in /lib/udev/rules.d/42-madfuload.rules):

ACTION=="add", SUBSYSTEM=="usb", ENV{PRODUCT}=="763/2806/*", RUN+="/usr/sbin/madfuload -l -3 -f /usr/share/usb/maudio/ma006100.bin -D $env{DEVNAME}"

I have restarted udev, and sometimes rebooted, each time after changing the rules. Lsusb output:

uli@EMACS-Keller:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0763:2806 Midiman M-Audio Transit DFU
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Debug output from udev in attachment.

I'm on Jaunty 32-bit. Running madfuload manually works, even though it generates an error:
cannot reset device: (19) No such device