Topic: Isa and unsuported pci NIC's

[Randy Brown]

Detailed Instructions on how to get an ISA NIC to work in e-smith and how to
get PCI NIC's that are supported by Linux but not the e-smith user interface.

Information that you will need:
1. The name of the driver for your NIC card.  
   (ne2000 = ne;, 3Com 509 = 3c509; CNet Pro200WL = dmfe)
    card #1____________; NIC #2______________
2. For ISA users, you will need the IO (mine is 0x240) of your NIC Card.
   (Most cards come with some dos utility on their driver disk that will give you
   the required Information.)
   NIC #1 IO = 0x_________ NIC #2 IO = 0x_________

The Scenario!  
You have just installed e-smith and you need to manually configure your NIC.

Linux is case sensitive!

1. Press ALT-F2 to get to a command consul.
2. Login as root, and enter your password.
3. Type in the following lines
   /sbin/e-smith/config set EthernetDriver1 3c509 < your driver here
   /sbin/e-smith/config set EthernetDriver2 3c509 < your driver here
4. Now add following lins to conf.modules by using pico.
   Pico /etc/conf.modules
   alias eth0 3c509  < your driver here
   alias eth1 3c509  < your driver here
   (For ISA cards you also need the following lines.)
   options eth0 io=0x < your IO here
   options eth1 io=0x < your IO here
5. To save press Ctrl-o, to exit press Ctrl-x.
6. Now type this.
   /sbin/e-smith/signal-event console-save
7. Press Alt -F1 to get back to the main menu and reboot.
8. After your reboot you can then continue your configuration and in Ethernet
   configuration just select #1 keep current configuration and continue.

You should now be live.
I hop that this was of some help to some of you out there.
All of the above information has been gathered from the e-smith user bulletin boards
at http://www.e-smith.org.

All Information Compiled by,
Randy Brown

I setup a lot of e-smith servers and use this information all off the time. So I will share it with you.

[Randy Brown]

Just a little up date.

   The new Beta's of e-smith no longer use conf.modules, they use modules.conf.

randy

[Michael R. McDonald]

Randy,

I am installing a wireless NIC (Cisco Aironet 340 - PCI) for Broadband internet access.  I have the aironet.o file and put it in the /lib/modules/x.x.x-x/net directory.  I reboot the e-smith server and get a 'unresolved symbols' error during the 'finding module dependancies' part of the boot up.


Could you shed come light on what steps I am missing.

I am currently running 4.0.1 of the Server/Gateway and just D/L'd the 4.1b2 (hoping it had the NIC driver - it didn't).

Thank You.

[Jose Q]

but how do i get the (ne.c or ne.o or ne.h ?) driver.
and where do i place it?

any help appreciated.

[Randy Brown]

it is already there!  : )

/sbin/modprobe ne io=0x240

[Randy Brown]

hay Michael,

  did you ever get your airo nic's working?

[SR]

Did this change in ver 4.1?  conf.modules does not work.  Looks like it is now modules.conf.

[SR]

Did this change in ver 4.1?  conf.modules does not work.  Looks like it is now modules.conf.

[Randy Brown]

e-smith 4.1 no longer use conf.modules, they use modules.conf

randy

[Edward Richardson]

I try to be brief.

I have followed these instruction (Several Times, and a couple of completely fresh installs), but am still unable to get any life from the NICs.

My equipment consists of the following:

2 x 3com Etherlink III (ISA based 509B Combo).
1 P100.
1 Intel motherboard.

I get 1 error on boot-up relating to the NIC (but it goes by so fast I can't read it), however the network part of the install reports as [OK].

When I try to manually start networking (/etc/rc.d/init.d/network), I get the message:

Delaying eth0....[FAILED].

I also get the dhcp demon (dhcpd) fail and ismod thread error relating to 3c509.0 error on shutdown.

I had this identical setup working on Red Hat Version 7 last week, with network access.

I know the problem relates to the kernel, but I'm relatively new to linux, and so kernel hacking is little out of my skill-set at the mo.

Does anybody have any suggestions, or should I just go out and buy a couple of PCI NICs? (Component prices are high here in the UK!)

Thanks for any help,

Eddy.