Hello, I'm working on linux 2.6.14.
My system has 2 on-chip ethernet ports (eth0-eth1).
I have included startup scripts for both ports in etc/sysconfig/network-scripts,
piloting each interface to be up on boot.
Point is: when I bootstrap without cable, my syslog is flooded by
the typical "Trying Speed..." printed by the auto negotiation machine.
Moreover if I perform a ethtool request on that interface, link is declared UP (!!).
This behavior stops when I insert a cable in the interface.

This is not correct in my opinion: indeed, when I plug off the cable again, syslog is no more flooded, and auto negotiation machine is started by the LINK UP event.
Is there any option I can use for having the correct event-driven behavior from the beginning?

Thanks!

L.

Probably it depends on the driver you are using. Ideally, you want driver software to have 'carrier detect' when it gets initialized. But in your case it looks like it only has 'carrier lost' and 'carrier sense' events after the driver is being installed. Though, not all drivers are the same, and maybe if you'd had other hardware it would've been different.

I'd agree, but what puzzles me is that when I insert the cable (link up etc..) and then remove it again, there's no more "Trying..." activity, and everything starts to work correctly in a carrier detect fashion...