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#8490 - mkinitcpio image incorrect when MODULES!=null and HOOKS="base"
Attached to Project:
Arch Linux
Opened by Joel McKee Cooper (mckooper) - Friday, 02 November 2007, 22:22 GMT
Last edited by Thomas Bächler (brain0) - Monday, 26 November 2007, 13:01 GMT
Opened by Joel McKee Cooper (mckooper) - Friday, 02 November 2007, 22:22 GMT
Last edited by Thomas Bächler (brain0) - Monday, 26 November 2007, 13:01 GMT
|
DetailsDescription:
mkinitcpio creates a non-functional image if MODULES is populated but HOOKS does not contain any hooks with modules. Additional info: using mkinitcpio 0.5.15-2 Steps to reproduce: For example, I've got nfsroot systems that really only need: MODULES="e1000" HOOKS="base" But using that config yields a kernel panic because the e1000 module never gets loaded. But, if I add some other hook (that I don't need) MODULES="e1000" HOOKS="base fw" Things work fine. Also, if I hack /lib/initcpio/functions I don't have to have any hooks but "base" for the image to work correctly @@ -137,7 +137,7 @@ fi } -HAS_MODULES="n" +HAS_MODULES="y" #modules are handled specially in order to enable autodetection add_module () { |
This task depends upon
Try copying the file http://projects.archlinux.org/git/?p=mkinitcpio.git;a=blob_plain;f=functions;h=421b85e3462431451e08c3fd927049c206648df9 to /lib/initcpio/functions and report back here.