Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3630 - Updating ipw2200-1.0.8-4
Attached to Project:
Arch Linux
Opened by Andy Roberts (arooaroo) - Saturday, 17 December 2005, 11:35 GMT
Opened by Andy Roberts (arooaroo) - Saturday, 17 December 2005, 11:35 GMT
|
DetailsRan pacman -Syu this morning. A new kernel, mkinitrd, initscripts and ip2200 was waiting for me. I set it off and let pacman do its stuff. According to the output, each component was updagraded, but the last thing to appear was the following:
... upgrading ipw2200... done. ==> In order to use the firmware you have to agree to Intel's license located ==> here: /lib/firmware/LICENSE-ipw2200 ==> If you don't agree, you must remove this package. WARNING: Couldn't open directory /lib/modules/2.6.13-ARCH: No such file or directory FATAL: Could not open /lib/modules/2.6.13-ARCH/modules.dep.temp for writing: No such file or directory I'm guessing that this is an issue since the 2.6.14 kernel was installed just moments before, and so no 2.6.13 dir exists any longer? This bug won't cause any problems with module loading, will it? |
This task depends upon
Comment by Judd Vinet (judd) -
Saturday, 17 December 2005, 20:24 GMT
Those look like errors from depmod, which is complaining because the 2.6.13 modules disappeared during the kernel upgrade. depmod will be run again when you boot up, so no problems there.