Installing new/second ethernet card

There's nothing in /proc/pci because this machine does not have any PCI cards or even a slot for them. This is ISA ONLY! Anyway, here is /proc/interrupts:

  0:    4093400          XT-PIC  timer
  1:          4          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  4:         42          XT-PIC  serial
  8:          1          XT-PIC  rtc
 10:       5706          XT-PIC  eth0
 13:          0          XT-PIC  fpu
 14:     159985          XT-PIC  ide0
NMI:          0

It's not showing up there. When I run

insmod /lib/modules/2.2.14-5.0/net/ne.o

I get:

/lib/modules/2.2.14-5.0/net/ne.o: unresolved symbol ei_open
/lib/modules/2.2.14-5.0/net/ne.o: unresolved symbol ethdev_init
/lib/modules/2.2.14-5.0/net/ne.o: unresolved symbol ei_interrupt
/lib/modules/2.2.14-5.0/net/ne.o: unresolved symbol NS8390_init
/lib/modules/2.2.14-5.0/net/ne.o: unresolved symbol ei_close

How do I manually assign the IRQ and IO port? It seems like that's something I need to do (although I could be wrong).

The question is why you are getting unresolved symbols when trying to load the ne module. And I'll bet when that's fixed that your Netgear card will work. Time to play 20 questions...

Is this a stock 6.2 system running the as-distributed kernel? Is the ne.o module in /lib/modules/2.2.14-5 the one distributed with 6.2? What is the model number of the Netgear card? Are there any other errors in the boot up messages?

FYI: I don't know if you are aware of it, but the 2.2.14 kernel has three serious security flaws that can lead to a root compromise of your system. I'd invite you to take a look at http://www.redhat.com/support/errata/rh62-errata-security.html and seriously consider getting and applying all of those updates.

OK, here goes!

The system is as close to standard 6.2 as can be. I haven't fiddled with the kernel at all (I'm not yet that brave). Originally this started as a 5.2 system which was upgraded to 6.2, but all of it from original RedHat installation stuff. The ne.o module is the original one distributed with 6.2, I haven't touched that one bit. The Netgear card is an EA201c.

OK, in doing some more poking around in my modules.dep file, I see:

/lib/modules/2.2.14-5.0/net/ne.o:       /lib/modules/2.2.14-5.0/net/8390.o

So, I run insmod /lib/modules/2.2.14-5.0/net/8390.o and that goes ok, and then I ran insmod /lib/modules/2.2.14-5.0/net/ne.o and got:

lib/modules/2.2.14-5.0/net/ne.o: init_module: Device or resource busy

So, that's where we are at. I've got those security patches installed, too. thanks.

What is the other card in the system (eth0)? And do you know what IRQ & IO port the EA210 is set to? It'll need to be set to some unused IRQ & IO port (IRQ 5 looks to be free). The first time you booted the system with the Netgear card installed kudzu should have noticed that a new device had been added to the system and offer to configure the device for you. Did that happen?

No. I kept watch on that, hoping it would find the new device and configure it by itself, but to no avail. It looks like it's wanting me to somehow set the IRQ and IO port myself, based on the messages it's giving me. I booted into Win95 just to see what settings that gave it, and it assigned it to IRQ 12 and io 0x240, but as far as whether or not I can safely transfer those numbers to Linux (and even how I would go about doing that) I don't know.

There should be some software on the Netgear website that will be able to set the mem and IRQ settings for your NIC.  You should not be running the card in PnP mode, it probably won't work well...linux isn't 100% PnP compatible with ISA devices.

this thread is of particular import to me, as I am attempting virtually the same thing....  my server has 2 Netgear enet cards (both PCI,) one of which is connected to a DSL modem and the other to a local network.  If its not already obvious, the goal is the same - a Linux router, with IP masquerading.  Yesterday, a friend and I made some progress...

previously, I could not ping across both cards.. now I can.
The IRQ settings were the first problem.  Both cards set to IRQ B=11.  We were able to fix this through a setting in my motherboard's bios (perhaps that is a PCI function?)
we never did find a software tool to do this, so I hope this important step doesn't impeed your progress.

next, we discovered that although the (Redhat and Suse) installation program chose the tulip driver for both (one is an FA310, the other FA311,) I needed to compile and install the driver source provided by Netgear for the FA311 - and the installation specified by Netgear was incomplete.  Fortuneatly, reading the comments in the file FA311.c lead me to insmod, which ultimately finished the install.

