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 am trying to preform a complete install and I am getting a kernel related error:
Code:
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh
Modules for kernel 4.4.14 aren't installed.
I know a generic kernel is suggested but is it needed and what, if anything, could go wrong with contending with the "huge" kernel. Some input would be appreciated.
...and perhaps next time pay attention to the text that flies by when running slackpkg upgrade-all, which might have alerted you to the kernel upgrade.
I am trying to preform a complete install and I am getting a kernel related error:
Code:
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh
Modules for kernel 4.4.14 aren't installed.
I know a generic kernel is suggested but is it needed and what, if anything, could go wrong with contending with the "huge" kernel. Some input would be appreciated.
If Richard Cranium's suggestion doesn't work:
I ran into the same problem when upgrading this week, except I was already on generic kernel 4.4.172. Here's how I got to the latest generic kernel.
After updgrading the kernel and running the same command you did above, my output was:
Code:
Modules for kernel 4.4.172 aren't installed.
So I searched and found a link that explained running a modified command like this (hinted at in the link at the bottom of this post, but I didn't understand what it was doing when I read it the first (few) time(s).)
mkinitrd -c -k 4.4.182 -f ext4 -r [ ... and a whole bunch of other stuff here in the middle ... ] /boot/initrd.gz
Which I ran as root. I got a bunch of "OK" messages, closing with
Code:
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
And so I was on 4.4.182 generic.
I don't use lilo, I have a multiboot system where Xubuntu's grub is the boss. I update booting an easy way by signing into Xubuntu and running sudo update-grub, instead of manually editing grub.
Of course, you can just use the huge kernel until you get comfortable upgrading to generic. I used huge until switching to generic with 4.4.172 just to learn how to do it, not because I saw any great advantage to generic.
I am trying to preform a complete install and I am getting a kernel related error:
[CODE]
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh
Modules for kernel 4.4.14 aren't installed.
.....
You've apparently got a 'partially' upgraded system where the huge kernel and supporting files like modules are different versions. Try doing your complete install so it's working and stable, then go here:
http://www.slackware.com/security/viewer.php?l=slackware-security&y=2019&m=slackware-security.1029019
and be sure to manually upgrade not just the huge and generic kernels but also the appropriate firmware, headers, modules, source. etc. so they're all on the same version. This should at least get you up-to-date to 4.4.182 (running huge). With that done, now go through the process to switch from huge to generic.
...and perhaps next time pay attention to the text that flies by when running slackpkg upgrade-all, which might have alerted you to the kernel upgrade.
Code:
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.182
Modules for kernel 4.4.182 aren't installed.
Mind you I am using the princeton mirror for current.
I ran into the same problem when upgrading this week, except I was already on generic kernel 4.4.172. Here's how I got to the latest generic kernel.
After updgrading the kernel and running the same command you did above, my output was:
Code:
Modules for kernel 4.4.172 aren't installed.
So I searched and found a link that explained running a modified command like this (hinted at in the link at the bottom of this post, but I didn't understand what it was doing when I read it the first (few) time(s).)
mkinitrd -c -k 4.4.182 -f ext4 -r [ ... and a whole bunch of other stuff here in the middle ... ] /boot/initrd.gz
Which I ran as root. I got a bunch of "OK" messages, closing with
Code:
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
And so I was on 4.4.182 generic.
I don't use lilo, I have a multiboot system where Xubuntu's grub is the boss. I update booting an easy way by signing into Xubuntu and running sudo update-grub, instead of manually editing grub.
Of course, you can just use the huge kernel until you get comfortable upgrading to generic. I used huge until switching to generic with 4.4.172 just to learn how to do it, not because I saw any great advantage to generic.
TKS
Code:
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh /boot/vmlinuz-generic-4.4.182
File /boot/vmlinuz-generic-4.4.182 not found!
You've apparently got a 'partially' upgraded system where the huge kernel and supporting files like modules are different versions. Try doing your complete install so it's working and stable, then go here: http://www.slackware.com/security/vi...curity.1029019
and be sure to manually upgrade not just the huge and generic kernels but also the appropriate firmware, headers, modules, source. etc. so they're all on the same version. This should at least get you up-to-date to 4.4.182 (running huge). With that done, now go through the process to switch from huge to generic.
Can someone please define to me what the hell a complete install infers? I keep hearing it and the slackdocuments really don't give a concrete logical definition of a complete install.
Can someone please define to me what the hell a complete install infers? I keep hearing it and the slackdocuments really don't give a concrete logical definition of a complete install.
It means every packages present in the slackware64 (or slackware on 32 bit) folder (on the installation disk); that is with the exception of the kdei -- that series doesn't need to be installed.
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.182
Modules for kernel 4.4.182 aren't installed.
Mind you I am using the princeton mirror for current.
The 4.4.x kernels are shipped with Slackware 14.2. In Slackware -current you will find 4.19 kernels.
Looks to me that you started off with installing Slackware 14.2 and then told slackpkg to use a package mirror meant for Slackware -current.
That is usually not going anywhere nice.
Your posts contain too little information to give good answers, but not all the answers given in this thread are going to help you if you are this new to Slackware.
I'd like you to start with a reboot of your computer, in the hope of course that it will reboot into your fresh Slackware, and then provide us with answers to the following questions cq. commands you need to run:
The 4.4.x kernels are shipped with Slackware 14.2. In Slackware -current you will find 4.19 kernels.
Looks to me that you started off with installing Slackware 14.2 and then told slackpkg to use a package mirror meant for Slackware -current.
That is usually not going anywhere nice.
Your posts contain too little information to give good answers, but not all the answers given in this thread are going to help you if you are this new to Slackware.
I'd like you to start with a reboot of your computer, in the hope of course that it will reboot into your fresh Slackware, and then provide us with answers to the following questions cq. commands you need to run:
Code:
uname -a
Code:
cat /etc/os-release
[CODE]ls -l /var/log/packages/kernel*
Code:
cat /etc/slackpkg/mirrors | grep -v "^ *#"
Code:
ls -l /boot/
Okay will do - I am somewhat familiar with slackware but heaven knows I am not new to Linux lol. I figured I downloaded 14.2 and used current - if that will be an issue in any internal manner I am willing to reinstall with the current ISO if you provide me the link. I will reboot now:
[reboot info] I just installed the latest current version from alien bob and ran; slackpkg update, install-new, upgrade-all and clean-system getting little results which I assume is good:
Code:
bash-5.0# slackpkg install-new
Looking for NEW packages to install. Please wait... DONE
No packages match the pattern for install. Try:
/usr/sbin/slackpkg upgrade|reinstall
bash-5.0# slackpkg upgrade-all
Checking local integrity... DONE
Looking for packages to upgrade. Please wait... DONE
No packages match the pattern for upgrade. Try:
/usr/sbin/slackpkg install|reinstall
bash-5.0# slackpkg clean-system
Looking for packages to remove. Please wait... DONE
No packages match the pattern for clean-system
bash-5.0# slackpkg update gpg
You have selected a mirror for Slackware -current in /etc/slackpkg/mirrors,
but Slackware version 14.2+ appears to be installed.
Slackware -current is the development (i.e. unstable) tree.
Is this really what you want?
To confirm your choice, press Y, else press N. Then, press Enter: y
Slackpkg will not show this warning again unless you remove the
/var/lib/slackpkg/current file.
Downloading https://mirrors.slackware.com/slackware/slackware64-current/GPG-KEY...
--2019-06-23 18:27:33-- https://mirrors.slackware.com/slackware/slackware64-current/GPG-KEY
Resolving mirrors.slackware.com (mirrors.slackware.com)... 207.223.116.213
Connecting to mirrors.slackware.com (mirrors.slackware.com)|207.223.116.213|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1572 (1.5K)
Saving to: ‘/tmp/slackpkg.yDu2yA/gpgkey’
/tmp/slackpkg.yDu2y 100%[===================>] 1.54K --.-KB/s in 0s
2019-06-23 18:27:34 (110 MB/s) - ‘/tmp/slackpkg.yDu2yA/gpgkey’ saved [1572/1572]
Slackware Linux Project's GPG key added
bash-5.0# slackpkg update
....
2019-06-23 18:28:14 (103 MB/s) - ‘/tmp/slackpkg.tLyixJ/testing-PACKAGES.TXT’ saved [727/727]
Formatting lists to slackpkg style...
Package List: using CHECKSUMS.md5 as source
Package descriptions
bash-5.0# slackpkg install-new
Looking for NEW packages to install. Please wait... DONE
No packages match the pattern for install. Try:
/usr/sbin/slackpkg upgrade|reinstall
bash-5.0# slackpkg upgrade-all
Checking local integrity... DONE
Looking for packages to upgrade. Please wait... DONE
No packages match the pattern for upgrade. Try:
/usr/sbin/slackpkg install|reinstall
bash-5.0# slackpkg clean-system
Looking for packages to remove. Please wait... DONE
No packages match the pattern for clean-system
bash-5.0#
I am assuming I am up to date and this version of slackware looks much more better and clean and works better I am to feel. Shall we call this solved?
Last edited by slackw1zard; 06-23-2019 at 05:33 PM.
Okay will do - I am somewhat familiar with slackware but heaven knows I am not new to Linux lol. I figured I downloaded 14.2 and used current - if that will be an issue in any internal manner I am willing to reinstall with the current ISO if you provide me the link. I will reboot now:
[reboot info]
Slackware current is the unreleased development branch of Slackware. When you use Slackware current you are by definition beta or alpha testing. Slackware 14.2 is the latest stable release of Slackware. If you want to use Slackware current you'll need to create your own iso or boot media from the Slackware current tree; or find and use something like AlienBob's Slackware current live disk.
Last edited by khronosschoty; 06-23-2019 at 04:07 PM.
Okay will do - I am somewhat familiar with slackware but heaven knows I am not new to Linux lol. I figured I downloaded 14.2 and used current - if that will be an issue in any internal manner I am willing to reinstall with the current ISO if you provide me the link.
See https://slackware.nl/slackware/slackware64-current-iso/
Note that this ISO is automatically (re-)generated when an update in Slackware-current occurs. No human involvement. Check the file "mkisofs-dvd.log" in that directory for any errors in generating the ISO.
Generally speaking, Slackware-current is stable, but that is not a guarantee. Things sometimes cause breakage in software which is not part of the distro itsrlf. So always check the ChangeLog.txt first before applying future updates. Possible breakages of 3rd party packages or software is usually announced in the ChangeLog.txt entry.
See https://slackware.nl/slackware/slackware64-current-iso/
Note that this ISO is automatically (re-)generated when an update in Slackware-current occurs. No human involvement. Check the file "mkisofs-dvd.log" in that directory for any errors in generating the ISO.
Generally speaking, Slackware-current is stable, but that is not a guarantee. Things sometimes cause breakage in software which is not part of the distro itsrlf. So always check the ChangeLog.txt first before applying future updates. Possible breakages of 3rd party packages or software is usually announced in the ChangeLog.txt entry.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.