[gobolinux-users] IPW2200 unable to load firmware; firmware package is installed

[Jonas Karlsson]

On Wed, 22 Aug 2007 04:01:19 +0200, Anshuman Aggarwal <anshuman at brillgene.com> wrote:

> I've put the answers below
>
> Jonas Karlsson wrote:
>> On Sun, 19 Aug 2007 23:05:04 +0200, Anshuman Aggarwal <anshuman at brillgene.com> wrote:
>>
>>
>>> IPW2200 is not a module but compiled into the kernel for me? Could that
>>> be an issue? It shouldn't be...
>>>
>>>
>> I don't know. IIrc I had some issues with ipw2200 built-in. Anyway it's
>> easier to find the error if it's a module, as one can force messages by
>> loading and onloading it and find which version of ipw2200 you're using by
>> using modinfo. Do you know which version you're using? Which kernel are you
>> using? If it's an earlier kernel you might want to try IPW2200-firmware 2.4
>> which is for IPW 1.1.0 and earlier.
>>
> Compiled version 2.6.22.1 with drivers as modules...all other modules
> including tg3 (eth0) work...but ipw2200 still gives the same error. The
> IPW2200 version that came with this kernel is IPW 1.2.0...hence firmware
> IPW2200-Firmware-3.0
>>> Hmmm....the plot thickens but we may be close to an answere here...the
>>> modprobe rules file is here:
>>> There are quite a few 05, 10- files that are not the persistent ones but
>>> they were all distributed with the recipe...maybe the recipe is broken
>>> ...which version of udev are you on? I could go back to that and check....
>>>
>>>
>> I have Udev 110-r2, but I think I'm using the rules from -r4. Make sure you
>> have revision 4 of Udev 110 as well by looking in
>> /Programs/Udev/Current/Resources/Revision.
>>
> cat /Programs/Udev/Current/Resources/Revision
> r4
>
> ll /Programs/Udev
> total 7
> drwxr-xr-x   4 boss root  120 2007-07-08 11:29 .
> drwxr-xr-x 273 boss root 7280 2007-08-18 21:27 ..
> drwxr-xr-x   9 boss root  224 2007-07-08 11:29 110
> lrwxrwxrwx   1 boss root    3 2007-07-08 11:29 Current -> 110
> drwxr-xr-x   4 boss root  128 2007-06-25 03:37 Settings
>>> lrwxrwxrwx 1 boss root  78 2007-03-10 21:03 60-modprobe.rules ->
>>> ../../../../Programs/Module-Init-Tools/Settings/udev/rules.d/60-modprobe.rules
>>>
>>> Also Module-Init-Tools is at 3.2.2...but the settings and the file
>>> distributed with the version is the same
>>>
>>>
>> I'm only at Module-Init-Tools 3.0 here and that doesn't come with that rules file.
>>
>>
>>> udevtest /class/net/eth1
>>>
>> [...]
>>
>>> unable to open device '/class/net/eth1'
>>>
>>>
>> Well, that would mean that eth1 isn't your network interface, or that
>> it wasn't set up. Change eth1 to whichever card that 'iwconfig' says has
>> wireless capabilities.
>>
>> As a final resort I'd recommend you to rebuild your kernel with ipw2200 as a module.
>> If you haven't removed the source directory for the kernel it'll go quite fast.
>>
> eth1 would have been my network interface (based on how modprobe.conf
> was set) alias eth1 ipw2200. It is now built as a module but the same
> firmware loading error...
> I thought if iwconfig showed any card with wireless capability, it would
> mean that the firmware is getting loaded...
>
> nothing is recognizing the ipw2200 card, with the module and without...
>
> Any other suggestions?
>
I have given this some more thought and have some things I want you to try,
unless you have got it running yet.
You did verify /System/Links/Libraries/udev/firmware.sh was a link to
/Programs/Udev/110/lib/udev/firmware.sh, but not that the latter was a file
(the link could be dead). Could you also remove/move
/System/Settings/Udev/rules.d/60-modprobe.rules, as the rules listed there
might conflict with the rule in 50-udev.rules (even if the rules in 50 is
executed first).
Also run 'udevmonitor' in one console and unload and load the 'ipw2200'
module and see what 'udevmonitor' prints. Unfortunatly I haven't found
a way to trigger how udev handles the firmware event you'll probably see
in that output. The other events can be simulated using 'udevtest', e.g.
'udevtest /module/ipw2200/drivers'. Play around with it and see if you
find something. Also make sure that FIRMWARE_DIRS, in
/Programs/Udev/110/lib/udev/firmware.sh lists the directory you have your
firmware in ('/lib/firmware' or similar). Verify this both ways, i.e.
list the contents of the directories listed in FIRMWARE_DIRS and see if
the firmware is there.

-- 
/Jonas

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/