All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Detlev Casanova <detlev.casanova@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes.berg@intel.com>,
	laurent.pinchart@ideasonboard.com
Subject: Re: NetworkManager not listing access points
Date: Wed, 18 Sep 2013 23:16:08 -0500	[thread overview]
Message-ID: <1379564168.13091.6.camel@dcbw.foobar.com> (raw)
In-Reply-To: <31357461.i5mG9q5IfA@naboo>

On Wed, 2013-09-18 at 22:47 +0200, Detlev Casanova wrote:
> Hello,
> 
> After a bisection on the kernel, it seems that a patch is causing a 
> problem with NetworkManager: 
> 
> commit 0172bb75073e11a5aa9d8a953bdaefb8709f00c8 ("cfg80211: 
> use DS or HT operation IEs to determine BSS channel")
> 
> The Wifi access points are not listed in the KDE plasma widget and it 
> won't even connect to the saved ones even if they are in range.
> 
> There is a fix though: running "iwlist wlan0 scan" twice as root (which 
> properly lists APs in reach) and the second time must be run about two 
> seconds after the first time.
> 
> Then NetworkManager lists the access points and connects to the 
> prefered one if possible (normal behavior).
> 
> This also happens with nm-applet in Gnome.
> 
> The hardware is: 14e4:4315 (Network controller: Broadcom Corporation 
> BCM4312 802.11b/g LP-PHY (rev 01)) on an Intel Core i3 M370 CPU (64 
> bits) computer.
> 
> The abnormal behaviour is not random, it happens every time.

Can you run wpa_supplicant with debugging output?  The quick and dirty
way is to:

mv /usr/sbin/wpa_supplicant /
killall -TERM wpa_supplicant
/wpa_supplicant -dddtu

and then wait for the problem to happen, and grab the log output for us
to analyze.

Dan


  reply	other threads:[~2013-09-19  4:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 20:47 NetworkManager not listing access points Detlev Casanova
2013-09-19  4:16 ` Dan Williams [this message]
2013-09-19  5:58   ` Detlev Casanova
2013-09-21 20:51     ` Johannes Berg
2013-09-22 14:20       ` Detlev Casanova
2013-09-23 16:13         ` Dan Williams
2013-09-29 19:29           ` Detlev Casanova
2013-10-02  9:08             ` Johannes Berg
     [not found]               ` <2916718.7t7kLXuBQV@naboo>
2013-10-07  7:40                 ` Johannes Berg
2013-10-11 15:43                   ` Detlev Casanova
2013-10-17 14:38                     ` Johannes Berg
2013-10-17 16:19                       ` Will Hawkins
2013-10-21 13:06                         ` Johannes Berg
2013-10-21 20:20                           ` Will Hawkins
2013-09-29 21:10 ` Rafał Miłecki
2013-09-29 21:11   ` Rafał Miłecki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1379564168.13091.6.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=detlev.casanova@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.