Wifi Activation Issue on F16, Dell XPS

[siddharthx64]

Before starting, let me state the laptop Details

Model: Dell XPS15 (L502X)
Videocard: Nvidia GT525-M, 1GB, with OPTIMUS
Processor: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
Ram: 6GB DDR3
Network: RTL8111/8168B PCI Express Gigabit Ethernet controller
Wifi: Centrino Advanced-N 6230
Bluetooth: Intel Centrino Based
Touchpad: Synaptec
Hotkey (Home, Eject, Suspend ...): Special Fn Keys : Projector, WiFi, touchpad-lock, Brightness control, backlight controls, Media Controls, Volume Controls, Mute
Also contains Touch based proprietary Keys
Display: 720p HD 15.6inch Display
OS: Fedora 16, 64bit
Kernel: 3.3.5-2
Comments: Currently using Bumblebee Project to reduce battery Consumption by Gcard.


The Problem is this:

I have Windows 7 and Fedora 16 running in Dual mode. Everything WiFi Related works Fine in Win 7. However, F16 has some issues.
The Wireless Shortcut Keys malfunction:

Whenever the Wifi is turned ON, and I use the Shortcut Key (Fn+F2(wifiToggle)) to turn it OFF, the Key works perfectly. Never Once has It malfunctioned till date. But once I do Switch It OFF, and use the same Keys to switch it back on, the WiFi almost always never turns back ON. It does Work sometimes, but a majority of times, there is no response. This does not happen in Win7.

I usually try multiple times to turn it back on. But most of the time, I have to Boot into Windows, manually enable the wifi using the shortcut keys and then go back to Fedora.
I have No idea why this is happening.
All other Shortcut Keys work perfectly Fine.
Can anyone tell me what is causing this?
Please Help!

[lightman47]

I don't know if this is even related, but for something to think about: I am running FC14-64 on a laptop. When I use the hardware switch/button to turn off the wireless it is successful. Getting it back on is another story. Apparently, when I turn it off via hardware, Fedora also 'disables' the adapter. Therefore, when I turn the hardware back ON, it is disabled in settings. I have to Enable it, then reboot the laptop - so NetworkManager can see it on startup and start it correctly. I have restarted NetworkManager (without the reboot) - doesn't work.