Red Hat Bugzilla – Bug 815331
Encrypted wifi networks are greyed out and can't be selected in Fallback Mode
Last modified: 2012-05-02 07:03:12 EDT
Created attachment 579506 [details]
Description of problem:
In Fallback Mode all the encrypted wifi networks are greyed out and you can't click on them, therefore you can't connect. See screenshot. In gnome-shell mode it works.
Version-Release number of selected component (if applicable):
I logged out and in, I pushed wifi switch on and off, still broken
Proposing as F17 Blocker, it fails criteria requiring network access.
Similar behavior of NM in LXDE spin - all WPA networks are grayed out.
WEP networks seem selectable.
Manually adding WPA2 wireless network works (automatic reconnection afterwards and everything ok).
I have to note I also use ipw2200 driver (using fixed kernel provided in bug 802106 comment 20). Maybe it can be related.
yes indeed! I've connected an old external wireless adapter to the same machine (pcmcia rt2500pci) and NM works as expected - i.e. WPA networks are visible and clickable and configured correctly by NM.
(except network is not connected on boot - I have to right-click NM to disable/enable wireless to have NM connect to saved network...)
1 more thing I noticed now - NM shows no Signal Strength bars nor connection speed with ipw2200 driver (iwconfig shows all these).
(and signal bars missing with aforementioned "test-ipw2200.fc16" and F17 kernel both).
I can confirm that a colleague of mine who has a different wifi card model has no problem connecting to WPA networks in the fallback mode, menu items are not greyed out. This bug seems to be affected by just ipw2200 (and maybe some more) models.
Appears to be a kernel driver bug, and an update has already been submitted.
*** This bug has been marked as a duplicate of bug 802106 ***
No, reopening. I was using the fixed kernel from bug 802106 comment 20. This is not a duplicate. Maybe it's another bug in ipw2200 driver. But it doesn't appear in gnome shell, just in fallback mode, that's suspicious.
(In reply to comment #7)
> it doesn't
> appear in gnome shell, just in fallback mode, that's suspicious.
Hm... it appears that nm-applet does some sanity-checking that gnome-shell doesn't do; nm-applet will gray out the network if your wireless card claims that it doesn't support the given encryption type.
nmcli dev list | grep WIFI-PROPERTIES
output? (If you have multiple wifi cards, do "nmcli dev list iface WHATEVER" to only list the properties of the ipw2200 card.)
*** Bug 817147 has been marked as a duplicate of this bug. ***
FYI I cannot reproduce the issue in Fallback mode with latest git NM on F15 using kernel 18.104.22.168. The only machine I have that's capable of using an ipw2200 is only running F15.
The only thing that I can see causing this is improper device capabilities that the kernel provides. That ipw2200 bug got fixed in the upstream kernel by the following patch:
which needs to be backported to the affected kernels. The suggested "nmcli dev list | grep WIFI-PROPERTIES" info would tell us whether that's the case or not.
I cloned this bug as Bug 817298 for the kernel to track the backport there. If we verify that is the actual problem, I may dupe this bug to the kernel bug.
In any case, please still provide the 'nmcli' output so we can minimally verify whether the kernel is the problem here.
yes, on e.g. Thinkpad R50e:
nmcli dev list | grep WIFI-PROPERTIES
F17 lxde spin;
kernel-3.3.4-1.fc17.i686 (from Bug 802106);
and defining by hand a NM wireless WPA2 network works ok still.
(but no Signal Strength bars, still)
(In reply to comment #8)
> nmcli dev list | grep WIFI-PROPERTIES
Dell Latitude D510 with ipw2200 (reported as D600)
(Reporter on the duplicate Bug 817147)
(In reply to comment #13)
> (In reply to comment #8)
> > nmcli dev list | grep WIFI-PROPERTIES
> WIFI-PROPERTIES.WEP: no
> WIFI-PROPERTIES.WPA: no
> WIFI-PROPERTIES.WPA2: no
> WIFI-PROPERTIES.TKIP: no
> WIFI-PROPERTIES.CCMP: no
> Dell Latitude D510 with ipw2200 (reported as D600)
> (Reporter on the duplicate Bug 817147)
Yep, that's the kernel driver cipher properties bug as described in bug 817298 which should get fixed soon. I'm going to dupe this bug to the kernel bug here since that's the underlying problem.
*** This bug has been marked as a duplicate of bug 817298 ***
Due to limited impact (encrypted wifi networks don't work with ipw2200 just using the fallback mode), I'm not transferring the blocker bug proposal to bug 817298.