Linux wireless drivers development
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh.dickins@tiscali.co.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-wireless@vger.kernel.org
Subject: Re: 2.6.31-git wireless broken
Date: Sat, 26 Sep 2009 16:31:06 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0909261625050.4336@sister.anvils> (raw)
In-Reply-To: <1253970049.5122.31.camel@johannes.local>

On Sat, 26 Sep 2009, Johannes Berg wrote:
> On Fri, 2009-09-25 at 15:15 +0100, Hugh Dickins wrote:
> > 
> > a9a11622c5c742c115fad371c0397ae86dd3bb67 is first bad commit
> > commit a9a11622c5c742c115fad371c0397ae86dd3bb67
> > Author: Johannes Berg <johannes@sipsolutions.net>
> > Date:   Mon Jul 27 12:01:53 2009 +0200
> > 
> >     cfg80211: self-contained wext handling where possible
> 
> Heh, fun.
> 
> Well the problem appears to be that wpa_supplicant isn't getting started
> by your distro any more. Unfortunately I'm not familiar with opensuse.
> It seems it thinks the device isn't wireless but wired, since it starts
> ifplugd. OTOH maybe it wants ifplugd for wireless too? It's possible in
> theory.

No, ifplugd was my choice: IIRC, at some stage of installation you're
given a choice between traditional ifplugd and super new NetworkManager:
my choice has been ifplugd (after being somehow burnt by NetworkManager
once in the past).

> 
> I'm downloading a livecd to figure out what might be going wrong.

Thanks a lot for going to this trouble - though I do realize it's not
all just for me!  My guess is the LiveCD will favour NetworkManager
(if that turns out to make any difference).

> 
> Can you try running wpa_supplicant manually to make sure it's a problem
> in the distro/kernel interaction and not in wpa_supplicant/kernel?

Good idea: I just tried that, and things indeed then work fine.

Hugh

  parent reply	other threads:[~2009-09-26 15:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 17:18 2.6.31-git wireless broken Hugh Dickins
2009-09-24 17:35 ` Johannes Berg
2009-09-24 18:14   ` Hugh Dickins
2009-09-24 18:23     ` Johannes Berg
2009-09-24 19:45       ` Hugh Dickins
2009-09-25  5:20         ` Johannes Berg
2009-09-25  8:06           ` Hugh Dickins
2009-09-25  8:43             ` Johannes Berg
2009-09-25 14:15               ` Hugh Dickins
2009-09-26 13:00                 ` Johannes Berg
2009-09-26 14:03                   ` Johannes Berg
2009-09-26 15:06                     ` Sven-Haegar Koch
2009-09-26 15:33                     ` Hugh Dickins
2009-09-27 11:08                       ` Johannes Berg
2009-09-27 11:15                       ` Johannes Berg
2009-09-26 15:31                   ` Hugh Dickins [this message]
2009-09-26 15:58                     ` Larry Finger
2009-09-25  8:45             ` Holger Schurig
2009-09-25 14:56               ` Christian Lamparter

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=Pine.LNX.4.64.0909261625050.4336@sister.anvils \
    --to=hugh.dickins@tiscali.co.uk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rjw@sisk.pl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox