WTF... update screwed wireless

[dwhitney67]

Hello,

This morning I updated my F7 system with the latest updates, including one for the wpa_supplicant (sp?).

Is there a way for me to back-out an update? My wireless is no longer working. I have the Intel 3945ABG wi-fi chip set. It was working before, but not anymore.

[dwhitney67]

Nevermind, a second reboot was all that was needed to "fix" the problem... whatever it was.

[Brian1]

Did you upgrade the kernel and are you suing DKMS to build modules that are not part of the kernel like youe intel nic? If so then it was probably compiled to work with the new kernel after the nic was trying to load. Current DKMS is started at S26 and Netowrking is started about S12. So netowrking had tried to start and no current nic module for the kernel existed. till the dkms app run during startup at S26.

This is just a guess as to what happened.

Brian

[dwhitney67]

No, I did not update the kernel at all. This list of items that were updated are listed below (I got this from /var/log/yum.log):

Nov 20 10:45:22 Updated: libselinux - 2.0.14-10.fc7.i386
Nov 20 10:45:23 Updated: elfutils-libelf - 0.131-1.fc7.i386
Nov 20 10:45:28 Updated: tomcat5-servlet-2.4-api - 5.5.25-1jpp.1.fc7.i386
Nov 20 10:45:28 Updated: elfutils-libs - 0.131-1.fc7.i386
Nov 20 10:45:32 Updated: system-config-printer-libs - 0.7.74.4-1.fc7.i386
Nov 20 10:45:36 Updated: samba-common - 3.0.27-0.fc7.i386
Nov 20 10:45:37 Updated: gnome-python2-extras - 2.14.3-6.fc7.i386
Nov 20 10:45:37 Installed: xdg-utils - 1.0.2-2.fc7.noarch
Nov 20 10:45:38 Updated: system-config-printer - 0.7.74.4-1.fc7.i386
Nov 20 10:45:39 Updated: elfutils-libelf-devel - 0.131-1.fc7.i386
Nov 20 10:45:40 Updated: libselinux-devel - 2.0.14-10.fc7.i386
Nov 20 10:45:41 Updated: tomcat5-jasper - 5.5.25-1jpp.1.fc7.i386
Nov 20 10:45:41 Updated: libselinux-python - 2.0.14-10.fc7.i386
Nov 20 10:45:42 Updated: libsmbclient - 3.0.27-0.fc7.i386
Nov 20 10:45:45 Updated: policycoreutils - 2.0.16-15.fc7.i386
Nov 20 10:45:47 Updated: tomcat5-server-lib - 5.5.25-1jpp.1.fc7.i386
Nov 20 10:45:52 Updated: gnome-libs - 1:1.4.2-7.fc7.i386
Nov 20 10:45:53 Updated: tomcat5-jsp-2.0-api - 5.5.25-1jpp.1.fc7.i386
Nov 20 10:45:54 Updated: tomcat5-common-lib - 5.5.25-1jpp.1.fc7.i386
Nov 20 10:45:55 Updated: system-config-securitylevel-tui - 1.7.0-6.fc7.i386
Nov 20 10:45:58 Updated: gnome-desktop - 2.18.3-4.fc7.i386
Nov 20 10:46:01 Updated: tomcat5 - 5.5.25-1jpp.1.fc7.i386
Nov 20 10:46:02 Updated: gnome-python2-gtkhtml2 - 2.14.3-6.fc7.i386
Nov 20 10:46:02 Updated: gnome-python2-libegg - 2.14.3-6.fc7.i386
Nov 20 10:46:05 Updated: samba - 3.0.27-0.fc7.i386
Nov 20 10:46:05 Updated: hal-cups-utils - 0.6.13-2.fc7.i386
Nov 20 10:46:06 Updated: elfutils - 0.131-1.fc7.i386
Nov 20 10:46:07 Updated: smartmontools - 1:5.37-3.3.fc7.i386
Nov 20 10:46:09 Updated: mplayer - 1.0-0.82.rc2.lvn7.i386
Nov 20 10:46:10 Updated: wpa_supplicant - 1:0.5.7-4.fc7.i386
Nov 20 10:46:13 Updated: system-config-securitylevel - 1.7.0-6.fc7.i386
Nov 20 10:46:15 Updated: policycoreutils-gui - 2.0.16-15.fc7.i386
Nov 20 10:46:25 Updated: perl - 4:5.8.8-26.fc7.i386
Nov 20 10:46:25 Updated: perl-libs - 4:5.8.8-26.fc7.i386
Nov 20 10:46:26 Updated: perl-Test-Harness - 2.56-26.fc7.i386
Nov 20 10:46:27 Updated: perl-CPAN - 1.76_02-26.fc7.i386
Nov 20 10:46:28 Updated: nas - 1.9.1-2.fc7.i386
Nov 20 10:46:34 Updated: arts - 8:1.5.8-4.fc7.i386
Nov 20 10:46:48 Updated: kdelibs - 6:3.5.8-7.fc7.i386
Nov 20 10:47:04 Updated: kdebase - 6:3.5.8-3.fc7.i386
Nov 20 10:47:06 Updated: perl-suidperl - 4:5.8.8-26.fc7.i386
Nov 20 10:47:09 Updated: samba-client - 3.0.27-0.fc7.i386
Nov 20 10:47:13 Updated: perl-Test-Simple - 0.62-26.fc7.i386
Nov 20 10:47:13 Updated: perl-ExtUtils-Embed - 1.26-26.fc7.i386
Nov 20 10:47:14 Updated: perl-devel - 4:5.8.8-26.fc7.i386
Nov 20 10:47:16 Updated: perl-ExtUtils-MakeMaker - 6.30-26.fc7.i386

[Iron_Mike]

Nevermind, a second reboot was all that was need to "fix" the problem... whatever it was.


I see the Windows fix worked.......

[Brian1]

I don't really see anything to cause your problem after the first boot. Oh well I would go along with Iron Mike theory.

Brian

[Iron_Mike]

It's the Windows Fix, when in doubt, REBOOT.......

[dwhitney67]

The same issue cropped up again today. :mad:

Maybe it has something to do with the Network Manager?

I was using wifi this morning at home, powered down my system to haul it into work where I use the wired-network, then powered down the system again to bring it home. When I boot up, the wifi interface is not enabled, thus Network Manager (or whatever) cannot find my Access Point.

I tried enabling the wifi interface using the System Network tool, but still no joy. I reboot the system, and voila it starts working.

Maybe M$ did have a hand in developing the latest version of the Network Manager?