public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: trelane@digitasaru.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: SoundBlaster 64 AWE and 2.6.1-mm1?
Date: Sun, 11 Jan 2004 07:09:46 +0100	[thread overview]
Message-ID: <4000E8AA.5040108@keyaccess.nl> (raw)
In-Reply-To: <20040110191950.GD5002@digitasaru.net>

Joseph Pingenot wrote:

> For some reason, while pnp detects the SoundBlaster card, it's not
>   recognized by ALSA for some reason, exactly as the CS4236 card was
>   (different machine, tho).
> Am I missing something?  Anyone using SoundBlaster 64 AWE under 2.6?

Yes, I am. If ALSA comletely ignores the card, it's likely that it
simply does not know it _should_ be driving it, that is, that it doesn't
list your card's PnP ID. You can check your card's ID(s) at:

cat /sys/bus/pnp/devices/01:??.O{0,1,2}

Example for my AWE64:

rene@7ixe4:~$ cat /sys/bus/pnp/devices/01:01.00/id
CTL0044
rene@7ixe4:~$ cat /sys/bus/pnp/devices/01:01.01/id
CTL7002
PNPb02f
rene@7ixe4:~$ cat /sys/bus/pnp/devices/01:01.02/id
CTL0023

That second device is the gameport and will be picked up by ns558.c
through the "compatible device" PNPb02f ID, but you'll need the 00
(SB/MPU/OPL part) and the 02 ID (wavetable) listed in
sound/isa/sb/sb16.c. Add them to the snd_sb16_pnpids[] table in that file.

Hope this helps,
Rene.



  reply	other threads:[~2004-01-11  6:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 19:19 SoundBlaster 64 AWE and 2.6.1-mm1? Joseph Pingenot
2004-01-11  6:09 ` Rene Herman [this message]
2004-01-11 22:17 ` Lucas de Souza Santos

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=4000E8AA.5040108@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trelane@digitasaru.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