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 asked him about his own made generic kernels (which uses initrd) , and which he published in the Slackware-current tree.
It just means that if you put aside unnecessary sensationalism, then it will be easy to see that the (fixable) issue is with Slackware kernel/elilo, not with kernel/elilo.
Similar errors happened with Grub too and it is possible that will happen in the future so no point to spread FUD.
Haha, well, my system configuration is really simple, so I decided to just use my system's UEFI firmware to boot the generic kernel directly with EFI stub and passing the initrd= parameter to the kernel so that it will use the given initrd. My initrd.gz and the generic kernel are put inside my ESP so the UEFI firmware can load them properly without any issues, and luckily my UEFI firmware support efibootmgr's "--unicode" option for passing kernel parameters to the loaded kernel so no issues there either. And, since I rarely change my boot configuration, I can just set it once using efibootmgr (following the Arch Wiki guide here: https://wiki.archlinux.org/title/EFISTUB) and forget about it, just like what I've always done with ELILO. Updating the kernel and initrd is just a matter of replacing the relevant kernel and initrd files in the ESP without needing any modifications to the UEFI firmware boot configuration, again just like what I'm used to with ELILO.
The downside of this is that I can't change/append kernel parameters on the fly: I have to boot to the system first then run the appropriate efibootmgr commands to change them, since my UEFI firmware doesn't provide an option in its setup interface to add additional parameters to the target EFI binary. But, I rarely do this anyway, since I rarely have a problem with booting my system, so I usually just pressed enter immediately when I was using ELILO, haha.
Last edited by mumahendras3; 08-02-2022 at 11:53 AM.
Reason: Minor grammar edits
It just means that if you put aside unnecessary sensationalism, then it will be easy to see that the (fixable) issue is with Slackware kernel/elilo, not with kernel/elilo.
Similar errors happened with Grub too and it is possible that will happen in the future so no point to spread FUD.
i agree with you and i couldn't Have Said It Better.
Fri Aug 5 21:04:39 UTC 2022
a/dcron-4.5-x86_64-12.txz: Rebuilt.
Rebase the run-parts script on the latest version from Fedora's crontabs
package. Thanks to avian.
a/elilo-3.16-x86_64-13.txz: Rebuilt.
Patched to disable the Confidential Computing blob for SEV-SNP, which
fixes booting a 5.19 kernel with the EFI stub enabled. If you use elilo,
be sure to either run eliloconfig again or manually copy (and rename) the
proper elilo binary to your EFI System Partition.
Thanks to PiterPunk.
a/sysklogd-2.4.2-x86_64-1.txz: Upgraded.
ap/most-5.2.0-x86_64-1.txz: Upgraded.
d/cmake-3.24.0-x86_64-1.txz: Upgraded.
x/ibus-table-1.16.10-x86_64-1.txz: Upgraded.
extra/brltty/brltty-6.5-x86_64-1.txz: Upgraded.
extra/php80/php80-8.0.22-x86_64-1.txz: Upgraded.
Sun Aug 7 18:45:57 UTC 2022
a/aaa_libraries-15.1-x86_64-8.txz: Rebuilt.
Upgraded: libffi.so.8.1.0.
a/mcelog-185-x86_64-1.txz: Upgraded.
l/libffi-3.4.2-x86_64-2.txz: Rebuilt.
Recompiled with --disable-exec-static-tramp to work around issues with
gobject-introspection. Thanks to chrisVV.
x/ibus-table-1.16.11-x86_64-1.txz: Upgraded.
Unless if we really need that mkswap in rc.6 for something fancy, I would suggest removing it:
Code:
# diff -ruN /etc/rc.d/rc.6.orig /etc/rc.d/rc.6
--- /etc/rc.d/rc.6.orig 2022-08-01 21:06:37.000000000 +0200
+++ /etc/rc.d/rc.6 2022-08-08 03:05:01.674925676 +0200
@@ -294,12 +294,9 @@
echo "Locking LUKS crypt volume '${LUKS}':"
/sbin/cryptsetup luksClose ${LUKS}
elif echo $OPTS | grep -wq swap ; then
- # If any of the volumes was used as encrypted swap,
- # then run mkswap on the underlying device -
- # in case other Linux installations on this computer should use it:
- echo "Erasing encrypted swap '${LUKS}' and restoring normal swap on ${DEV}:"
- /sbin/cryptsetup remove ${LUKS}
- mkswap $DEV
+ # If any of the volumes were used as encrypted swap:
+ echo "Closing encrypted swap '${LUKS}' on ${DEV}:"
+ /sbin/cryptsetup close ${LUKS}
fi
done
fi
It appears that cryptsetup is now checking raw devices, even though manpage claims otherwise for plain mode - because it shows this warning on boot:
Quote:
WARNING: Device /dev/xyz already contains a 'swap' superblock signature.
WARNING!
========
Detected device signature(s) on /dev/xyz. Proceeding further may damage existing data.
Are you sure? (Type 'yes' in capital letters):
While we are at it, according to manpage create/remove are obsolete, so it is probably best to update rc.luks as well:
Code:
# diff -ruN /etc/rc.d/rc.luks.orig /etc/rc.d/rc.luks
--- /etc/rc.d/rc.luks.orig 2022-08-08 03:00:45.317524450 +0200
+++ /etc/rc.d/rc.luks 2022-08-08 03:01:08.068653704 +0200
@@ -83,7 +83,7 @@
# If any of the volumes is to be used as encrypted swap,
# then encrypt it using a random key and run mkswap:
echo "Creating encrypted swap volume '${LUKS}' on device '$DEV':"
- /sbin/cryptsetup --cipher=aes --key-file=/dev/urandom --key-size=256 create $LUKS $DEV
+ /sbin/cryptsetup --cipher=aes --key-file=/dev/urandom --key-size=256 open --type plain $DEV $LUKS
mkswap /dev/mapper/$LUKS
fi
done 3< <(grep -vE '^(#|$)' /etc/crypttab)
Unless if we really need that mkswap in rc.6 for something fancy, I would suggest removing it:
Code:
# diff -ruN /etc/rc.d/rc.6.orig /etc/rc.d/rc.6
--- /etc/rc.d/rc.6.orig 2022-08-01 21:06:37.000000000 +0200
+++ /etc/rc.d/rc.6 2022-08-08 03:05:01.674925676 +0200
@@ -294,12 +294,9 @@
echo "Locking LUKS crypt volume '${LUKS}':"
/sbin/cryptsetup luksClose ${LUKS}
elif echo $OPTS | grep -wq swap ; then
- # If any of the volumes was used as encrypted swap,
- # then run mkswap on the underlying device -
- # in case other Linux installations on this computer should use it:
- echo "Erasing encrypted swap '${LUKS}' and restoring normal swap on ${DEV}:"
- /sbin/cryptsetup remove ${LUKS}
- mkswap $DEV
+ # If any of the volumes were used as encrypted swap:
+ echo "Closing encrypted swap '${LUKS}' on ${DEV}:"
+ /sbin/cryptsetup close ${LUKS}
fi
done
fi
Reading the comment that I made bold which you suggest removing may give a hint as to why mkswap is called.
Mon Aug 8 23:29:31 UTC 2022
Hey folks, here's that graphics stack upgrade that you've been waiting for!
After looking at what drivers are currently shipped by other projects, I took
an axe to the driver list. Some of the removed drivers will still compile even
though they are abandoned, and some of the others are still getting git commits
(which allows *some* of them to compile). The removed stuff mostly looks
obsolete to me (we really can't support ancient hardware forever). But if you
think I've gone too far with any of these removals, please make or contribute
to a thread about it on LQ and I'll take any comments there into consideration.
a/kernel-firmware-20220808_e6857b6-noarch-1.txz: Upgraded.
ap/vim-9.0.0174-x86_64-1.txz: Upgraded.
l/gnu-efi-3.0.15-x86_64-1.txz: Upgraded.
n/libtirpc-1.3.3-x86_64-1.txz: Upgraded.
n/mutt-2.2.7-x86_64-1.txz: Upgraded.
x/egl-wayland-1.1.10-x86_64-1.txz: Upgraded.
x/libdrm-2.4.112-x86_64-1.txz: Upgraded.
x/libglvnd-1.4.0-x86_64-1.txz: Upgraded.
x/mesa-22.1.5-x86_64-1.txz: Upgraded.
Includes Mesa amber 21.3.9 DRI drivers, and mesa-demos-8.5.0.
Thanks to LuckyCyborg for posting some valuable hints on LQ.
x/xcb-proto-1.15.2-x86_64-1.txz: Upgraded.
x/xf86-input-acecad-1.5.0-x86_64-14.txz: Removed.
x/xf86-input-evdev-2.10.6-x86_64-4.txz: Rebuilt.
x/xf86-input-joystick-1.6.3-x86_64-5.txz: Removed.
x/xf86-input-keyboard-1.9.0-x86_64-5.txz: Removed.
x/xf86-input-libinput-1.2.1-x86_64-2.txz: Rebuilt.
x/xf86-input-mouse-1.9.3-x86_64-3.txz: Removed.
x/xf86-input-penmount-1.5.0-x86_64-14.txz: Removed.
x/xf86-input-synaptics-1.9.2-x86_64-1.txz: Upgraded.
x/xf86-input-vmmouse-13.1.0-x86_64-9.txz: Removed.
x/xf86-input-void-1.4.1-x86_64-3.txz: Removed.
x/xf86-input-wacom-1.0.0-x86_64-2.txz: Rebuilt.
x/xf86-video-amdgpu-22.0.0-x86_64-2.txz: Rebuilt.
x/xf86-video-apm-1.3.0-x86_64-3.txz: Removed.
x/xf86-video-ark-0.7.5-x86_64-13.txz: Removed.
x/xf86-video-ast-1.1.5-x86_64-7.txz: Removed.
x/xf86-video-ati-20220730_7a6a34af-x86_64-1.txz: Upgraded.
x/xf86-video-chips-1.4.0-x86_64-3.txz: Removed.
x/xf86-video-cirrus-1.5.3-x86_64-7.txz: Removed.
x/xf86-video-dummy-0.4.0-x86_64-2.txz: Rebuilt.
x/xf86-video-glint-1.2.9-x86_64-5.txz: Removed.
x/xf86-video-i128-1.4.0-x86_64-3.txz: Removed.
x/xf86-video-i740-1.4.0-x86_64-3.txz: Removed.
x/xf86-video-intel-20210115_31486f40-x86_64-1.txz: Upgraded.
x/xf86-video-mach64-6.9.6-x86_64-3.txz: Removed.
x/xf86-video-mga-2.0.0-x86_64-3.txz: Removed.
x/xf86-video-neomagic-1.3.0-x86_64-3.txz: Removed.
x/xf86-video-nouveau-20220125_29cc528-x86_64-1.txz: Upgraded.
x/xf86-video-nv-2.1.21-x86_64-5.txz: Removed.
x/xf86-video-openchrome-0.6.0-x86_64-6.txz: Rebuilt.
x/xf86-video-r128-6.12.0-x86_64-3.txz: Removed.
x/xf86-video-rendition-4.2.7-x86_64-3.txz: Removed.
x/xf86-video-s3-0.7.0-x86_64-3.txz: Removed.
x/xf86-video-s3virge-1.11.0-x86_64-3.txz: Removed.
x/xf86-video-savage-20190128_8579718-x86_64-3.txz: Removed.
x/xf86-video-siliconmotion-1.7.9-x86_64-5.txz: Removed.
x/xf86-video-sis-0.12.0-x86_64-3.txz: Removed.
x/xf86-video-sisusb-0.9.7-x86_64-5.txz: Removed.
x/xf86-video-tdfx-1.5.0-x86_64-3.txz: Removed.
x/xf86-video-tga-1.2.2-x86_64-13.txz: Removed.
x/xf86-video-trident-1.3.8-x86_64-5.txz: Removed.
x/xf86-video-tseng-1.2.5-x86_64-13.txz: Removed.
x/xf86-video-v4l-0.3.0-x86_64-3.txz: Removed.
x/xf86-video-vboxvideo-1.0.0-x86_64-5.txz: Removed.
x/xf86-video-vesa-2.5.0-x86_64-4.txz: Rebuilt.
x/xf86-video-vmware-20220621_ff5637a-x86_64-1.txz: Upgraded.
x/xf86-video-voodoo-1.2.5-x86_64-14.txz: Removed.
x/xorg-server-21.1.4-x86_64-1.txz: Upgraded.
x/xorg-server-xephyr-21.1.4-x86_64-1.txz: Upgraded.
x/xorg-server-xnest-21.1.4-x86_64-1.txz: Upgraded.
x/xorg-server-xvfb-21.1.4-x86_64-1.txz: Upgraded.
x/xorg-server-xwayland-22.1.3-x86_64-1.txz: Upgraded.
x/xorgproto-2022.1-x86_64-1.txz: Upgraded.
xap/geeqie-2.0-x86_64-1.txz: Upgraded.
xap/mozilla-firefox-103.0.2-x86_64-1.txz: Upgraded.
This is a bugfix release.
For more information, see:
https://www.mozilla.org/en-US/firefox/103.0.2/releasenotes/
xap/vim-gvim-9.0.0174-x86_64-1.txz: Upgraded.
extra/xf86-video-fbdev/xf86-video-fbdev-0.5.0-x86_64-2.txz: Rebuilt.
Just remember that slackpkg -onoff=off clean-system is your friend. That way you have to actively select what's being removed. Let's just say a friend of mine had to rebuild a hell of a lot of slackbuilds one night and learned her lesson.
Last edited by garpu; 08-08-2022 at 10:42 PM.
Reason: My friend messed up the order on the slackpkg command.
Just remember that slackpkg -onoff=off clean-system is your friend. That way you have to actively select what's being removed. Let's just say a friend of mine had to rebuild a hell of a lot of slackbuilds one night and learned her lesson.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
