ipw2200 drivers for Intel Wireless Pro Adapter 2195

[fatcow]

I've been trying to get the ipw2200 drivers for this Intel Wireless Pro wifi adapter working on my ProStar ProStar 3724 Notebook, with Slackware 10.2, but I'm giving up hope.

Yesterday, I installed the latest ipw2200 drivers (ipw2200-1.1.2), ipw2200 firmware (ipw2200-fw-3.0), and the required iee80211 drivers (1.1.13), which makes it the 4th time I've tried this with 'the latest' revisions of these drivers, and still I have no luck getting dhclient to connect to a hotspot.

From the looks of it, I can see the device in iwconfig...

# iwconfig eth0
eth0      unassociated  ESSID:off/any  Nickname:"deathstar"
          Mode:Managed  Channel=0  Access Point: 00:00:00:00:00:00   
          Bit Rate=0 kb/s   Tx-Power=20 dBm   
          Retry limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          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

I can also see the device in ifconfig...

# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:12:F0:0D:A0:D9  
          inet6 addr: fe80::212:f0ff:fe0d:a0d9/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19604 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5893 (5.7 Kb)  TX bytes:348 (348.0 b)
          Interrupt:10 Memory:d0000000-d0000fff

and iwlist seems to work ok...

# iwlist scan
lo        Interface doesn't support scanning.

eth0      No scan results
eth1      Interface doesn't support scanning.

sit0      Interface doesn't support scanning.

The router is currently turned off, but when I turn it on, it appears in the 'iwlist scan' results just fine.

When I goto connect via dhclient, I receive the following response:

# iwconfig eth0 ESSID myrouter; ifconfig eth0 up; dhclient eth0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

eth0: not found

I then tried to probe the ipw2200 module, but it doesn't return any message.

# modprobe ipw2200

I then tried to probe the eth0 and eth1 modules, which returns a fatal error...

# modprobe eth0     
FATAL: Module eth0 not found.

# modprobe eth1
FATAL: Module eth1 not found.

eth1 is working fine as a wired ethernet adapter, so I'm not sure why modprobe isn't recognizing it.

I figure if dhclient doesn't see eth0, it's because modprobe can't recognize it either, but I may be (and probably am) mistaken.

I don't use dhclient to connect eth1 to my router, I use dhcpcd, which works fine w/ my router (which runs dnsmasq).

I tried using dhcpcd to connect...

# dhcpcd eth0

but that didn't work either. =/

Anyhow, I've exhausted all the options that I can think of.

I'm really not sure if the problem is the drivers, or dhclient/dhcpcd.

Anyone have any ideas or suggestions?

Thanks!

[kakariko81280]

It looks like everything should be working. Have you tried to assign a static IP to your laptop to see if it will ping the router? (make sure eth1 isn't up at the same time)

Modprobe will not say anything unless there is a problem. If you ran those commands in order it will already have the ipw2200 module loaded so it will simply do nothing. To get some diagnostic messages try

modprobe -r ipw2200
modprobe ipw2200
dmesg | tail

Modprobe eth0 and modprobe eth1 wont work because modprobe takes a kernel module name as it's argument. You can set up aliases in /etc/modprobe.conf so those commands will work, but I don't think there is a good reason to right now.

If setting a static IP works, try killing all of the dhcpcd and dhclient processes and then trying them again. I would suggest sticking with dhcpcd because it is known to work (although I've never had problems with either).

Let us know how you get on,

Chris...

[spencerf]

try these commands as root

ifconfig eth0 up
iwconfig eth0 key xxxxxxxxx  (where xxxx is your router wep key if you have one, if not just skip)
iwconfig eth0 essid "name-of-your-routers-essid"
dhcpcd eth0

[fatcow]

modprobe -r ipw2200
modprobe ipw2200
dmesg | tail

Chris...

I tried the following commands, and received the following results...

bash-3.00# dmesg -c;
bash-3.00# modprobe -r ipw2200                 
bash-3.00# modprobe ipw2200   
bash-3.00# dmesg              
ACPI: PCI interrupt for device 0000:02:03.0 disabled
ieee80211_crypt: unregistered algorithm 'NULL'
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, 1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2dmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)

Seems fine to me, with the obvious question about the ieee80211_crypt message.

Spencer: Yes, I did try those commands, and still no luck. I even tried it on some poor/unwitting neighbor's insecure/unencrypted router (w/ no key), and still no luck. =/

Any other suggestions?

[spencerf]

the only thing I can think of is you have the wrong firmware for you particular card. Try out some other ones if you can.

[fatcow]

doh, nevermind, got it.

I reset my router, and then it worked, so I guess it was my fault for forgetting my password!! *DUH!* =/

I guess upgrading these ipw2200/fw & ieee80211 drivers also helped, as I couldn't get a connection @ school/work when I had tried, with the previous drivers, but it should work now! =)

note: I have to use dhcpcd for this, as dhclient still returns: eth0 not found

Anyhow, thanks guys! =)

[shashank]

where do i get ipw2200 drivers (ipw2200-1.1.2), ipw2200 firmware (ipw2200-fw-3.0 drivers