Hello,
according to http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html
[1.] One line summary of the problem:
[2.6.26-rc5] iwlwifi 4965 not working - last on 2.6.23
[2.] Full description of the problem/report:
linux: gentoo
kernel vanilla-sources-2-6-26-rc5
laptop: Asus S96S
WiFi: intel 4695
WiFi not working.
In the same config, but with gentoo-sources-2.6.23 WiFi working well.
dmesg - 2.6.23
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.25ds
iwl4965: Copyright(c) 2003-2007 Intel Corporation
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:04:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
wmaster0: Selected rate control algorithm 'iwl-4965-rs'
...
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 21
PM: Writing back config space on device 0000:04:00.0 at offset 1 (was 100102,
writing 100106)
iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
ADDRCONF(NETDEV_UP): wlan0: link is not ready
r8169: eth0: link up
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 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
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=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
dmesg 2.6.26
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.26kds
iwl4965: Copyright(c) 2003-2008 Intel Corporation
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:04:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
phy0: Selected rate control algorithm 'iwl-4965-rs'
ACPI: PCI interrupt for device 0000:04:00.0 disabled
EXT3 FS on sda3, internal journal
Adding 987988k swap on /dev/sda2. Priority:-1 extents:1 across:987988k
r8169: eth0: link up
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)
firmware: requesting iwlwifi-4965-1.ucode
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-5)
iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -5
iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
...
iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
ACPI: PCI interrupt for device 0000:04:00.0 disabled
[3.] Keywords (i.e., modules, networking, kernel):
kernel, wifi, iwlwifi, asus, laptop
[4.] Kernel version (from /proc/version):
Linux version 2.6.23-gentoo-r2 (root@laptok) (gcc version 4.2.2 (Gentoo 4.2.2
p1.0)) #3 SMP Sun Jan 13 12:46:44 CET 2008
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
none
[6.] A small shell script or example program which triggers the
problem (if possible)
dmesg | grep -E '(KB)|(KiB)|(MB)'
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
[7.2.] Processor information (from /proc/cpuinfo):
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
stepping : 10
cpu MHz : 1995.081
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16
xtpr lahf_lm
bogomips : 3992.41
clflush size : 64
X 2
[7.3.] Module information (from /proc/modules):
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
[7.5.] PCI information ('lspci -vvv' as root)
[7.6.] SCSI information (from /proc/scsi/scsi)
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
[X.] Other notes, patches, fixes, workarounds:
compressed files:
dmesg-2.6.23
dmesg-2.6.26
.config-2.6.26
.config-2.6.23
at http://michal.kudla.googlepages.com/iwl-problem.tar.gz
[Added some CCs.]
On Friday, 6 of June 2008, Michał Kudła wrote:
> Hello,
> according to http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html
> [1.] One line summary of the problem:
> [2.6.26-rc5] iwlwifi 4965 not working - last on 2.6.23
>
> [2.] Full description of the problem/report:
> linux: gentoo
> kernel vanilla-sources-2-6-26-rc5
> laptop: Asus S96S
> WiFi: intel 4695
> WiFi not working.
> In the same config, but with gentoo-sources-2.6.23 WiFi working well.
>
> dmesg - 2.6.23
> iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.25ds
> iwl4965: Copyright(c) 2003-2007 Intel Corporation
> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 21
> PCI: Setting latency timer of device 0000:04:00.0 to 64
> iwl4965: Detected Intel Wireless WiFi Link 4965AGN
> wmaster0: Selected rate control algorithm 'iwl-4965-rs'
> ...
> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 21
> PM: Writing back config space on device 0000:04:00.0 at offset 1 (was 100102,
> writing 100106)
> iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> r8169: eth0: link up
> wlan0: Initial auth_alg=0
> wlan0: authenticate with AP 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
> 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=2)
> wlan0: associated
> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> wlan0: no IPv6 routers present
>
> dmesg 2.6.26
> iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.26kds
> iwl4965: Copyright(c) 2003-2008 Intel Corporation
> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:04:00.0 to 64
> iwl4965: Detected Intel Wireless WiFi Link 4965AGN
> iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
> phy0: Selected rate control algorithm 'iwl-4965-rs'
> ACPI: PCI interrupt for device 0000:04:00.0 disabled
> EXT3 FS on sda3, internal journal
> Adding 987988k swap on /dev/sda2. Priority:-1 extents:1 across:987988k
> r8169: eth0: link up
> 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)
> firmware: requesting iwlwifi-4965-1.ucode
> Registered led device: iwl-phy0:radio
> Registered led device: iwl-phy0:assoc
> Registered led device: iwl-phy0:RX
> Registered led device: iwl-phy0:TX
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
> mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-5)
> iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -5
> iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
> iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
> ...
> iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
> ACPI: PCI interrupt for device 0000:04:00.0 disabled
>
>
> [3.] Keywords (i.e., modules, networking, kernel):
> kernel, wifi, iwlwifi, asus, laptop
> [4.] Kernel version (from /proc/version):
> Linux version 2.6.23-gentoo-r2 (root@laptok) (gcc version 4.2.2 (Gentoo 4.2.2
> p1.0)) #3 SMP Sun Jan 13 12:46:44 CET 2008
> [5.] Output of Oops.. message (if applicable) with symbolic information
> resolved (see Documentation/oops-tracing.txt)
> none
> [6.] A small shell script or example program which triggers the
> problem (if possible)
> dmesg | grep -E '(KB)|(KiB)|(MB)'
> [7.] Environment
> [7.1.] Software (add the output of the ver_linux script here)
> [7.2.] Processor information (from /proc/cpuinfo):
> cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
> stepping : 10
> cpu MHz : 1995.081
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 2
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
> constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16
> xtpr lahf_lm
> bogomips : 3992.41
> clflush size : 64
>
> X 2
>
> [7.3.] Module information (from /proc/modules):
> [7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
> [7.5.] PCI information ('lspci -vvv' as root)
> [7.6.] SCSI information (from /proc/scsi/scsi)
> [7.7.] Other information that might be relevant to the problem
> (please look in /proc and include all information that you
> think to be relevant):
> [X.] Other notes, patches, fixes, workarounds:
> compressed files:
> dmesg-2.6.23
> dmesg-2.6.26
> .config-2.6.26
> .config-2.6.23
> at http://michal.kudla.googlepages.com/iwl-problem.tar.gz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
--
"Premature optimization is the root of all evil." - Donald Knuth
(cc linux-wireless)
On Fri, 6 Jun 2008 00:39:48 +0200 Micha__ Kud__a <[email protected]> wrote:
> Hello,
> according to http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html
> [1.] One line summary of the problem:
> [2.6.26-rc5] iwlwifi 4965 not working - last on 2.6.23
Thanks. Do you know if it worked in 2.6.24 or 2.6.25?
> [2.] Full description of the problem/report:
> linux: gentoo
> kernel vanilla-sources-2-6-26-rc5
> laptop: Asus S96S
> WiFi: intel 4695
> WiFi not working.
> In the same config, but with gentoo-sources-2.6.23 WiFi working well.
>
> dmesg - 2.6.23
> iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.25ds
> iwl4965: Copyright(c) 2003-2007 Intel Corporation
> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 21
> PCI: Setting latency timer of device 0000:04:00.0 to 64
> iwl4965: Detected Intel Wireless WiFi Link 4965AGN
> wmaster0: Selected rate control algorithm 'iwl-4965-rs'
> ...
> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 21
> PM: Writing back config space on device 0000:04:00.0 at offset 1 (was 100102,
> writing 100106)
> iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> r8169: eth0: link up
> wlan0: Initial auth_alg=0
> wlan0: authenticate with AP 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
> 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=2)
> wlan0: associated
> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> wlan0: no IPv6 routers present
>
> dmesg 2.6.26
> iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.26kds
> iwl4965: Copyright(c) 2003-2008 Intel Corporation
> ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:04:00.0 to 64
> iwl4965: Detected Intel Wireless WiFi Link 4965AGN
> iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
> phy0: Selected rate control algorithm 'iwl-4965-rs'
> ACPI: PCI interrupt for device 0000:04:00.0 disabled
> EXT3 FS on sda3, internal journal
> Adding 987988k swap on /dev/sda2. Priority:-1 extents:1 across:987988k
> r8169: eth0: link up
> 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)
> firmware: requesting iwlwifi-4965-1.ucode
> Registered led device: iwl-phy0:radio
> Registered led device: iwl-phy0:assoc
> Registered led device: iwl-phy0:RX
> Registered led device: iwl-phy0:TX
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
> mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-5)
> iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -5
> iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
> iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
> ...
> iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
> ACPI: PCI interrupt for device 0000:04:00.0 disabled
>
>
> [3.] Keywords (i.e., modules, networking, kernel):
> kernel, wifi, iwlwifi, asus, laptop
> [4.] Kernel version (from /proc/version):
> Linux version 2.6.23-gentoo-r2 (root@laptok) (gcc version 4.2.2 (Gentoo 4.2.2
> p1.0)) #3 SMP Sun Jan 13 12:46:44 CET 2008
> [5.] Output of Oops.. message (if applicable) with symbolic information
> resolved (see Documentation/oops-tracing.txt)
> none
> [6.] A small shell script or example program which triggers the
> problem (if possible)
> dmesg | grep -E '(KB)|(KiB)|(MB)'
> [7.] Environment
> [7.1.] Software (add the output of the ver_linux script here)
> [7.2.] Processor information (from /proc/cpuinfo):
> cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
> stepping : 10
> cpu MHz : 1995.081
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 2
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
> constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16
> xtpr lahf_lm
> bogomips : 3992.41
> clflush size : 64
>
> X 2
>
> [7.3.] Module information (from /proc/modules):
> [7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
> [7.5.] PCI information ('lspci -vvv' as root)
> [7.6.] SCSI information (from /proc/scsi/scsi)
> [7.7.] Other information that might be relevant to the problem
> (please look in /proc and include all information that you
> think to be relevant):
> [X.] Other notes, patches, fixes, workarounds:
> compressed files:
> dmesg-2.6.23
> dmesg-2.6.26
> .config-2.6.26
> .config-2.6.23
> at http://michal.kudla.googlepages.com/iwl-problem.tar.gz
W liście datowanym na piątek, 6 czerwca 2008, Andrew Morton pisze:
>AM > [2.6.26-rc5] iwlwifi 4965 not working - last on 2.6.23
>AM
>AM Thanks. Do you know if it worked in 2.6.24 or 2.6.25?
I checked:
- vanilla-sources-2.6.24.7 (works),
- gentoo-sources-2.6.25-r4 (don't work)
I uploaded files:
.config-2.6.23
.config.2.6.24.7
.config.2.6.25-gentoo-r4
.config-2.6.26
dmesg-2.6.23
dmesg-2.6.24.txt
dmesg-2.6.25.txt
dmesg-2.6.26
http://michal.kudla.googlepages.com/iwlwifi-problem-2.bz2
more infos about 2.6.25 anf iwlwifi:
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1657
http://bugs.gentoo.org/show_bug.cgi?format=multiple&id=218565
On Fri, 2008-06-06 at 03:47 -0700, Andrew Morton wrote:
> > ADDRCONF(NETDEV_UP): wlan0: link is not ready
> > iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
> > mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from
> hardware (-5)
> > iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed:
> -5
> > iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
> > iwl4965: WARNING: Requesting MAC access during RFKILL wakes up NIC
Looks like a rfkill related problem. Can you please try this patch?
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1673
Thanks,
-yi
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
On Wed, 2008-06-11 at 21:17 +0200, Michał Kudła wrote:
> 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
Can you please load the module with "debug=0x20002" and attached the
dmesg?
Thanks,
-yi
Hi,
laptok ~ # modprobe -rv iwl4965
laptok ~ # modprobe -v iwl4965 debug=0x20002
laptok ~ # dmesg >dmesg-`uname -r`_`date +%F`.txt
laptok iwlwifi # ls -1
dmesg-2.6.23-gentoo-r2_2008-06-13.txt
dmesg-2.6.24.7_2008-06-13.txt
dmesg-2.6.25-gentoo-r4_2008-06-13.txt
dmesg-2.6.26-rc5_2008-06-13.txt
results:
http://michal.kudla.googlepages.com/dmesg-debug0x20002.tar.gz
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
On Fri, 2008-06-13 at 19:37 +0200, Michał Kudła wrote:
> dmesg-2.6.26-rc5_2008-06-13.txt
>From this log:
iwl4965: U iwl4965_radio_kill_sw Manual SW RF KILL set to: RADIO OFF
iwl4965: I iwl4965_rx_card_state_notif Card state received: HW:On
SW:Kill
iwl4965: U iwl4965_mac_config leave - radio disabled
iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -5
iwl4965: U iwl4965_bg_rf_kill Can not turn radio back on - disabled by
SW switch
iwl4965: Error sending REPLY_WEPKEY: enqueue_hcmd failed: -5
Your radio is disabled by the software rf_kill switch. Please do a
$ echo 0 > /sys/bus/pci/drivers/iwl4965/<dev id>/rfkill\:rfkill0/state
I wonder if you (or some application) did something like a `iwconfig
wlan0 txpower off` so that the radio is disabled. Maybe you can try
`iwconfig wlan0 txpower on`?
Thanks,
-yi
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
On Mon, 2008-06-16 at 20:21 +0200, Michał Kudła wrote:
> And my wifi working!
>
> Bt, I don't know why my wifi working under 2.6.23 and 2.6.24?
mac80211 in those (old) kernels doesn't indicate to switch the SW
rf_kill on with user sets txpower off.
Thanks,
-yi
Hi,
I installed new version - 2.6.26-rc7.
There is some changes and I don't execute last settings
>ZY Your radio is disabled by the software rf_kill switch. Please do a
>ZY $ echo 0 > /sys/bus/pci/drivers/iwl4965/<dev id>/rfkill\:rfkill0/state
Still don't work
If my distro (Gentoo) is conflicted, please point to proper distro
My dmesg
http://michal.kudla.googlepages.com/dmesg-2.6.26-rc7_2008-06-23.txt
My console log
Password:
Last login: Mon Jun 23 04:58:21 CEST 2008 on tty1
laptok ~ # modprobe -rv iwl4965
rmmod /lib/modules/2.6.26-rc7/kernel/drivers/net/wireless/iwlwifi/iwl4965.ko
rmmod /lib/modules/2.6.26-rc7/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko
rmmod /lib/modules/2.6.26-rc7/kernel/net/mac80211/mac80211.ko
laptok ~ # modprobe -v iwl4965 debug=0x20002
insmod /lib/modules/2.6.26-rc7/kernel/net/mac80211/mac80211.ko
insmod /lib/modules/2.6.26-rc7/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko
insmod /lib/modules/2.6.26-rc7/kernel/drivers/net/wireless/iwlwifi/iwl4965.ko
debug=0x20002
laptok ~ # iwconfig wlan0 txpower on
laptok ~ # /etc/init.d/net.wlan0 restart
* Service net.wlan0 starting
SIOCSIFFLAGS: No such device
SIOCSIFFLAGS: No such device
SIOCSIFFLAGS: No such device
Failed to configure wireless for wlan0
[ !! ] * ERROR: net.wlan0 failed to start
laptok ~ # dmesg >dmesg-`uname -r`_`date +%F`.txt
laptok ~ # cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/[TAB key]
antenna ieee80211:phy1/ resource0
broken_parity_status input:input5/ retry_rate
bus/ irq rfkill:rfkill1/
channels local_cpulist rs_window
class local_cpus statistics
config measurement status
device modalias subsystem/
driver/ msi_bus subsystem_device
dump_errors net:wlan0/ subsystem_vendor
dump_events net:wmaster0/ temperature
enable power/ tx_power
filter_flags power_level uevent
flags resource vendor
laptok ~ #
cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill\:rfkill1/[TAB key]
claim name state type
device/ power/ subsystem/ uevent
laptok ~ #
cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill\:rfkill1/state
0
W liście datowanym na wtorek, 17 czerwca 2008, Zhu Yi pisze:
>ZY On Mon, 2008-06-16 at 20:21 +0200, Michał Kudła wrote:
>ZY > And my wifi working!
>ZY >
>ZY > Bt, I don't know why my wifi working under 2.6.23 and 2.6.24?
>ZY
>ZY mac80211 in those (old) kernels doesn't indicate to switch the SW
>ZY rf_kill on with user sets txpower off.
>ZY
>ZY Thanks,
>ZY -yi
>ZY
>ZY
On Mon, 2008-06-23 at 05:30 +0200, Michał Kudła wrote:
> >ZY Your radio is disabled by the software rf_kill switch. Please do a
> >ZY $ echo 0 > /sys/bus/pci/drivers/iwl4965/<dev id>/rfkill
> \:rfkill0/state
>
> Still don't work
Oops, you should echo 1 instead.
Thanks,
-yi
Hi,
With "0" and "1" result the same - failed.
W liście datowanym na poniedziałek, 23 czerwca 2008, Zhu Yi pisze:
>ZY Oops, you should echo 1 instead.
On Mon, 2008-06-23 at 07:32 +0200, Michał Kudła wrote:
> With "0" and "1" result the same - failed.
Please post the dmesg with debug=0x20002 before and after you echo "1"
to rfkill.
Thanks,
-yi
Hi,
If I reload kernel module, I get rfkill[n] with new [n].
rfkill0
rfkill1
rfkill2
After reloading I always get 0 int state
/sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill\:rfkill2/state
0
I attached files form console log and dmesg
console-rfkill-0.txt
dmesg-2.6.26-rc7_2008-06-23-rfkill-0.txt
console-rfkill-1.txt
dmesg-2.6.26-rc7_2008-06-23-rfkill-1.txt
W liście datowanym na poniedziałek, 23 czerwca 2008, Zhu Yi pisze:
>ZY On Mon, 2008-06-23 at 07:32 +0200, Michał Kudła wrote:
>ZY > With "0" and "1" result the same - failed.
>ZY
>ZY Please post the dmesg with debug=0x20002 before and after you echo "1"
>ZY to rfkill.
>ZY
>ZY Thanks,
>ZY -yi
>ZY
>ZY
On Mon, 2008-06-23 at 21:03 +0200, Michał Kudła wrote:
>
> I attached files form console log and dmesg
> console-rfkill-0.txt
> dmesg-2.6.26-rc7_2008-06-23-rfkill-0.txt
> console-rfkill-1.txt
> dmesg-2.6.26-rc7_2008-06-23-rfkill-1.txt
Please try attached patch.
Thanks,
-yi
Hi,
ok, i pached.
Results (failed) in attached files:
console-rfkill-1.patch.txt
dmesg-2.6.26-rc7_2008-06-24-rfkill-1.patch.txt
W liście datowanym na wtorek, 24 czerwca 2008, Zhu Yi pisze:
>ZY On Mon, 2008-06-23 at 21:03 +0200, Michał Kudła wrote:
>ZY >
>ZY > I attached files form console log and dmesg
>ZY > console-rfkill-0.txt
>ZY > dmesg-2.6.26-rc7_2008-06-23-rfkill-0.txt
>ZY > console-rfkill-1.txt
>ZY > dmesg-2.6.26-rc7_2008-06-23-rfkill-1.txt
>ZY
>ZY Please try attached patch.
>ZY
>ZY Thanks,
>ZY -yi
>ZY
On Tue, 2008-06-24 at 05:37 +0200, Michał Kudła wrote:
> laptok ~ # cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill
> \:rfkill1/state
> 0
> laptok ~ # echo "1"> /sys/bus/pci/drivers/iwl4965/0000\:04
> \:00.0/rfkill\:rfkill1/state
> laptok ~ # iwconfig wlan0 txpower on
> laptok ~ # /etc/init.d/net.wlan0 restart
> * Service net.wlan0 starting
> Failed to configure wireless for wlan0
> [ !! ] * ERROR: net.wlan0 failed to start
Looks like the wireless config scripts in your distro did something
(probably txpower off) to disable the SW radio. Can you try the
following commands after wlan0 restart?
$ cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill\:rfkill1/state
$ echo 1 > /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill
\:rfkill1/state
$ ifconfig wlan0 up
Thanks,
-yi
Hi,
I do
ifconfig wlan0 up
results in files:
console-frkill-1-iwconfig.txt
dmesg-2.6.26-rc7_2008-06-24-rfkill-1-ifconfig.txt
net - script config
net.lo - run script
How to run my wifi?
W liście datowanym na wtorek, 24 czerwca 2008, Zhu Yi pisze:
>ZY On Tue, 2008-06-24 at 05:37 +0200, Michał Kudła wrote:
>ZY > laptok ~ # cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill
>ZY > \:rfkill1/state
>ZY > 0
>ZY > laptok ~ # echo "1"> /sys/bus/pci/drivers/iwl4965/0000\:04
>ZY > \:00.0/rfkill\:rfkill1/state
>ZY > laptok ~ # iwconfig wlan0 txpower on
>ZY > laptok ~ # /etc/init.d/net.wlan0 restart
>ZY > * Service net.wlan0 starting
>ZY > Failed to configure wireless for wlan0
>ZY > [ !! ] * ERROR: net.wlan0 failed to start
>ZY
>ZY Looks like the wireless config scripts in your distro did something
>ZY (probably txpower off) to disable the SW radio. Can you try the
>ZY following commands after wlan0 restart?
>ZY
>ZY $ cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill\:rfkill1/state
>ZY $ echo 1 > /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill
>ZY \:rfkill1/state
>ZY $ ifconfig wlan0 up
>ZY
>ZY Thanks,
>ZY -yi
>ZY
>ZY
Hi,
my WiFi still don't wokrk
Now, I have new kernel 2.6.26-rc8.
Should I patch again this kernel?
Is good patch for rc7 for rc8?
W liście datowanym na wtorek, 24 czerwca 2008, Zhu Yi pisze:
>ZY On Tue, 2008-06-24 at 05:37 +0200, Michał Kudła wrote:
>ZY > laptok ~ # cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill
>ZY > \:rfkill1/state
>ZY > 0
>ZY > laptok ~ # echo "1"> /sys/bus/pci/drivers/iwl4965/0000\:04
>ZY > \:00.0/rfkill\:rfkill1/state
>ZY > laptok ~ # iwconfig wlan0 txpower on
>ZY > laptok ~ # /etc/init.d/net.wlan0 restart
>ZY > * Service net.wlan0 starting
>ZY > Failed to configure wireless for wlan0
>ZY > [ !! ] * ERROR: net.wlan0 failed to start
>ZY
>ZY Looks like the wireless config scripts in your distro did something
>ZY (probably txpower off) to disable the SW radio. Can you try the
>ZY following commands after wlan0 restart?
>ZY
>ZY $ cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill\:rfkill1/state
>ZY $ echo 1 > /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill
>ZY \:rfkill1/state
>ZY $ ifconfig wlan0 up
>ZY
>ZY Thanks,
>ZY -yi
>ZY
>ZY
Hi,
with new build -rc9 iwl4965 still don't work.
I don't know, witch distro I should use to check, that current kernel and my
WiFi is OK.
I returned to good 2.6.24-gentoo-r8
W liście datowanym na wtorek, 24 czerwca 2008, Zhu Yi pisze:
>ZY On Tue, 2008-06-24 at 05:37 +0200, Michał Kudła wrote:
>ZY > laptok ~ # cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill
>ZY > \:rfkill1/state
>ZY > 0
>ZY > laptok ~ # echo "1"> /sys/bus/pci/drivers/iwl4965/0000\:04
>ZY > \:00.0/rfkill\:rfkill1/state
>ZY > laptok ~ # iwconfig wlan0 txpower on
>ZY > laptok ~ # /etc/init.d/net.wlan0 restart
>ZY > * Service net.wlan0 starting
>ZY > Failed to configure wireless for wlan0
>ZY > [ !! ] * ERROR: net.wlan0 failed to start
>ZY
>ZY Looks like the wireless config scripts in your distro did something
>ZY (probably txpower off) to disable the SW radio. Can you try the
>ZY following commands after wlan0 restart?
>ZY
>ZY $ cat /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill\:rfkill1/state
>ZY $ echo 1 > /sys/bus/pci/drivers/iwl4965/0000\:04\:00.0/rfkill
>ZY \:rfkill1/state
>ZY $ ifconfig wlan0 up
>ZY
>ZY Thanks,
>ZY -yi
>ZY
>ZY
On Sun, 2008-07-06 at 22:44 +0200, Michał Kudła wrote:
> with new build -rc9 iwl4965 still don't work.
> I don't know, witch distro I should use to check, that current kernel
> and my WiFi is OK.
>
> I returned to good 2.6.24-gentoo-r8
This is not a regression. The rfkill subsystem changed a lot since then.
>From what you reported, it looks like a configuration problem since I
don't see any other report on this. Could you please file a bug on
bughost.org so we can track it there?
Thanks,
-yi