Recent changes to bugs

udevinfo replaced by udevadm

Andrew Hamlin — Fri, 18 Nov 2011 22:16:30 -0000

Here is a patch to configure to use udevadm

M-Audio Transit - new firmware version ma006101.bin

Neil Wilson — Sat, 22 Aug 2009 08:02:25 -0000

There is a new version of firmware available for the M-Audio Transit - ma006101.bin

configure fails - udevinfo: command not found

Anonymous — Tue, 21 Apr 2009 18:47:00 -0000

since udevinfo is replaced by udevadm the configure script fails,
here is my diff-file:

1740c1740
< udev_ver=`udevinfo -V | awk '{ print $3 }'`
---
> udev_ver=`udevadm info -V`

copy the 4 lines above and save the file as configure.diff
simply applie the patch by:
$ patch configure configure.diff

if it still fails try to run configure as root

No playback anymore with M-Audio Transit

Guillaume Pellerin — Fri, 30 Jan 2009 08:37:20 -0000

Hi all !

I use an M-Audio Transit at home which was working pretty good for some weeks. However, the playback hangs now... Although the device seems well detected and the firmware loaded, there is no sound playing back anymore.

Some consequences of this new bug :
- amarok gets the device and seems to play, but I get nothing on the output,
- qjackctl detects the card, starts jackd but shows many XRUNs and always 0% as
process loading.

This bug can be reproduced on Debian Sid and Lenny. May it be due to some new methods used by udev to load the firmware or abnormal detecting by network-manager (see the logs) or a default config using 16 bit word length and not 24 bits ? Can someone reproduce this bevahior using the Transit ?

Thanks for your help !
Guillaume

udevinfo no longer with udev package

Anonymous — Mon, 19 Jan 2009 22:07:38 -0000

hi clemens. the udev package on my arch linux doesn't have udevinfo so the configure fails. changeing line 1740 from udevinfo -V to udevd -V still fails. i'm no programmer ! i'll email you this as well.

best,

geoff beasley.
geoff@laughingboyrecords.com

udev rules for openSuse 11 and Ubuntu 8+

Paul Alfille — Fri, 17 Oct 2008 20:12:20 -0000

# midisport-firmware.rules - udev rules for loading firmware into MidiSport devices

# DEVPATH=="/*.0" selects interface 0 only
# (some udev versions don't work with SYSFS{bInterfaceNumber})

# MidiSport 2x2
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1001", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport2x2.ihx -D $env{DEVNAME}"
# MidiSport 1x1
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1010", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport1x1.ihx -D $env{DEVNAME}"
# KeyStation
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1014", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSportKS.ihx -D $env{DEVNAME}"
# MidiSport 4x4
#ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1020", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport4x4.ihx -D $env{DEVNAME}"
# MidiSport 8x8
#ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1031", ATTRS{bcdDevice}=="0110", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport8x8-2.10.ihx -D $env{DEVNAME}"
#ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1031", ATTRS{bcdDevice}=="0121", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport8x8-2.21.ihx -D $env{DEVNAME}"

# vim: ft=conf

madfuload segfaults on Linux x86_64

mr_batschner — Sun, 02 Mar 2008 09:47:26 -0000

On my AMD64 system, madfuload segaults when trying to download the firmware to an M-Audio transit (ma006100.bin).

$: uname -a
Linux Xerxes 2.6.17.3 #1 Wed Nov 1 22:32:51 CET 2006 x86_64 GNU/Linux

$: lsusb
Bus 005 Device 007: ID 0763:2006 Midiman
Bus 005 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 003 Device 002: ID 041e:3f08 Creative Technology, Ltd

Following stuff happens (yes, I did specify the wrong device file on purpose):

#:~/maudio/madfuload-1.2# ./madfuload -l -n -D /proc/bus/usb/005/005 -f /lib/firmware/`uname -r`/maudio/m006100.bin
Segmentation fault

With GDB, I see that there is some problem in fatal() and subsequently print():

(gdb) run
Starting program: ~/maudio/madfuload-1.2/madfuload -n -D /proc/bus/usb/005/006 -f ma006100.bin

Program received signal SIGSEGV, Segmentation fault.
0x00002b99c5643620 in strlen () from /lib/libc.so.6
(gdb) bt
#0 0x00002b99c5643620 in strlen () from /lib/libc.so.6
#1 0x00002b99c56137a7 in vfprintf () from /lib/libc.so.6
#2 0x00002b99c56141a6 in ?? () from /lib/libc.so.6
#3 0x00002b99c560fdaf in vfprintf () from /lib/libc.so.6
#4 0x0000000000400a8c in print (level=<value optimized out>, format=0x0, ap=0x7fffe56f89e0)
at madfuload.c:96
#5 0x0000000000400b43 in fatal (format=0x0) at madfuload.c:106
#6 0x000000000040132d in main (argc=6, argv=<value optimized out>) at madfuload.c:286

