View Full Version : Wireless 3945ABG won't work on fedora 14 x86
23rd October 2010, 07:38 PM
Since the of kernel 2.6.34.XXX I have the problem that my wirelles 3945 is not detected by Fedora 13, now I have downloaded Fedora 14 RC1 and I have the same issue. Do you know how to fix it?
PD: Here is my the previous post: http://forums.fedoraforum.org/showthread.php?t=249210
23rd October 2010, 10:12 PM
Still supported. Does it work with earlier F14 kernels?
23rd October 2010, 11:03 PM
Sorry, I do not know it, this is my first try of F14 on my Laptop.
Ups, so I cannot use F14 until Intel add the new support for my wireless card?
23rd October 2010, 11:35 PM
Is the firmware installed? Open a terminal and type
rpm -qa iwl3945*
You will see the following if it is installed.
24th October 2010, 02:28 AM
Yes, it is installed.
27th October 2010, 04:07 AM
Sorry to reply the post again, but I have another question:
I have tested Ubuntu 10.10 and the Wireless is detected perfectly, Does it mean that Fedora does not contain the right drivers for 2.6.34 kernel?
27th October 2010, 10:04 AM
As you might suspect from the previous replies, usually the Intel wireless chipsets are supported by Fedora.
The trick now will be to find why yours isn't. If you are up for it we can try some diagnostics one step at a time.
We need to know that Fedora is finding your wireless hardware.
I see from the link that you posted that you tried "lspci".
How about running:
lsmod | grep iwl
to see if the "iwlagn" module is loading.
27th October 2010, 05:24 PM
Hello bbfuller. thank you for your help.
Here is the output on Fedora 13:
iwl3945 88082 0
iwlcore 192650 1 iwl3945
mac80211 181979 2 iwl3945,iwlcore
cfg80211 110949 3 iwl3945,iwlcore,mac80211
If you need it, I can test it on F14.
27th October 2010, 09:11 PM
Well, now that we know Fedora is finding your hardware and loading the correct driver we need to see if we can find out what it is doing with it.
Could you run in your terminal:
That should tell us if Fedora is doing enough to create a wireless interface. If it is, it will most likely be "wlan0" but just once in a while you see "eth1"
In any event, I then suggest you run:
dmesg | grep iwl
That should look through the startup messages and list what happens as "iwl" loads.
If the first command detected a wireless interface, you could also try:
dmesg | grep <whatever wireless interface>
and see if that lists anything.
Post the output of those back and we'll see if anything can be made of it.
27th October 2010, 10:55 PM
Sorry, but laptop does not work any more, I do not see any anything on the screen, I think it is a video card issue. I will try it again when I fix it, sorry.
Thank you so much for your help!
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.