Description of problem:
i m using fct4 with latest kernel 2.6.21-1.3116.fc7
I have strange problems with wireless network. At fist (straight after booting)
NetworkManager shows my network and reports connection established.
But i cant view any web page and my laptop's wireless led never comes up...
Trying to disconnect and connect back again never succeeds and additionally it
triggers endless hard disk activity.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 153843 [details]
this output repeats again and again propably during the endless disk activity
Thanks for the report.
Could you please add the following information:
1. What is the brand and model of the laptop? (in case another user solved it
2. Which wireless card is this?
"lspci" should show the important details. It is a "miniPCI" (embedded to the
laptop) card, isn't it?
Also, please be sure to try the latest available rawhide kernels, including
1.3122 (or later) when they become available tomorrow. There have been a lot
of important fixes to the iwlwifi driver very recently.
I m waiting for the new kernel to try.
In the mean time:
[root@localhost ~]# iwlist wlan0 scan
Warning: Driver for device wlan0 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...
wlan0 Scan completed :
Cell 01 - Address: 00:90:4C:7E:00:29
Signal level=-15 dBm
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
In my situation using 2.6.21-1.3142 finally allowed me to connect to my AP using
WEP, though I still get some errors (I presume) in the messages:
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:c0:02:7a:1a:a2
wlan0: RX authentication from 00:c0:02:7a:1a:a2 (alg=0 transaction=2 status=0)
wlan0: associate with AP 00:c0:02:7a:1a:a2
wlan0: RX AssocResp from 00:c0:02:7a:1a:a2 (capab=0x411 status=0 aid=2)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
iwl3945: REPLY_ADD_STA failed
wlan0: duplicate address detected!
There is still another annoyance when using iwlwifi driver as opposed to ipw3945
driver from Intel, LED indicating that the wifi is in use does not work (stays
dark), with Intel driver it blinks when there is no connection (or reconnect) or
stays lit if there is connection/assotiation.
I have Dell Latitude D620 with
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection (rev 02)
Same results from me. I did not try yet WEP/WAP though.
Also during booting i have to wait about one minute when tries (and fails) to
get IP for wmaster0 with a message saying something like " SIOCSIFFLAGS not
For this test i disabled SELinux and i m using NetworkManager.
Is this still a problem w/ the 1.3194 kernel?
You can close this bug. There are other problems (suspend-led off) but this is
I am getting the following dmsg. My system worked fine under FC6 with ipw3945
drivers but when I did a clean upgrade to FC7 this is the messages I get during
boot. An I fail to get a connection.
BUG: warning at kernel/softirq.c:138/local_bh_enable() (Tainted: P )
iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
Closing as per comment 8.
Robbert, there is an F7 kernel-update candidate available here:
Which amongst other things contains various fixes to the iwl3945 driver. Please
try this kernel and report back how it works for you.
Always be carefull when testing new kernels. Use rpm -ivh to install the new
kernel besides your current one so that you can always boot back into the old
If that doesn't work please file a new bug for your problem.
Please try the kernels from here:
Do they work any better for you?
I tried a new kernel from official updates (22.214.171.124-27.fc7)and now nothing works.
NetworkManager can't do any connection to wireless access point. Even
system-config-network seems that is not aware of any wireless device...
So, now i use kernel-2.6.21-1.3228.fc7 which is working (without led, and within
shorter distances compared to fc6-freshrpms's iwp3945 driver)
These new kernels need the latest firmware, that should help!