On 2/10/10, Peter Chubb <peter.chubb@xxxxxxxxxxxx> wrote: >>>>>> "Alan" == Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx> writes: > > Alan> Peter Chubb wrote: >>> Hi Alan. I noticed you were last working on hp-wmi. I'm finding >>> that if I load hp-wmi then the wireless network does not work --- >>> dmesg output always says `iwlagn 0000:02:00: Radio disabled by HW >>> RF Kill switch' regardless of the position of the switch. > > I've discovered that if I load the rfkill module *before* hp-wmi then > everything works properly. Can you show me what "udevadm monitor -ke" reports in both cases? Use one of the 2.6.33-rc kernels, and show me your kernel config. > Maybe there's a missing dependency? If you've built the rfkill module, "modprobe hp-wmi" should load it automatically. If it didn't, then hp-wmi would fail to load. So it sounds more like a race condition. > I > hadn't even been building the rfkill input module before --- it > doesn't get automatically selected. Um. rfkill-input is no longer a separate module. You can disable it individually, *if* you have CONFIG_EMBEDDED enabled. If that causes problems, we need to fix that as well (because rfkill-input is theoretically going away). Or perhaps you have rfkill as a whole disabled? In that case, we'd expect that hp-wmi wouldn't have any effect on the wireless. If it does, that's also a bug (albeit a more obscure one with an easy workaround). Regards Alan -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
