From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Taco IJsselmuiden <taco@wep.tudelft.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ne2000 (ISA) & test11+
Date: Tue, 02 Jan 2001 03:27:52 -0500 [thread overview]
Message-ID: <3A519108.23A41385@yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101020157290.637-100000@hewpac.taco.dhs.org>
Taco IJsselmuiden wrote:
>
> Second: I'm having problems loading my ne2000 (ISA) card as a module since
> test11 (test10 + 2.2.17 works perfectly. Haven't tried 2.2.18...):
>
> When loading the module with 'modprobe ne io=0x360 irq=4' it says:
>
> /lib/modules/2.4.0-prerelease/kernel/drivers/net/ne.o: init_module: No
> such device or address
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters
>
> When using test10 or 2.2.17 it works ;)
> I'm I just being plain stupid (as in: did I miss something...), or is
> something wrong ??
Ok, I suspect the phasing out of check_region(...) is responsible
here. In test10 and older, check_region() wasn't done if an explicit
i/o address was supplied - this was to accomodate the now rarely used
reserve= bootprompt which dates back to before modules existed.
Since ne.c doesn't allow modular autoprobing, there was always an i/o
address present, and hence you could still load the module even if
there was a potential i/o space conflict.
In test11 and newer, check_region() is gone and an unconditional
request_region() takes place, which will not allow any i/o space
conflict. In your case, 0x360 is suspect since a ne2000 is 0x20
wide in i/o space and you are probably bumping into either:
0376-0376 : ide1
0378-037a : parport0
Check your /proc/ioports, and relocate your ne card as appropriate.
Paul.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-02 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 1:08 ne2000 (ISA) & test11+ Taco IJsselmuiden
2001-01-02 8:27 ` Paul Gortmaker [this message]
2001-01-02 9:51 ` Taco IJsselmuiden
-- strict thread matches above, loose matches on Subject: below --
2001-01-02 1:48 Les Schaffer
2001-01-02 9:12 ` Paul Gortmaker
2001-01-02 13:23 ` Les Schaffer
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=3A519108.23A41385@yahoo.com \
--to=p_gortmaker@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=taco@wep.tudelft.nl \
/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.