diff options
author | Patrick J Volkerding <volkerdi@slackware.com> | 2020-12-17 04:05:14 +0000 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2020-12-17 08:59:51 +0100 |
commit | eae6d71c33a23e358e827cfd0e7e6fa5739c32be (patch) | |
tree | 18a902cd3face7da22c1c981e9539c0d69cd9acb /README.initrd | |
parent | c56a16f1ecd0afa42c16dab6fdfb1f0b667dc287 (diff) | |
download | current-eae6d71c33a23e358e827cfd0e7e6fa5739c32be.tar.gz |
Thu Dec 17 04:05:14 UTC 202020201217040514
I'm still poking at that other kernel, but it shouldn't take too much longer.
a/kernel-generic-5.4.84-x86_64-1.txz: Upgraded.
a/kernel-huge-5.4.84-x86_64-1.txz: Upgraded.
a/kernel-modules-5.4.84-x86_64-1.txz: Upgraded.
ap/rpm-4.16.1.2-x86_64-1.txz: Upgraded.
d/cmake-3.19.2-x86_64-1.txz: Upgraded.
d/kernel-headers-5.4.84-x86-1.txz: Upgraded.
k/kernel-source-5.4.84-noarch-1.txz: Upgraded.
l/utf8proc-2.6.1-x86_64-1.txz: Upgraded.
x/fonttosfnt-1.2.1-x86_64-1.txz: Upgraded.
x/mesa-20.3.1-x86_64-1.txz: Upgraded.
Don't specify dri-drivers-path. Thanks to 414N.
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Diffstat (limited to 'README.initrd')
-rw-r--r-- | README.initrd | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/README.initrd b/README.initrd index 3f273449..b2aea32c 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Sat Dec 12 22:03:09 UTC 2020 +Thu Dec 17 03:34:26 UTC 2020 This document describes how to create and install an initrd, which may be required to use the 4.x kernel. Also see "man mkinitrd". @@ -33,15 +33,15 @@ flexible to ship a generic kernel and a set of kernel modules for it. The easiest way to make the initrd is to use the mkinitrd script included in Slackware's mkinitrd package. We'll walk through the process of -upgrading to the generic 5.4.83 Linux kernel using the packages +upgrading to the generic 5.4.84 Linux kernel using the packages found in Slackware's slackware/a/ directory. First, make sure the kernel, kernel modules, and mkinitrd package are installed (the current version numbers might be a little different, so this is just an example): - installpkg kernel-generic-5.4.83-x86_64-1.txz - installpkg kernel-modules-5.4.83-x86_64-1.txz + installpkg kernel-generic-5.4.84-x86_64-1.txz + installpkg kernel-modules-5.4.84-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-15.txz Change into the /boot directory: @@ -52,7 +52,7 @@ Now you'll want to run "mkinitrd". I'm using ext4 for my root filesystem, and since the disk controller requires no special support the ext4 module will be the only one I need to load: - mkinitrd -c -k 5.4.83 -m ext4 + mkinitrd -c -k 5.4.84 -m ext4 This should do two things. First, it will create a directory /boot/initrd-tree containing the initrd's filesystem. Then it will @@ -61,10 +61,10 @@ you could make some additional changes in /boot/initrd-tree/ and then run mkinitrd again without options to rebuild the image. That's optional, though, and only advanced users will need to think about that. -Here's another example: Build an initrd image using Linux 5.4.83 +Here's another example: Build an initrd image using Linux 5.4.84 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 5.4.83 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 5.4.84 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |