public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: reinette chatre <reinette.chatre@intel.com>
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	johannes@sipsolutions.net
Subject: Re: iwlwifi (4965) regression since 2.6.30
Date: Mon, 27 Jul 2009 18:07:34 +0200	[thread overview]
Message-ID: <1248710854.28545.202.camel@violet> (raw)
In-Reply-To: <1248710618.1216.452.camel@rc-desk>

Hi Reinette,

> > I noticed regression in 2.6.31-rc{3,4}. iwlagn driver does not work for me.
> > I got:
> > ifconfig wlan0 up
> > SIOCSIFFLAGS: Unknown error 132
> 
> yes - this is a rfkill error
> 
> > 
> > dmesg shows:
> > [ 1812.806813] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux,
> > 1.3.27kds
> > [ 1812.806820] iwlagn: Copyright(c) 2003-2009 Intel Corporation
> > [ 1812.806996] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> > [ 1812.807024] iwlagn 0000:03:00.0: setting latency timer to 64
> > [ 1812.807699] iwlagn 0000:03:00.0: Detected Intel Wireless WiFi Link 4965AGN
> > REV=0x4
> > [ 1812.860879] iwlagn 0000:03:00.0: Tunable channels: 11 802.11bg, 13 802.11a
> > channels
> > [ 1812.861012]   alloc irq_desc for 32 on node -1
> > [ 1812.861017]   alloc kstat_irqs on node -1
> > [ 1812.861069] iwlagn 0000:03:00.0: irq 32 for MSI/MSI-X
> > [ 1812.882796] phy0: Selected rate control algorithm 'iwl-agn-rs'
> > 
> > I definitely have rfkill on. I tried to even toggle rfkill, no success. The HW
> > is Lenovo T61 (thus acer/hp rfkill patches do not work for me).
> 
> Maybe Johannes knows if there is something that you need for thinkpad.

it works fine with my X200 and a 5350 card, but it could be that the
code inside the thinkpad driver is different for a T61.

Regards

Marcel



      parent reply	other threads:[~2009-07-27 16:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26  7:57 iwlwifi (4965) regression since 2.6.30 Lukas Hejtmanek
2009-07-27 16:03 ` reinette chatre
2009-07-27 16:06   ` Johannes Berg
2009-07-28 11:21     ` Lukas Hejtmanek
2009-07-28 12:54       ` Johannes Berg
2009-08-02 22:12         ` Lukas Hejtmanek
2009-08-03 21:47       ` reinette chatre
2009-08-04  8:49         ` Lukas Hejtmanek
2009-08-04 22:49           ` reinette chatre
2009-08-04 22:56             ` Lukas Hejtmanek
2009-08-04 23:38               ` reinette chatre
2009-08-06 13:22                 ` Henrique de Moraes Holschuh
2009-08-06 22:41                   ` Lukas Hejtmanek
2009-08-06 23:07                     ` Henrique de Moraes Holschuh
2009-08-07 20:32                       ` Johannes Stezenbach
2009-08-07 21:16                         ` Lukas Hejtmanek
2009-08-07 21:35                       ` Lukas Hejtmanek
2009-08-13 22:59                         ` reinette chatre
2009-08-14  2:10                           ` Henrique de Moraes Holschuh
2009-08-14 16:07                             ` reinette chatre
2009-07-27 16:07   ` Marcel Holtmann [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=1248710854.28545.202.camel@violet \
    --to=marcel@holtmann.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=xhejtman@ics.muni.cz \
    /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