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: Fri, 25 Sep 2009 09:06:53 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0909250838420.3783@sister.anvils> (raw)
In-Reply-To: <1253856038.3868.500.camel@johannes.local>

On Fri, 25 Sep 2009, Johannes Berg wrote:
> 
> Very odd. Haven't really looked at the config, but I see the phy0: idle
> message that indicates you have debug on. However, it's like nothing
> ever tells the kernel to connect to a network.
> 
> Are you running wpa_supplicant?

Should be, but you're right, for whatever reason it is not running
with these recent kernels.

I expect that correlates with iwconfig showing me ESSID:off/any.

I'm thinking that (unless you've a better idea) I should do another
bisect for when that behaviour starts - hoping that whatever problem
led me to your patch, got fixed up later on, but superseded by this
different problem.

The bootup messages on the Aspire One tell me:
    wlan0     device: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
    wlan0     is controlled by ifplugd
    wlan0    
waiting
    wlan0     device: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
    wlan0     ifplugd is running
    wlan0     no cable connected
    wlan0     DHCP4 client NOT running
    wlan0    

And the bootup messages on the Fujitsu Siemens say:
    wlan0     device: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
    wlan0     is controlled by ifplugd
    wlan0    
    wlan0     device: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
    wlan0     ifplugd is running
    wlan0     no cable connected
    wlan0     . . . is just beeing set up
    wlan0    

In each case, "no cable connected".

I wonder, have there been more yet more regdom reworks since 2.6.31?
Would this be the stage at which regdom problems manifest?  I'm not
running whatever-it-is daemon for setting regdom, usually just patch
static char *ieee80211_regdom = "EU";
into my kernels; but in the past have only needed that when the router
decides to use channel 13 or something - currently it's on channel 1.

Hugh

  reply	other threads:[~2009-09-25  8:06 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 [this message]
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
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.0909250838420.3783@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