... However, in my case it was because I had previously been using the fix for Wireless N Intel chipsets...

/etc/modprobe.d/iwlagn.conf

options iwlagn 11n_disable50=1 11n_disable=1

Once I disabled this line, and rebooted, then wireless started working again. I still have issues with wireless N speeds, but at least wireless is working again.

It appears that the "11n_disable50" option was removed in 2.6.40, causing the driver to fail to load, which resulted in the loss of wireless in your case. However, on my machine, the driver is successfully loaded, and can scan for APs, but is unable to connect to them, giving the errors in my original post.

I also tried the F16 alpha ISO - the same issue is present in the live session.

Any other ideas? It's still a good long while before my current laptop gets replaced by a ThinkPad

It doesn't solve the problem - "rfkill list" doesn't show my wireless as hard or soft blocked. It's likely a driver bug as stevea has mentioned. I've subscribed to the linux-wireless mailing list and have been reading for related news as a result.

On my HP Pavillion DM4 I can connect to Wifi, but it's really slow and sometimes I have to reconnect. What's funny is sometimes Chrome works but Firefox doesn't which makes no sense since if there is TCP/IP connectivity they both should work.

On my HP Pavillion DM4 I can connect to Wifi, but it's really slow and sometimes I have to reconnect. What's funny is sometimes Chrome works but Firefox doesn't which makes no sense since if there is TCP/IP connectivity they both should work.

I had to remove the hard drive from that machine that had my dualboot Windows 7/Fedora. The replacement drive only has Windows (I never bothered to install Fedora for this reason). Once I pull the data off the old drive I could try putting it back it and try.