eepro100 does not detect the link beat on NetGEAR switch FS608v2 !?

Joseph Kubik josephkubik-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Tue May 10 14:05:42 UTC 2005


I don't know the details of what / why....
Here is one way to work around "erroneous" link down detection:

http://www.vmware.com/support/kb/enduser/std_adp.php?p_sid=lyhn*3Fh&p_lva=&p_faqid=977

Good luck,
-Joseph-
On 5/10/05, Lennart Sorensen <lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:
> On Mon, May 09, 2005 at 07:30:42PM -0400, Marc Lijour wrote:
> > I got the switch working.
> > However there is a problem:
> >
> > (extract from #service network start)
> > May  9 18:45:22 router ifplugd(eth0)[28473]: ifplugd 0.21b initializing.
> > May  9 18:45:22 router ifplugd(eth0)[28473]: Using interface
> > eth0/00:A0:C9:39:DB:80 with driver <eepro100> (version: eepro100.c:v1.09j-t
> > 9/29
> > /99 Don)
> > May  9 18:45:22 router ifplugd(eth0)[28473]: Using detection mode: SIOCGMIIPHY
> > May  9 18:45:22 router ifplugd(eth0)[28473]: Initialization complete, link
> > beat not detected.
> > May  9 18:45:22 router network: Bringing up interface eth0:  failed
> >
> > ifplugd monitors eth0 on this system (well, I learnt something today!).
> > But it fails seeing the link beat and shuts down my card.
> >
> > But is works with the other card working with the 8139too driver.
> > May  9 18:31:39 router ifplugd(eth2)[25008]: ifplugd 0.21b initializing.
> > May  9 18:31:39 router kernel: eth2: link up, 10Mbps, half-duplex, lpa 0x0000
> > May  9 18:31:39 router ifplugd(eth2)[25008]: Using interface
> > eth2/00:60:67:72:4F:EE with driver <8139too> (version: 0.9.27)
> > May  9 18:31:39 router ifplugd(eth2)[25008]: Using detection mode: SIOCGMIIPHY
> > May  9 18:31:39 router ifplugd(eth2)[25008]: Initialization complete, link
> > beat detected.
> > May  9 18:31:39 router ifplugd(eth2)[25008]: Executing
> > '/etc/ifplugd/ifplugd.action eth2 up'.
> > May  9 18:31:41 router ifplugd(eth2)[25008]: Program executed successfully.
> > May  9 18:31:41 router network: Bringing up interface eth2:  succeeded
> >
> >
> > Now my next question is: how do I disable nicely ifplugd?
> 
> Never heard of it.  Did you try e100 driver?  It tends to be far
> superior to the crappy old eepro100 driver in my experience.  Maybe
> ifplugd uses an interface the old driver doesn't provide or something.
> 
> Lennart Sorensen
> --
> The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
>
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml





More information about the Legacy mailing list