[gentoo-user] NE module, modprobe, etc.

[gentoo-user] NE module, modprobe, etc.

[Paul M Foster]

I've got an older machine whose NIC uses the ne module. When I run 
generate-modprobe.conf, I get the following two lines (among others) in 
my modprobe.conf:

alias ne off
install eth0 /bin/true

If I change the one line to:

alias eth0 ne

and add this line:

options ne io=0x330

and remove the "install eth0 /bin/true" line, I can "modprobe ne" and 
it will load fine. My /etc/modules.autoload.d/kernel-2.6 file contains 
(among other lines) the following:

ne
options ne io=0x300

This is all gentoo 2005.0. I'm brand new to this, so could someone 
explain to me what is causing the original two lines in the 
modprobe.conf file, and what file I can edit (and how) to make the 
modules system do what I want?

Paul

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NE module, modprobe, etc.

[William Kenworthy]

You will also need the irq (irq=5) - may have to pull the card and check
the jumpers, who load doze and see if it finds it if dual booted.

This link gives some more info:
http://clarkconnect.com/wiki/index.php?title=ISA_Network_Cards

BillK


On Sun, 2005-08-07 at 18:17 -0400, Paul M Foster wrote:
> I've got an older machine whose NIC uses the ne module. When I run 
> generate-modprobe.conf, I get the following two lines (among others) in 
> my modprobe.conf:
> 
> alias ne off
> install eth0 /bin/true
> 
> If I change the one line to:
> 
> alias eth0 ne
> 
> and add this line:
> 
> options ne io=0x330


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NE module, modprobe, etc.

[Paul M Foster]

On Mon, Aug 08, 2005 at 06:39:09AM +0800, William Kenworthy wrote:

> You will also need the irq (irq=5) - may have to pull the card and check
> the jumpers, who load doze and see if it finds it if dual booted.
> 
> This link gives some more info:
> http://clarkconnect.com/wiki/index.php?title=ISA_Network_Cards
> 

The IRQ is not needed on the ne driver unless you have more than one ne 
card in the machine.

Paul


> 
> On Sun, 2005-08-07 at 18:17 -0400, Paul M Foster wrote:
> > I've got an older machine whose NIC uses the ne module. When I run
> > generate-modprobe.conf, I get the following two lines (among others) in
> > my modprobe.conf:
> >
> > alias ne off
> > install eth0 /bin/true
> >
> > If I change the one line to:
> >
> > alias eth0 ne
> >
> > and add this line:
> >
> > options ne io=0x330
> 
> 
> --
> gentoo-user@gentoo.org mailing list
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NE module, modprobe, etc.

[W.Kenworthy]

Experience across a number of cards on a number of machines (both
running 2.4 and early 2.6 kernels) says otherwise - and its not working
so its worth a try!  In fact, I cant remember it ever working without
the irq option, even if the card uses "auto".  This brings up another
memory - some cards refuse to work under auto, or plugnplay setting
(planet I think in my case), I had to force a fixed IRQ with a jumper
(nominally the same as the auto seemed to be).

BillK


On Sun, 2005-08-07 at 22:14 -0400, Paul M Foster wrote:
> On Mon, Aug 08, 2005 at 06:39:09AM +0800, William Kenworthy wrote:
> 
> > You will also need the irq (irq=5) - may have to pull the card and check
> > the jumpers, who load doze and see if it finds it if dual booted.
> > 
> > This link gives some more info:
> > http://clarkconnect.com/wiki/index.php?title=ISA_Network_Cards
> > 
> 
> The IRQ is not needed on the ne driver unless you have more than one ne 
> card in the machine.
> 
> Paul
> 
> 
> > 
> > On Sun, 2005-08-07 at 18:17 -0400, Paul M Foster wrote:
> > > I've got an older machine whose NIC uses the ne module. When I run
> > > generate-modprobe.conf, I get the following two lines (among others) in
> > > my modprobe.conf:
> > >
> > > alias ne off
> > > install eth0 /bin/true
> > >
> > > If I change the one line to:
> > >
> > > alias eth0 ne
> > >
> > > and add this line:
> > >
> > > options ne io=0x330
> > 
> > 
> > --
> > gentoo-user@gentoo.org mailing list

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NE module, modprobe, etc.

[Nick Rout]

On Mon, 08 Aug 2005 10:41:56 +0800
W.Kenworthy wrote:

> Experience across a number of cards on a number of machines (both
> running 2.4 and early 2.6 kernels) says otherwise - and its not working
> so its worth a try!  

actually if you read the original post the card IS working, the original
question was asking about how a certain setting got set, as below:

> I've got an older machine whose NIC uses the ne module. When I run 
> generate-modprobe.conf, I get the following two lines (among others) in 
> my modprobe.conf:

[snip]

> This is all gentoo 2005.0. I'm brand new to this, so could someone 
> explain to me what is causing the original two lines in the 
> modprobe.conf file, and what file I can edit (and how) to make the 
> modules system do what I want?


And the answer I suspect may be running a script called "generate-modprobe.conf"
which I have never heard of. Unless something has changed the script is
"update-modules" on gentoo.

generate-modprobe.conf seems to come from module-init-tools and
update-modules from baselayout. I suspect that the former is generic and
the latter specific to gentoo. 

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NE module, modprobe, etc.

[Paul M Foster]

On Mon, Aug 08, 2005 at 10:41:56AM +0800, W.Kenworthy wrote:

> Experience across a number of cards on a number of machines (both
> running 2.4 and early 2.6 kernels) says otherwise - and its not working
> so its worth a try!  In fact, I cant remember it ever working without
> the irq option, even if the card uses "auto".  This brings up another
> memory - some cards refuse to work under auto, or plugnplay setting
> (planet I think in my case), I had to force a fixed IRQ with a jumper
> (nominally the same as the auto seemed to be).
> 

Be that as it may, if you check my original post, you'll see that (after 
hacking the config files manually) I was able to run modprobe ne 
io=0x300 and the module would load, without specifying the IRQ setting.

Aside from that, the original problem wasn't that I couldn't load the 
module. I could, but only _if_ I hacked the config files manually, in a 
way you weren't supposed to do. So the original question was how to hack 
them _correctly_ to make the load occur _automatically_.

Paul

-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] NE module, modprobe, etc.

[Michael Kintzios]

> -----Original Message-----
> From: W.Kenworthy [mailto:billk@iinet.net.au] 
> Sent: 08 August 2005 03:42
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] NE module, modprobe, etc.
> 
> 
> Experience across a number of cards on a number of machines (both
> running 2.4 and early 2.6 kernels) says otherwise - and its 
> not working
> so its worth a try!  In fact, I cant remember it ever working without
> the irq option, even if the card uses "auto".  This brings up another
> memory - some cards refuse to work under auto, or plugnplay setting
> (planet I think in my case), I had to force a fixed IRQ with a jumper
> (nominally the same as the auto seemed to be).

Whenever I boot a LiveCD (Gentoo, Knoppix, etc.) I have to kick start
mine by:
===============
modprobe ne io=0x300 irq=3
===============
If you have M$Windoze check which irq the card uses and adjust
accordingly.
-- 
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list