From: Sangohn Christian <sango-ch@reze-1.rz.rwth-aachen.de>
To: linux-sound@vger.kernel.org
Subject: Re: AWE32 initialization wiht isapnp
Date: Mon, 28 Sep 1998 02:08:46 +0000 [thread overview]
Message-ID: <marc-linux-sound-90703509605379@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90692428831897@msgid-missing>
On Sun, 27 Sep 1998, Bill Nottingham wrote:
>Alexis DOMJAN (disco@igaia.ch) said:
>> In order to use the wavetable device of my AWE32 I was starting under
>> MSDOS, executing ctpnp to configure the card and then I was running
>> loadlin and the Wavetable was properly detected.
>>
>> However I only want to use lilo, so I'm using isapnp to configure the
>> awe32 (audio and wavetable) and then I "modprobe" sound module. Then the
>> audio device (dsp, opl2/3) is correclty detected, but the AWE32 Wavetable
>> on port 0x620 is not detected (according to /proc/ioports).
>
>Find the line in your isapnp.conf file that says:
>
> (IO 0 (BASE 0x0620))
>
>Add right after it:
>
> (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20))
>
>pnpdump, for whatever reason, doesn't see all the IO ports for
>the EMU chip on the AWE.
Her is an excerpt of my /etc/isapnp.conf
(CONFIGURE CTL0042/83463
(LD 3
# ANSI string -->WaveTable<--
(IO 0 (BASE 0x0620))
(IO 1 (BASE 0x0A20))
(IO 2 (BASE 0x0E20))
(ACT Y)
)
)
But I still have the problem.
>
>Bill
next prev parent reply other threads:[~1998-09-28 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-27 19:04 AWE32 initialization wiht isapnp Alexis DOMJAN
1998-09-27 19:31 ` Bill Nottingham
1998-09-27 23:50 ` Ricardo Peres
1998-09-28 2:08 ` Sangohn Christian [this message]
1998-09-28 20:15 ` Emil Stephan
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-90703509605379@msgid-missing \
--to=sango-ch@reze-1.rz.rwth-aachen.de \
--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