iemcd wrote:It's not an old thread!
Well maybe it's just me then.
Please be aware that I upgrated (fresh install) to MGA3. I posted about it here:
viewtopic.php?f=25&t=6492Still not out of the woods. The hardware is recognized and it is now loading a driver. Still not detecting any network. The wifi radio in the dongle seems to be powered off. It's been a long time since I've had to troubleshoot wifi issues.
I'm not sure how similar the USB dongle will be, but there are some steps I've already taken:
-uninstall Network manager
-remove /etc/sysconfig/network-scripts/ifcfg-wlan0
/etc/sysconfig/network-scripts/wireless.d/*
/etc/wpa_supplicant.conf
and regenerate them.
(these appear to solve the problem where the encryption insists on reverting to WEP each time you connect).
I tried all that just now. edited the "any" entry under wireless.d (couldn't use net_applet to configure the interface otherwise) and it seems to be okay in terms of the encryption.
What are the symptoms you share? Can you always see your network in the GUI? What is the output of ifup-wlan0 (or equivalent)?
I can not see the network (SSID) in the GUI. I am attmpting to connect to "any" SSID and failing.
- Code: Select all
# ifup wlan1
RTNETLINK aswers: Operation not possible due to RF-kill
wireless device wlan1 is configured with a roaming daemon but isn't associated
Determining IP information for wlan1...SIOCSIFFLAGS: Operation not possible due to RF-kill
SIOCSIFFLAGS: Operatoin not possible due to RF-kill
failed.
Seems like RF-kill may have something to do with it. So, I Googled that.
I had to run "rfkill unblock wifi" and that improved things. After that, I could see SSID's in the gui but I still couldn't connect to my router/AP.
I rebooted the router, rebooted the laptop and still no joy. Also, everything is coming up blocked again by rfkill when I reboot.
I'm going to have to hit the rack and get some sleep, but I'll be back on this through Thursday. It's my daughter's machine and I need to get her off Windows by Friday. Let me know if this helps at all.
I'm not sure that grepping for "rt" will return everything that's relevant, because (at least in my case) "rt" is for realtek, not ralink.
You're probably right. I was kind of burned out by the time I got to that stage.
Mark
Let's just reboot everything all the time.