* Re: SB32 Problem
1998-09-25 1:20 SB32 Problem Ricardo Peres
@ 1998-09-25 16:23 ` David Manifold
1998-09-26 0:07 ` Raymond Hall
1 sibling, 0 replies; 3+ messages in thread
From: David Manifold @ 1998-09-25 16:23 UTC (permalink / raw)
To: linux-sound
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: SB32 Problem
1998-09-25 1:20 SB32 Problem Ricardo Peres
1998-09-25 16:23 ` David Manifold
@ 1998-09-26 0:07 ` Raymond Hall
1 sibling, 0 replies; 3+ messages in thread
From: Raymond Hall @ 1998-09-26 0:07 UTC (permalink / raw)
To: linux-sound
> On Fri, 25 Sep 1998, Ricardo Peres wrote:
>
> > 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
>
> > 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,
1- I assume you're initializing the card via isapnptools at boot...
There's one caveat though: pnpdump fails to detect all the 3 ioports to
the wavetable (...er, I'm talking AWE here, but maybe it's the same)
So check your pnpconfig, in the wavetable section it SHOULD init 3
ioports, in my case they're: (ymmv)
(CONFIGURE CTL0039/23833 (LD 2
(IO 0 (BASE 0x0620))
(IO 1 (BASE 0x0A20))
(IO 2 (BASE 0x0E20))
(ACT Y)
))
2- You have to insmod the modules in proper order, preferably insmoding
sound.o at boot time (DMA buffer space allocation gets scarce), and the
rest whenever you like. I have sound.o insmoded in rc.local, and a script
called sound, as follows:
#!/bin/sh
/sbin/insmod uart401
/sbin/insmod sb io=0x220 irq=5 dma=0 dma16=5 type=5
/sbin/insmod opl3 io=0x388
/sbin/insmod sbawe
(remember, though, that for kernels 2.1.x it's a different story)
(btw, recent kernels include the awe module, don't attemp to patch'em)
(... unless of course, u know what u're doing)
3- Finally, to hear anything from the wavetable, you've got to upload some
samples to it (i.e. sfbanks, either *.sbk or *.sf2), for which theres a
beautifull utility called sfxload available at your nearest bahamut
mirror.(guess there's a rpm too)
Conclussion: I know (for I went through it) how frustrating it can be to
get your SB going, especially later on when you'll want full duplex, opl3,
external midi AND wave, but the key ingredient here is patience, and IT
DOES HELP to take a look at the sources.
(hint: /usr/src/linux/drivers/sound/<whatever, especially docs>)
Regards,
Raymond
^ permalink raw reply [flat|nested] 3+ messages in thread