Le 18/02/2019 à 15:05, Dr. Nikolaus Klepp a écrit :
> Anno domini 2019 Mon, 18 Feb 14:51:03 +0100
> Didier Kryn scripsit:
>> Le 18/02/2019 à 14:07, Dr. Nikolaus Klepp a écrit :
>>> Comming back to the original issue: I tested ifplugd - which turned out to be not very reliable, but worked at least some hours. Now I tested "netplugd". The result is not verry promising: eudev logged the plug-event immediately, but netplugd sometimes took a break for 5 minutes ore more to detect that the cable was plugged in.
>>     Eudev should react to the detection of the eth interface and create
>> the device. It isn't supposed to react to carrier detection (cable
>> connected). And, of course, the device should exist prior to
>> ifplugd/netplug to detect the carrier.
>>
>>     What kind of ethernet interface do you have? Is it some external
>> device connected through usb ?
> It's the built-in ethernet of T60/T61 laptops. This is what "dmesg" says (cable plugged in, device booted. Then cable detatched (232.150573), cable reattached (236.562619) and detached again (764.652272) - same to be found in /var/log/messages:
>
> [ 57.202695] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> [ 57.202873] e1000e 0000:01:00.0 eth0: 10/100 speed: disabling TSO
> [ 232.150573] e1000e: eth0 NIC Link is Down
> [ 232.465673] e1000e: eth0 NIC Link is Down
> [ 234.126681] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> [ 234.126860] e1000e 0000:01:00.0 eth0: 10/100 speed: disabling TSO
> [ 234.850510] e1000e: eth0 NIC Link is Down
> [ 236.562619] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> [ 236.562797] e1000e 0000:01:00.0 eth0: 10/100 speed: disabling TSO
> [ 764.652272] e1000e: eth0 NIC Link is Down
> [ 768.674596] e1000e 0000:01:00.0 eth0: MAC Wakeup cause - Link Status Change
> [ 769.121767] e1000e: eth0 NIC Link is Down
> [ 769.397761] e1000e: eth0 NIC Link is Down
> [ 769.741891] e1000e: eth0 NIC Link is Down
>
> What I do not understand: In my understanding "udevadm monitor" should print all events, not only the events it has rules for. But it does not print anything of these plug/unplug events. What's the point I am missing?
>

    Dunno for udevadm. I've used my own uevent logger in the past to
watch what was happening.

    It is clear that the driver logs a message every time the cable is
plugged/unplugged; I've observed that many times on various hosts. But I
don't think if it generates an uevent for that, therefore, I don't this
message is from udev and I dunno how ifplugd is notified.

    Didier