Check this out:
http://fedoraproject.org/wiki/Bugs/F...97983a3822f143
You may have the i586 Kernel installed and it sounds like you need the i686. It's a known bug with FC6. Just follow the directions on the above website and you should be good.
I've made notes for my adventures trying to get the IPW cards running. Here's what my notes are..mostly copied from different websites.
Start notes:
-----------------------------
Go to:
http://atrpms.net/name/
download and install these rpms
ieee80211-kmdl-2.6.19-1.2895.fc6-1.2.16-16.fc6.at.i686.rpm
ipw3945d-1.7.22-4.at.i386.rpm
ipw3945-ucode-1.14.2-3.1.at.noarch.rpm
ipw3945-kmdl-2.6.19-1.2895.fc6-1.2.0-18.2.fc6.at.i686.rpm
ipw3945-1.2.0-18.2.fc6.at.i386.rpm
Now, once you have installed all rpms successfully, ur done...do this in terminal/konsole:
#depmod -a
#modprobe ipw3945 <- this loads the module.
to chk if its done do ...
#dmesg | grep ipw <- this should list the driver detected.
#lsmod <- this should list the driver detected. look for ipw3945
OK now finally...
#ps -C ipw3945 <- this should list the ipw3945d deamon running ...
this means its running successfully and got loaded.
else try,
#/sbin/ipw3945d to start it ...
thats it,
now #system-config-network &
select FILE>NEW>WIRELESS>FORWARD>SELECT UR DRIVER NOW LISTED> FORWARD> COMPLETE
THE CONFIGURATION
i.e. add ur essid, key etc and ok
U R DONE ...
its up and running , do #ifconfig it should show it running....displays its address and other details....
---------------------------------------
end
From another website,
Start notes
--------------------------------------
Getting the wireless interface running
Now we need to get three further mods done to get the wireless up and running:
1. First we need to add three lines to the file /etc/modprobe.conf
1. alias eth1 ipw3945
2. install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; sleep
0.5 ; /sbin/ipw3945d --quiet
3. remove ipw3945 /sbin/ipw3945d --kill ; /sbin/modprobe -r
--ignore-remove ipw3945
The first line assumes that we will have the wireless interface as eth1.
2. Next we need to add a line to the file /etc/rc.local
/sbin/ipw3945d --quiet
This is critical since although the modules do load at boot the
regulatory daemon does not run unless this change is made
3. Finally we need to prepare a file to handle the interface eth1.
Go into the directory /etc/sysconfig/network-scripts and prepare a file
called ifcfg-eth1 (it may already exist)
The file will have various parameters depending on whether you have wep
security and which options you wish to set. My file looks like:
1. # Please read /usr/share/doc/initscripts-*/sysconfig.txt
2. # for the documentation of these parameters.
3. ONBOOT=no
4. USERCTL=yes
5. PEERDNS=no
6. TYPE=Wireless
7. DEVICE=eth1
8. HWADDR=xx:xx:xx:xx:xx:xx
9. BOOTPROTO=dhcp
10. ESSID=xxxxxxx
11. KEY='xxxxxxxxxxxxxxxxxxxxxxxxxx restricted'
12. MODE=Managed
13. RATE=Auto
14. PEERNTP=no
The xxx here will be replaced by the values appropriate to your system.
Once the system has booted with these changes, then first time after the
re-boot you may need to do "depmod -a" as root, and then re-boot again.
However if you are changing the driver or the regulatory daemon for a new
version, you can do "modprobe -rv ipw3945" as root, then make the changes, and
then "modprobe -av ipw3945" to reload the daemon. Then after logging on the
wireless interface should be running and immediately give a network connection
via the Access Point. Of course this presumes that the files /etc/resolv.conf,
/etc/hosts, /etc/sysconfig/network have been amended to suit the network
parameters of the local network. If network changes have been done, then as
root type "service network restart" to update the system.
The wireless network can be started or stopped by any user (since USERCTL has
been set to yes in the ifcfg file) by doing /sbin/ifup eth1 or /sbin/ifdown
eth1.
In KDE a nice taskbar wireless monitor icon can be added using right click in
the taskbar and then "add applet" - and selecting the Wireless Information
applet
-------------------------------------
end notes
Hope this helps some...sorry if the notes seem jumbled.
You may also need to play around with the eth1 settings switching them from managed to Auto....
These IPW drivers have really pissed me off lately....
Good luck!
Steve