All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Kudła" <michal.kudla@gmail.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [2.6.26-rc5] iwlwifi 4965 not working - last on 2.6.23
Date: Wed, 11 Jun 2008 21:17:00 +0200	[thread overview]
Message-ID: <200806112117.01544.Michal.Kudla@gmail.com> (raw)
In-Reply-To: <1213151464.7814.630.camel@debian.sh.intel.com>

Hi,
Still don't work.
I have tested this patch with and without RFKILL kernel settings
Compressed result files:
config-2.6.26-rc5-no-rfkill.txt
config-2.6.26-rc5-rfkill.txt
dmesg-2.6.26-rc5-no-rfkill.txt
dmesg-2.6.26-rc5-rfkill.txt
are in
http://michal.kudla.googlepages.com/iwlwifi-problem-with-patch-Zhu-Yi.t=
a.bz2



W li=C5=9Bcie datowanym na =C5=9Broda, 11 czerwca 2008, Zhu Yi pisze:
>ZY On Fri, 2008-06-06 at 03:47 -0700, Andrew Morton wrote:
>ZY > > ADDRCONF(NETDEV_UP): wlan0: link is not ready
>ZY > > iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
>ZY > > mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from
>ZY > hardware (-5)
>ZY > > iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd fai=
led:
>ZY > -5
>ZY > > iwl4965: WARNING: Requesting MAC access during RFKILL wakes up =
NIC
>ZY > > iwl4965: WARNING: Requesting MAC access during RFKILL wakes up =
NIC
>ZY
>ZY Looks like a rfkill related problem. Can you please try this patch?
>ZY http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=3D1673
>ZY
>ZY Thanks,
>ZY -yi
>ZY
>ZY


--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "Michał Kudła" <michal.kudla@gmail.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [2.6.26-rc5] iwlwifi 4965 not working - last on 2.6.23
Date: Wed, 11 Jun 2008 21:17:00 +0200	[thread overview]
Message-ID: <200806112117.01544.Michal.Kudla@gmail.com> (raw)
In-Reply-To: <1213151464.7814.630.camel@debian.sh.intel.com>

Hi,
Still don't work.
I have tested this patch with and without RFKILL kernel settings
Compressed result files:
config-2.6.26-rc5-no-rfkill.txt
config-2.6.26-rc5-rfkill.txt
dmesg-2.6.26-rc5-no-rfkill.txt
dmesg-2.6.26-rc5-rfkill.txt
are in
http://michal.kudla.googlepages.com/iwlwifi-problem-with-patch-Zhu-Yi.ta.bz2



W liście datowanym na środa, 11 czerwca 2008, Zhu Yi pisze:
>ZY On Fri, 2008-06-06 at 03:47 -0700, Andrew Morton wrote:
>ZY > > ADDRCONF(NETDEV_UP): wlan0: link is not ready
>ZY > > iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
>ZY > > mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from
>ZY > hardware (-5)
>ZY > > iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed:
>ZY > -5
>ZY > > iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
>ZY > > iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
>ZY
>ZY Looks like a rfkill related problem. Can you please try this patch?
>ZY http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1673
>ZY
>ZY Thanks,
>ZY -yi
>ZY
>ZY



  reply	other threads:[~2008-06-11 19:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 22:39 [2.6.26-rc5] iwlwifi 4965 not working - last on 2.6.23 Michał Kudła
2008-06-06 10:47 ` Andrew Morton
2008-06-06 19:37   ` Michał Kudła
2008-06-06 19:37     ` Michał Kudła
2008-06-11  2:31   ` Zhu Yi
2008-06-11 19:17     ` Michał Kudła [this message]
2008-06-11 19:17       ` Michał Kudła
2008-06-13  7:54       ` Zhu Yi
2008-06-13  7:54         ` Zhu Yi
2008-06-13 17:37     ` Michał Kudła
2008-06-13 17:37       ` Michał Kudła
2008-06-16  1:51       ` Zhu Yi
2008-06-16  1:51         ` Zhu Yi
2008-06-16 18:21         ` Michał Kudła
2008-06-16 18:21           ` Michał Kudła
2008-06-17  1:11           ` Zhu Yi
2008-06-17  1:11             ` Zhu Yi
2008-06-23  3:30             ` Michał Kudła
2008-06-23  5:05               ` Zhu Yi
2008-06-23  5:05                 ` Zhu Yi
2008-06-23  5:32                 ` Michał Kudła
2008-06-23  5:32                   ` Michał Kudła
2008-06-23  5:52                   ` Zhu Yi
2008-06-23  5:52                     ` Zhu Yi
2008-06-23 19:03                     ` Michał Kudła
2008-06-24  2:41                       ` Zhu Yi
2008-06-24  3:37                         ` Michał Kudła
2008-06-24  3:51                           ` Zhu Yi
2008-06-24  3:51                             ` Zhu Yi
2008-06-24  6:12                             ` Michał Kudła
2008-06-27 18:01                             ` Michał Kudła
2008-06-27 18:01                               ` Michał Kudła
2008-07-06 20:44                             ` Michał Kudła
2008-07-06 20:44                               ` Michał Kudła
2008-07-07  1:45                               ` Zhu Yi
2008-07-07  1:45                                 ` Zhu Yi
2008-06-06 10:47 ` Rafael J. Wysocki
2008-06-06 10:47   ` Rafael J. Wysocki

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=200806112117.01544.Michal.Kudla@gmail.com \
    --to=michal.kudla@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yi.zhu@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.