Juhani (I suppose that is your first name :-),
I finally fixed the problem by doing the following :
1) I enabled the /dev/bus/usb support (I commented the necessary lines
in /etc/init.d/mountdevsubfs.sh)
2) The trick is in the /etc/udev/rules.d/42-madfuload.rules file :
The line that contains the "ma006100.bin" (which should be called
when you plug in the transit) you should put :
ACTION=="add", SUBSYSTEM=="usb", ENV{PRODUCT}=="763/2806/*",
RUN+="/usr/local/sbin/madfuload -l -3 -f
/usr/local/share/usb/maudio/ma006100.bin -D $env{DEVNAME}"
Note that, compared to the original line, I changed two things :
- the condition DEVPATH=="/*.0" is removed : this makes sure the bin
executable is called when all env variables are know.
- the ma006100.bin executable is called with the option -D
$ENV{DEVNAME}. The reason for this is, when you call the bin executable
without an option, it assumes to use the device as specified in the
$DEVICE environment variable (/proc/bus/usb/004/016 in your case) but
for some strange reason Gutsy does not know this environment variable at
startup time (but does now it when you plug in the transit and have
udevmonitor running). Using the DEVNAME variable solves this problem.
Hope this works out for you ...
--
UDEV problem with madfu-firmware for M-Audio Transit USB audio interface under
Feisty
https://bugs.launchpad.net/bugs/102631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
