linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: klink@clouddancer.com (Colonel)
To: kernel@Expansa.sns.it, linux-kernel@vger.kernel.org
Date: Wed, 13 Jun 2001 03:40:51 -0700 (PDT)	[thread overview]
raw)

From: Colonel <klink@clouddancer.com>
To: kernel@Expansa.sns.it
CC: linux-kernel@vger.kernel.org
In-reply-to: <Pine.LNX.4.33.0106131130200.22415-100000@Expansa.sns.it>
	(message from Luigi Genoni on Wed, 13 Jun 2001 11:32:35 +0200 (CEST))
Subject: Re: your mail
Reply-to: klink@clouddancer.com
In-Reply-To:  <Pine.LNX.4.33.0106131130200.22415-100000@Expansa.sns.it>

   Date: Wed, 13 Jun 2001 11:32:35 +0200 (CEST)
   From: Luigi Genoni <kernel@Expansa.sns.it>
   Cc: <linux-kernel@vger.kernel.org>
   Content-Type: TEXT/PLAIN; charset=US-ASCII

   I have the sound blaster 16 card on one of my athlon (on PIII i have
   es1731), that has one isa slot on its MB.
   It works well, but i do not use isapnp nor any pnp support is enabled
   inside of the kernel.
   running 2.4.5/2.4.6-pre2

   Luigi


Yes, dropping any PNP support does resolve the problem.  For my
installation, I don't need PNP support, so it's OK.  The bug is in the
communication between the 2 modules.




   On Tue, 12 Jun 2001, Colonel wrote:

   > From: Colonel <klink@clouddancer.com>
   > To: linux-kernel@vger.kernel.org
   > Subject: ISA Soundblaster problem
   > Reply-to: klink@clouddancer.com
   >
   >
   > The Maintainers list does not contain anyone for 2.4 Soundblaster
   > modules, so perhaps some one on the mailing list is aware of a
   > solution.  My ISA Soundblaster 16waveffects worked fine in kernel 2.2
   > with XMMS.  But I have never been successful in a varity of 2.4
   > kernels, the latest being 2.4.5-ac12.  This is what I know:
   >
   > [DMESG]
   > isapnp: Scanning for PnP cards...
   > isapnp: Calling quirk for 01:00
   > isapnp: SB audio device quirk - increasing port range
   > isapnp: Card 'Creative SB16 PnP'
   > isapnp: 1 Plug & Play card detected total
   >
   > }modprobe sb
   > /lib/modules/2.4.5-ac12/kernel/drivers/sound/sb.o: init_module: No such device
   > /lib/modules/2.4.5-ac12/kernel/drivers/sound/sb.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
   > /lib/modules/2.4.5-ac12/kernel/drivers/sound/sb.o: insmod /lib/modules/2.4.5-ac12/kernel/drivers/sound/sb.o failed
   > /lib/modules/2.4.5-ac12/kernel/drivers/sound/sb.o: insmod sb failed
   >
   >
   > [/etc/modules.conf]
   > options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
   >
   >
   > [DMESG}
   > Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
   > sb: No ISAPnP cards found, trying standard ones...
   > sb: dsp reset failed.
   >
   >
   > So it seems that PnP finds the card, but the connections (or even the
   > forced values) to the sb module fail.  Back when this was a single
   > processor machine, but still running 2.4 kernel, a windoze
   > installation found the SB at the listed interface parameters.
   >
   >
   > Anyone have a solution?
   >
   > Same problem without modules.conf settings, valid version of mod
   > utilities, a web search did not help,...

                 reply	other threads:[~2001-06-13 10:41 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=20010613104051.247C778599@mail.clouddancer.com \
    --to=klink@clouddancer.com \
    --cc=kernel@Expansa.sns.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;
as well as URLs for NNTP newsgroup(s).