[opensuse] dracut - how do I get to see a summary of kernel modules and dracut modules chosen?
See $SUBJ - with mkinitrd, there was always a couple of lines listing which modules had been included. With dracut, I get what looks mostly like debug output, but no summary of what was built, see below. # mkinitrd -k vmlinuz-3.16.6-2-default -i initrd-3.16.6-2-default Creating initrd: /boot/initrd-3.16.6-2-default Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-3.16.6-2-default 3.16.6-2-default dracut module 'plymouth' will not be installed, because command 'plymouthd' could not be found! dracut module 'plymouth' will not be installed, because command 'plymouth' could not be found! dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! *** Including module: bash *** *** Including module: warpclock *** *** Including module: i18n *** *** Including module: network *** *** Including module: ifcfg *** *** Including module: kernel-modules *** Omitting driver i2o_scsi *** Including module: nfs *** *** Including module: rootfs-block *** *** Including module: terminfo *** *** Including module: udev-rules *** Skipping udev rule: 91-permissions.rules Skipping udev rule: 80-drivers-modprobe.rules *** Including module: systemd *** *** Including module: usrmount *** *** Including module: base *** *** Including module: fs-lib *** *** Including module: shutdown *** *** Including module: suse *** *** Including modules done *** *** Installing kernel module dependencies and firmware *** *** Installing kernel module dependencies and firmware done *** *** Resolving executable dependencies *** *** Resolving executable dependencies done*** *** Hardlinking files *** *** Hardlinking files done *** *** Stripping files *** *** Stripping files done *** *** Generating early-microcode cpio image *** *** Constructing GenuineIntel.bin **** *** Store current command line parameters *** Stored kernel commandline: root=nfs4:mirage:/home/airbus:rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.146,local_lock=none,addr=192.168.2.151 ip=enp3s1f0:static *** Creating image file *** *** Creating image file done *** Update bootloader... -- Per Jessen, Zürich (5.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 03/12/14 a las 10:56, Per Jessen escribió:
See $SUBJ - with mkinitrd, there was always a couple of lines listing which modules had been included. With dracut, I get what looks mostly like debug output, but no summary of what was built, see below.
You can use lsinitrd to examine the file list. (for now, I agree that it will be cool to have a switch to list the included modules only) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Dec 3, 2014 at 4:56 PM, Per Jessen <per@computer.org> wrote:
See $SUBJ - with mkinitrd, there was always a couple of lines listing which modules had been included.
kernel modules or dracut/mkinitrd module? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
On Wed, Dec 3, 2014 at 4:56 PM, Per Jessen <per@computer.org> wrote:
See $SUBJ - with mkinitrd, there was always a couple of lines listing which modules had been included.
kernel modules or dracut/mkinitrd module?
Both. I was migrating some 13.1 systems to 13.2 and because the cmdline arguments syntax for nfs root was changed, I occasionally ended up with a non-booting system, so I needed to check that the initrd was built with the right options+modules. -- Per Jessen, Zürich (4.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Wed, 03 Dec 2014 16:26:17 +0100 Per Jessen <per@computer.org> пишет:
Andrei Borzenkov wrote:
On Wed, Dec 3, 2014 at 4:56 PM, Per Jessen <per@computer.org> wrote:
See $SUBJ - with mkinitrd, there was always a couple of lines listing which modules had been included.
kernel modules or dracut/mkinitrd module?
Both.
Dracut modules are printed in the beginning of lsinitrd output: dracut modules: bash warpclock i18n ifcfg drm plymouth dm kernel-modules lvm resume rootfs-block terminfo udev-rules biosdevname systemd usrmount base fs-lib shutdown suse Upstream now has -m option to print only modules, you may consider opening bug report to request it. I do not think mkinitrd printed kernel modules either. Suitable approximation is lsinitrd /boot/initrd | grep lib/modules/ What I really miss is the easy way to unpack and rebuild initrd (it is concatenation of several compressed cpio images so trivial zcat | cpio does not work). I'm tempted to send patch for "lsinitrd -x".
I was migrating some 13.1 systems to 13.2 and because the cmdline arguments syntax for nfs root was changed, I occasionally ended up with a non-booting system, so I needed to check that the initrd was built with the right options+modules.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
В Wed, 03 Dec 2014 16:26:17 +0100 Per Jessen <per@computer.org> пишет:
Andrei Borzenkov wrote:
On Wed, Dec 3, 2014 at 4:56 PM, Per Jessen <per@computer.org> wrote:
See $SUBJ - with mkinitrd, there was always a couple of lines listing which modules had been included.
kernel modules or dracut/mkinitrd module?
Both.
Upstream now has -m option to print only modules, you may consider opening bug report to request it.
I do not think mkinitrd printed kernel modules either.
It did/does : # mkinitrd -k vmlinuz-3.11.10-11-default -i something Kernel image: /boot/vmlinuz-3.11.10-11-default Initrd image: /boot/klop99 Root device: /dev/disk/by-id/cciss-3600508b1001fffffa00184c9aaf70004-part2 (/dev/cciss/c0d0p2) (mounted on / as ext4) Kernel Modules: thermal_sys thermal processor fan cciss ata_piix ata_generic scsi_dh scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw usb-common usbcore ohci-hcd uhci-hcd ehci-hcd xhci-hcd usbhid hid-logitech-dj hid-generic hid-holtek-kbd hid-lenovo-tpkbd hid-ortek hid-roccat hid-roccat-common hid-roccat-arvo hid-roccat-isku hid-samsung ehci-pci ohci-pci Features: acpi block usb Other differences - the initrds built by dracut are bigger, sometimes twice the size of the ones built by mkinitrd, and dracut is slooooooooooow. Both are annoying, but no big deal.
What I really miss is the easy way to unpack and rebuild initrd (it is concatenation of several compressed cpio images so trivial zcat | cpio does not work). I'm tempted to send patch for "lsinitrd -x".
I've been wondering about that too. I would also like the reverse to be easy, to facilitate creating initrds myself. -- Per Jessen, Zürich (4.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
Cristian Rodríguez -
Per Jessen