From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Cc: meyers_j@freeshell1.65535.net
Subject: Re: sound card
Date: Sun, 23 Mar 2003 09:54:53 +0100 [thread overview]
Message-ID: <20030323085453.GN22528@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0303230840001.25376-100000@rimmer.65535.net>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
On Sun, 2003-03-23 08:43:40 +0000, meyers_j@freeshell1.65535.net <meyers_j@freeshell1.65535.net>
wrote in message <Pine.LNX.4.44.0303230840001.25376-100000@rimmer.65535.net>:
> I don't know exactly which card is on my friends board
Oh, come on. Is it onboard? Is it an add-on card? What does "lspci" tell
you? What mainboard is it? Please, if there's no other way, take a
screwdriver and have a look. If you fail to guess (looking at your
friend's machine), how can you expect us to correctly guess? And guess -
your question is most probably also off-topic...
> i thought it is soundblaster and tried ioport=0x220 which i found on the
> net.But it didn't work.SO is there any way of finding the address ?
> or any list to guess 0x230 etc
Just out of the courious, if that's a "modern" (read: inexpensive
mass-marked) computer, then it's most probable a SB Live (emu10k) or an
AC97 based codec. Google for that, but first look at "lspci" output.
It's most probably there...
> pnpdump shows
Are you *sure* this sound card is an ISA add-on card or ISA-based
connected to your friend's box? Most probably not...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-03-23 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 8:43 meyers_j
2003-03-23 8:54 ` Jan-Benedict Glaw [this message]
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=20030323085453.GN22528@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=meyers_j@freeshell1.65535.net \
/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
all inboxes | Powered by JetHome®