and lastly (at least to this point,) the 311 did not live through reboot, so that I needed to re-issue the insmod command after reboot.  The man pages on insmod lead me to
the file (I'm writing this away from the machine, if its off a little) "/etc/modules.conf"  where I was able to modify the line for eth1 to read "alias eth1 fa311" - after which all this stuff came together.

Hope that all helps....

But now for my question...  somehow during all this, IP forwarding seems to have been disabled (or never was enabled.)  When, from another machine on the local network, I ping the remote gateway, the request times out.
Can anyone help me to get this functioning?

gljr:
Although this should get you started, you really should address this as a separate question so points can be awarded properly.

netcfg& --> Routing --> Gateway Device --> ppp0
Default Gateway should be assigned dynamically by ISP
Check "Network Packet Forwarding (IPv4)"
Should create /etc/sysconfig/network with contents:
NETWORKING=yes
FORWARD_IPV4=yes
HOSTNAME=host.domain
GATEWAY=
NISDOMAIN=""
GATEWAYDEV=ppp0


Should also put a "1" in /proc/sys/net/ipv4/ip_forward
If not, then:
echo "1" > /proc/sys/net/ipv4/ip_forward

If you are also using unregistered IP addresses, then you need ipchains.

all, please accept my apologies for mis-using this thread.
Yesterday was my first exposure to EE and I let my excitement get ahead of my understanding...

I have entered another question on EE to remedy this situation:   qid=20111928

dkloes, jlevie, if you leave (any) comment on that question
(and the comments here turn out to be sufficient,) I will gladly award you the points.

Hopefully you've already been helped with this question, but thought you'd appreciate knowing this.

WindowsUpdate has new updates for .NET users; Details follow - Microsoft .NET Framework
The .NET Framework is a new feature of Windows. Applications built using the .NET Framework are more reliable and secure. You need to install the .NET Framework only if you have software that requires it.

For more information about the .NET Framework, see http://www.microsoft.com/net. (This site is in English.)

System Requirements
The .NET Framework can be installed on the following operating systems:
Windows 98
Windows 98 Second Edition (SE)
Windows Millennium Edition (Windows Me)
Windows NT 4.0® (Workstation or Server) with Service Pack 6.0a
Windows 2000 with the latest service pack installed (Professional, Server, Datacenter Server, or Advanced Server)
Windows XP (Home Edition and Professional)
You must be running Internet Explorer version 5.01 or later for all installations of the .NET Framework.

To install the .NET Framework, your computer must meet or exceed the following software and hardware requirements:

Software requirements for server operating systems:
MDAC 2.6
Hardware requirements:
For computers running only a .NET Framework application, Pentium 90 mHz CPU with 32 MB memory or the minimum CPU and RAM required by the operating system, whichever is higher.
For server operating systems, Pentium 133 mHz CPU with 128 MB memory or the minimum CPU and RAM required by the operating system, whichever is higher.
Recomended software:
MDAC 2.7 is recommended.
Recommended hardware: For computers running only a .NET Framework application, Pentium 90 MHz CPU with 96 MB memory or the minimum CPU and RAM required by the operating system, whichever is higher.
For server operating systems, Pentium 133 MHz CPU with 256 MB memory or the minimum CPU and RAM required by the operating system, whichever is higher.

How to use -> Restart your computer to complete the installation. No other action is required to run .NET Framework applications. If you are developing applications using the .NET Framework, you can use the command-line compilers or you can use a development environment, such as Visual Studio .NET, that supports using the .NET Framework.

How to uninstall
To uninstall the .NET Framework: Click Start, point to Settings, and then click Control Panel (In Windows XP, click Start and then click Control Panel.).
Click Add/Remove Programs.
Click Microsoft .NET Framework (English) v1.0.3705 and then click Change/Remove.
More here  http://www.microsoft.com/net/

The .NET topic is being considered for addition to our All Topics link soon, so this may interest you as well:
http://www.experts-exchange.com/newtopics/Q.20276589.html

EXPERTS POINTS are waiting to be claimed here:  http://www.experts-exchange.com/commspt/Q.20277028.html

":0)
Asta

Well I am sure that you have figured out your problem by now.  However, since this question was never actually fully answered, I will try to do so now.  I was pretty much in the same boat as you were about a year ago.  I installed another network card into my old system so I can make a gateway out of it.  Since it only has one pci slot I had to get an ISA card and I happened to get the same Netgear EA201c.  I tried everything you did, read up on a few more newsgroups, then finally got everything to work.  So for all you ISA (Netgear EA201c to be specific) people out there here it is:
1) Check your BIOS, make sure plug and play oS is disabled
2) Boot up into DOS (try to find your old win98 boot disks somewhere) then put in the diskette that came with your netgear (or whoever your manufacturer is) card (you may be able to dl it from netgear's site).
3) Run the diagnostic program or setup program appropriate for your card (for netgear it was setup.exe)
4) Disable Plug and Play for the card and configure your I/O settings and if you want your interrupt (i don't think the interrupt really matters but definitely the I/O does)
5) Write down what you set the I/O to and the interrupt (just in case).  You might also want to write down the MAC addresses of each card for future reference.
6) Save your changes (write to the NIC's EEPROM), remove your diskette then boot into linux.
7) Now in /etc/conf.modules you would type something like this:  
     alias eth0 ne
     options ne io=0x###

where ### is the I/O setting you wrote down in step 5.  Don't forget it has to be in the format 0x###.  More info at:
 
http://www.linuxpowered.com/archive/howto/Net-HOWTO-6.html

Oh yeah if you use Debian you should use /usr/sbin/modconf, select the right module, and in the command line options type io=0x###, and install into the kernel.
8) Type:
     modprobe ne

9) If it still doesn't work try:
http://www.google.com/linux

For you Debian people trying to figure out how to setup an alias for your newly installed network card, use /etc/network/interface to set up your card (ex. eth0 or eth1, etc...etc...)  The kernel is smart enough to figure it out it seems (I think the order depends on the listing in /etc/modules).

http://www.debian.org/doc/manuals/reference/ch-gateway.en.html

if you need more help.

Hope this helps.

andyring:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations!  No comment means you don't care.