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
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
