Originally Posted by mikewhatever
I've tried Kubuntu 8.04, Ubuntu 8.04 8.10 (live and install) and 9.04, Fedora, OpenSuse and Pardus with ipw3945, iwl3945 or ndiswrapper. They all had problems with the wireless card. I suspect that the problem is with the rfkill switch, according to my previous thread.
My problem is something like that:
Independent of the position of the wireless kill switch (which is a sliding hardware switch on my machine, not a Function+F4 combination or something) when i boot linux, i get output similar to this (dmesg | grep 3945):
iwl3945: MAC is in deep sleep
iwl3945: Unable to int nic
After applying some recommendations such as:
iwl3945: Detected Intel Wireless WiFi Link 3945ABG
iwl3945: Error: saturation power is -1, less than minimum expected 40
iwl3945: Invalid power index
iwl3945: initializing regulatory failed: -5
iwl3945 0000:0b:00.0: PCI INT A disabled
iwl3945: probe of 0000:0b:00.0 failed with error -5
or installing backports modules or upgrading kernel version i got nothing! Turning the wireless switch on and off several times was not a fix neither.
sudo rmmod -f iwl3945 && sudo modprobe iwl3945 disable_hw_scan=1
I should say that this is not always the case. Sometimes I can scan the wireless networks around me and connect without any problem in linux.
I can simply check the output of
and if the MAC address of my wireless card goes 00:00:00:00:00:00 then definitely there will be no wireless connection. But if the MAC address is correct, then everything will be alright (By the way, this is nothing to do with the Ubuntu's default action of disabling wireless card when the machine is connected to a wired network, since disabling a network card never resets it MAC address, as this was argued at some point).
sudo lshw -C network
This was the summary of what i've experienced, hoping it was clear enough. My machine is a Dell. Not all 3945 cards has this problem. But this is not a hardware failure, since Windows works perfectly, as i said.
By looking at the number of replies to this thread, i can see that this is not a frequently met problem in the community so i will be celebrating this alone
Thanks for your reply anyway.