Return-path: Received: from mbox2.netikka.net ([213.250.81.203]:48595 "EHLO mbox2.netikka.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933343AbZGQAdN (ORCPT ); Thu, 16 Jul 2009 20:33:13 -0400 Message-ID: <4A5FC6C6.7010404@mandriva.org> Date: Fri, 17 Jul 2009 03:33:10 +0300 From: Thomas Backlund MIME-Version: 1.0 To: Johannes Berg CC: reinette chatre , "linux-wireless@vger.kernel.org" Subject: Re: unable to bring up iwlagn wireless after update from 2.6.29.6 to 2.6.31-rc3 References: <4A5D0374.5040702@mandriva.org> <1247611024.1796.21.camel@johannes.local> <4A5D0A7F.5090108@mandriva.org> <1247672725.17896.1974.camel@rc-desk> <4A5FA52D.7030701@mandriva.org> <1247782731.31442.3.camel@johannes.local> <4A5FB944.90709@mandriva.org> <1247788728.1055.15.camel@johannes.local> In-Reply-To: <1247788728.1055.15.camel@johannes.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: Johannes Berg skrev: > On Fri, 2009-07-17 at 02:35 +0300, Thomas Backlund wrote: > >>> So far so good. Your platform's soft-switch is wired to the card's hard >>> kill line. Mind trying >>> >>> ./rfkill unblock 0 >>> >>> (or whatever ID the acer-wireless has) at this point to see what >>> happens? I would hope it goes back to the working state. >>> >> Nothing happends... >> >> It does not change anything on either acer-wireless or phy0 > > Humm. Can you try this? > > johannes > > --- wireless-testing.orig/drivers/platform/x86/acer-wmi.c 2009-07-17 00:19:20.000000000 +0200 > +++ wireless-testing/drivers/platform/x86/acer-wmi.c 2009-07-17 01:58:11.000000000 +0200 > @@ -973,7 +973,7 @@ static int acer_rfkill_set(void *data, b > { > acpi_status status; > u32 cap = (unsigned long)data; > - status = set_u32(!!blocked, cap); > + status = set_u32(!blocked, cap); > if (ACPI_FAILURE(status)) > return -ENODEV; > return 0; > Funny how easy the fix was... Now the rfkill works... ;-) I can enable/disable it as many times as I want... So it's: Tested-by: Thomas Backlund The difference is that before this patch, bluetooth & wireless were both disabled at boot... With this patch the system boots up with bluetooth & wireless is enabled by default (But it's not a regression as it now behaves just like 2.6.29 & 2.6.30 series kernels)