When installing modules it is possible that they are
not registered properly.
postinst does a depmod -A and update-modules
However depmod -A means according to the man page:
-A --quick
This option scans to see if any
modules are newer the mod‐
ules.dep file before any work is
done: if not, it silently
exits rather than regenerating the
files.
Now this can lead to the following scenario.
module 1 is installed, depmod -A runs and modules.dep
is updated.
next module 2 is installed and depmod -A is run again.
However as the date of the .ko file is the date at
which it is build, not when it is installed, depmod -A
will not find modules newer than modules.dep so it
will silently exit and not register the new modules.
My proposal to fix this is to change depmod -A into
depmod or depmod -a.
However I feel somewhat uncomfortable in this area, so
therefore instead of changing things myself, I'd like
to hear others opinions.
As far as I can see the following files are affected:
./classes/kernel.bbclass
./classes/module.bbclass
./packages/linux/mnci-ramses_2.4.21-rmk2-pxa1.bb
./packages/modutils/files/mnci/modutils.sh
./packages/modutils/files/modutils.sh
./packages/update-modules/update-modules-1.0/update-modules
eFfeM
PS: I assume this will also affect lines like:
${HOST_PREFIX}depmod-${KERNEL_MAJOR_VERSION} in
kernel.bbclass
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Oe mailing list
[email protected]
https://www.handhelds.org/mailman/listinfo/oe
