2 3Com 3c59x NICs

tarballedtux · 10-23-2001, 07:37 PM

I am having trouble getting two 3com 3c59x cards to detect.
One is detected and set up by Kudzu, the other is not detected.
The cards exactly the same.

Tell me if you need more information.

Thanks in advance.

acid_kewpie · 10-24-2001, 04:10 AM

does the card get listed in /proc/pci ?

mcleodnine · 10-24-2001, 09:06 AM

As A_K said you need to see if they were picked up by the PCI scan. If they were not, you'll need to find out why. Could be a plain old IRQ problem, so you may want to get the DOS setup program to fiddle with the addresses of the cards - or just reset them to factory defaults. You may also want to shuffle the actual PCI slot location of the cards as some boards 'reserve' a home for on-board devices (ATA controllers mostly).

If you can actually see the devices in /proc/pci you may want to try and get them up manually by using

Code:

modprobe 3c59x alias eth0

and

Code:

modprobe 3c59x alias eth1

If no errors result then you should be able to start your network.

tarballedtux · 10-24-2001, 11:09 AM

Ths is the contents of the /proc/pci file

Bus 0, device 13 function 0:
Ethernet Controller: 3Com 3595 100bTX(rev 0)
Medium devsel IRQ 10 Master Capable
I/O at 0xdcc0 [0xdcc1]

Bus 0, device 14 function 0:
Ethernet Controller: 3Com 3595 100bTX(rev 0)
Medium devsel IRQ 9 Master Capable
I/O at 0xdca0 [0xdca1]

To mention again these are identical cards non-onboard.

acid_kewpie · 10-24-2001, 12:35 PM

looks perfect to me, try installing them manually then, if kudzu isn't being helpful.

lsof · 10-24-2001, 11:09 PM

Quote:

Originally posted by tarballedtux
Ths is the contents of the /proc/pci file

Bus 0, device 13 function 0:
Ethernet Controller: 3Com 3595 100bTX(rev 0)
Medium devsel IRQ 10 Master Capable
I/O at 0xdcc0 [0xdcc1]

Bus 0, device 14 function 0:
Ethernet Controller: 3Com 3595 100bTX(rev 0)
Medium devsel IRQ 9 Master Capable
I/O at 0xdca0 [0xdca1]

To mention again these are identical cards non-onboard.

maybe also try as root:

/usr/bin/netcfg

or

/sbin/netconf

go to the interfaces section. check to see if u have eth0 & eth1.
edit them if u do, assign them with a ip etc... & set them to activate on boot.

hope this helps

acid_kewpie · 10-25-2001, 06:18 AM

for as and when they get up and running:

you're not planning on usign the cards on the same sub-network are you? if so, it aint gonna happen, not legal inlinux, it'll stop one working.

tarballedtux · 10-25-2001, 03:36 PM

How do I set it up manually?

Can you name all the possible methods for getting Linux to detect. i tried adding
alias eth1 3c59x
to modules.conf but nothing.

Where could i go to learn about the subnetting issue.
Does this subnetting problem occur with NT|2K, i'm trying to prove the Linux importance, so I am wondering if this is a Linux flaw or overall flaw.

acid_kewpie · 10-25-2001, 03:52 PM

it can easily be seen as a flaw, but going by the book, it is not.

ethernet, ieee802.3 is a bus network standard, whereby all machines in the network are connected via a direct common bus, typically provided by a Hub.

Packets are placed onto the bus via a broadcast to the bus, via a suitable NIC interface. Now if a machine has two cards on the same network, with the ame access rights, then you are trying to create a system whereby both interfaces are allowed to broadcast the same data. Now this will obviously cause a horrendous mess, as you can appreciate, both MAC's will recieve collisions, and resend data and all hell would break loose.

Windows doesn't bother addressing this issue, which although convenient on a small system, where daisy chaining is more appropriate that fast hub hardware.

anyway, your system:

ok, so once you've updated modules.conf run 'depmod' and then 'modprobe eth1'. Assuming you've configured the interface properly (meaning.. copy the existing ifcfg-eth0 file to ..eth1 and modify as needed) you should then be able to

ifup eth1

maybe.