From: Chris Ruvolo <chris+lkml@ruvolo.net>
To: Adam Belay <ambx1@neo.rr.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net,
Jaroslav Kysela <perex@suse.cz>
Subject: alsa sbawe fails w/o isapnp (was: garbage in /proc/ioports and oops)
Date: Mon, 28 Jul 2003 09:20:18 -0700 [thread overview]
Message-ID: <20030728162018.GA24886@ruvolo.net> (raw)
In-Reply-To: <20030727224357.GA27040@neo.rr.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
On Sun, Jul 27, 2003 at 10:43:57PM +0000, Adam Belay wrote:
> > The fix would be to run release_region() either at the end of
> > snd_sb16_probe() or on module unload.
> >
> > Adam or Jaroslav, could you please take care of this?
>
> I believe this will fix it. Testing would be appreciated.
Adam,
Yes, this looks good. The module loads and fails cleanly. /proc/ioports is
then readable. Thanks for this fix.
However, this doesn't fix the loading of the module without in-kernel isapnp.
# modprobe --verbose snd-sbawe
insmod /lib/modules/2.6.0-test1/kernel/sound/isa/sb/snd-sbawe.ko
sbawe: fatal error - EMU-8000 synthesizer not detected at 0x620
Sound Blaster 16 soundcard not found or device busy
In case, if you have non-AWE card, try snd-sb16 module
FATAL: Error inserting snd_sbawe (/lib/modules/2.6.0-test1/kernel/sound/isa/sb/snd-sbawe.ko): No such device
Specifying the parameters (port, irq, awe_port, etc.) doesn't seem to help.
In-kernel isapnp has been working though.
Thanks
-Chris
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-07-28 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 1:11 2.6.0-t1 garbage in /proc/ioports and oops Chris Ruvolo
2003-07-18 4:15 ` Andrew Morton
2003-07-18 15:04 ` Chris Ruvolo
2003-07-27 23:38 ` Andrew Morton
2003-07-27 22:43 ` Adam Belay
2003-07-28 16:20 ` Chris Ruvolo [this message]
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=20030728162018.GA24886@ruvolo.net \
--to=chris+lkml@ruvolo.net \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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).