From: fe88 <fe88@dial.pipex.com>
To: linux-sound@vger.kernel.org
Subject: AWE64 Gold
Date: Sat, 15 May 1999 09:39:40 +0000 [thread overview]
Message-ID: <marc-linux-sound-92679833902066@msgid-missing> (raw)
Hi Folks
Help, AAARRRRRRRRRGhhhhhhhhhhhh !
I've done a seriously large amount of RTFM of numerous FAQ's, HOWTO's and
other documentation that are sound related out on the Web and in the kernel
source tree and getting this blighter to work is still proving elusive. I even
went through a proof reading exercise this week on the ALSA-sound-mini-HOWTO
to help me understand this more. 99% of the documentation is excellent, some
that I have come across could be taken as being contradictory and more than a
little confusing unfortunately.
Before I go ahead and post the contents of the usual suspects, dmesg, cat
/dev/sndstat, /etc/isapnp.conf, etc/conf.modules, cat /proc/ioports, procinfo
and the sound section from the kernel configure file etcetera for your
amusement I have a couple of simple requests:
If there is anyone on this listing who has succeeded in getting the AWE64 to
work please could they share copies of their /etc/isapnp.conf,
/etc/conf.modules and the sound section from the kernel configure file with
us. Does some of the #define #undef of awe_configure.h in the kernel source
need some editing ? To my eye there seems to be a couple of #define that
should be included there which I have tried but to no avail though.
My feeling is that once I have sight of genuine working versions of these
three main items I will be able to edit my own versions appropriately and if
needed do another kernel recompile...
Currently running RH6. 2.2.9 kernel with SMP.
Hoping someone can cure this growing feeling of frustration.
Cheers
--
Steve Crowder clerk.kant@dial.pipex.com
reply other threads:[~1999-05-15 9:39 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-92679833902066@msgid-missing \
--to=fe88@dial.pipex.com \
--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