From: Bill Nottingham <notting@redhat.com>
To: linux-sound@vger.kernel.org
Subject: Re: 2.1.128 : AWE64 problems
Date: Sun, 15 Nov 1998 19:20:44 +0000 [thread overview]
Message-ID: <marc-linux-sound-91116360111597@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91107867019319@msgid-missing>
Andy Jefferson (andy@ajsoft.demon.co.uk) said:
> and insmodding the awe_wave.o (whereas on 2.0.35, I didn't need to do this).
>
> i.e there are no Installed drivers !
Actually, that's the normal output for the sound drivers
as modules - it looks like it's working fine.
Does the sound device work OK?
Bill
next prev parent reply other threads:[~1998-11-15 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-14 15:03 2.1.128 : AWE64 problems Andy Jefferson
1998-11-15 19:20 ` Bill Nottingham [this message]
1998-11-16 12:17 ` Andy Jefferson
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-91116360111597@msgid-missing \
--to=notting@redhat.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