IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Kernel modules may be needed to access rootfs.
Such modules must be present in the initramfs.
The mkmodpack script finds modules by given patterns.
If the pattern is specified incorrectly, the module
will not be found and booting will become impossible.
Need to warn about module patterns
that do not match with anything.
The pattern can match the name of a module built into
the kernel as given by modprobe.
However, modprobe can fix some incorrect patterns.
These patterns should also be reported.
Here's the culprit:
open("/lib/modules/3.4.7-std-def-alt1/modules.dep.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/lib/modules/3.4.7-std-def-alt1/modules.dep.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/lib/modules/3.4.7-std-def-alt1/modules.alias.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
exit_group(1) = ?
+++ exited with 1 +++
[root@builder .in]# ls -l /lib/modules/3.4.7-std-def-alt1/modules.dep*
-rw-r--r-- 1 root root 370664 Jul 29 18:20 /lib/modules/3.4.7-std-def-alt1/modules.dep
Here's the typical result for mkimage:
ERROR: could not open directory /tmp/mkmodpack.sWzMWshm9Z/lib/modules/3.4.7-std-def-alt1: No such file or directory
FATAL: could not search modules: No such file or directory
mkmodpack: Failed to create modules dependencies.
