On Thu, 10 Dec 1998, Andreas Behnert wrote:
> Linux I configured the card with isapnp and it seems to function -
> almost. I did set it to IRQ 9, I/O 220, DMA 1 and and DMA 3. The card
> only accepts DMA channels 0 - 3. The MPU-401 MIDI device on the card
> requires an own IRQ, I used No. 11 and Port 300. I configured the
> kernel (2.0.36) to use the card as a SB16 (CONFIG_MPU401 not defined
> because of the advice in various help texts, but with SB_MPU_IRQ=11).
> If I do a "cat /dev/sndstat" everything looks fine. Insinde my
> /var/log/messages I found "kernel: SB16: Bad or missing 16 bit DMA".
You have not given it a 16bit DMA channel (0-3 are all 8bit). If the card
will not accept any DMA above 3, that suggests that it is an 8bit card, so
there ain't much you can do about it.
> If I try "cat sound16bit.wav > /dev/dsp" only noise comes out of my
> speakers.
It is (probably) trying to play it at 8bit. /dev/dsp does not understand
wav headers, and there is no particular reason why this should work.
> Using an 8 bit WAV file it functions perfectly. I already
> tried to use DMA channel No. 1 for both but wihout success. Is there
> a known solution for this? Using DOS the soundcard functions very well
> and there are no problems. However, I am able to play 16Bit Wav Files
> in Linux using "mxv"!? Does this mean that my card is correctly
> configured or is mxv unsing some sort of 8-bit-downmixing?
>
It could be either. I don't know how mxv handles things. Try running
wavplay on a 16bit wav. If that works then the card is working correctly
(although I'm not quite sure how). If not then mxv is converting it to
8bit.
> After loading the kernel sound module the volume on the card is set to
> almost 100%. Is it possible to access the mixer directly after loading
> the module and what program should I use if there is any? I only know
There is a program called aumix which will provide a curses interface.
There is also mixer which works from the command line.
> "xmix" but this is for X. And everytime the kernel reloads the sound
> module the volume will be set to the default value. Is there a way to
> keep the module in the kernel or even better: How can I change the
> defaults so that kerneld can load and unload the module as often as he
> wants and the mixer settings will remain? (BTW: I know some people load
> the sound module with "modprobe" - will this make the module
> "permament" in the kernel?)
>
It would be possible to hack the kernel and/or kerneld to preserve mixer
settings. However, it would be better to leave the sound module inserted
all the time. Inserting it with modprobe will mean that kerneld won't
remove it. There are good reasons (to do with running out of memory for
DMA access) why sound modules are best left in.
HTH
--
Mike <[EMAIL PROTECTED]>
Only that in you which is me can hear what I'm saying.
-- Baba Ram Dass