On Thu, 11 Sep 2003, [nboichat] wrote:

> ------- Additional Comments From [EMAIL PROTECTED]  2003-11-09 21:31 -------
> Results with cable unplugged () :
> # ifstatus -v eth0
> eth0:
>     SIOCETHTOOL failed (Operation not supported)
>     SIOCGMIIPHY: unplugged
>     SIOCDEVPRIVATE: unplugged
>     Wireless failed.
> (Nothing changes)
> # mii-tool -v
> eth0: no link
>   product info: National DP83840A rev 1
>   basic mode:   autonegotiation enabled
>   basic status: no link
>   capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>   advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> (This is correct I think)

OK, so it seems mii-tool is correct, when ifstatus isn't? If so, I guess 
this is indeed an ifplugd bug (but it's weird that it isn't affecting more 
machines ...)

> 
> I dl and compiled kernel 2.4.23pre3 from kernel.org, it does not solve the
> problem (ifstatus and mii-tool gives exactly the same output as with kernel
> 2.4.22-5mdk).
> 
> I ran again drakconnect (last version: drakxtools 9.2-10mdk), and "Network
> hotplugging" was checked by default : I will add a new bug report to blacklist
> my card.

I am not sure if this is the right way to fix it in the long run, if 
mii-tool can detect the cable, ifstatus should be able to, and then 
ifplugd should work correctly.

I can't help you further with this though ... maybe the ifplugd maintainer 
can have a look.

Regarsd,
Buchan

-- 
|----------------Registered Linux User #182071-----------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************

Reply via email to