Bug 158381

did you also update the firmware file ?

Ipw2200-firmware-2.2.3 is the version that is used, I upgraded to version 2.3.6
the error isn't the same but I still can not bring it up.
It is trying to change the loopbak into eth1 in other words it does not see the
device correctly.
And all my normal tricks will not solve it.

(In reply to comment #1)
> did you also update the firmware file ?
> 

What's your ifcfg file look like? What messages do you get when loading the driver?

My ifcfg-eth1 file looks like this:

IPV6INIT=no
ONBOOT=yes
USERCTL=no
TYPE=Wireless
DEVICE=eth1
HWADDR=00:00:00:00:00:00
BOOTPROTO=dhcp
DHCP_HOSTNAME=stripes
ESSID=3Com4linux
MODE=Managed
RATE='0 kb/s'
CHANNEL=1

Strangely enough I do not get any errors now when loading the module not with
modprobe and not with insmod.
But when I do a network restart or stop, start it starts again with interface
'devxxxxx' not found.
It still does not see the device.
I will update the machine on an other kernel now and see if it changes anything.

Do you have any ifcfg-devXXXX files, or 'alias devXXXX <something>' in
/etc/modprobe.conf?

Out of my head it is something like 
alias eth1 ipw2200

I also updated the kernel to 2.6.11-1.1329_FC4
It also is impossible to bring that interface up in there (I couldn't do a
compleet update because of dependency problems with openoffice) and I didn't had
much time to doe so.

Update:

Updated to kernel 2.6.11-1.1341_FC4
Same problem, I found something else now when shutting down I noticed a message;
ipw2200: radio frequeny kill switch is on, must be turned off.

Update,
2.6.11-1.1353_FC4
The module is loaded but the device not found.
unloaded the module and started it with modprobe ipw2200 led=1
It knows that the divice is there the led changes when I press the button,
The rf_kill file shows 0
Still not able to find the device at boot up.
I,ve tried to change rf_kill to a different value but it changes back to 0 everytime

During a rmmod ipw2200 after a reboot I got the following message from syslogd;
Disabling IRQ #10.

That was an error that I had before in the earlier kernels from FC3, I only
could solve that by building my own kernel.
It gave that error when initializing hardware during bootup

Explain???
'cause I do not understand this..
I copied the hardware address from the device out of /etc/sysconfig/hwconf into
/etc/sysconfig/network-scripts/ifcfg-eth1 on its own it would come up everytime
with 00:00:00:00:00:00, also when I tried to get it's MAC address with
system-config-network.
After restarting the network it came up?? 

After a reboot it came up without a problem, out of itself.
Mhhh, it looks like it can't determine its hardware address during the
iniatializing from the hardware although it's in its hwconf. 

Due to the nature of this card (on - off button) shouldn't it be hotpluggable?

? It is hotpluggable; at least, I don't know of why it wouldn't be.

That would be the first time that it would work then I never managed to bring
that device up when the system was running. 

If somebody out there is trying to make my live difficult, you can tell him it's
working.....
Update kernel 2.6.11-1.1363_FC4,
dmesg:
ipw2200: detected Intel PRO/wireless
ipw2200: ipw-2.2-boot.fw load failed:Reason -2
ipw2200: Unable to load firmware: 0xFFFFFFFE
ipw2200: failed to register network device
ipw2200: probe for 0000:02:04 failed with error -5

After I unloaded the module and loading it again in the meantime holding the
button down it is present but I can not make a connection to the AP.

During normal boot up I got the message ipw2200 device eth0 does not seems to be
present: delaying initializing.
When it is hotpluggable it should come up after pressing the button, right?
no newer version of ipw2200-firmware then I've got now...

ipw2200: ipw-2.2-boot.fw load failed:Reason -2

-2 means the file wasn't found. You need that version of the firmware for the
driver in 1363 (it was reverted because of various problems that were reported.)

OK downgraded the firmware to 2.2-5 Still got an error it "sees" the device but
I can not bring it up.
modprobe ipw2200 led=1 doesn't work now, no way to find out how far it "sees"
the device. hardware address is back to 00:00:00:00:00:00 no hardware address in
hwconf anymore.
The messages in dmesg is still the same even after changing firmware version.
About that hotpluggable shouldn,t there be an entry in /etc/hotplug/pci for that
device then (maybe a stupid question I know)?

mhhh, maybe time to start a new bug, but somehow I think that it is related to
this problem they both share IRQ 10, as I told before I always had a problem
with this card.
Also with the soundcard snd-intel8x0, to make that card work I have to unload
the module and load it again after that it works.
I've gone back to 1353, I understand what they are trying to do there, it also
looks like a better way to deal with it firmware 2.3-6, it nows the card is
there no matter if it is turned on or off, and yes I can turn it on and off when
the system is running, it even comes up.
What kind of problems did you had with it?
After changing that hardware address I didn't had any problems with it, the
network would not always come up after a reboot, after pressing the button and
activating the device in system-config-network it always came up.
A simple service network restart also works after pressing the button.

Now back to 2.2-5 firmware there is no way that I can bring it back up in 1363.

Update,

Kernel 1366, no problem bringing the device up, it came up all by itself.
But does this mean that you stick with ipw2200 firmware 2.2 now?
Then it would help if you would give that firmware version by this release of FC4.
If tried to make it work with fimware 2.3 but that will not work at all.

/etc/sysconfig/hwconf finds the mac address
Also probing it with system-config-network it finds the correct mac address, a
first in this firmware version.

The version in 1366 is 1.0.0, which uses version 2.2 of the firmware.

A later update *may* be version 1.0.4 of the driver, which will use version 2.3
of the firmware.

Closing, as it appears to work now.

Confused now.

1381_FC5 but still rawhide release?
Well anyhow the module will not load 'cause there is no such device.
No message in dmesg about eth1 at all

* Thu Jun 09 2005 Dave Jones <davej>
- 2.6.12-rc6-git3
- Temporarily disable the ipw drivers until I sort them out.


The FC4 kernel does have them enabled.

This is fixed for FC4 release, and the FC5 (rawhide) kernel is intentionally
broken right now.

OK Thanks,

I was just confused about it, I didn't know that your changing so fast to
another release, FC4 isn't released officiel yet.., although I could have know.