I'm unable to get my ipw2100 to work in FC4 (kernel-2.6.11-1.1369_FC4) . Everything looks fine except can't finally work. dmesg shows following trace:

Jul 23 16:38:56 localhost kernel: ipw2100: Unknown parameter `irq'
Jul 23 16:38:56 localhost kernel: ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 1.0.5
Jul 23 16:38:56 localhost kernel: ipw2100: Copyright(c) 2003-2004 Intel Corporation
Jul 23 16:38:56 localhost kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
Jul 23 16:38:56 localhost auditd[1889]: Init complete, audit pid set to: 1889
Jul 23 16:38:56 localhost kernel: ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
...
...
Jul 23 16:44:29 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 20
Jul 23 16:44:49 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2
Jul 23 16:44:51 localhost dhclient: No DHCPOFFERS received.

I tried setting static IP but didn't work either (destination unreachable).

"iwconfig" yields following result:
eth1 IEEE 802.11b ESSID:"WLAN" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.457 GHz Access Point: 00:03:6D:20:7B:64
Bit Rate=11 Mb/s Tx-Powerff
Retryn RTS thrff Fragment thrff
Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-0000-00 Security modepen
Power Managementff
Link Quality=100/100 Signal level=-37 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0

"iwlist eth1 scan" yields following result:
eth1 Scan completed :
...
Cell 03 - Address: 00:03:6D:20:7B:64
ESSID:"WLAN"
Protocol:IEEE 802.11b
Mode:Master
Channel:10
Encryption keyn
Bit Rate:11 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 11
Signal level=-37 dBm
Extra: Last beacon: 89ms ago


Any advice would be appreciated!

did you ever get a reply for this problem? i'm having the same thing with the ipw2200 drivers. all looks well with iwconfig, but i can't get a dynamic ip. grr.
caid

i've got more or less the same prob.
i see you've got wpa enabled as i do, and i'm SURE my prob is related to this because i can connect & recieve IP from my linksys AP without WPA.
as soon as i put on WPA --> AP/network found but no IP received

i'm running fedora 4 with kernel 2.6.12.1-398 on a medion md95131 with intel 2200b/g.
1st problem was the RF-switch --> solved this with sourceforge-project-help
then loaded last ieee80211-modules, intel 1.0.6 driver & firmware 2.2-5
now it's the WPA-problem which i thought would be solved with wpa_supplicant but no progress this far.
i've tried every possible wpa_supplicant-configuration possible for my system.
BUT : there's 1 thing i don't know : do i have to start wpa_supplicant somehow or is this done automatically ?

if anyone, ANYONE, could give some tips/advise it would be appreciated enormously because after 3 weeks i'm getting a little bit

normally i start up wpa supplicant with the command below:

wpa_supplicant -i eth1 -c /etc/wpa_supplicant.conf -D ipw -dddd

with -i being your interface, -c being your wpa config file, -D your driver, and -dddd telling the program to show as much debugging output as poss.
using -B will start supplicant as a daemon.

run dhclient after that.

still can't get my adapter working with WEP/WPA, so if you do, let us all know how! ;o)

caid

thx caid,

i've tried to use the command you gave (& some variations) but i'm always receiving "prism host ap"-errors. because i never made a custom .config for the wpa_supplicant make-file and i've been messing with drivers, ndiswrapper, driverloader etc i'm going to do a fresh install of FC4.
When i've done so, i'll put the result here.