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: Mon, 16 Jun 2008 20:21:36 +0200 [thread overview]
Message-ID: <200806162021.37105.Michal.Kudla@gmail.com> (raw)
In-Reply-To: <1213581088.7814.882.camel@debian.sh.intel.com>
Hi,
After
laptok ~ # echo 0 > /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rf_kill
laptok ~ # iwconfig wlan0 txpower on
laptok ~ # /etc/init.d/net.wlan0 restart
* Service net.wlan0 starting
* Service net.wlan0 started
laptok ~ # dmesg >dmesg-`uname -r`_`date +%F`.txt
I get in dmesg
=2E..
iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
ACPI: PCI interrupt for device 0000:04:00.0 disabled
HW CONFIG: channel=3D10 freq=3D2457 phymode=3D2
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PM: Writing back config space on device 0000:04:00.0 at offset 1 (was 1=
00102,=20
writing 100106)
HW CONFIG: channel=3D10 freq=3D2457 phymode=3D2
ADDRCONF(NETDEV_UP): wlan0: link is not ready
HW CONFIG: channel=3D10 freq=3D2457 phymode=3D2
wlan0: Initial auth_alg=3D0
wlan0: authenticate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=3D30) FC=3D0x00b0 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
HW CONFIG: channel=3D10 freq=3D2457 phymode=3D2
wlan0: Initial auth_alg=3D0
wlan0: authenticate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=3D30) FC=3D0x00b0 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
wlan0: RX authentication from 00:01:e3:06:00:35 (alg=3D0 transaction=3D=
2 status=3D0)
wlan0: authenticated
wlan0: associate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=3D50) FC=3D0x0000 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
wlan0: authentication frame received from 00:01:e3:06:00:35, but not in=
=20
authenticate state - ignored
wlan0: authentication frame received from 00:01:e3:06:00:35, but not in=
=20
authenticate state - ignored
wlan0: RX AssocResp from 00:01:e3:06:00:35 (capab=3D0x11 status=3D0 aid=
=3D1)
wlan0: associated
phy0: Added STA 00:01:e3:06:00:35
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
phy0: TX to low-level driver (len=3D116) FC=3D0x4108 DUR=3D0x0102=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D33:33:00:00:00:16
HW CONFIG: channel=3D10 freq=3D2457 phymode=3D2
wlan0: Initial auth_alg=3D0
wlan0: authenticate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=3D30) FC=3D0x00b0 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
wlan0: RX authentication from 00:01:e3:06:00:35 (alg=3D0 transaction=3D=
2 status=3D0)
wlan0: authenticated
wlan0: associate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=3D56) FC=3D0x0020 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
wlan0: RX ReassocResp from 00:01:e3:06:00:35 (capab=3D0x11 status=3D0 a=
id=3D1)
wlan0: associated
wlan0: association frame received from 00:01:e3:06:00:35, but not in as=
sociate=20
state - ignored
phy0: TX to low-level driver (len=3D104) FC=3D0x4108 DUR=3D0x0102=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D33:33:ff:42:88:f9
phy0: TX to low-level driver (len=3D96) FC=3D0x4108 DUR=3D0x0102=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D33:33:00:00:00:02
phy0: TX to low-level driver (len=3D68) FC=3D0x4108 DUR=3D0x0102=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3Dff:ff:ff:ff:ff:ff
phy0: TX to low-level driver (len=3D116) FC=3D0x4108 DUR=3D0x0102=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D33:33:00:00:00:16
phy0: TX to low-level driver (len=3D68) FC=3D0x4108 DUR=3D0x0102=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3Dff:ff:ff:ff:ff:ff
phy0: TX to low-level driver (len=3D96) FC=3D0x4108 DUR=3D0x0102=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D33:33:00:00:00:02
phy0: TX to low-level driver (len=3D96) FC=3D0x4108 DUR=3D0x0102=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D33:33:00:00:00:02
wlan0: no IPv6 routers present
phy0: TX to low-level driver (len=3D46) FC=3D0x0040 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
phy0: TX to low-level driver (len=3D46) FC=3D0x0040 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
phy0: TX to low-level driver (len=3D46) FC=3D0x0040 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
phy0: TX to low-level driver (len=3D46) FC=3D0x0040 DUR=3D0x013a=20
A1=3D00:01:e3:06:00:35 A2=3D00:13:e8:42:88:f9 A3=3D00:01:e3:06:00:35
And my wifi working!
Bt, I don't know why my wifi working under 2.6.23 and 2.6.24?
W li=C5=9Bcie datowanym na poniedzia=C5=82ek, 16 czerwca 2008, Zhu Yi p=
isze:
>ZY On Fri, 2008-06-13 at 19:37 +0200, Micha=C5=82 Kud=C5=82a wrote:
>ZY > dmesg-2.6.26-rc5_2008-06-13.txt
>ZY
>ZY >From this log:
>ZY
>ZY iwl4965: U iwl4965_radio_kill_sw Manual SW RF KILL set to: RADIO OF=
=46
>ZY iwl4965: I iwl4965_rx_card_state_notif Card state received: HW:On
>ZY SW:Kill
>ZY iwl4965: U iwl4965_mac_config leave - radio disabled
>ZY iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed:=
-5
>ZY iwl4965: U iwl4965_bg_rf_kill Can not turn radio back on - disabled=
by
>ZY SW switch
>ZY iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
>ZY
>ZY Your radio is disabled by the software rf_kill switch. Please do a
>ZY
>ZY $ echo 0 > /sys/bus/pci/drivers/iwl4965/<dev id>/rfkill\:rfkill0/st=
ate
>ZY
>ZY I wonder if you (or some application) did something like a `iwconfi=
g
>ZY wlan0 txpower off` so that the radio is disabled. Maybe you can try
>ZY `iwconfig wlan0 txpower on`?
>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: Mon, 16 Jun 2008 20:21:36 +0200 [thread overview]
Message-ID: <200806162021.37105.Michal.Kudla@gmail.com> (raw)
In-Reply-To: <1213581088.7814.882.camel@debian.sh.intel.com>
Hi,
After
laptok ~ # echo 0 > /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rf_kill
laptok ~ # iwconfig wlan0 txpower on
laptok ~ # /etc/init.d/net.wlan0 restart
* Service net.wlan0 starting
* Service net.wlan0 started
laptok ~ # dmesg >dmesg-`uname -r`_`date +%F`.txt
I get in dmesg
...
iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
ACPI: PCI interrupt for device 0000:04:00.0 disabled
HW CONFIG: channel=10 freq=2457 phymode=2
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PM: Writing back config space on device 0000:04:00.0 at offset 1 (was 100102,
writing 100106)
HW CONFIG: channel=10 freq=2457 phymode=2
ADDRCONF(NETDEV_UP): wlan0: link is not ready
HW CONFIG: channel=10 freq=2457 phymode=2
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
HW CONFIG: channel=10 freq=2457 phymode=2
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
wlan0: RX authentication from 00:01:e3:06:00:35 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=50) FC=0x0000 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
wlan0: authentication frame received from 00:01:e3:06:00:35, but not in
authenticate state - ignored
wlan0: authentication frame received from 00:01:e3:06:00:35, but not in
authenticate state - ignored
wlan0: RX AssocResp from 00:01:e3:06:00:35 (capab=0x11 status=0 aid=1)
wlan0: associated
phy0: Added STA 00:01:e3:06:00:35
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
phy0: TX to low-level driver (len=116) FC=0x4108 DUR=0x0102
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=33:33:00:00:00:16
HW CONFIG: channel=10 freq=2457 phymode=2
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
wlan0: RX authentication from 00:01:e3:06:00:35 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:01:e3:06:00:35
phy0: TX to low-level driver (len=56) FC=0x0020 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
wlan0: RX ReassocResp from 00:01:e3:06:00:35 (capab=0x11 status=0 aid=1)
wlan0: associated
wlan0: association frame received from 00:01:e3:06:00:35, but not in associate
state - ignored
phy0: TX to low-level driver (len=104) FC=0x4108 DUR=0x0102
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=33:33:ff:42:88:f9
phy0: TX to low-level driver (len=96) FC=0x4108 DUR=0x0102
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=33:33:00:00:00:02
phy0: TX to low-level driver (len=68) FC=0x4108 DUR=0x0102
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=ff:ff:ff:ff:ff:ff
phy0: TX to low-level driver (len=116) FC=0x4108 DUR=0x0102
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=33:33:00:00:00:16
phy0: TX to low-level driver (len=68) FC=0x4108 DUR=0x0102
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=ff:ff:ff:ff:ff:ff
phy0: TX to low-level driver (len=96) FC=0x4108 DUR=0x0102
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=33:33:00:00:00:02
phy0: TX to low-level driver (len=96) FC=0x4108 DUR=0x0102
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=33:33:00:00:00:02
wlan0: no IPv6 routers present
phy0: TX to low-level driver (len=46) FC=0x0040 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
phy0: TX to low-level driver (len=46) FC=0x0040 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
phy0: TX to low-level driver (len=46) FC=0x0040 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
phy0: TX to low-level driver (len=46) FC=0x0040 DUR=0x013a
A1=00:01:e3:06:00:35 A2=00:13:e8:42:88:f9 A3=00:01:e3:06:00:35
And my wifi working!
Bt, I don't know why my wifi working under 2.6.23 and 2.6.24?
W liście datowanym na poniedziałek, 16 czerwca 2008, Zhu Yi pisze:
>ZY On Fri, 2008-06-13 at 19:37 +0200, Michał Kudła wrote:
>ZY > dmesg-2.6.26-rc5_2008-06-13.txt
>ZY
>ZY >From this log:
>ZY
>ZY iwl4965: U iwl4965_radio_kill_sw Manual SW RF KILL set to: RADIO OFF
>ZY iwl4965: I iwl4965_rx_card_state_notif Card state received: HW:On
>ZY SW:Kill
>ZY iwl4965: U iwl4965_mac_config leave - radio disabled
>ZY iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -5
>ZY iwl4965: U iwl4965_bg_rf_kill Can not turn radio back on - disabled by
>ZY SW switch
>ZY iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
>ZY
>ZY Your radio is disabled by the software rf_kill switch. Please do a
>ZY
>ZY $ echo 0 > /sys/bus/pci/drivers/iwl4965/<dev id>/rfkill\:rfkill0/state
>ZY
>ZY I wonder if you (or some application) did something like a `iwconfig
>ZY wlan0 txpower off` so that the radio is disabled. Maybe you can try
>ZY `iwconfig wlan0 txpower on`?
>ZY
>ZY Thanks,
>ZY -yi
>ZY
>ZY
next prev parent reply other threads:[~2008-06-16 18:21 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
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 [this message]
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=200806162021.37105.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.