ArchThis Forum is for the discussion of Arch Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I thought i'd have a go at using this. Can anyone advise on what's the best way to configure hooks for optimal booting speed?
Below are the important bits of my /etc/mkinitcpio.conf
Code:
MODULES="generic via82cxxx ext3 ide_disk"
HOOKS="base autodetect ide filesystems"
Do I need to include 'ide' and 'filesystems' as I have specified those in the modules section?
Also, what's the deal with the Beyond kernel? I can boot my Beyond kernel if I change my initrd entry via /boot/grub/menu.lst to the following, but I dont see the advantages to be had, as the image was created using /etc/mkinitcpio.conf - there's not a /etc/mkinitcpio-beyond.conf.
Interesting stuff! I don't use mkinitcpio (yet), but have you read the Configuring mkinitcpio page on the ArchWiki? AFAICT, you should *not* remove the 'ide' and 'filesystems' hooks. Unfortunately, I am not entirely sure what the deal is with "beyond", but according to the wiki there should exist a /boot/mkinitcpio-kernel26beyond.conf file with default settings. So perhaps that is why no /etc/mkinitcpio-beyond.conf is required? Sorry, I'm a bit out of my depth here. Hope that helps anyway.
As I understand it, the info on the wiki tends to be a bit contradictory, eg this:
Quote:
There will be 2 images created during kernel installation/upgrade:
- kernel26
- kernel26beyond (2.6.17 not yet available)
Seems to contradict this:
Quote:
You can use mkinitcpio with any kernel, so kernel26 and kernel26-beyond users are encouraged to try it.
I have successfully booted the stock kernal using only the 'base' and 'autodetect' parameter as I have specified my modules. And this from /etc/mkinitcpio.conf:
Quote:
'filesystems' is _required_ unless you specify your fs modules in MODULES
@Junctajuvant
Quote:
according to the wiki there should exist a /boot/mkinitcpio-kernel26beyond.conf file with defaults
As you can see, I have the stock kernel & beyond kernel; the original initrd26.img, my beyond initramfs-beyond.img; and the *new* stock kernel image 'kernel26.img' and the initcpio.img but no arch26beyond.img.
So, I guess my original questions still stand, eg when will there be an upgrade - if that's what is gonna happen - so that theres a /etc/mkinitcpio-beyond.conf which will create a kernel26beyond.img, and what are the best hook parameters to specify for optimal booting?
that is my /boot directory after the latest upgrades including mkinitcpio it created the images for stock and beyond right off the bat (maybe because i was updating from the beyond kernel boot?)
It updated mine fine it seems, my mkinitcpio-kernel26beyond.conf is as follows if yo uwant to use it as a guide
Code:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
#BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide filesystems raid encrypt"
#
# This setup loads an LVM volume group on a usb device.
# HOOKS="base udev usb filesystems lvm"
HOOKS="base udev ide scsi sata usbinput filesystems"
Note: i have not tweaked myinitcpio atall, it still has the default hooks
In light of my original post, I realise that I misread the wiki (wouldnt be a first). I thought that the mkinitcpio-kernel26beyond.conf file was situated in /etc, but on rereading the wiki that file should be in /boot.
Quote:
Note: i have not tweaked myinitcpio atall, it still has the default hooks
When you have tweaked your mkinitcpio, I would be interested to see how you have set up your hooks.
Edit - just after posting this I noticed the wiki updated. Syu'd and above files now generated. All good.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.