12-04-2011 10:47 AM
On my new laptop (Lenovo IdeaPad Z-570), I have it setup and working
fine (for about 2 months now), as dual boot between Linux and Win-7.
The wifi hardware is the Intel 1000-N Centrino, which plugs into the PCI-E
bus slot. (I've had the large bottom-cover plate off and examined the
card, which has two wires, 1 white, 1 black, and is held into its
slot by a single phillips-screw. [Seems they may have put 'lock-tight'
cement on the screw threads...the screw won't budge.]
Here's my current dilemma: 2 days ago, while booted under Linux,
rather than powering down as usual, I closed the lid, and went to bed.
In the morning, when opened the lid, I realized...hmm...maybe it was
hibernating (if I recall correctly).
So, I powered it down, and then cold-booted up. The wifi wasn't seeing
any signal(s) at all. (Clearly the wifi/router was working as my wife's
laptop was connecting fine.) I brought up a cmd-prompt, su'ed, and
did 'iwlist scan', and confirmed there was a problem. Says it couldn't
scan via 'wlan0' interface, because network was down.
I went into ceni, and walked thru a re-configure, and got:
"...can't set wireless-flags...operation not possible, due to RF-kill"
Puzzled, I rebooted, over to Win-7, and it too, could not see any wifi-signals.
I double-checked the slide-switch on the front-edge-panel...it looked fine,
was switched to the right-side. Sliding it left causes a front-panel-LED
to go off, sliding switch back to right, causes a front-panel-LED to come back
on. (My understanding is that this switch controls both bluetooth and wifi
devices. I haven't played with the Bluetooth at all yet.)
My conclusion 2 days ago, was that the hardware 'broke' on the wifi-adapter.
But, now my 'gut' is thinking that maybe I'm missing some other possibility.
(e.g. does a BIOS-setting govern the wifi?) Could a mis-configured 'hibernate'
setup have put the wifi-adapter into a 'firmware-level/BIOS-level-disabled' condition?
[e.g. such that neither OS can readily get the wifi-adapter to see signals?]
Solved! Go to Solution.
12-04-2011 05:19 PM - edited 12-04-2011 05:21 PM
Thanks. The Fn-F5 (under Win-7) no doubt would also have solved it.
Under Linux, we earlier found a pgm, called 'rfkill', which has some 'block' and 'unblock'
operators. So, the cmd:
rfkill unblock "wifi"
solved the problem. And, when I rebooted (from Linux, to Windows-7),
the wifi-adapter started working again there, too.
Marking this thread SOLVED.
Thanks again for the help.
12-05-2011 05:22 AM
>>fn+f5 should also work in linux, by the way.
Hmm...well, we discussed that, in a Linux forum. Better, might be to say
that 'maybe it COULD be made to work in Linux'.
Bear in mind,that Linux distros support VARIOUS 'DE's (Desktop Environments)
[aka GUIs], such as Gnome vs KDE vs (a number of others).
In our view, it would have been much BETTER for the BIOS itself to (also)
implement this enabling/disabling of 'wireless'.
That became readily apparent...the first early replies suggested that I go
into the BIOS and see if it could be re-enabled THERE. (But, I didn't find
Maybe it could be considered for inclusion, in a future update of the BIOS(es)
for these models!?