IPW2100, On/Off/On to get working... :\

bfloeagle · 08-31-2005, 02:01 PM

Just got the wireless working on my Averatec 5110h laptop. Running Gentoo with the ipw2100, ipw2100-firmware, wpa_supplicant, and the av5100 rf switch packages/programs.

Here is what is odd. If the system automatically loads or I do a manual modprobe at the end of the boot process I get the following errors:

Code:

Aug 31 13:11:47 Voyager ipw2100: eth1: Firmware 'ipw2100-1.3.fw' not 
available or load failed.
Aug 31 13:11:47 Voyager ipw2100: eth1: ipw2100_get_firmware failed: -2
Aug 31 13:11:47 Voyager ipw2100: eth1: Failed to power on the adapter.
Aug 31 13:11:47 Voyager ipw2100: eth1: Failed to start the firmware.
Aug 31 13:11:47 Voyager ipw2100Error calling register_netdev.
Aug 31 13:11:47 Voyager ipw2100: probe of 0000:02:01.0 failed with error -5

I figured it was a problem with the firmware but after lots of testing it was not (and here is why)... Then I run:

Code:

rmmod ipw2100
modprobe ipw1200

And I get:

Code:

Aug 31 13:12:11 Voyager ipw2100: Intel(R) PRO/Wireless 2100 Network 
Driver, 1.1.2
Aug 31 13:12:11 Voyager ipw2100: Copyright(c) 2003-2005 Intel Corporation
Aug 31 13:12:11 Voyager ipw2100: Detected Intel PRO/Wireless 2100 
Network Connection

And presto, IP activity and wireless connectivity... ??? It's not a major problem b/c I can just write a script to load, unload, and load the ipw2100 module to get my wireless card working, but I was wondering if anyone else out there who has a centrino based system and is running into similar problems... Or if anyone can tell my why it would seem that unloading a module fixes something...

Andy

Hangdog42 · 09-03-2005, 08:30 AM

To be honest, I have no idea why this happens, but I've seen it happen with other modules as well such as ndiswrapper. The only thing that comes to mind is that something about the system isn't done loading, even at the end of the boot. If you put in a delay before loading this during boot, does that work?

bfloeagle · 09-03-2005, 07:54 PM

Tried it an it didn't work... I put the modprobe commands in rc.local (or whatever gentoo uses to run local commands, I forgot its exact name) and I had the same results... Even if I wait ten minutes, I still get the errors on the first load, then everything fine on the second load.