I'm trying to get ALSA to recognize my Edirol UM-1 usb midi interface and I'm not having much luck.
I'm using a Debian system and I'm trying to use either the 2.4.19 or 2.4.20 distributed kernel images.
Regarding the 2.4.19 kernel, there is an alsa-modules package that has the alsa 0.9.0rc6 modules. With the stock distribution, I get audio sound (KDE plays it's welcome sound... I can play stuff on xmms, etc), but plugging in the UM-1 didn't do anything. So, I went and downloaded the usbmidi package written by Nagano Daisuke and Richard Penner. I compiled and installed that into my modules directory and now, when I plug the UM-1, I get (in summary):
usb.c: registered new driver midi ALSA ../alsa-kernel/usb/usbaudio.c:2187: cannot create a card instance 0 ALSA ../alsa-kernel/usb/usbaudio.c:2187: cannot create a card instance 0 usb.c: registered new driver midi ALSA ../alsa-kernel/usb/usbaudio.c:2187: cannot create a card instance 0 ALSA ../alsa-kernel/usb/usbaudio.c:2187: cannot create a card instance 0 usb-midi: found [ Roland UM-1 ] .... usb-midi: /dev/midi00 ....
So, you can see that one of the alsa drivers (the "audio" driver, of all things... which implies audible sound, but whatever...) is trying to handle the new device, but it fails and the rogue usb-midi.o driver gets a chance at it and thinks it succeeds (but I haven't had a successful test yet).
Now, with the 2.4.20 kernel, there aren't any alsa drivers packaged yet. However, it *does* seem to include Daisuke/Penner's usb-midi.o driver (or some other driver called usb-midi). When I plug my UM-1 into the usb port with the stock kernel, it says it recognizes the Roland UM-1 and says it has assigned it to /dev/midi00 (even though the alsa snddevices script creates /dev/midi0... but that's the least of my problems right now). So, to summarize: 2.4.20 kernel *without* alsa recognizes the UM-1. (However, I haven't been able to get a successful loopback test... but, again, that's a problem for later).
Now, since I want *sound* on my laptop, I wanted to compile the alsa driver. So, I compiled the 0.9.2 drivers (without recompiling the kernel... I just pointed it at the kernel header files and the .config file used to create the running kernel). The compile went okay. I installed the modules and was able to get audio on my laptop. THEN, when I plugged in the midi interface, the kern.log read (in summary):
hub.c: new USB device 00:1d:0-1 assigned address 2 usb.c: USB device 2 ... not claimed by any active driver usb.c: registered new driver snd-usb-audio devfs_register(unknown): could not append to parent, err -17 devfs_register(unknown): could not append to parent, err -17 usb.c: registered new driver midi
(Sidenote: I *don't* think that it's a problem with devfs because I can go into /proc/bus/usb and see interesting stuff about the usb layer.)
So, this behaves a little differently from the 2.4.19 configuration in that it doesn't fail over to the usb-midi driver. However, if I move the snd-usb-audio to someplace where depmod won't find it, then the usb-midi driver will get loaded and it claims to recognize the midi interface (but, again, no successful test).
I'm so baffled at this point that I don't even know which questions to begin asking....
1 - Is snd-usb-audio supposed to be driving usb midi interfaces? If so, does anyone have any idea why it's failing?
2 - What does "could not append to parent" mean, and how do I fix it?
3 - I thought that the "snd-" prefix got dropped a while back, yet the Makefile still makes the modules with the "snd-" on the front. Was dropping "snd-" a debianism, or is there something stranger happening?
4 - What tools are good for testing the midi-in and midi-out ports? Right now, I'm trying to use a home-grown loopback test which, even if it's working properly, doesn't tell the difference between a problem with input and output.
- Joe
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
