From: Josh Huber <huber+keyword+alsa.9c0e1c@alum.wpi.edu>
To: alsa-devel@lists.sourceforge.net
Subject: snd-usb-midi fails to load w/current CVS
Date: Fri, 20 Sep 2002 00:21:11 -0400 [thread overview]
Message-ID: <87admdi954.fsf@mail.paradoxical.net> (raw)
I've got a USB midi device (MidiSport 2x2), but the snd-usb-midi
driver from current CVS does not load for me:
mystic:/home/huber# modprobe snd-usb-midi
/lib/modules/2.4.19/kernel/sound/acore/seq/snd-seq-virmidi.o:
unresolved symbol snd_rawmidi_set_ops_Rc01247d9
/lib/modules/2.4.19/kernel/sound/acore/seq/snd-seq-virmidi.o:
unresolved symbol snd_rawmidi_transmit_peek_R9d1a0acb
/lib/modules/2.4.19/kernel/sound/acore/seq/snd-seq-virmidi.o:
unresolved symbol snd_rawmidi_new_R14f74041
/lib/modules/2.4.19/kernel/sound/acore/seq/snd-seq-virmidi.o:
unresolved symbol snd_rawmidi_transmit_ack_Ra57c2838
/lib/modules/2.4.19/kernel/sound/acore/seq/snd-seq-virmidi.o:
unresolved symbol snd_rawmidi_receive_R8e703b33
/lib/modules/2.4.19/kernel/sound/acore/seq/snd-seq-virmidi.o: insmod
/lib/modules/2.4.19/kernel/sound/acore/seq/snd-seq-virmidi.o failed
/lib/modules/2.4.19/kernel/sound/acore/seq/snd-seq-virmidi.o: insmod
snd-usb-midi failed
mystic:/home/huber#
Ah, it's because the "usb-rawmidi" module does not get installed with
a make install.
I was originally using ./configure --with-cards=powermac,usb-audio,
which built all the modules required for usb-midi, including
snd-rawmidi. To get the rawmidi module to install, I had to specify
support for virmidi as well.
Just FYI.
--
Josh Huber
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-09-20 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 4:21 Josh Huber [this message]
2002-09-20 9:52 ` snd-usb-midi fails to load w/current CVS Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87admdi954.fsf@mail.paradoxical.net \
--to=huber+keyword+alsa.9c0e1c@alum.wpi.edu \
--cc=alsa-devel@lists.sourceforge.net \
--cc=huber+dated+1032926673.3f2d8b@alum.wpi.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.