First to address the subject of this bug, the driver does not ignore the state of the hardware RF kill switch. More below. On , Andrew Morton wrote: > On Thu, 17 Apr 2008 14:17:51 -0700 (PDT) > bugme-daemon@xxxxxxxxxxxxxxxxxxx wrote: > >> >> >> messages during boot: >> ----------------------------------- >> SIOCSIFFLAGS: No such device >> [3 lines of irrelevant output on my iwl3945] >> SIOCSIFFLAGS: No such device This is exactly the error returned by the driver when it detects that the hardware RF kill switch is set. With several message like above in your logs - could it be a user app that keeps trying to bring the interface up even when it returns an error? >> dmesg: >> ----------- >> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17 >> PM: Writing back config space on device 0000:04:00.0 at offset 1 >> (was 100002, writing 100006) iwl3945: Radio disabled by HW RF Kill >> switch [message repeated 7 more times] It is right after printing this message that the driver returns "ENODEV". >From what I can tell the driver is doing the right thing. What is the expected behavior in this scenario? Reinette -- 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
