Wireless won't connect after today's updates...

[jonrpick]

I did a "yum update" today. I love how every time, it's like a waiting game to see what broke.


Anyway, aside from a weird Nvidia issue that doesn't concern me, the most noticeable problem is that my wireless will NOT connect to my WPA2 network. This laptop is the only machine that changed. The other laptops and wireless devices (smartphones, etc) didn't change.

It sees all of the available wireless networks. It attempts to connect, but never does. After a short period of time, a dialog box appears, stating that authentication is required... The password is correct, it just won't connect.

Here's a copy of the Yum log... I do see that NetworkManager has been updated, along with the kernel being updated.

*sigh*

Oct 23 14:57:23 Updated: kernel-headers-2.6.34.7-61.fc13.i686
Oct 23 14:58:32 Installed: kernel-devel-2.6.34.7-61.fc13.i686
Oct 23 14:59:11 Updated: google-chrome-stable-7.0.517.41-62167.i386
Oct 23 14:59:13 Updated: perf-2.6.34.7-61.fc13.noarch
Oct 23 14:59:18 Updated: kmod-wl-2.6.34.7-56.fc13.i686-5.60.48.36-2.fc13.i686
Oct 23 14:59:51 Updated: glibc-common-2.12.1-3.i686
Oct 23 15:00:06 Updated: glibc-2.12.1-3.i686
Oct 23 15:00:07 Updated: freetype-2.3.11-6.fc13.i686
Oct 23 15:00:14 Updated: coreutils-8.4-9.fc13.i686
Oct 23 15:00:15 Updated: coreutils-libs-8.4-9.fc13.i686
Oct 23 15:00:17 Updated: poppler-0.12.4-6.fc13.i686
Oct 23 15:00:19 Updated: 1:NetworkManager-glib-0.8.1-8.git20100831.fc13.i686
Oct 23 15:01:53 Updated: selinux-policy-3.7.19-65.fc13.noarch
Oct 23 15:01:58 Updated: glibc-headers-2.12.1-3.i686
Oct 23 15:02:00 Updated: glibc-devel-2.12.1-3.i686
Oct 23 15:04:35 Updated: selinux-policy-targeted-3.7.19-65.fc13.noarch
Oct 23 15:04:37 Updated: freetype-devel-2.3.11-6.fc13.i686
Oct 23 15:04:39 Updated: libunicap-0.9.12-2.fc13.i686
Oct 23 15:05:03 Installed: kernel-2.6.34.7-61.fc13.i686
Oct 23 15:05:07 Updated: setroubleshoot-server-2.2.102-1.fc13.i686
Oct 23 15:05:11 Updated: nvidia-settings-1.0-8.fc13.i686
Oct 23 15:05:12 Updated: nvidia-xconfig-1.0-5.fc13.i686
Oct 23 15:05:14 Updated: iproute-2.6.33-7.fc13.i686
Oct 23 15:05:19 Updated: 1:NetworkManager-0.8.1-8.git20100831.fc13.i686
Oct 23 15:05:31 Updated: 1:NetworkManager-gnome-0.8.1-8.git20100831.fc13.i686
Oct 23 15:05:35 Updated: setroubleshoot-2.2.102-1.fc13.i686
Oct 23 15:05:36 Updated: poppler-utils-0.12.4-6.fc13.i686
Oct 23 15:05:37 Updated: poppler-glib-0.12.4-6.fc13.i686
Oct 23 15:05:40 Updated: tigervnc-server-1.0.90-0.15.20100420svn4030.fc13.i686
Oct 23 15:05:42 Updated: nscd-2.12.1-3.i686
Oct 23 15:05:53 Updated: gnome-screensaver-2.30.0-2.fc13.i686
Oct 23 15:05:59 Updated: webkitgtk-1.2.5-1.fc13.i686
Oct 23 15:06:01 Updated: 2:ntfs-3g-2010.10.2-1.fc13.i686
Oct 23 15:06:02 Updated: postgresql-libs-8.4.5-1.fc13.i686
Oct 23 15:06:04 Updated: psmisc-22.6-14.fc13.i686
Oct 23 15:06:07 Updated: mysql-libs-5.1.51-2.fc13.i686
Oct 23 15:06:14 Updated: anthy-9100h-15.fc13.i686
Oct 23 15:06:15 Updated: nc-1.84-23.fc13.i686
Oct 23 15:06:17 Updated: 1:akmod-nvidia-260.19.12-1.fc13.i686
Oct 23 15:06:31 Updated: 1:xorg-x11-drv-nvidia-libs-260.19.12-1.fc13.i686
Oct 23 15:06:35 Updated: 1:xorg-x11-drv-nvidia-260.19.12-1.fc13.i686
Oct 23 15:06:38 Installed: kmod-wl-2.6.34.7-61.fc13.i686-5.60.48.36-2.fc13.1.i686
Oct 23 15:06:39 Updated: kmod-wl-5.60.48.36-2.fc13.1.i686
Oct 23 15:06:44 Updated: 1:kmod-nvidia-2.6.34.7-56.fc13.i686-260.19.12-1.fc13.i686
Oct 23 15:07:19 Erased: kmod-nvidia-2.6.33.6-147.2.4.fc13.i686
Oct 23 15:07:41 Erased: kmod-wl-2.6.33.6-147.2.4.fc13.i686

