The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Simone Piunno <pioppo@ferrara.linux.it>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Cc: devel@ferrara.linux.it
Subject: 2.5.42 ACPI/Sb16 IRQ conflict
Date: Wed, 16 Oct 2002 22:29:08 +0200	[thread overview]
Message-ID: <20021016202907.GA2256@ferrara.linux.it> (raw)


Hi,

I'm trying 2.5.42 compiled with ACPI and OSS ISA-Pnp Soundblaster 16.
When playing audio, the sound is heavily chopped.
dmesg says:

ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
isapnp: Scanning for PnP cards...
isapnp: SB audio device quirk - increasing port range
isapnp: Card 'Creative SB16 PnP'
isapnp: 1 Plug & Play card detected total
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
[-cut-]
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
sb: Creative SB16 PnP detected
sb: ISAPnP reports 'Creative SB16 PnP' at i/o 0x220, irq 5, dma 1, 5
SB 4.13 detected OK (220)
sb: Interrupt test on IRQ5 failed - Probable IRQ conflict
<Sound Blaster 16 (4.13)> at 0x220 irq 5 dma 1,5
<Sound Blaster 16> at 0x330 irq 5 dma 0,0
sb: 1 Soundblaster PnP card(s) found.

Motherboard is Asus P5A.
Audio is compiled as a module
isapnp and ACPI are statically linked

With ALSA was even worse (no output at all).

After appending "pci=noapci" into lilo.conf, now OSS happily works
again without problems.  I haven't tried yet if ALSA too benefits
from pci=noapci.

Feel free to contact me if you need more info.

Regards,
Simone

-- 
Adde parvum parvo magnus acervus erit.
Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo

                 reply	other threads:[~2002-10-16 20:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021016202907.GA2256@ferrara.linux.it \
    --to=pioppo@ferrara.linux.it \
    --cc=devel@ferrara.linux.it \
    --cc=linux-kernel@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