Subject: Re: [linux-audio-user] ALSA with midisports ? _YES, here's how
From: Fernando Pablo Lopez-Lezcano (nando_AT_ccrma.Stanford.EDU)
Date: Tue Sep 03 2002 - 21:49:49 EEST
> > Sep 1 10:30:49 localhost kernel: usb.c: USB device 9 (vend/prod
> > 0x763/0x1001) is not claimed by any active driver.
> > The problem might be that the usb-midi module is never triggered. It seems
> Probably yes.
> > options snd-usb-midi snd_index=1
> options snd-usb-midi snd_vid=0x763 snd_pid=0x1001
> ... you could also try preloading snd-usb-midi with modprobe
> before hotplugging the device.
We could try but I doubt it will work and here's why:
The sequence of events we saw last week was (assuming we are
using fxload to load the firmware):
- plug the device
- kernel messages about it being there
Aug 30 19:20:49 localhost kernel: hub.c: USB new device connect \
on bus2/2, assigned device number 20
Aug 30 19:20:49 localhost kernel: usb.c: USB device 20 (vend/prod \
0x763/0x1010) is not claimed by any active driver.
that is correct because there is no driver loaded (it is not
any different if a usb-midi device driver is loaded beforehand).
- hotplug catches the connection (because the vendor/id has
been added to the list), triggers the script
Aug 30 19:20:52 localhost /etc/hotplug/usb.agent: Setup ezusbmidi \
for USB product 763/1010/1
Aug 30 19:20:52 localhost /etc/hotplug/usb.agent: Module setup \
ezusbmidi for USB product 763/1010/1
- the script calls fxload which loads the new firmware
Aug 30 19:20:52 localhost /etc/hotplug/usb/ezusbmidi: load \
/usr/share/usb/ezusbmidi/ezusbmidi1x1.ihx for 763/1010/1 to \
- the device disconnects and is reset after the new firmware is loaded
Aug 30 19:20:52 localhost kernel: usb.c: USB disconnect on device 20
Aug 30 19:22:28 localhost kernel: hub.c: connect-debounce failed, \
port 2 disabled
End of the story.
No more messages.
Same result if we try again (and we did :-)
There is never a reconnect from the device so that obviously
no midi device is going to recognize what is just not there.
My guess is that this version of the Midisport 1x1 is slightly
different (hardware-wise) and the just downloaded firmware
crashes on reboot. There are no kernel level messages after
the firmware is loaded showing a new usb device reconnecting
to the bus.
Most probably other older Midisport 1x1s work just fine...
This archive was generated by hypermail 2b28 : Tue Sep 03 2002 - 21:54:05 EEST