Johannes Berg wrote:
>
> Could you try, without the patch in question, what happens in terms of
> uevents
> * have everything on
> * press rfkill button (expect -> hw_blocked transition)
> * put interface down
> * press rfkill button (expect -> unblocked transition)
> * put interface up
I'm running v2.6.30-rc8-25743-g3b2029b from wireless-testing.
This is with interface UP and switch off:
larrylap:/etc/sysconfig/network # cat /sys/class/rfkill/rfkill0/uevent
PHYSDEVPATH=/devices/pci0000:00/0000:00:0d.0/0000:04:00.0/ssb0:0
PHYSDEVBUS=ssb
PHYSDEVDRIVER=b43
RFKILL_NAME=phy0
RFKILL_TYPE=wlan
RFKILL_STATE=2
larrylap:/etc/sysconfig/network # ifdown eth1
eth1 name: BCM4312 802.11a/b/g
larrylap:/etc/sysconfig/network # cat /sys/class/rfkill/rfkill0/uevent
PHYSDEVPATH=/devices/pci0000:00/0000:00:0d.0/0000:04:00.0/ssb0:0
PHYSDEVBUS=ssb
PHYSDEVDRIVER=b43
RFKILL_NAME=phy0
RFKILL_TYPE=wlan
RFKILL_STATE=2
At this point, radio kill switch turned on:
larrylap:/etc/sysconfig/network # ifup eth1
eth1 name: BCM4312 802.11a/b/g
eth1 warning: WPA configured but may be unsupported
eth1 warning: by this device
eth1 starting wpa_supplicant
SIOCSIFFLAGS: Unknown error 132
Could not set interface 'eth1' UP
RTNETLINK answers: Unknown error 132
Starting DHCP4 client on eth1. . . .
eth1 DHCP4 client NOT running
RTNETLINK answers: Unknown error 132
Cannot enable interface eth1.
interface eth1 is not up
larrylap:/etc/sysconfig/network # cat /sys/class/rfkill/rfkill0/uevent
PHYSDEVPATH=/devices/pci0000:00/0000:00:0d.0/0000:04:00.0/ssb0:0
PHYSDEVBUS=ssb
PHYSDEVDRIVER=b43
RFKILL_NAME=phy0
RFKILL_TYPE=wlan
RFKILL_STATE=2
The ERFKILL (132) prevents it from coming up. Again, the switch was on
at this point.
I could not restore service until rmmod/insmod of b43.
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
