diff options
| author | Patrick J Volkerding <volkerdi@slackware.com> | 2018-12-29 23:13:15 +0000 |
|---|---|---|
| committer | Eric Hameleers <alien@slackware.com> | 2018-12-30 08:59:46 +0100 |
| commit | 527328c5da0d2375ca5dfc2a053c9fe328839918 (patch) | |
| tree | d2773d407aba234712f864db90e15c99a9e08da5 /README.initrd | |
| parent | 1e1c447e2ef274f8b3733ba21570e74c3bc757b7 (diff) | |
| download | current-527328c5da0d2375ca5dfc2a053c9fe328839918.tar.gz | |
Sat Dec 29 23:13:15 UTC 201820181229231315
a/kernel-generic-4.19.13-x86_64-1.txz: Upgraded.
a/kernel-huge-4.19.13-x86_64-1.txz: Upgraded.
a/kernel-modules-4.19.13-x86_64-1.txz: Upgraded.
d/doxygen-1.8.15-x86_64-1.txz: Upgraded.
d/kernel-headers-4.19.13-x86-1.txz: Upgraded.
k/kernel-source-4.19.13-noarch-1.txz: Upgraded.
FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER y -> n
l/libsecret-0.18.7-x86_64-1.txz: Upgraded.
n/wpa_supplicant-2.6-x86_64-6.txz: Upgraded.
It seems we're not the only ones with broken WPA2-Enterprise support
with wpa_supplicant-2.7, so we'll fix it the same way as everyone else -
by reverting to wpa_supplicant-2.6 for now.
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
testing/packages/wpa_supplicant-2.7-x86_64-2.txz: Upgraded.
Applied a patch from Gentoo to allow building CONFIG_IEEE80211X=y without
the experimental CONFIG_FILS=y option.
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 def3a105..724e6295 100644 --- a/README.initrd +++ b/README.initrd @@ -1,7 +1,7 @@ Slackware initrd mini HOWTO by Patrick Volkerding, volkerdi@slackware.com -Sat Dec 22 04:03:09 UTC 2018 +Sat Dec 29 22:37:42 UTC 2018 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 4.19.12 Linux kernel using the packages +upgrading to the generic 4.19.13 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-4.19.12-x86_64-1.txz - installpkg kernel-modules-4.19.12-x86_64-1.txz + installpkg kernel-generic-4.19.13-x86_64-1.txz + installpkg kernel-modules-4.19.13-x86_64-1.txz installpkg mkinitrd-1.4.11-x86_64-8.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 4.19.12 -m ext4 + mkinitrd -c -k 4.19.13 -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 4.19.12 +Here's another example: Build an initrd image using Linux 4.19.13 kernel modules for a system with an ext4 root partition on /dev/sdb3: - mkinitrd -c -k 4.19.12 -m ext4 -f ext4 -r /dev/sdb3 + mkinitrd -c -k 4.19.13 -m ext4 -f ext4 -r /dev/sdb3 4. Now that I've built an initrd, how do I use it? |