ipw2200 can see but not connect

[cMechanism]

Hello,

I'm running Fedora Core 3 on a Dell Inspiron 8600. So far I have been able to get the majority of my system up and running by reading through similar problems in this forum. I've been having serious problems connecting to my Linksys Wireless-G router.

Based on similar posts, I believe that I have successfully installed both the driver and the firmware for my ipw2200 wireless modem. A week ago when I first installed them my connections were working. Now I'm in a different state and I'm not connecting to my own router 6 inches away.


When I run 'iwlist scanning' I can see my connection on eth1:

eth1 Scan completed :
Cell 01 - Address: ##:##:##:##:#E:## //only with numbers, :)
ESSID:"My Network"
Protocol: IEEE 802.11bg
Mode: Master
Channel:6
Encryption key:on
Bit Rate: 54Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
Signal level=-23 dBm
Extra: Last beacon: 2ms ago


When I run ifup eth1 I get the usual "Set Bit Rate" error, and then (very frustratingly) a simple "failed; no link present. Check cable?" Fortunately, I'm getting errors elsewhere:


[root@localhost ~]# cat /var/log/messages | grep ipw2200
Mar 13 04:19:44 localhost kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Netwo rk Driver, 1.0.0
Mar 13 04:19:44 localhost kernel: ipw2200: Copyright(c) 2003-2004 Intel Corporat ion
Mar 13 04:19:44 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Ne twork Connection
Mar 13 04:19:44 localhost kernel: ipw2200: ipw-2.2-boot.fw load failed: Reason - 2
Mar 13 04:19:44 localhost kernel: ipw2200: Unable to load firmware: 0xFFFFFFFE
Mar 13 04:19:44 localhost kernel: ipw2200: Failed to up device
Mar 13 04:19:44 localhost kernel: ipw2200: No space for Tx
Mar 13 04:19:44 localhost kernel: ipw2200: failed to send SCAN_REQUEST_EXT comma nd
Mar 13 10:45:22 localhost kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Netwo rk Driver, 1.0.0
Mar 13 10:45:22 localhost kernel: ipw2200: Copyright(c) 2003-2004 Intel Corporat ion
Mar 13 10:45:22 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Ne twork Connection
Mar 13 10:45:23 localhost kernel: ipw2200: Firmware error detected. Restarting.
Mar 13 10:45:23 localhost kernel: ipw2200: ipw-2.2-boot.fw load failed: Reason - 2
Mar 13 10:45:23 localhost kernel: ipw2200: Unable to load firmware: 0xFFFFFFFE
Mar 13 10:45:23 localhost kernel: ipw2200: Failed to up device
Mar 13 10:45:23 localhost kernel: ipw2200: No space for Tx
Mar 13 10:45:23 localhost kernel: ipw2200: failed to send SCAN_REQUEST_EXT comma nd
Mar 13 11:41:13 localhost kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Netwo rk Driver, 1.0.0
Mar 13 11:41:13 localhost kernel: ipw2200: Copyright(c) 2003-2004 Intel Corporat ion
Mar 13 11:41:13 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Ne twork Connection
Mar 13 11:41:13 localhost kernel: ipw2200: ipw-2.2-boot.fw load failed: Reason - 2
Mar 13 11:41:13 localhost kernel: ipw2200: Unable to load firmware: 0xFFFFFFFE
Mar 13 11:41:13 localhost kernel: ipw2200: Failed to up device
Mar 13 11:41:13 localhost kernel: ipw2200: No space for Tx
Mar 13 11:41:13 localhost kernel: ipw2200: failed to send SCAN_REQUEST_EXT comma nd
Mar 13 11:41:13 localhost kernel: ipw2200: ipw-2.2-boot.fw load failed: Reason - 2
Mar 13 11:41:13 localhost kernel: ipw2200: Unable to load firmware: 0xFFFFFFFE
Mar 13 11:41:13 localhost kernel: ipw2200: Failed to up device
Mar 13 11:41:13 localhost kernel: ipw2200: No space for Tx
Mar 13 11:41:13 localhost kernel: ipw2200: failed to send SCAN_REQUEST_EXT comma nd

iwconfig gives the following:


If I were in Windows, (which is what I'm familiar with) I'd probably just reinstall the drivers at this point. Does that seem like a good idea, and if I wanted to do that, what would be the cleanest way to do it? I'm guessing installing the driver on top of itself isn't the best idea, but I don't know.


[root@localhost ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID:off/any Nickname:"localhost.localdomain"
Mode:Managed Frequency=2.412GHz Access Point: 00:00:00:00:00:00
Bit Rate=0kb/s Tx-Power=20 dBm
RTS thr:off Fragment thr:off
Encryption key:3742-3330-3932-3138-4635-0000-00 Security mode:open
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.


Thank you very much for your time and help (in advance).

Matt

[Jezster]

Have you installed 'ipw2200-firmware-2.2..at.norarch.rpm', I only wonder because your error messages indicated you have not installed the firmware drivers.

The process is listed else where on the forums... I've been through it today also and I'm writing this via my ipw2200, FC3 and HP NC6000 :D

Jezster.

[cMechanism]

I have installed the RPM and copied the drivers (including license) to the firmware directory. Maybe I haven't installed it correctly though. How would I check?

[jim]

See these links
http://fedoranews.org/contributors/jim_lawrence/wireless/
http://fedoranews.org/contributors/jim_lawrence/securewireless/
http://fedoranews.org/contributors/jim_lawrence/network_manager/

the 3rd link is about NetworkManager, I use it because I now don't have to type in all that crap when i ewant to connect wirelessly. Just run
NetworkManangerInfo from the terminal then run ( if you use gnome) gnome-session-save


Also judging by the iwlist scan

You do have the correct key to gain access correct? if so, what type of encryption are you using with the new AP?

Do you have your wireless device set to be active on boot? if so, change that. NM will activate it for you

[cMechanism]

Here's another error message I'm getting:


Determining IP information for eth1...PING 192.168.0.1
(192.168.0.1) 56(84) bytes of data.

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 0 recieved, +3, 100% packet loss, time 2999ms
, pipe 4
failed.

[cMechanism]

Thank you very much for your help. The Network Manager is wonderful and makes me feel like I'm making progress. However, although the Network Manager will find the network and attempt a connection, it simply slips back into searching after a minute or two without ever actually connecting.

I'm using WEP passphrase and 64 bit 10 hex digits, and have tried connecting using both the passphrase and one of the WEP keys. Do you have any other suggestions?