Franklin PIAT wrote:
On Mon, 2008-07-14 at 15:34 +0200, Michael Biebl wrote:
It seems as if the tulip driver or the emulated hardware doesn't
support link beat detection. That's why NM doesn't activate the
connection.

This is not a bug in NM itself but rather a driver problem.


I don't understand what's the exact problem. Is it :

A.The driver sends inaccurate information about the link detection
  capability and/or the current link state. In which case the driver
  should be fixed (i.e forward this bug the kernel).

or

B.The driver sends information that accurately describe the link detection capability and link state. But NM don't handle it properly (for example if NM don't handle the case where the card can't do link detection).

I was referring to this log snippet:

NetworkManager: <info>  eth0: Driver 'tulip' does not support carrier
detection.        You must switch to it manually.

So it's A) afaict.

It this is a driver bug or hardware limitation, I don't know.

Cheers,
Michael


--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to