[glennzo]

Originally Posted by jonrpick

I did a "yum update" today. I love how every time, it's like a waiting game to see what broke.

Well, it is Fedora

[jonrpick]

Originally Posted by glennzo

Well, it is Fedora

True, but still...

Wish there was some half-way point between stability and cutting edge. I suppose I could just stay one version number behind (I'm running 13 on this machine), but I'd prefer to have some level of "newness".

I usually always waited until a version was 3 months old before upgrading. Maybe I should slow my schedule down...like try waiting until I'm 2 version numbers before. Maybe I'll upgrade to 14 on the day that 16 is released. (smacks forehead).

---------- Post added at 08:33 PM GMT ---------- Previous post was at 07:22 PM GMT ----------

Just changed locations... The wireless here is unsecured, and it connected automatically. I'm typing this, so obviously it's working. Seems to be a problem with WPA.

[glennzo]

Sorry John. My comment wasn't very helpful. I do feel your pain though. I have a laptop here that I've been trying to get wireless working on now for weeks. It's an old box that I've tried several distributions on but it's becoming obvious that this just isn't going to work. Extremely frustrating.

[leigh123linux]

Originally Posted by glennzo

Sorry John. My comment wasn't very helpful. I do feel your pain though. I have a laptop here that I've been trying to get wireless working on now for weeks. It's an old box that I've tried several distributions on but it's becoming obvious that this just isn't going to work. Extremely frustrating.

It took me 2 days to get wifi working properly with my laptop, I replaced the ipw2200bg with this.

http://cgi.ebay.co.uk/ws/eBayISAPI.d...=STRK:MEWNX:IT

It solved all my issues ( the ipw2200bg wouldn't work with wpa2 )

[glennzo]

Mine is an Intersil Prism 2.5. This is on an old ThinkPad R32. I have another card, Broadcom based I think, that I installed but the BOIS rejected it stating that it was an unauthorized card. Remove and reboot. There is a workaround for this too. Works on most all ThinkPasds but this one and one or two others


Think maybe John should downgrade NetworkManager?

[leigh123linux]

Originally Posted by glennzo

Mine is an Intersil Prism 2.5. This is on an old ThinkPad R32. I have another card, Broadcom based I think, that I installed but the BOIS rejected it stating that it was an unauthorized card. Remove and reboot. There is a workaround for this too. Works on most all ThinkPasds but this one and one or two others


Think maybe John should downgrade NetworkManager?

No, not till he tried deleting the wifi settings in networkmanager and tested to see if it helps.
Then if it doesn't work try downgrading.

[jonrpick]

Guys... Even more frustrating than having non-working wireless is having suddenly-working-for-no-reason wireless.

I was checking through other threads last night, and finally happened upon a fairly recent one in which someone suggested "yum downgrade NetworkManager".

I tried it, and it failed. It threw up a dependency error.

ANYWAY... As I stated in my last update, I'd gone to another place with an unsecured wireless connection and all was well. Came home, went straight up bed. When I fired up the laptop a few minutes ago (with the intention of working on the problem) I was surprised to see the 4 wireless bars (signal strength) up on the panel.

I didn't do anything to make it work!!! The machine had been rebooted several times. Nothing has changed in my configuration. Ironically, the next thing I was going to try was deleting the profile for the wireless network here, and letting NetworkManager create a new one. Of course, I didn't get a chance to try it, since it's now working. Good to see that Leigh suggested the same...at least I was probably working toward an eventual solution.

*sigh*

[glennzo]

Well, at least it's working. Too bad you don't have a reason that it suddenly started working though. If it happens again try going to bed again, for at least 8 hours, and see if that helps

[jonrpick]

Originally Posted by glennzo

Well, at least it's working. Too bad you don't have a reason that it suddenly started working though. If it happens again try going to bed again, for at least 8 hours, and see if that helps

LOL! I know, right?!?!

[DodgeJ]

Actually I was having a really similar problem. Yesterday my wifi wouldn't connect to my home network (my password was correct but it kept asking for it) but I found that after I restarted it worked for a few min before giving me an error. It did work when connecting to my neighbor's unsecured wireless, and now I'm at school and the unsecured here works fine.

Gah! If this problem persists, I'll report back. Hopefully my good eight hours of rest last night solved my problem too.