Topic: 3C509TP NICs Not Transmitting

[Brian Barber]

I've had this problem with RedHat installs.  After installing, I compile 3c509 support into the kernel and the NIC initializes, but neither transmits nor receives.  When loading as a module, the NICs work no problem.

Upon installing e-smith, I get the same thing once I configure it to use 3C509TP NICs - one in a dial-up configuration, two in a dedicated configuration.

Can anyone out there help?

[Peter Hollandare]

In "Admin mode" choose *any* card, press F2 and a new console window opens.
Log in as root with your admin password.

Execute the following command : /sbin/e-smith/config set EthernetDriver1 3C509 .

Do the same if nick 2 is a 3C509, but change the 1 to 2.

After that, execute this command : /sbin/e-smith/signal-event console-save (This takes a while, upto 2-3min depending how fast puter you have).

Go back to the config menu (alt F1) - now go back to config nicks, and the 3C509 will show, choose ok to use them.

Hope this helps.

[Brian Barber]

I actually completed these steps to get the cards to initialize.  As I said, the cards initialize and e-smith recognizes them, but they neither transmit nor receive.  I have four of these cards and all exhibit the same behaviour.  I also have eliminated the possibility of bad cables and bad ports on the hub.

Any suggestions?

BB

[ed sharpe archivist for]

Brain, are these new or used cards...
One time in my distant past I came across a batch of network cards... all the same.... used..... alas they turned out to be
a group of the dead ones a large company that used  oddles of this one particular type, had discarded! THEY WERE ALL BAD.... I almost lost my mind checking through them... could this be the case here perhaps?

thanks ed sharpe archivist  for smecc

see amazing olde technology at
www.smecc.org

[Brian Barber]

A very good point.  All cards are used, but they all work under Windows, and they also all work under Linux when driver support is configured in the kernel to load as a module, and not compiled directly into the kernel.

I believe that it is the "compiled into the kernel" thing that is at issue here.  If there's any e-smith folks reading this thread, I'm willing to lend you my cards to see if it is the software or a general Linux kernel thing.

Cheers,
BB

[ed sharpe archivist for]

ok then if they work that far they should be ok!
the batch I got were dead dead dead!

ed!

[Peter Hollandare]

Brian,

Have you checked for IRQ conflicts? Theres a software on 3COM's homepage to change irq/dma + PnP (Plug and Pray:).

[Brian Barber]

Thank you, Peter, for jogging my memory.  I did a cat /proc/interrupts and found that eth0 was getting the IRQ I configured the NIC with (10).  I then restarted the machine and went into the PCI Management section of my BIOS to see what IRQs were available to be assigned to PCI cards and IRQ 10 was at the top of the list.  In my estimation, the PCI video card grabbed 10 which explains why the NIC initialized and then didn't do anything.

What a rookie error.  I should be sent down to AAA on a rehab assignment.

Sincerest thanks to all who took the time and effort to respond.  I appreciated every response as it prevented me from overlooking even the smallest aspect of the configuration.

Cheers,
BB