From: Robert Joop <rj@rainbow.in-berlin.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: help needed for my AD1816A based soundcard
Date: Sat, 30 Mar 2002 21:27:13 +0100 [thread overview]
Message-ID: <20020330202713.GF707@rainbow.internal> (raw)
In-Reply-To: <20020329230421.GD707@rainbow.internal>
On 02-03-30 00:04:21 MET, Robert Joop wrote:
> alsa's ad1816a driver doesn't find my card.
> i've ISAPNP turned on.
> the card is a Highscreen Sound-Boostar 32 Wave 3D, it doesn't seem to
> have an entry in card-ad1816a.c.
> the entries in snd_ad1816a_pnpids[] look rather esoteric and i haven't
> found any documentation on adding an entry.
> how do i collect the necessary information?
> is it sufficient just adding an entry to the array?
>
> the card has an AD1816A and two DSP chips on it.
>
> (btw, with kernel 2.2.x's sb driver the card worked, but 2.4.18's sb it
> hangs the computer.
> and kernel 2.4.18's ad1816 driver doesn't detect the card either.)
btw, i'm using debian's alsa-source 0.9+0beta10-6 package.
what makes me wonder is:
- at boot time, the BIOS says it initializes the plug and play cards
and detects the sound card, it prints its name.
- but the linux ISA PNP does not seem to detect it:
Mar 30 19:20:13 moonbow kernel: isapnp: Scanning for PnP cards...
Mar 30 19:20:13 moonbow kernel: isapnp: No Plug & Play device found
- nor does the soundcard driver:
Mar 30 19:20:18 moonbow kernel: ALSA card-ad1816a.c:348: no AD1816A based soundcards found.
i've tried to make some sense of the output of pnpdump(1) and added an
entry to snd_ad1816a_pnpids[], but it hasn't helped.
rj
next prev parent reply other threads:[~2002-03-30 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 23:04 help needed for my AD1816A based soundcard Robert Joop
2002-03-30 20:27 ` Robert Joop [this message]
2002-03-30 21:53 ` Robert Siemer
2002-03-31 0:48 ` Robert Joop
2002-03-31 1:25 ` Robert Siemer
2002-03-31 11:38 ` Robert Joop
2002-03-31 11:53 ` Robert Joop
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=20020330202713.GF707@rainbow.internal \
--to=rj@rainbow.in-berlin.de \
--cc=alsa-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.