On Mon, 11 Aug 2008, Philip Langdale wrote: > Henrique de Moraes Holschuh wrote: >> Hmm? UNBLOCKED means it is not being rfkilled. Why is not working? Put >> some debug printks on your toggle_radio callback, that might help fix the >> issue... > > Well, what I see is this: > > At modprobe, I get an explicit unblock request. When I modify 'state' in sysfs, > I see appropriate requests to soft block and unblock. When I activate the hardware > kill switch, the rfkill state goes to hard_block but no one calls toggle_radio > and when I release the kill switch, the state goes to soft_block and no one > calls toggle_radio. Looks like either rfkill-input is inactive, or something is binding to the toshiba_acpi input device and setting it to exclusive mode (X evdev does this). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
