[gobolinux-users] IPW2200 unable to load firmware; firmware package is installed
Anshuman Aggarwal
anshuman at brillgene.com
Sun Aug 19 21:34:35 UTC 2007
One other thing in the kernel logs is the udev errors around
hotplug...but I don't see any hotplug scripts with this version
08/18/2007 11:38:23 PM (none) udevd-event[4904] delete_path:
rmdir(/System/Kernel/Devices) failed: Device or resource busy
----
08/18/2007 11:54:53 PM (none) udevd-event[1586] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1587] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1593] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1594] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1598] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1599] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1600] run_program:
exec of program '/sbin/mod_wrap' failed
08/18/2007 11:54:53 PM (none) udevd-event[1606] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1607] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1610] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1611] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1614] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:54:53 PM (none) udevd-event[1615] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:55:09 PM (none) kernel [ 1517.000000] usb 5-1:
USB disconnect, address 4
08/18/2007 11:55:09 PM (none) udevd-event[1616] delete_path:
rmdir(/System/Kernel/Devices) failed: Device or resource busy
08/18/2007 11:55:09 PM (none) udevd-event[1617] delete_path:
rmdir(/System/Kernel/Devices) failed: Device or resource busy
08/18/2007 11:55:09 PM (none) udevd-event[1619] delete_path:
rmdir(/System/Kernel/Devices) failed: Device or resource busy
08/18/2007 11:55:09 PM (none) udevd-event[1622] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1623] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1626] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1627] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1631] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1632] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1635] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1636] run_program:
exec of program '/lib/udev/udev_run_devd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1639] run_program:
exec of program '/lib/udev/udev_run_hotplugd' failed
08/18/2007 11:55:09 PM (none) udevd-event[1640] run_program:
exec of program '/lib/udev/udev_run_devd' failed
Anshuman Aggarwal wrote:
> IPW2200 is not a module but compiled into the kernel for me? Could that
> be an issue? It shouldn't be...
>
> 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....
>
> 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
>
> udevtest /class/net/eth1
> parse_file: reading '/System/Settings/udev/rules.d/05-udev-early.rules'
> as rules file
> parse_file: reading '/System/Settings/udev/rules.d/10-udev.rules' as
> rules file
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:2'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:3'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:6'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:9'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:10'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:11'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:12'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:15'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:16'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:17'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:18'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:19'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:22'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:25'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:26'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:27'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:28'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:31'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:32'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:33'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:34'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:35'
> add_to_rules: invalid SUBSYSTEMS operation
> add_to_rules: invalid rule '/System/Settings/udev/rules.d/10-udev.rules:36'
> parse_file: reading '/System/Settings/udev/rules.d/50-udev.rules' as
> rules file
> parse_file: reading '/System/Settings/udev/rules.d/51-hotplug.rules' as
> rules file
> parse_file: reading '/System/Settings/udev/rules.d/52-hotplugd.rules' as
> rules file
> parse_file: reading '/System/Settings/udev/rules.d/60-cdrom_id.rules' as
> rules file
> parse_file: reading '/System/Settings/udev/rules.d/60-libpisock.rules'
> as rules file
> parse_file: reading '/System/Settings/udev/rules.d/60-modprobe.rules' as
> rules file
> parse_file: reading
> '/System/Settings/udev/rules.d/60-persistent-input.rules' as rules file
> parse_file: reading
> '/System/Settings/udev/rules.d/60-persistent-storage.rules' as rules file
> add_to_rules: do not reference parent sysfs directories directly, that
> may break with a future kernel, please fix it in
> /System/Settings/udev/rules.d/60-persistent-storage.rules:12
> parse_file: reading
> '/System/Settings/udev/rules.d/70-persistent-cd.rules' as rules file
> parse_file: reading
> '/System/Settings/udev/rules.d/70-persistent-net.rules' as rules file
> parse_file: reading
> '/System/Settings/udev/rules.d/75-cd-aliases-generator.rules' as rules file
> parse_file: reading
> '/System/Settings/udev/rules.d/75-persistent-net-generator.rules' as
> rules file
> parse_file: reading '/System/Settings/udev/rules.d/99-fuse.rules' as
> rules file
> unable to open device '/class/net/eth1'
>
> **************************************
> /System/Settings/udev/rules.d]ll
> total 9
> drwxr-xr-x 2 boss root 656 2007-08-19 13:03 .
> drwxr-xr-x 3 boss root 104 2007-08-19 13:03 ..
> lrwxrwxrwx 1 boss root 56 2007-08-19 13:03 05-udev-early.rules ->
> /Programs/Udev/Settings/udev/rules.d/05-udev-early.rules
> lrwxrwxrwx 1 boss root 50 2007-08-19 13:03 10-udev.rules ->
> /Programs/Udev/Settings/udev/rules.d/10-udev.rules
> lrwxrwxrwx 1 boss root 50 2007-08-19 13:03 50-udev.rules ->
> /Programs/Udev/Settings/udev/rules.d/50-udev.rules
> lrwxrwxrwx 1 boss root 53 2007-08-19 13:03 51-hotplug.rules ->
> /Programs/Udev/Settings/udev/rules.d/51-hotplug.rules
> lrwxrwxrwx 1 boss root 54 2007-08-19 13:03 52-hotplugd.rules ->
> /Programs/Udev/Settings/udev/rules.d/52-hotplugd.rules
> lrwxrwxrwx 1 boss root 54 2007-08-19 13:03 60-cdrom_id.rules ->
> /Programs/Udev/Settings/udev/rules.d/60-cdrom_id.rules
> lrwxrwxrwx 1 boss root 61 2007-07-06 21:31 60-libpisock.rules ->
> /Programs/Pilot-Link/Settings/udev/rules.d/60-libpisock.rules
> lrwxrwxrwx 1 boss root 78 2007-03-10 21:03 60-modprobe.rules ->
> ../../../../Programs/Module-Init-Tools/Settings/udev/rules.d/60-modprobe.rules
> lrwxrwxrwx 1 boss root 62 2007-08-19 13:03 60-persistent-input.rules ->
> /Programs/Udev/Settings/udev/rules.d/60-persistent-input.rules
> lrwxrwxrwx 1 boss root 64 2007-08-19 13:03 60-persistent-storage.rules
> -> /Programs/Udev/Settings/udev/rules.d/60-persistent-storage.rules
> -rw-r--r-- 1 boss root 607 2007-06-26 19:36 70-persistent-cd.rules
> -rw-r--r-- 1 boss root 334 2007-06-26 19:36 70-persistent-net.rules
> lrwxrwxrwx 1 boss root 66 2007-08-19 13:03
> 75-cd-aliases-generator.rules ->
> /Programs/Udev/Settings/udev/rules.d/75-cd-aliases-generator.rules
> lrwxrwxrwx 1 boss root 70 2007-08-19 13:03
> 75-persistent-net-generator.rules ->
> /Programs/Udev/Settings/udev/rules.d/75-persistent-net-generator.rules
> lrwxrwxrwx 1 boss root 50 2007-08-16 00:37 99-fuse.rules ->
> /Programs/Fuse/Settings/udev/rules.d/99-fuse.rules
> *************************************************
>
> Jonas Karlsson wrote:
>
>> On Sun, 19 Aug 2007 18:07:55 +0200, Anshuman Aggarwal <anshuman at brillgene.com> wrote:
>>
>>
>>
>>> Jonas Karlsson wrote:
>>>
>>>
>>>> On Sun, 19 Aug 2007 15:26:59 +0200, Anshuman Aggarwal <anshuman at brillgene.com> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> On Sun, 19 Aug 2007 02:00:23 +0200, Anshuman Aggarwal
>>>>> <anshuman at brillgene.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>> Jul 7 01:16:59 (none) kernel: [ 1.436000] ipw2200: Detected Intel
>>>>>>> PRO/Wireless 2915ABG Network Connection
>>>>>>> Jul 7 01:16:59 (none) kernel: [ 11.437000] ipw2200: ipw2200-bss.fw
>>>>>>> request_firmware failed: Reason -2
>>>>>>> Jul 7 01:16:59 (none) kernel: [ 11.438000] ipw2200: Unable to load
>>>>>>> firmware: -2
>>>>>>> Jul 7 01:16:59 (none) kernel: [ 11.439000] ipw2200: failed to
>>>>>>> register network device
>>>>>>>
>>>>>>>
>>>>>>> I have the IPW2200 firmware packaged installed
>>>>>>> Any ideas on this?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> What version of Udev do you have installed?
>>>>>>
>>>>>> What does 'grep -i firmware /System/Settings/udev/rules.d/*' give? If that
>>>>>> doesn't return anything you might want to try 'grep -i firmware
>>>>>> /Programs/Udev/Current/Resources/Defaults/Settings/udev/rules.d/*'.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> /System/Links/Libraries/firmware]grep -i firmware
>>>>> /System/Settings/udev/rules.d/*
>>>>> /System/Settings/udev/rules.d/50-udev.rules:ACTION=="add",
>>>>> SUBSYSTEM=="firmware", RUN+="/System/Links/Libraries/udev/firmware.sh"
>>>>> /System/Settings/udev/rules.d/60-modprobe.rules:ACTION=="add",
>>>>> SUBSYSTEM=="firmware", ENV{FIRMWARE}="*", \
>>>>> /System/Settings/udev/rules.d/60-modprobe.rules:
>>>>> RUN+="/sbin/firmware_helper"
>>>>>
>>>>> I get a lot of udev errors when I boot up not specific to the the
>>>>> wireless connection but I am not sure how to capture them. the kernel
>>>>> log does not have them and I am not sure how to capture the console log.
>>>>>
>>>>>
>>>>>
>>>>>
>>>> You did not answer what version of Udev you had...
>>>> Make sure that you have /Programs/Udev/Current/lib/udev/firmware.sh and that
>>>> /System/Links/Libraries/udev/firmware.sh points there. Also try and run
>>>> 'UpdateSettings Udev' followed by 'SymlinkProgram Udev'.
>>>>
>>>>
>>>>
>>>>
>>> Sorry, I missed the bit about udev version (110). i have the latest
>>> available in the recipe tree. The link is there and working....
>>>
>>> cd udev
>>> boss@ /System/Links/Libraries/udev]ll firmware.sh
>>>
>>> lrwxrwxrwx 1 boss root 39 2007-08-18 12:11 firmware.sh ->
>>> /Programs/Udev/110/lib/udev/firmware.sh
>>>
>>> Here is the output of UpdateSettings and Symlink...I don't think this
>>> did anything though...any other clues on how I can deal with the udev
>>> errors (and capture them) ...maybe they are related to this (though i
>>> never see anything about firmware scroll by)
>>>
>>> boss@ /System/Links/Libraries/udev]UpdateSettings Udev
>>> UpdateSettings: Current and default settings match
>>>
>>>
>> Strange, as there shouldn't exist any 60-modprobe.rules file in the default
>> settings of your version of udev. Make sure you don't have any *files* in
>> /System/Settings/udev/rules.d, besides some NN-persistant*.rules. Where is that
>> 60-modprobe.rules file located? Make sure that /System/Settings/udev/rules.d is
>> in sync with /Programs/Udev/Current/Resources/Default/Settings/udev/rules.d.
>>
>>
>>
>>> boss@ /System/Links/Libraries/udev]SymlinkProgram Udev
>>> SymlinkProgram: Symlinking Udev 110.
>>> SymlinkProgram: Symlinking global settings...
>>> SymlinkProgram: Processed 15 files.
>>>
>>>
>> Hard to tell if this is correct as directories isn't always expanded (and that
>> there existed a counting bug until just now).
>>
>> Another question, what does 'udevtest /class/net/eth1' (where eth1 is your wireless
>> card) output?
>>
>>
>>
> _______________________________________________
> gobolinux-users mailing list
> gobolinux-users at lists.gobolinux.org
> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>
More information about the gobolinux-users
mailing list