From: Thomas Backlund <tmb@mandriva.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Thomas Backlund <tmb@mandriva.org>,
"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: Wed, 15 Jul 2009 01:45:19 +0300 [thread overview]
Message-ID: <4A5D0A7F.5090108@mandriva.org> (raw)
In-Reply-To: <1247611024.1796.21.camel@johannes.local>
Johannes Berg skrev:
> On Wed, 2009-07-15 at 01:15 +0300, Thomas Backlund wrote:
>> Hi,
>> (please cc me on replies)
>>
>> before I start to try and figure this out, I thought of asking here if
>> it rings any bells...
>>
>> Distribution: Mandriva Cooker
>> Arch: x86_64.
>>
>> NIC: 04:00.0 Network controller [0280]: Intel Corporation PRO/Wireless
>> 4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61)
>>
>> ucode version: 228.61.2.24
>>
>> wpa_supplicant version: 0.6.9
>> crda version: 1.1.0
>> wireless-regdb version: 2009.04.17
>>
>> Running a 2.6.29.6 based kernel works with iwlagn
>> Running a 2.6.30.1 based kernel works with iwlagn
>>
>> Running a 2.6.31-rc3 based kernel gets me this:
>>
>> --- cut ---
>> Bringing up interface wlan0: RTNETLINK answers: Unknown error 132
>> RTNETLINK answers: Unknown error 132
>
> press your rfkill button.
I wish it was that simple :-(
I already tried it, but it does not help...
I get no reaction what so ever from pressing it...
The laptop is an Acer 5720G if that makes any difference...
Could it be that rfkill has been broken for my laptop ?
And why should I need to press rfkill now, when I didn't before ?
Has some kernel defaults changed since 2.6.30 series ?
--
Thomas
next prev parent reply other threads:[~2009-07-14 22:45 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 [this message]
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
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=4A5D0A7F.5090108@mandriva.org \
--to=tmb@mandriva.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).