From: David Manifold <dem@pacificrim.net>
To: linux-sound@vger.kernel.org
Subject: Re: SB32 Problem
Date: Fri, 25 Sep 1998 16:23:25 +0000 [thread overview]
Message-ID: <marc-linux-sound-90674686519780@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90671325305938@msgid-missing>
On Fri, 25 Sep 1998, Ricardo Peres wrote:
> Hi!
>
> I have two problems: first, I cannot play midi files in Linux.
> I have RedHat 5.1 and a SoundBlaster 32 soundcard, have sound compiled in
> the kernel, and everything else works fine.
> When I try to play a midi file, I get a message like "/dev/sequencer is
> not configured"... Any ideas?
Well, you either forgot to say 'y' to MIDI support in the sound module, or
the /dev/sequencer device file is not set up. It should be major 14,
minor 1.
crw-rw-rw- 1 root sys 14, 1 Jul 18 1994 /dev/sequencer
You can re-create this with:
rm -f /dev/sequencer;mknod /dev/sequencer c 14 1;chmod 666 /dev/sequencer
> Second, although I compiled the kernel with the SB32 low-level driver
> from http://bahamut.mm.t.u-tokyo.ac.jp/~iwai/awedrv/ as a module,
> whenever I try to `insmod sbawe` I get a message saying: "AWE32: not
> detected". It is true that my soundcard is NOT a SB AWE32, just a SB32,
> but I use it in Windows and everywhere else as AWE. What is the
> difference between these two soundcards? How can I fix this (if it is
> possible) ?
The SB32 is just an SB16 with more voices (or there are other changes,
but it is more like an SB16 than an AWE), so you should load the regular
SB driver.
David Manifold <dem@tunes.org>
next prev parent reply other threads:[~1998-09-25 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-25 1:20 SB32 Problem Ricardo Peres
1998-09-25 16:23 ` David Manifold [this message]
1998-09-26 0:07 ` Raymond Hall
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=marc-linux-sound-90674686519780@msgid-missing \
--to=dem@pacificrim.net \
--cc=linux-sound@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox