Bug 433770 - mac80211 fails to initialise WEP
Summary: mac80211 fails to initialise WEP
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-21 12:28 UTC by Brad Walker
Modified: 2008-03-14 14:08 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-03-14 14:08:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output (41.14 KB, text/plain)
2008-02-21 12:28 UTC, Brad Walker
no flags Details
config-x86_64-generic from kernel-2.6.25-0.61.rc2.git4.fc9.src.rpm (5.30 KB, text/plain)
2008-02-21 21:59 UTC, Brad Walker
no flags Details
/boot/config-2.6.25-0.61.rc2.git4.fc9 (77.86 KB, text/plain)
2008-02-21 22:05 UTC, Brad Walker
no flags Details

Description Brad Walker 2008-02-21 12:28:32 UTC
Description of problem: iwl4965 driver doesn't support 4965AGN card.


Version-Release number of selected component (if applicable):
kernel-2.6.25-0.61.rc2.git4.fc9.x86_64


How reproducible: everytime


Steps to Reproduce: Install kernel-2.6.25-0.61.rc2.git4.fc9.x86_64 and boot into it.

  
Actual results:
dmesg excerpt
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.23kds
iwl4965: Copyright(c) 2003-2007 Intel Corporation
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:03:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iTCO_vendor_support: vendor-support=0
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
iTCO_wdt: Found a ICH8M-E TCO device (Version=2, TCOBASE=0x1060)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
phy0: Selected rate control algorithm 'iwl-4965-rs'
input: PC Speaker as /devices/platform/pcspkr/input/input6
phy0: Failed to initialize wep
iwl4965: Failed to register network device (error -12)
ACPI: PCI interrupt for device 0000:03:00.0 disabled
iwl4965: probe of 0000:03:00.0 failed with error -12

NetworkManager doesn't show a checkbox for toggling wireless support. Nor do any
scanned netwokrs appear.


Expected results: WLANs visible


Additional info: kernel-2.6.25-0.40.rc1.git2.fc9.x86_64 is the latest kernel my
machine boots and that detects WLANs. I've attached a full dmesg.

Comment 1 Brad Walker 2008-02-21 12:28:32 UTC
Created attachment 295499 [details]
dmesg output

Comment 2 John W. Linville 2008-02-21 14:09:12 UTC
OK, what is happening with the "Failed to initialize wep" thing?  I thought 
that this came down to enabling KMOD, but that is enabled in Fedora kernels.

Any ideas?  Clearly this is an upstream issue as well.

Comment 3 Johannes Berg 2008-02-21 19:27:06 UTC
No, no idea, but it has been reported upstream as well. If the reporter can
attach the .config file of the failing kernel I can ping Herbert Xu about it
again, he requested that but I couldn't provide it.


Comment 4 Brad Walker 2008-02-21 21:59:29 UTC
Created attachment 295563 [details]
config-x86_64-generic from kernel-2.6.25-0.61.rc2.git4.fc9.src.rpm

Comment 5 Brad Walker 2008-02-21 22:05:38 UTC
Created attachment 295564 [details]
/boot/config-2.6.25-0.61.rc2.git4.fc9

Comment 6 Brad Walker 2008-02-21 23:12:26 UTC
kernel-2.6.25-0.64.rc2.git5.x86_64 seems to have fixed this problem. The device
is enabled and NM shows scanned WLANs. The machine successfully connected to a
WLAN. It's again having problems with the RFKILL switch like bug 432927.

Comment 7 Johannes Berg 2008-02-22 14:00:02 UTC
So which is the failing and which is the good config?

Comment 8 Brad Walker 2008-02-22 17:34:49 UTC
Neither of the configs I attached has working wireless. The first one's a
template or something while the second's the actual config of the failing kernel.

The later kernel 2.6.25-0.64 works, but I didn't attach its config. It slightly
differs:

--- config-2.6.25-0.61.rc2.git4.fc9	2008-02-20 23:51:58.000000000 -0700
+++ config-2.6.25-0.64.rc2.git5.fc9	2008-02-21 14:26:11.000000000 -0700
@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
-# Linux kernel version: 2.6.25-0.61.rc2.git4.fc9
-# Thu Feb 21 01:42:54 2008
+# Linux kernel version: 2.6.25-0.64.rc2.git5.fc9
+# Thu Feb 21 16:17:28 2008
 #
 CONFIG_64BIT=y
 # CONFIG_X86_32 is not set
@@ -1604,13 +1604,11 @@
 CONFIG_ATH5K=m
 CONFIG_ATH5K_DEBUG=y
 CONFIG_IWL4965=m
-CONFIG_IWL4965_QOS=y
 CONFIG_IWL4965_HT=y
 CONFIG_IWL4965_SPECTRUM_MEASUREMENT=y
 CONFIG_IWL4965_SENSITIVITY=y
 CONFIG_IWL4965_DEBUG=y
 CONFIG_IWL3945=m
-CONFIG_IWL3945_QOS=y
 CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
 CONFIG_IWL3945_DEBUG=y
 CONFIG_HOSTAP=m

Comment 9 John W. Linville 2008-03-13 15:23:27 UTC
Does this continue to be a problem with current rawhide kernels?

   http://koji.fedoraproject.org/koji/buildinfo?buildID=42641

Comment 10 Brad Walker 2008-03-14 03:21:55 UTC
John Linville,

All kernels, including kernel-2.6.25-0.113.rc5.git2.fc9.x86_64, since
kernel-2.6.25-0.64.rc2.git5.x86_64 haven't had this WEP problem. However at some
release after kernel-2.6.25-0.64.rc2.git5.x86_64, NetworkManager can no longer
connect the wireless interface to networks, even unencrypted ones. The current
FC8 kernels do the same. I've been running kernel-2.6.23.13-105.fc8.x86_64 for
working iwl4965. I test new kernels whenever they're done building on Koji.

I believe kernel-2.6.25-0.64.rc2.git5.x86_64 solved this particular WEP issue. 

Comment 11 Brad Walker 2008-03-14 04:33:46 UTC
John Linville,

Actually, I can connect to encrypted and unencrypted networks on the 2.4ghz band
w/kernel-2.6.25-0.113.rc5.git2.fc9.x86_64. On the 5ghz band it'll connect to
unencrypted networks but it won't authenticated WPA. Testing on a D-Link
DGL-4500 dual-band router

Comment 12 John W. Linville 2008-03-14 14:08:14 UTC
It sounds like this issue is resolved.  You may want to open another bug for 
the NetworkManager-related problem you described.


Note You need to log in before you can comment on or make changes to this bug.