Conference nlfdc::linux-users

582.0. "Second Ethernet card not seen?" by LORRIN::LEE () Sat Mar 08 1997 05:36

    
    
    	Hello,
    
    	I am running RedHat 4.1 Linux on the following equipment.
    	Digital 486-DX266, 24 meg of memory, DE205 ethernet controller.
    	Everything works fine in this configuration, Samba, NFS, Telnet,
    	pushing Xwindows, etc. 
    
    	BUT- I am trying to add a second DE205 Ethernet controller to play
    	with the Firewall stuff (ipfw) and IP masquerading, etc. I have
    	tried for a couple of days, with all permutations of Lilo.conf,
    	and DE205 addresses, but I can't seem to get Linux to see the
    	second controller. If I pull the first DE205, the second one is
    	seen, and works fine. I have reserved the address space for the
    	second controller using the "append" command in lilo.conf,
    	specified the actual Irq and address, etc., but I always get
    	the message "Delaying eth1 initialization". After the system comes
    	up, device eth1 is not there. If I try to use "insmod ewrk3", I
    	am told that the ewrk3 module is already loaded (makes sense, it's
    	already driving the first controller). I also have always gotten
    	the message "SIOCTRL- Invalid argument" (or something close)
    	immediately after the first card is seen, even when the system
    	was first built with only one controller, and nothing added to
    	lilo.conf (and was working fine on one DE205).
    
    	Example: 
    	append="ether=10,0x340,eth1"
    	or
    	append="reserve=0x340,32 ether=10,0x340,eth1"
    	or 
    	append="ether=0,0,eth1"
    	and many, many others.	
    
    	Has anyone got any ideas or suggestions?
    
    							Thanks,			
    							Lorrin Lee

The trouble is that the kernel-supplied "ether=" parameters are designed for
drivers compiled into the kernel, not loaded as modules.  If you want to 
pass these parameters to a module, you can do so on the "insmod" or "modprobe"
command line, giving the appropriate values for both cards at once: for 
example,

	insmod ewrk3 io=0x300,0x340 irq=10,11

Under RedHat, most drivers are modules, and you can put the insmod command
into /etc/rc.d/rc.modules to force the module to be loaded and initialised
appropriately during boot time.

Alternatively, if you are already running with the ewrk3 driver on eth0 and
want to start up eth1 afterwards, you should be able to load another instance
of the driver using a different internal name: for example,

	insmod ewrk3 -o ewrk3-eth1 io=0x340 irq=11

 Stephen.

    
    Thanks for the help, everything works fine now.
    
    
    						Thanks,
    						Lorrin Lee