From: Dave Mielke <dave@mielke.cc>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64
Date: Fri, 19 Nov 1999 04:29:42 +0000 [thread overview]
Message-ID: <marc-linux-sound-94298584204148@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91965172830159@msgid-missing>
[quoted lines by Heikki Kallasjoki on November 19, 1999, at 00:38]
>Another possible problem with sbAWE64, that many people seem to have, is
>the fact that pnpdump fails to recognize correctly those IO-ports for the
>wavetable part of the card. I have never used Red Hat personally, so I
>don't know much about how configuring it goes, but when you get the card
>working so that sound can be heard, if you then notice that the wavetable
>driver doesn't find the card, and it is a PnP version, (is there a
>non-PnP-awe64?) the cause might be this.
I have a RedHat system, and RedHat's "sndconfig" works just fine with my PNP
AWE64 card. Even the wave tables work.
The relevant part of "/etc/conf.modules" is:
alias sound sb
pre-install sound insmod sound dmabuf=1
options opl3 io=0x388
alias midi awe_wave
post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2
options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
The relevant parts of "/etc/isapnp.conf" are:
(CONFIGURE CTL00c5/63091016 (LD 0
# ANSI string -->Audio<--
(INT 0 (IRQ 5 (MODE +E)))
(DMA 0 (CHANNEL 1))
(DMA 1 (CHANNEL 5))
(IO 0 (SIZE 16) (BASE 0x0220))
(IO 1 (SIZE 2) (BASE 0x0330))
(IO 2 (SIZE 4) (BASE 0x0388))
(NAME "CTL00c5/63091016[0]{Audio }")
(ACT Y)
))
(CONFIGURE CTL00c5/63091016 (LD 2
# ANSI string -->WaveTable<--
(IO 0 (BASE 0x0620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20))
(NAME "CTL00c5/63091016[2]{WaveTable }")
(ACT Y)
))
>Now, AWE64 uses also ports 0xA20 and 0xE20 in addition to 0x620, and all
>implementations of pnpdump I've seen have been unable to detect that.
As you can see from tyhe above, REdHat's "sndconfig" utility did find all of
the ports just fine.
--
Dave Mielke | 856 Grenon Avenue | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me
EMail: dave@mielke.cc | Canada K2B 6G3 | if you're concerned about Hell.
next prev parent reply other threads:[~1999-11-19 4:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-22 2:37 AWE64 Conde Martinez Rodolfo
1999-02-22 4:24 ` AWE64 Conde Martinez Rodolfo
1999-02-22 21:20 ` AWE64 Keith Duthie
1999-11-18 22:06 ` AWE64 Dave Mielke
1999-11-18 22:38 ` AWE64 Heikki Kallasjoki
1999-11-19 4:29 ` Dave Mielke [this message]
1999-11-19 14:53 ` AWE64 Heikki Kallasjoki
1999-11-19 18:32 ` AWE64 Paco
1999-11-19 18:49 ` AWE64 Bill Nottingham
1999-11-19 18:57 ` AWE64 Paco
1999-11-19 18:58 ` AWE64 Paco
-- strict thread matches above, loose matches on Subject: below --
1999-11-18 21:20 AWE64 Great One
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-94298584204148@msgid-missing \
--to=dave@mielke.cc \
--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