etch/ipw2100 troubles

**kern** · 11-19-2006

I've used exactly the same procedure I used in slackware 11.0 on this laptop, placing the firmware down from the intel site in /lib/firmware, and configuring the interface etc, but I can't see what the problem is, I just can't seem to get a DHCP IP on eth1 (wifi) using dhclient, or dhcpcd

I'm not sure why, when i manually configure the interface for a static ip and gateway etc it doesnt work either.

I've searched a bit, googled, and checked previous posts here. but I cannot see why it doesnt work like it did in slackware, the procedure is very similar - it just used to magically work after i placed the firmware down.

..help?

**kakariko81280** · 11-19-2006

Can we get you to run this command to see if it's actually picking up the firmware

Code:

dmesg | grep ipw

Also, are you sure you put it in the correct kernel directory.

Code:

ls /lib/firmware/`uname -r`/ipw*

Once we've got that we'll hopefully be able to help further.

Let us know how you get on,

Chris...

**antidrugue** · 11-19-2006

On Debian the possible firmware directories are either /lib/firmware or /usr/lib/hotplug/firmware. But of course dmesg output is the key here.

**kern** · 11-19-2006

here we go

Code:

lappy:/home/shaun# dmesg | grep ipw
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
ipw2100: Copyright(c) 2003-2006 Intel Corporation
ipw2100: Detected Intel PRO/Wireless 2100 Network Connection

I have the firmware files in /lib/firmware directly, not in their own kernel dir

Code:

lappy:/home/shaun# ls /lib/firmware/
ipw2100-1.3.fw  ipw2100-1.3-i.fw  ipw2100-1.3-p.fw
lappy:/home/shaun#

**kern** · 11-19-2006

it must be working to some extent as I can scan for wireless networks using

Code:

iwlist eth1 scan

I have the details such as wep key etc in /etc/network/interfaces, but the device doesnt seem to get a dhcp IP even though I'm typing this from my wired connection right now and thats gets a dhcp IP fine, it doesnt work if I set it up manually with a static IP either.

maybe I'm doing something wrong or missing something out with iwconfig/ifconfig, but theres nothing instantly visible to me.

**kern** · 11-19-2006

Seems I get this every now and again, I think its when I'm configuring eth1, the wifi device

Code:

ADDRCONF(NETDEV_UP): eth1: link is not ready

**kern** · 11-20-2006

any ideas?

**kakariko81280** · 11-21-2006

The firmware seems to be Ok or there would have been errors in dmesg. I would suggest dropping dhcp for the moment, we can get that working once everything else is going.

Try disabling wep on the access point and see if that fixes it. There are a couple of ways of entering wep keys (string and hex) so it might be that.

I've never seen the "link not ready" error before and google is failing to turn up anything useful so far. With a little luck we will fix it when we get something else worked out.

Let us know how you get on,

Chris...

**kern** · 11-22-2006

I've set it static before to no avail

and turning WEP off is a good idea to test I guess, but it worked under slackware using exactly the same setup.

bah

I'll try farting around tonight, maybe I did something stupid like get the wep key wrong, I dunno

thanks

Thread Tools

Display

etch/ipw2100 troubles

Posting Permissions