All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Backlund <tmb@mandriva.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: reinette chatre <reinette.chatre@intel.com>,
	"linux-wireless@vger.kernel.org" <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
Date: Fri, 17 Jul 2009 03:33:10 +0300	[thread overview]
Message-ID: <4A5FC6C6.7010404@mandriva.org> (raw)
In-Reply-To: <1247788728.1055.15.camel@johannes.local>

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 <tmb@mandriva.org>


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)


      reply	other threads:[~2009-07-17  0:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 22:15 unable to bring up iwlagn wireless after update from 2.6.29.6 to 2.6.31-rc3 Thomas Backlund
2009-07-14 22:37 ` Johannes Berg
2009-07-14 22:45   ` Thomas Backlund
2009-07-15 15:45     ` reinette chatre
2009-07-16 22:09       ` Thomas Backlund
2009-07-16 22:18         ` Johannes Berg
2009-07-16 22:30           ` Johannes Berg
2009-07-16 23:35             ` Thomas Backlund
2009-07-16 23:43               ` Luis R. Rodriguez
2009-07-16 23:51                 ` Luis R. Rodriguez
2009-07-16 23:51               ` Thomas Backlund
2009-07-16 23:53                 ` Johannes Berg
2009-07-16 23:35           ` Thomas Backlund
2009-07-16 23:58             ` Johannes Berg
2009-07-17  0:33               ` Thomas Backlund [this message]

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=4A5FC6C6.7010404@mandriva.org \
    --to=tmb@mandriva.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.