[Bug 330573] Re: madfuload doesn't work on Jaunty

Neil Wilson neil at aldur.co.uk
Sat Jun 20 15:51:27 UTC 2009


Try getting a bit more detail in the log by using

sudo udevadm control --log-priority=<value>

where <value> = err, info or debug

That should give you an idea as to why udev isn't using calling the
rule.

2009/6/20 oudalrich <uhkeller at web.de>:
> 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 at 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
>
> ** Attachment added: "Udev debug output when plugging in my Transit"
>   http://launchpadlibrarian.net/28138111/syslog
>
> --
> madfuload doesn't work on Jaunty
> https://bugs.launchpad.net/bugs/330573
> You received this bug notification because you are a direct subscriber
> of the bug.
>


-- 
Neil Wilson

-- 
madfuload doesn't work on Jaunty
https://bugs.launchpad.net/bugs/330573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


More information about the universe-bugs mailing list