Re: F16 NetworkManager icon showing connecting when connected



On Thu, 2012-11-08 at 16:23 -0500, Robert Moskowitz wrote:
> On 11/08/2012 03:11 PM, Dan Williams wrote:
> > On Thu, 2012-11-08 at 14:31 -0500, Robert Moskowitz wrote:
> >> On 11/08/2012 02:10 PM, Dan Williams wrote:
> >>> On Thu, 2012-11-08 at 13:34 -0500, Robert Moskowitz wrote:
> >>>> Nov  8 12:48:23 lx120e NetworkManager[918]: <info> (wlan0): roamed
> >>>> from
> >>>> BSSID 00:17:DF:A8:D2:21 (ietf) to (none) ((none))
> >>> Is the problem.  Let me guess; Broadcom hardware using wl.o perhaps?  Or
> >>> a staging driver?  We try to paper over this driver issue when we can,
> >>> and perhaps we can hack something else in here.
> >> GENERAL.VENDOR:                         Realtek Semiconductor Co., Ltd.
> >> GENERAL.PRODUCT:                        RTL8188CE 802.11b/g/n WiFi Adapter
> >> GENERAL.DRIVER:                         rtl8192ce
> >>
> >>
> >>> If possible, can you:
> >>>
> >>> dbus-send --system --print-reply
> >>> --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
> >>> org.freedesktop.NetworkManager.SetLogging string:"debug"
> >>> string:"wifi,wifi_scan,core,device,hw"
> >> # dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager
> >> /org/freedesktop/NetworkManager
> >> org.freedesktop.NetworkManager.SetLogging string:"debug"
> >> string:"wifi,wifi_scan,core,device,hw"
> >> method return sender=:1.4 -> dest=:1.221 reply_serial=2
> >>
> >>> (with sudo or as root) and then reconnect to the IETF AP and grab the
> >>> resulting log output?  We're specifically interested in the bits for
> >>> "get_active_ap" and why there's no match; also what the values are for:
> >>>
> >>> get_active_ap(): (wlan0): active BSSID: 00:30:gg:ff:ee:dd
> >>> get_active_ap(): (wlan0): active SSID: 'xxxxxxx'
> >> This is unclear.  I turned off the wireless then turned it back on. Here
> >> is everything from /var/log/messages from that.  How do I turn off the
> >> debug logging now?
> > same dbus-send command, just instead of "debug" put "info".
> >
> > [nm-device-wifi.c:513] get_active_ap(): (wlan0): active BSSID:
> > 00:00:00:00:00:00
> >
> > is the problem.  The device is saying it's not connected to anything.
> > When you see the "roamed from..." thing, can you run "iwconfig wlan0"
> > for me?  also "iw dev wlan0 link".
> 
> Anyway, this is what I am seeing right now:
> 
> # iwconfig wlan0
> wlan0     IEEE 802.11bgn  ESSID:off/any
>            Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
>            Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
>            Encryption key:off
>            Power Management:off
> 
> # iw dev wlan0 link
> Not connected.
> 
> And yet I know I am connected as this message will be going out when I 
> click on send!

So at this point it's completely a driver problem.  If you're actually
connected, then *both* these commands should report that fact.  NM
trusts the kernel here, and the kernel is letting us down.  NM has no
way of knowing that we're connected to anything at all if the kernel
doesn't report that correctly :(

Dan



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]