From: Neale Banks <neale@lowendale.com.au>
To: linux-sound@vger.kernel.org
Subject: [PATCHLET 2.2]Doc/sound/VIBRA16
Date: Mon, 28 Jan 2002 04:37:56 +0000 [thread overview]
Message-ID: <marc-linux-sound-101219266614626@msgid-missing> (raw)
Appended patch has corrections and minor update for
Documentation/sound/VIBRA16
These changes are based on my experience with VIBRA16 and 2.2.21-pre2 on
Debian Potato on a Compaq Deskpro (which seems to manage all the ISApnp
itself :-).
Regards,
Neale.
--- linux-2.2.21-pre2-pristine/Documentation/sound/VIBRA16 Mon Mar 26 02:31:59 2001
+++ linux-2.2.21-pre2-ntb/Documentation/sound/VIBRA16 Mon Jan 28 14:50:40 2002
@@ -15,6 +15,8 @@
(tried it with a 2.2.2-ac7), nor in the commercial OSS package (it reports
it as half-duplex soundcard). Oh, I almost forgot, the RedHat sndconfig
failed detecting it ;)
+ Kernel 2.2.21pre2 also works with this card. /proc/sound
+reports "OSS/Free:3.8s2++-971130" and "Sound Blaster 16 (4.13) (DUPLEX)"
So, the big problem still remains, because the sb module wants a
8-bit and a 16-bit dma, which we could not allocate for vibra... it supports
only two 8-bit dma channels, the second one will be passed to the module
@@ -59,6 +61,8 @@
you may want to:
modprobe sb io=0x220 irq=5 dma=1 dma16=3
+# do you need MIDI?
+modprobe opl3 io=0x388
Or, take the hard way:
@@ -67,14 +71,18 @@
insmod uart401
insmod sb io=0x220 irq=5 dma=1 dma16=3
# do you need MIDI?
-insmod opl3=0x388
+insmod opl3 io=0x388
Just in case, the kernel sound support should be:
CONFIG_SOUND=m
CONFIG_SOUND_OSS=m
CONFIG_SOUND_SB=m
+# do you need MIDI? YM3812 gets you opl3.o...
+CONFIG_SOUND_YM3812=m
Enjoy your new noisy Linux box! ;)
+Minor corrections and updates
+ Neale Banks <neale@lowendale.com.au> Mon, 28 Jan 2002 15:06:35 +1100
reply other threads:[~2002-01-28 4:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-101219266614626@msgid-missing \
--to=neale@lowendale.com.au \
--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