Re: Detecting wired network on resume with 8139

[Nikolaus Filus <nfilus gmx net>]

Hi,

I have exactly the same problem and wanted to collect some information for 
a bug report. Now here they are


On Wednesday 08 February 2006 17:27, Dan Williams wrote:
> On Wed, 2006-02-08 at 16:27 +0000, James Ettle wrote:
> > Something I've noticed is that if I'm on a wireless network
> > (ipw2200), suspend, move outside the range of that network, plug in
> > to wired, and then resume, NM doesn't seem to pick up on the
> > connection. This is with the 8139too driver on an RTL-8100B/8139D.
>
> Immediately after resuming, can you:
>
> cat /sys/class/net/eth0/carrier
>
> (replace eth0 with the interface name of your 8139).  This tells us
> what netlink thinks the current carrier state of the card is (ie,
> whether it thinks there's a cable or not).

eth1 is my wired, using 8139too from 2.6.14.3:
after resume and nm wake up 

mobile ~ # ifplugstatus -v
eth1:
    SIOCETHTOOL: link beat detected
    SIOCGMIIPHY: link beat detected
    Wireless failed.
    IFF_RUNNING: unplugged
    SIOCDEVPRIVATE failed (Operation not supported)

mobile ~ # cat /sys/class/net/eth0/carrier
1
mobile ~ # cat /sys/class/net/eth1/carrier
cat: /sys/class/net/eth1/carrier: Invalid argument
----------
then, after restarting nm:

mobile ~ # ifplugstatus -v eth1
eth1:
    SIOCETHTOOL: link beat detected
    SIOCGMIIPHY: link beat detected
    Wireless failed.
    IFF_RUNNING: link beat detected
    SIOCDEVPRIVATE failed (Operation not supported)

mobile ~ # cat /sys/class/net/eth1/carrier
1



Hope that helps.


Nikolaus