Re: Second Ethernet Card/IP Masquerading

["Adam Alexander" <adam tjconline com>]

Jonathan-

Those cards' IRQ settings and other hardware configuration information are
stored on an EEPROM on the card.  Providing parameters to the module can NOT
change the IRQs those cards are set to use.  What you need to do is go to
3com's site (http://support.3com.com/infodeli/tools/nic/3c509.htm) and
download the first file on that page "V5.1 Etherdisk for the 3C509 and
3C509B Etherlink III NIC" and extract that file onto a bootable DOS
diskette.  Then boot from the disk, run 3c5x9cfg.exe and set the cards to
two different IRQs and make sure there are no other conflicts.  They should
also be taken out of plug'n'play mode if they are set to use plug'n'play.
If that program only sees one card (which it shouldn't) then try taking one
card out and configure them one at a time.  At any rate, once there are no
more conflicts, then simply loading the module for the card will detect both
cards and set them up accordingly.  Good luck!  =)

Adam Alexander


-----Original Message-----
From: Jonathan Bossman <jonbos columbus rr com>
To: redhat-list redhat com <redhat-list redhat com>
Date: Tuesday, December 29, 1998 7:18 PM
Subject: Second Ethernet Card/IP Masquerading


>Running 5.1 (Linux 2.0.34) Cannot proceed with IP Maquerading without
>getting my two 3com 3c509 cards to be recognized with different IRQs and
>i/o addresses. My first and 2nd cards are  both assigned IRQ 10 at boot
>time, no matter what I do.
>
>There's a lot of info on the Web on how to set it up. Simplest way, I
>read, is to enable auto-probing of both cards by editing the
>etc/conf.modules file like
>this:
>alias eth0 3c509
>alias eth1 3c509....
>... then reboot. Didn't work for me. It appears that of all the 3com
>{driver}.o modules, 3c509.o is the only one that will not take explicit
>"io" and "irq" parameters. So you can't specify your i/o addresses or
>Irq settings.
>
>Have tried passing parameters to the kernel at boot time like this:
>ether=0,0,0,0,eth0 . (During one reinstall). Didn't work either.
>In desperation, attempted to force the probing of eth1. Modified the
>kernel netcard probe tables in drivers/net/Space.c, recompiled the
>kernel and rebooted. That failed too.
>
>In all these scenarios, both cards were recognized, but both were on IRQ
>10!!
>Surely there's someone out there with two 3c509 cards on a Redhat 5.x
>system who's gotten this to work.
>
>Any help would be appreciated.
>Jon.