It Works ! Re: 3Com Etherlink III (3C509B) won't work
"P.T. Breuer" <ptb@oboe.it.uc3m.es> wrote in message
news:10rmtb.uc.ln@news.it.uc3m.es...
> In comp.os.linux.networking Geoff <geoff_r@canada.com> wrote:
> > ----------------------------------------------------------
> > No received packets
> > If a 3c509, 3c562 or 3c589 can successfully transmit packets, but never
> > receives packets (as reported by /proc/net/dev or 'ifconfig') you likely
> > have an interrupt line problem. Check /proc/interrupts to verify that
the
> > card is actually generating interrupts. If the interrupt count is not
> > increasing you likely have a physical conflict with two devices trying
to
> > use the same ISA IRQ line. The common conflict is with a sound card on
IRQ10
> > or IRQ5. The easiest solution is to move the 3c509 to a different
interrupt
> > line.
> > --------------------------------------------
>
> > How do I change the interrupt line ? - can I just change the value in
the
> > modules.conf file ?
>
> That only informs the driver of what IRQ the card is using. (and I
> thought the driver could find that by interrogating the card nowadays,
> so maybe if you HAVE an irq= thing there, that is wrong?).
>
> If you want to change the irq that the card uses, you have to set it on
> the card.
>
> Depending on the card, that may involve using the dos setup disk for
> it, or if you are lucky and it is pnp (which probably is faulty on the
> card ..), using isapnp, or if you are very very lucky, use 3c5x9setup.
>
> Peter
I changed the IRQ in the tool under the XWindows App - changed it to 10,
then rebooted and I can
now ping no problem at all ;)
My performance seems low, (I expect i'm not in full duplex mode... not a big
deal at this point)
Thanks to all.... now off to the next problem ;)
|