Subject: Re: 2.6.31-git wireless broken - msg#00961

Previous Message by Date: click to view message preview

Re: 2.6.31-git wireless broken

On Fri, 2009-09-25 at 09:06 +0100, Hugh Dickins wrote: > 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. Well it showing you that means that nothing is even trying to connect :) > 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. Not sure, might be very time consuming. > 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". Oi. This looks like it doesn't know that it's a wireless device I guess? johannes signature.asc Description: This is a digitally signed message part

Next Message by Date: click to view message preview

Re: [PATCH] sony-laptop: check for rfkill hard block at load time

Mattia Dongili wrote: > On Thu, Sep 24, 2009 at 08:15:24PM +0100, Alan Jenkins wrote: > >> "I recently (on a flight) I found out that when I boot with the hard-switch >> activated, so turning off all wireless activity on my laptop, the state >> is not correctly announced in /dev/rfkill (reading it with rfkill command, >> or my own gnome applet)... >> >> After turning off and on again the hard-switch the events were right." >> >> We can fix this by querying the firmware at load time and calling >> rfkill_set_hw_state(). >> > > Is it worth trying to get this into a stable release? > Sure. It seems to fit, and all we have to do is add a CC to the patch >> Signed-off-by: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx> >> Tested-by: Norbert Preining <preining@xxxxxxxx> >> > > Acked-by: Mattia Dongili <malattia@xxxxxxxx> > CC: stable@xxxxxxxxxx > >> --- >> drivers/platform/x86/sony-laptop.c | 6 ++++++ >> 1 files changed, 6 insertions(+), 0 deletions(-) >> >> diff --git a/drivers/platform/x86/sony-laptop.c >> b/drivers/platform/x86/sony-laptop.c >> index dafaa4a..a234a9d 100644 >> --- a/drivers/platform/x86/sony-laptop.c >> +++ b/drivers/platform/x86/sony-laptop.c >> @@ -1081,6 +1081,8 @@ static int sony_nc_setup_rfkill(struct acpi_device >> *device, >> struct rfkill *rfk; >> enum rfkill_type type; >> const char *name; >> + int result; >> + bool hwblock; >> >> switch (nc_type) { >> case SONY_WIFI: >> @@ -1108,6 +1110,10 @@ static int sony_nc_setup_rfkill(struct acpi_device >> *device, >> if (!rfk) >> return -ENOMEM; >> >> + sony_call_snc_handle(0x124, 0x200, &result); >> + hwblock = !(result & 0x1); >> + rfkill_set_hw_state(rfk, hwblock); >> + >> err = rfkill_register(rfk); >> if (err) { >> rfkill_destroy(rfk); >> -- >> 1.6.3.2 >> >> >> >> -- 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

Previous Message by Thread: click to view message preview

Re: 2.6.31-git wireless broken

Hugh Dickins wrote: > 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@xxxxxxxxxxxxxxxx> >>> 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). FWIW, the current version of NetworkManager used by the KDE 3.5 desktop in openSUSE 11.1 works, as does the Gnome version. There have been problems with KDE4.2 and earlier, but 4.3 works. I have been testing openSUSE 11.2. As of Milestone 7, wireless networking works with KDE and Gnome in both i386 and x86_64 architectures. I have also tested networks with no encryption, WEP, WPA TKIP, and WPA2 TKIP. My inclination is to set wired connections with ifplugd, but wireless to "on boot". Larry -- 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

Next Message by Thread: click to view message preview

Re: 2.6.31-git wireless broken

On Friday 25 September 2009 10:45:38 Holger Schurig wrote: > > 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. > > I've install crda and it works great with 2.6.31, althought I had > to override the EEPROM, which reports bugus data: > > - ath_regd_sanitize(reg); > - > - printk(KERN_DEBUG "ath: EEPROM regdomain: 0x%0x\n", reg->current_rd); > + reg->current_rd = CTRY_GERMANY | COUNTRY_ERD_FLAG; > FYI: the athinfo (from the madwifi-project) utility can be used to write a a sane regdomain code into the EEPROM chip on most ath5k cards. -- 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