Hin-Tak Leung wrote: > --- On Tue, 25/8/09, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote: > >>> [PATCH] rtl8187: fix circular locking >> (rtl8187_stop/rtl8187_work) >> >> This patch fixes the problem. You can add a Tested-by to >> it. > > Hmm, I am still wondering about why NM insists on if up'ing the device. I read bits of things and apparently hal is supposed to know the device is rfkill'ed and let NM know. But lshal is not listing the device as having an killswitch. I don't know how hal is supposed to work out that info though. > > also I noted that /sys/class/rfkill_backport/rfkill0/state goes from 1 to 2 when I slide the switch to the 'off' position. Some says it should be 0? > Don't know if hal is affected by its being rfkill_backport (compat-wireless) rather than rfkill (stock vendor kernel). well, it should look there if it isn't :-). > > It looks like it is a hal problem... The interpretation is as follows: 0 - blocked by software such as 'rfkill block 1' 1 - unblocked 2 - blocked by hardware Your state is doing exactly what I would expect. When NM brings the device up, does the above state change? Does dmesg show anything? 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
