Problems with multiple NE2000

Eric Jorgensen
Fri Apr 21 12:16:30 2000

	You're right, it doesn't have anything to do with the tulip driver. But
i can help you anyway. 

	I am starting from the presumption that you are using ISA cards.
Further, that you are not using genuine Eagle NE2000's but probably the
more recent clone PnP boards. 

	The first step, of course, to configure them manually and write down
the configuration. ISA PnP is for the birds, I avoid it whenever

	The second step is to load the module with the correct module
arguments. That would be, include the io addresses of the nics

	Therefore, if you had four RTL8019's at io's 300, 320, 340, and 360,
you'd load the module like this: 

modprobe ne io=0x0300,0x0320,0x0340,0x0360

	This will load the 300 card as eth0, the 320 as eth1, etc. 

	Now, that's good enough for government work but you can do better. 

	Edit /etc/conf.modules and add something like this: 

alias eth0 ne
options ne io=0x0300,0x0320,0x0340,0x0360

	And the module should be automagically loaded when the system tries to
ifconfig eth0. 

	Good luck. 

 - Eric wrote:
> Dave Pfaltzgraff@PATAPSCO
> 04/21/2000 08:13 AM
> I know that this is not a problem with the tulip driver per se, but I'm not sure
> where to address this. If there is a better forum, please direct me.
> I am trying to get two NE2000 cards to operate in the same system (Slackware
> 7.0, kernel 2.2.13). I have been unsuccessful, even with the advice of several
> others concerning conf.modules, etc. My only success was to compile the NE2000
> into the kernel and append the parameters into LILO.
> Since I'd like to understand the module approach and why this behaves as it
> does, I'd appreciate some help.
> Thanks,
> Dave
> -------------------------------------------------------------------
> To unsubscribe send a message body containing "unsubscribe"
> to
To unsubscribe send a message body containing "unsubscribe"