All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Nehring <dnehring@telemedia.de>
To: linux-sound@vger.kernel.org
Subject: Re: AWE32 PNP not working with 2.1.13x/2.2.0-prex
Date: Fri, 01 Jan 1999 18:06:24 +0000	[thread overview]
Message-ID: <marc-linux-sound-91521608300406@msgid-missing> (raw)

On Wed, Dec 30, 1998 at 11:51:22PM +0100, Dirk Nehring wrote:
> Hi,
>
> it is impossible to run my AWE32 PNP with a prestine 2.1.13x or higher
> kernel. It works flawlessly under 2.0 and 2.0 with the commercial OSS
> drivers. I use the same settings under 2.1, but it failed:
>
> root@titan:~$ modprobe sb
> SB 4.13 detected OK (220)
> sb: Interrupt test on IRQ5 failed - Probable IRQ conflict
>
> isapnp.conf is correct:
>
> [...]
> #     ANSI string -->Creative SB AWE32 PnP<--
> (CONFIGURE CTL0043/80381 (LD 1
> #     ANSI string -->Audio<--
>  (INT 0 (IRQ 5 (MODE +E)))
>  (DMA 0 (CHANNEL 1))
>  (DMA 1 (CHANNEL 5))
>  (IO 0 (BASE 0x0220))
>  (IO 1 (BASE 0x0330))
>  (IO 2 (BASE 0x0388))
>  (ACT Y)
> ))
> [...]
>
> It also doesn't work with other tested interrupts.
>
> Do anyone have an idea?

I've found the bug: pnpdump 1.15 from RedHat 5.2 is broken (doesn't
reset the LD counters for new cards). I upgraded to 1.17 and it
magically works. Something for the FAQ?

Dirk

--
Dirk Nehring                 | Phone: +49 5241 80-<censored>
Telemedia Bertelsmann AG     | Fax:   +49 5241 80-9518
Carl-Bertelsmann-Str. 161 I  | E-Mail: dnehring @ telemedia.de
33311 Gütersloh              |

             reply	other threads:[~1999-01-01 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-01 18:06 Dirk Nehring [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-12-30 22:51 AWE32 PNP not working with 2.1.13x/2.2.0-prex Dirk Nehring

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-91521608300406@msgid-missing \
    --to=dnehring@telemedia.de \
    --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 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.