Midisport 2x2 doesn't work with 2.6.22-multimedia

  • Patrice Brousseau
Posted: Fri, 08/10/2007 - 16:35
Yesterday, I installed the 2.6.22 multimedia kernel and to my surprise, the firmware of the midisport isn't loaded anymore at boot time. The unit works because if I boot with another kernel (2.6.19 or 2.6.21), the led flicker as usual and it register in jack. If I reboot in 2.6.22, as the firmware is already loaded, the device register in jack... So definitely, it is just a problem of loading the firmware. For the record, I also tried the 2.6.22-rt4 kernel of the Musix repo and it does the same thing. Any advices or workaround? Thanks.

I installed another version of 2.6.22 so it's fine now...

  • Patrice Brousseau
  • 06/04/07
  • Mon, 12/24/2007 - 00:32
Two other versions of 2.6.22 replaced the initial one (one coming from Jacklab and one self-compiled) and the Midisport is now loaded correctly at boot.

I upgraded my kernel on my

  • deadgobby
  • 09/01/07
  • Sat, 09/01/2007 - 20:34
I upgraded my kernel on my Ubuntu box and seems to be fine with my midi sport. Are you running the 64bit or the 32bit version? Have you tried to re-install the firmware for midi sport? http://packages.debian.org/unstable/sound/midisport-firmware On the live 32bit cd of S64 as I said ran fine. Just cannot get my sound blaster to have any sound. Gobby

I run the 32 bit version. As

  • Patrice Brousseau
  • 06/04/07
  • Sun, 09/02/2007 - 19:21
I run the 32 bit version. As for the firmware reinstallation, I did it but anyway it loads fine under 2.6.19 or 2.6.21. Again, is the live cd based on 2.6.21 or 2.6.22?

Kernel

  • sirven
  • 07/25/07
  • Sat, 12/15/2007 - 20:25
The live CD is based on 2.6.21 for 64 Studio, if this is your question. Another thing is that your script could be good except that I my Midisport1x1 is always going to a different address ! So I would need to tell every possible address corresponding to bus/device. You need a variable somewhere into the script. Thanks.

Interesting...

  • Quentin Harley
  • 05/24/07
  • Sat, 09/01/2007 - 20:26
Why should it work on live-CD and not on the installed? Perhaps Free has the answer...

It definitely doesn't work...

  • Patrice Brousseau
  • 06/04/07
  • Sat, 09/01/2007 - 20:12
I tried the plug/unplug solution deadgobby and it definitely doesn't work with the Midisport2x2. Maybe the live cd is based on the 2.6.21 kernel??

I ran the S64 live CD and

  • deadgobby
  • 09/01/07
  • Sat, 09/01/2007 - 17:23
I ran the S64 live CD and pick up my Midisport Uno just fine. You may need to unplug and replug the cable in. If the usvb starts flashing on and off. You are in biz. Gobby

Kernel

  • elkan9
  • 08/29/07
  • Sat, 09/01/2007 - 01:53
Well the working system is not the problem, but I've said the 2.6.21 does not work with the M-Audio Transit USB. I need another kernel multimedia maybe the 2.6.18, but I don't know where I found it.

Kernel

  • Quentin Harley
  • 05/24/07
  • Wed, 08/29/2007 - 06:03
If the slight hardware limitations of 2.6.21 does not affect you then at least you still have a working system. The later kernels generally provide better hardware support, and I was already quite happy with 2.6.17! I do test the later kernels on my hardware to check for regressions, but luckily I haven't had any (so far)

Transit m-audio

  • elkan9
  • 08/29/07
  • Wed, 08/29/2007 - 02:20
Well, I found some who have the same problem. I have the transit usb, and use the madfuload to charge the firmware. The problem is for all the kernels over the 2.6.21. I prove in fedora, ubuntu-studio, and now I've install 64studio and the same thing. I'm not found any way to load the firmware. I've to install the kernel multimedia 2.6.21. If some know anything, just post please.

Well, it's a no go for the

  • Patrice Brousseau
  • 06/04/07
  • Tue, 08/14/2007 - 17:44
Well, it's a no go for the Midisport 0.5 firmware managed by hotplug. As soon as I want to install hotplug, synaptic wants to remove 2.6.22 image, hal and some other important packages. For now, I'll go manually until something change...

Help?

  • Quentin Harley
  • 05/24/07
  • Mon, 08/13/2007 - 18:46
Did you find an answer yet? I don't know the midisport unfortunately, but please post your solution if you find it. Thanks,

The only workable solution I

  • Patrice Brousseau
  • 06/04/07
  • Tue, 08/14/2007 - 16:59
The only workable solution I found yet (and it is far from elegant) is to download the firmware manually. To do this, I made a file (Midisport.sh) that contains the following lines: #!/bin/sh /sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSport2x2.ihx -D /dev/bus/usb/002/002 /sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSport2x2.ihx -D /dev/bus/usb/001/003 I have to different lines because sometimes the Midisport is on /002/002 and sometimes on /001/003. Anyone else can confirm there's a bug with Midisport Firmware and 2.6.22 kernel?? Thanks **I know there is a way to load the firmware via hotplug instead of udev... Maybe I'll try it and report back.