LinuxQuestions.org - firmware loading fails at boot time

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - firmware loading fails at boot time (https://www.linuxquestions.org/questions/linux-from-scratch-13/firmware-loading-fails-at-boot-time-347349/)

Thanks desenfrenada,

unfortunately for me, that solution doesn't work for me, but it's strange you had to go into an 'external' website to get that info, it's posted in the ipw2200 sourceforge site :P

anyway, thanks for your... 2 cents ;)

Julio

Urks - sorry, I did not see someone pointed out the issue and the link in the second post :(

My wireless stopped working as well now (same /var/log/messages output, iwconfig doesn't show device), from the error messages I get it seems I am in a similar situation as you. Did you try to follow tudorh's suggestion yet? I will, and post the results here.

desenfrenada

Hi desenfrenada,

maybe the problem would be with the udev installation or the hotplug scripts, but... I think I've read the udev installation is not right... I have to research a bit more... but I'll keep you informed with my progress...

Julio

</there goes my 0.02 euros :p>

Hi,

@tudorh: my wireless device works with Gentoo kernel 2.6.12-ck5-r1, ipw2200 1.0.6 and ieee80211 1.0.2.

@Julio: It keeps nagging me that the same setup with the newest ieee80211 worked this morning, then suddenly stopped doing so.
If I make any progress, I too will return with some more loose cash to drop.

EDIT: I am still with devfs, so udev cannot be the culprit here. Setting firmware timeout to 100 and using the versions tudorh suggested works, although sometimes I need two or three rmmod and modprobe's of ipw2200 to get it working. I will experiment with that later (for now I am happy I have a connection at all :)

@desenfrenada:

it's like the doings of the devil, suddenly everything goes to hell hehehe... :p

I talked several weeks ago with James Ketrenos at the ipw2200 sourceforge site, but the procedure he recommended me to perform was just enabling the DEBUG=yes export DEBUG lines in the hotplug agent, but... in my case, it didn't show any clue...

maybe you could try the same and see if it gives you an answer...

Julio

Quote:

Originally posted by ParticleHunter
Hi tudorh,

bad news you bring with you... but it's ok... maybe we should try to receive an answer from the ipw2200 people but I've contacted James Ketrenos and he recommended me to uncomment all the #DEBUG=yes export DEBUG and I don't know where can I get the system log with all the debuf statements...

have you tried to replace the hotplug scripts with the hotplug-ng package?

Julio

hi,
after few try ( make uninstall; . remove-old; make clean. also use the same version as stated above.), i still can't get my wireless card worked.

the dmesg message shown as below

Code:

[4294687.098000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6

[4294687.098000] ipw2200: Copyright(c) 2003-2004 Intel Corporation

[4294687.098000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection

[4294687.571000] ipw2200: Radio Frequency Kill Switch is On:

looks like there's no error, but
aftr disabling my network eth0 (tg3) and , then,loading the wireless card (ipw2200), i still can't ping the host, e.g., www.google.com

the version used are the same as quoted (i.e., ieee80211 1.0.2 / ipw2200 1.0.6/ ipw2200-fw-2.3 )
btw, the firmware i copy them to /usr/lib/hotplug/firmware (7 files), of which path stated in the /etc/hotplug/firmware.agent

Code:

FIRMWARE_DIRS="/lib/firmware /usr/local/lib/firmware /usr/lib/hotplug/firmware"

what else i may go wrong?
or what should i check to correct this dilemma?
i appreciate any suggestion, sincerely.

Quote:

[4294687.571000] ipw2200: Radio Frequency Kill Switch is On:

????

that doesn't show up for me... what have you done? :scratch:

Julio

Quote:

Originally posted by ParticleHunter
????

that doesn't show up for me... what have you done? :scratch:

Julio

i suppose i lost to attach the following line because, in the previous post, i used command 'dmesg | grep ipw'.
and the missing line is "Kill switch must be turned off for wireless networking to work".
(sorry if this is still not clear, for i'm not very familir these stuff. i may miss some points that i'm not aware of)

for i read the post referred to by tudorh, saying that he'd successed in setting up ipw2200, then i follow his post to test weather it works for my laptop or not. (the env i use is debian sarge stable 3.1 r0a with kernel 2.6.12 manually built )
however, this solution (ipw2200-1.0.6/ ieee80211-1.0.2/ ipw2200-fw-2.3) seems doesn't work for me.
btw, i can't find any weird message, which looks like error message, both in /var/log/syslog and dmesg. so i'm confused what part i may do it wrong.

message in /var/log/syslog

Code:

...

ieee80211_crypt: registered algorithm 'NULL'

ieee80211: 802.11 data/management/control stack, 1.0.2

ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>



ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6

ipw2200: Copyright(c) 2003-2004 Intel Corporation



ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection

ipw2200: Radio Frequency Kill Switch is On:

Kill switch must be turned off for wireless networking to work.

...

as well as in dmesg (dmesg | grep ipw )

Code:

ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6

ipw2200: Copyright(c) 2003-2004 Intel Corporation

ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection

ipw2200: Radio Frequency Kill Switch is On:

i do not find any message similar to previous post referred to (e.g., "Unable to load firmware: 0xFFFFFFFE"), which occurred when building with ieee80211-1.0.3.

so i hope to know where i did was wrong in order to solve the problem.

i appreciate any suggestion, sincerely.

p.s.: i use laptop HP NC6230.

today i decide to update kernel for after re-read the post, i found out the version is slight different from the version i previously used (, which is 2.6.12).
so i update it to 2.6.12.4.
and now it has such message appeared in /var/log/syslog.

what does it mean??

Code:

 ieee80211_crypt: registered algorithm 'NULL'

 ieee80211_crypt: registered algorithm 'WEP'

ieee80211_crypt: registered algorithm 'TKIP'

ieee80211_crypt: registered algorithm 'CCMP'

ieee80211: 802.11 data/management/control stack, 1.0.2

ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>

ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6

 ipw2200: Copyright(c) 2003-2004 Intel Corporation



......



 ipw2200: U ipw_pci_probe pci_resource_len = 0x00001000

ipw2200: U ipw_pci_probe pci_resource_base = f897e000

ipw2200: U ipw_sw_reset Hardware crypto [on]

ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection

ipw2200: U ipw_get_fw Loading firmware 'ipw-2.3-boot.fw' file v2.0 (6464 bytes)

 ipw2200: U ipw_get_fw Loading firmware 'ipw-2.3-bss_ucode.fw' file v2.0 (16326 bytes)

 ipw2200: U ipw_get_fw Loading firmware 'ipw-2.3-bss.fw' file v2.0 (166952 bytes)

 ipw2200: U ipw_load initial device response after 10ms

 ipw2200: U ipw_stop_master stop master 0ms

ipw2200: U ipw_load_ucode Microcode OK, rev. 53594 (0xd15a) dev. 3 (0x3) of 11/22/04 20:27

 ipw2200: U ipw_load device response after 50ms

 ipw2200: U ipw_eeprom_init_sram Writing EEPROM data into SRAM

ipw2200: U ipw_up Geography 000 [ZZM] detected.

 ipw2200: Radio Frequency Kill Switch is On:

 Kill switch must be turned off for wireless networking to work.

ipw2200: U ipw_net_open dev->open



......

ipw2200: U ipw_wx_get_name Name: radio off

 ipw2200: U ipw_wx_get_freq GET Freq/Channel -> 0

ipw2200: U ipw_wx_get_essid Getting essid: ANY

 ipw2200: U ipw_wx_get_mode Get MODE -> 2

 ipw2200: U ipw_wx_get_range GET Range

 ipw2200: U ipw_wx_get_wap Getting WAP BSSID: 00:00:00:00:00:00

 ipw2200: U ipw_wx_get_nick Getting nick

 ipw2200: U ipw_wx_get_rate GET Rate -> 0

 ipw2200: U ipw_wx_get_rts GET RTS Threshold -> 2304

ipw2200: U ipw_wx_get_frag GET Frag Threshold -> 2346

ipw2200: U ipw_wx_get_power GET Power Management Mode -> 06

 ipw2200: U ipw_wx_get_txpow GET TX Power -> ON 20

 ipw2200: U ipw_wx_get_retry GET retry -> 7

if this doesn't show any error of the ipw2200 driver. is it possible resulted from my wireless setting?
because i setup eth1 in /etc/network/interfaces, which works when i use another notebook (acer 290xci ).
but i found out output of iwconfig (HP NC6230) is as follow:

Code:

lo        no wireless extensions.



eth0      no wireless extensions.



sit0      no wireless extensions.



eth1      radio off  ESSID:off/any

          Mode:Managed  Channel:0  Access Point: 00:00:00:00:00:00

          Bit Rate=0 kb/s  Tx-Power=off

          Retry limit:7  RTS thr:off  Fragment thr:off

          Encryption key:off

          Power Management:off

          Link Quality:0  Signal level:0  Noise level:0

          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

if it's the problem in setting wireless ip. what should i do ?(how to configure it or where there's related resource)
i appreciate it, sincerely.

Quote:

Originally posted by shogun1234
[B]today i decide to update kernel for after re-read the post, i found out the version is slight different from the version i previously used (, which is 2.6.12).
so i update it to 2.6.12.4.
and now it has such message appeared in /var/log/syslog.

what does it mean??

It means you're doing fine now; it's registering some ciphers for WEP/WPA and then goes through initializing the driver.
On a quick look, I see no clear problems in the output you got. Did you try the network? :)

Quote:

eth1 radio off ESSID:off/any
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Bit Rate=0 kb/s Tx-Power=off
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

you could try

Code:

# iwconfig eth1 mode ad-hoc

# dhclient eth1

there and see if you get an IP.

I'm fighting with the ipw2200 on an Acer Aspire 1363WLMi with FC3. I will post if I find a working configuration.

Quote:

Originally posted by jute
It means you're doing fine now; it's registering some ciphers for WEP/WPA and then goes through initializing the driver.
On a quick look, I see no clear problems in the output you got. Did you try the network? :)

you could try

Code:

# iwconfig eth1 mode ad-hoc # dhclient eth1

there and see if you get an IP.

I'm fighting with the ipw2200 on an Acer Aspire 1363WLMi with FC3. I will post if I find a working configuration.

yet due to i use static ip, thus i configure /etc/network/interfaces as follow:

Code:

auto lo

iface lo inet loopback



# The primary network interface

auto eth0

auto eth1

iface eth0 inet static

        address xxx.xxx.xxx.xxx

        netmask 255.255.255.0

        network xxx.xxx.xxx.xxx

        broadcast xxx.xxx.xxx.xxx

        gateway xxx.xxx.xxx.1



iface eth1 inet static

        address xxx.xxx.xxx.xxx

        netmask 255.255.255.0

        network xxx.xxx.xxx.xxx

        broadcast xxx.xxx.xxx.xxx

        gateway xxx.xxx.xxx.1

but, after typing command "iwconfig eth1 mode ad-hoc", the following one (to get ip from dhcp) would not work.
what should i do (after this command if i use static ip)?
for after "ping" the gateway, it simply response with

Code:

PING xxx.xxx.xxx.1  (xxx.xxx.xxx.1) 56(84) bytes of data.

From xxx.xxx.xxx.xxx icmp_seq=2 Destination Host Unreachable

From xxx.xxx.xxx.xxx icmp_seq=3 Destination Host Unreachable

From xxx.xxx.xxx.xxx icmp_seq=4 Destination Host Unreachable

hope you will success.
thanks your reply, i appreciate it sincerely.; )

I'm still fighting with the Acer -- I just can't get a hand-compiled 2.6.13 to boot properly
in that Fedora environment. It seems to be something to do with SELinux, but I can't
get my head around it.

If you're using static IP's, then the commands after to enter the network (after iwconfig
shows the device is configure correctly) would be

> ifconfig eth0 YOUR_IP_HERE up
> route add default gw YOUR_GATEWAY_IP

and if you have a nameserver available,

> echo "search YOUR_DOMAIN" > /etc/resolv.conf
> echo "nameserver YOUR_NAME_SERVER" >> /etc/resolv.conf

-- YOUR_IP_HERE is the IP you've chosen for you machine if you're in a LAN (behind a NAT/router),
for example 192.168.0.100
-- YOUR_GATEWAY_IP is the IP of your router
-- YOUR_DOMAIN you know it if you need to
-- YOUR_NAME_SERVER is the IP of a suitable DNS service, it could be the DNS of
your isp, or a DNS cache in your LAN

Please refer to 'man iwconfig' for explanation of wlan mods (ad-hoc/managed).
Changes are that you really need the managed mode. If your wlan is using
encryption, check 'man iwconfig' for 'key' parameter.

--
jussi