solved: Re: ifplugd detects beat link at startup though no caple is plugged in

2005-09-13 Thread Jens Nachtigall
> It seems to be a driver problem > (http://bugzilla.kernel.org/show_bug.cgi?id=4755). Cheers. For the record: I found a patch (see my comment at the link above), which solved this problem. Peter, maybe you could also try if the patch works for you and comment on http://bugzilla.kernel.org/sh

Re: ifplugd detects beat link at startup though no caple is plugged in

2005-09-13 Thread Koen Vermeer
On Tue, 2005-09-13 at 11:38 +0200, Jens Nachtigall wrote: > at boot up and when no caple is plugged in into my laptop (Fujitsu Siemens > Amilo M 7400), the ifplugd daemon still detects a beat link and therefore > causes dhclient to run. This means that the boot up process is paused until > dhcli

Re: ifplugd detects beat link at startup though no caple is plugged in

2005-09-13 Thread Peter Funk
Hi, Jens Nachtigall wrote: > at boot up and when no caple is plugged in into my laptop (Fujitsu Siemens > Amilo M 7400), the ifplugd daemon still detects a beat link and therefore > causes dhclient to run. This means that the boot up process is paused until > dhclient gives up: ... Same behavio

ifplugd detects beat link at startup though no caple is plugged in

2005-09-13 Thread Jens Nachtigall
Hi all, at boot up and when no caple is plugged in into my laptop (Fujitsu Siemens Amilo M 7400), the ifplugd daemon still detects a beat link and therefore causes dhclient to run. This means that the boot up process is paused until dhclient gives up: ifplugd(eth0)[4073]: ifplugd 0.26 initiali