-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Nov 06, 2007 at 10:39:47PM -0000, arisstotle.54695488(a)bloglines.com wrote:
--- gnome(a)hawaii.rr.com wrote:
Kjetil S. Matheussen wrote:
> david:
>> David Griffith wrote:
>>> On Sun, 4 Nov 2007, ANDERSON GREGORY
wrote:
>>>> I am looking to buy a MIDI
keyboard controller but I
am
>>>> having trouble coming up with a
site that has
>>>> compatibility
info on it. Could someone point me in the
>>>> right direction?
>>> Any MIDI keyboard will work as long as you have a MIDI interface that
>>> works. Trickiness comes into play with USB/MIDI keyboards. Those
are
>>> essentially USB/MIDI interfaces
tucked into a keyboard. As
>> previously-discussed here, USB/MIDI devices may or may not work with
>>> Linux. Roland/Edirol and Korg are two brands known to work.
>> When ALSA isn't fighting over which sound card to load in which order
on
>> my system, the E-MU Xmidi1x1 works just
fine.
> In your
modules settings file (mine is /etc/modules.d/alsa), set:
I don't have
an /etc/modules.d
directory. I have an /etc/modprobe.d
directory.
alias snd-card-0 snd-<card1>
alias snd-card-1 snd-<card2>
etc.
I found a file called "sound" in the modprobe.d directory. It
already
had an alias setting snd-card-0 to the intel sound driver. So I added
an
alias to it for the snd-usb-audio. Restarting
only brought up error
messages about usb device 2,2, and killed both the USB<>MIDI adapter and
my external flash card reader. So I decided to go the other way -
renamed the sound file to something else and restarted again. Then
everything
came up.
So far, audio has been working since then, but
won't really
know for awhile.
Running GNU/Debian Linux ...
use
the vendor and product IDs from lsusb and lspci to give each alsa driver an
index number to make sure that each driver gets put in the same spot each
boot.
in my modprobe.d/alsa file I have:
options snd-usb-audio index=1,2,3
vid=0x08bb,0x0763,0x0c45 pid=0x2902,0x0199,0x1
7fd