The variable format submitted to fatal is a NULL-pointer.

Another GDB session:

(gdb) br fatal
Breakpoint 1 at 0x400ab0: file madfuload.c, line 102.
(gdb) br print
Breakpoint 2 at 0x400a60: file madfuload.c, line 92.
(gdb) run
Starting program: ~/maudio/madfuload-1.2/madfuload -n -D /proc/bus/usb/005/005 -f /lib/firmware/2.6.17.3/maudio/m006100.bin

Breakpoint 1, fatal (format=0x4018b2 "cannot open %s: %s") at madfuload.c:102
102 {
(gdb) c
Continuing.

Breakpoint 2, print (level=3, format=0x4018b2 "cannot open %s: %s", ap=0x7fff67197430) at madfuload.c:92
92 {
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00002b4943ba4620 in strlen () from /lib/libc.so.6

And yet another GDB session:

(gdb) br print
Breakpoint 1 at 0x400a60: file madfuload.c, line 92.
(gdb) run
Starting program: ~/maudio/madfuload-1.2/madfuload -n -D /proc/bus/usb/005/006 -f ma006100.bin

Breakpoint 1, print (level=3, format=0x4019d0 "cannot open %s: %s", ap=0x7fff17959c10) at madfuload.c:92
92 {
(gdb) s
93 if (to_logger) {
(gdb) s
96 vfprintf(stderr, format, ap);
(gdb) p format
$1 = 0x4019d0 "cannot open %s: %s"
(gdb) p ap
$2 = (struct __va_list_tag *) 0x7fff17959c10
(gdb) s

Program received signal SIGSEGV, Segmentation fault.
0x00002b9c933e2620 in strlen () from /lib/libc.so.6

(gdb) bt
#0 0x00002b9c933e2620 in strlen () from /lib/libc.so.6
#1 0x00002b9c933b27a7 in vfprintf () from /lib/libc.so.6
#2 0x00002b9c933b31a6 in ?? () from /lib/libc.so.6
#3 0x00002b9c933aedaf in vfprintf () from /lib/libc.so.6
#4 0x0000000000400a8c in print (level=<value optimized out>, format=0x0, ap=0x7fff17959c40)
at madfuload.c:96
#5 0x0000000000400b43 in fatal (format=0x0) at madfuload.c:106
#6 0x000000000040132d in main (argc=6, argv=<value optimized out>) at madfuload.c:286

For some reason I do not understand, on its way down to vfprintf, the "format" gets changed from a valid pointer to a NULL-pointer, causing madfuload to crash.

Regards, Thomas

42-midisport-firmware.rules

Stefan Sauer — Sat, 17 Feb 2007 17:50:53 -0000

like in
http://sourceforge.net/tracker/index.php?func=detail&aid=1622573&group_id=87777&atid=584353

the rules should be updated. To get my keystation to run I had to change

ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1014/*", RUN+="/sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSportKS.ihx"

to this ( suggested by https://bugzilla.novell.com/show_bug.cgi?id=246055
)

ACTION=="add", SUBSYSTEM=="usb_device" ATTRS{idVendor}=="0763", ATTRS{idProduct}=="1014", RUN+="/sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSportKS.ihx -D $env{DEVNAME}"

Loader doesn't work with ALSA modules and M-Audio Oxygen 8

Anonymous — Thu, 18 Jan 2007 12:45:58 -0000

With Linux 2.6.17.14 the udev version of the loader (1.2) only works with ALSA compiled into the kernel, not as modules.

System: Debian Etch
Linux 2.6.17.14, AMD Duron (k7) (self compiled)
udev 0-103

$ lsusb
Bus 001 Device 005: ID 0763:1015 Midiman
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 002: ID 1822:3202 Twinhan VisionDTV USB-Ter/HAMA USB DVB-T device warm
Bus 002 Device 001: ID 0000:0000

$ lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
00:0d.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2)

Thomas

Fixed 42-madfuload.rules.in with SuSE 10.2

Berthold Höllmann — Tue, 26 Dec 2006 20:30:46 -0000

With SuSE 10.2, as with 10.1 the provided udev rule with madfuload does not work. The command does not get the DEVICE environment variable anymore. 10.1 provided the posibility to mount the usbfs for fixing this problem, but usbfs is not provided in the 10.2 default kernel.

With the help of linux-hotplug-devel@lists.sourceforge.net I was able the to fix the rules an get my M-Audio Transit working again. I'll attach a fixed 42-madfuload.rules.in that should work for the other cards also.

Kind regards
Berthold