SlackwareThis Forum is for the discussion of Slackware 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 have been building generic kernels on 64-current for a while now and all runs just fine when I build my initrd.gz using "mkinitrd -c -R -k $kerno -m ext4"(no quotes) in a short script where I prompt for the kernel version. If I use the mkinitrd shell script in /usr/share to generate a mkinitrd.conf in /etc and then generate my initrd.gz using mkinitrd -c -F at a command prompt from the /boot directory it generated the initrd.gz but the system won't boot, stopping shortly after the boot starts saying that it can't find /mnt. The mkinitrd.conf file is -
Code:
cat mkinitrd.conf
#
# mkinitrd_command_generator.sh revision 1.45
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:
mkinitrd -c -k 5.12.12 -f ext4 -r /dev/md126 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:crc32c_intel:crc32c_generic:ext4 -R -u -o /boot/initrd.gz
This is exactly what happened some time ago when I tried to boot a generic kernel and had not read the man page thoroughly for mkinitrd and had neglected to add the -R command line parameter to reflect that it is a raid system. The mkinitrd.conf file does however include a -R so that should not be the problem.
I'm Probably missing something obvious but can't see forrest for trees at this point. Thanks in advance.
That's not a mkinitrd.conf file you've generated. It's a script containing a mkinitrd command.
A mkinitrd.conf will look something like this:
Code:
# mkinitrd.conf.sample
# See "man mkinitrd.conf" for details on the syntax of this file
#
#SOURCE_TREE="/boot/initrd-tree"
CLEAR_TREE="1"
#OUTPUT_IMAGE="/boot/initrd.gz"
#KERNEL_VERSION="$(uname -r)"
KEYMAP="uk"
# MODULE_LIST="xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch"
MODULE_LIST="ext4:xhci-pci:xhci-hcd:usbhid:hid-generic"
LUKSDEV="/dev/sda4"
ROOTDEV="/dev/sysvg/lvslack"
ROOTFS="ext4"
LVM="1"
MICROCODE_ARCH='/boot/intel-ucode-local.cpio'
My laptop has a very long line for the MODULE_LIST entry similar to GazL's
Yes, mkinitrd_command_generation does go overboard with included modules, as can be seen by the commented out line in my example, compared to what I actually need below it.
Can't believe I could be so DOOF (German for dumb ass)! Thank you gentlemen. Major dumb shit here. Did as you described and of course it worked like a charm. Thank you again. Will have RTFM tatooed on the inside of my eyelids.
Can't believe I could be so DOOF (German for dumb ass)! Thank you gentlemen. Major dumb shit here. Did as you described and of course it worked like a charm. Thank you again. Will have RTFM tatooed on the inside of my eyelids.
Hey we all do DOOF things every now and then. Glad it all sorted out.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Are you booting from a usb disk? I'm asking because of the presence of usb modules in your modules list.
I think you missed the -w option, usb needs some time to be recognized.
In the chrisretusn's config file it is 'WAIT=1'
Are you booting from a usb disk? I'm asking because of the presence of usb modules in your modules list.
I think you missed the -w option, usb needs some time to be recognized.
In the chrisretusn's config file it is 'WAIT=1'
No, booting from regular hard disk raid. Will refine the config script in the future to remove some of the unnecessary modules. This was just a first go to get it running with a .conf file.
Yes, mkinitrd_command_generation does go overboard with included modules, as can be seen by the commented out line in my example, compared to what I actually need below it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.