On Wed, 1 Jun 2005, Casey Harkins wrote: > [after connecting the cable] > signal interface=org.freedesktop.Hal.Device; member=PropertyModified; > sender=:1.1 > int32:2 > string:net.80203.rate > boolean:false > boolean:true > string:net.80203.link > boolean:false > boolean:false > > [after removing the cable] > signal interface=org.freedesktop.Hal.Device; member=PropertyModified; > sender=:1.1 > int32:2 > string:net.80203.rate > boolean:true > boolean:false > string:net.80203.link > boolean:false > boolean:false
Ok, take a look at the two booleans after the net.80203.link. They are both false. Unfortunately, that means that the driver doesn't seem to be relaying the link status to HAL. But file a bug against HAL and see if David can fix it. It may well be a driver issue, which driver are you using (ie, what module is loaded for your sis900?) Even if the driver prints messages, it doesn't mean the driver is forwarding link events over netlink sockets, which is what HAL and just about everything else uses. The driver needs to be using netif_carrier_on() and netif_carrier_off() rather than just printing messages to the console. Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
