/dev/sequencer doesn't work, RH7.1, SB128PCI and SB16PCI
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
/dev/sequencer doesn't work, RH7.1, SB128PCI and SB16PCI
I've been reading HOWTOs and FAQs and other all caps alphabet documents over and over for the past couple of months, but I just can't get my midi port to function. (And I mean the midi port, for talking to my synths, not FM synth on a sound card.) I have RedHat 7.1 with a SoundBlaster 128 PCI (and I tried a SB16 PCI before that) and I can't get the midi port to activate. /dev/sequencer just doesn't respond.
The specific error message I get when I try to start my sequencer (Jazz) is
/dev/sequencer2 or /dev/music: Device not configured
/dev/sequencer2 or /dev/music: Device not configured
/dev/music: Device not configured
The device files exist and the permissions & major/minor are correct.
One thing I noticed is that sndconfig doesn't seem to install the midi drivers by default, so I've tried inserting sound.o and uart401.o by hand but although the modules load without errors the device still doesn't work.
I tried turning off aRtsd to see if that was conflicting, but it made no difference.
So is there any way at all to activate the midi port? Am I going to have to switch to ALSA? I will if I've got some hope that it will work. Right now I'm keeping an older ISA based computer sitting around just to use the ISA SB16 that's in it, and I'm getting rather desperate at this point.
This soundcard does not have any hardware MIDI synthesizer;
MIDI synthesis has to be done in software. To allow this
the driver/soundcard supports two PCM (/dev/dsp) interfaces.
There is a freely available software package that allows
MIDI file playback on this soundcard called Timidity.
See http://www.cgs.fi/~tt/timidity/.
> From /usr/src/linux/Documentation/sound/es1371,
> This soundcard does not have any hardware MIDI synthesizer;
I know this - that was one of the first files I ever read. But I'm not trying to activate any 2-bit synth on a soundcard - I'm trying to activate the MIDI data port. MIDI is a data protocol for sending note on/off messages and other control codes to musical instruments, and the Sound Blaster joystick port also serves as a MIDI data port to allow you to control an external synthesizer with your computer.
What I want to do is connect my Roland and Alesis keyboard synths to my computer so I can sequence music that's more complicated than I can play solo. To do this I need to activate the MIDI port on the SB. With earlier SB16 cards I'd just insmod sound.o, insmod uart401.o and away I'd go, and all the documentation I've found for the SB16PCI and SB128PCI says that this ought to work for them as well. (Actually, most of the documentation seems to assume that the MIDI drivers are installed by default when you run sndconfig. Manual installation is only rarely mentioned.)
Of course, theory is often easier than reality and I've hit a brick wall with this one. I'm about to try installing a different distro to see if this is just a bug in RH 7.1.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.