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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,098
Rep:
"-current" will become Slackware-15. If you download and install an .iso of -current it says, when it boots up, "Welcome to Slackware64 15", or something along that line.
You should at least blacklist kernel-huge kernel-generic and kernel-modules if you are using slackpkg.
Never let slackpkg upgrade your kernels unless you're an absolute newbie and don't even know why having multiple kernels is a thing.
My system boots -huge kernels from efi, plus I also have failsafe kernels which I can always choose at boot.
Therefore I never had any problems in updating kernels with slackpkg. I also have a script which rebuilds nvidia drivers after an upgrade, which works (more or less) within one minor version series of kernels.
In principle, I can always build the kernel myself. But I'd still like to be able to test "the actual Slackware binaries".
My system boots -huge kernels from efi, plus I also have failsafe kernels which I can always choose at boot.
Therefore I never had any problems in updating kernels with slackpkg. I also have a script which rebuilds nvidia drivers after an upgrade, which works (more or less) within one minor version series of kernels.
In principle, I can always build the kernel myself. But I'd still like to be able to test "the actual Slackware binaries".
Whole disk is btrfs except for /boot/efi which is vfat.
(Fedora installer does not allow /boot on a btrfs but I accomplish that by moving initrd and vmlinuz to ESP)
Maybe it is not CONFIG_CRYPTO_CRC32C but CONFIG_LIBCRC32C should be set to m?
If it is really btrfs's problem why cannot I find any bug report about 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.