Wifi not recognised - yum update

[CORS_1ER]

Hey guys,

im hoping to get some help, i first booted into pidora last night (not noobs, single image).

i have an edimax wifi adapter in one usb port, the other port has a 4 port usb adapter with mouse, keyboard and a powered ext hdd.

this combination ran with absolutely no isee whatsoever. Great.

I decided to install vlc, so i updated rpm and did a yum update (which took forever lol).

without any other changes, i reboot my pi. I log in (once under root and then under user) and to my surprise i get a message saying network disconected. I cannot connect to wifi as it does not appear in my list of connections nor in ifconfig.

also i have noticed i no longer have a blue light on the edimax.

what could have happened?

[m0n]

I can confirm similar or same issue. Had been working great until recent yum update
Now it will not recognize the wireless adapter

[macemoneta]

Was your kernel updated? The kernel has the drivers for all hardware, so I would assume so. You can check by opening a terminal, and (as root) running:

Code: Select all

ls -ltr /boot/kernel*

If you see multiple entries of the form 'kernel-x.y.z...img' then you probably updated. You can easily go back to the previous kernel by copying the older kernel over 'kernel.img':

Code: Select all

cp /boot/kernel-x.y.z...img /boot/kernel.img
sync

When you reboot, you will be up on the older kernel. You can confirm which kernel you are running with:

Code: Select all

uname -r

[jmontleon]

Was a raspberrypi-kernel-3.11.6 package? that reports 3.6.11 when you run uname -r? If so downgrade as you've been hit by a bad package (or grab a newer one off of koji.pidora.ca) which was a bad module path (it is actually a 3.6.11 kernel despite the package name). This happened to me while working on building stuff for Pidora 19 (though not this kernel). Shame if it was actually released.

[m0n]

I re-imaged with a backup then had some scriptlet errors in lightdm and a few other packages after attempting another yum update
I did a rpm -e --noscripts to the specific files that were giving the errors then yum update worked fine but now NAT is not recognized with iptables - none of the files that were giving previous errors were related to iptables however
I use my Pi as a ssh tunnel proxy
The kernel that is in use is 3.12.0-2 after running yum update

[spacial]

Same with me.

I noticed that the modules aren't loading on new kernel.

Later I'll try to get the old kernel back.

Seems to me that is a wrong versioning in the new kernel

kernel-3.11.6-3.20131023git10bc582.rpfr18.img <-- last update.
kernel-3.6.11-7.20130415git197d15b.rpfr18.img