Why do I have to reload the wireless module to make it work??

kloss · 02-19-2006, 09:32 AM

Since a kernel update (2.6-12 => 2.6-15) with Debian Etch, my wireless module has a curious behavior. It does not work when I start the computer, but if I reload it, it does. Why ??

Thanks for enlighting me

Code:

17:23:02 /home/foo
ROOT 01# ifconfig eth2 up # i want to see my wireless card !
eth2: ERROR while getting interface flags: No such device

17:23:10 /home/foo
ROOT 01# dmesg | grep ipw # what's the problem with this card ?
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8
ipw2200: Copyright(c) 2003-2005 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw-2.4-boot.fw load failed: Reason -2
ipw2200: Unable to load firmware: -2
ipw2200: failed to register network device
ipw2200: probe of 0000:02:04.0 failed with error -5

17:23:44 /home/foo
ROOT 01# modprobe -r ipw2200 && modprobe ipw2200 # reload the module

17:23:54 /home/foo
ROOT 01# ifconfig eth2 up && iwlist eth2 scan # let's see if it works now
eth2      Scan completed :
          Cell 01 - Address: 00:03:C9:A4:05:41
                    ESSID:"<hidden>"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:11
                    Encryption key:on
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
                    Quality=39/100  Signal level=-77 dBm
                    Extra: Last beacon: 652ms ago
          Cell 02 - Address: 00:90:4C:7E:00:29
                    ESSID:"Goo"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:3
                    Encryption key:on
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
                    Quality=39/100  Signal level=-77 dBm
                    Extra: Last beacon: 2346ms ago
          Cell 03 - Address: 00:01:E3:44:8B:BE
                    ESSID:"<hidden>"
                    Protocol:IEEE 802.11b
                    Mode:Master
                    Channel:10
                    Encryption key:on
                    Bit Rates:11 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 11
                    Quality=39/100  Signal level=-77 dBm
                    Extra: Last beacon: 5091ms ago

kilgoretrout · 02-19-2006, 10:54 AM

It doesn't look like it's loading to me. Did you check with lsmod to see if the module was, in fact, loaded?
I know debian doesn't have an rc.local but you can create a script to run your modprobe commands at the end of the boot process. Here's a link describing the process for making an rc.local script equivalent for debian:

http://www.plope.com/Members/chrism/...rc_local_equiv

It might be a timing problem with the new kernel and loading that module. Putting the module load at the end of the boot process will probably take care of that.

kloss · 02-19-2006, 11:21 AM

Quote:

Originally Posted by kilgoretrout

It doesn't look like it's loading to me.

In fact, lsmod shows ipw2200. Maybe the driver only is loaded, not the firmware.

Quote:

It might be a timing problem with the new kernel and loading that module. Putting the module load at the end of the boot process will probably take care of that.

Yeah that is the point ! I did not notice that the kernel tries to load the driver /usr/lib/hotplug/<driver name> before /usr is mounted (that is a separate partition) !
In fact the kernel update gave me "udev" - which caused the mess.

But the problem is not solved. What shall i do ? Changing the order of the different scripts in /etc/init.d in order the partitions to be mounted erlier ? This seems to be hasardous hacking.

(Why did the debian developer not pay attention to that issue ?

)

Thanks for your help

kloss · 02-19-2006, 12:45 PM

Solved :

Code:

mv /usr/lib/hotplug/firmware/* /lib/firmware/*
depmod -ae

++