Switch to a generic kernel error.
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 |
Assuming you are running 14.2,
Did you update before trying to switch to the generic kernel? If so, the kernel version is 4.4.182. |
Quote:
I "updated" in that I ran: Code:
# slackpkg update gpg Code:
bash-4.3# uname -a |
There have been several kernel updates since the original release.
You would have been better served by completing the installation, rebooting, and then upgrading. IMO, anyways. Try... Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.182 |
Quote:
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. Code:
# /usr/share/mkinitrd/mkinitrd_command_generator.sh /boot/vmlinuz-generic-4.4.182 Code:
mkinitrd -c -k 4.4.182 -f ext4 -r [ ... and a whole bunch of other stuff here in the middle ... ] /boot/initrd.gz Code:
/boot/initrd.gz created. 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. If you use lilo, use the steps here https://docs.slackware.com/slackware...[]=generic Read the "Switch to a generic kernel" section. More than once if needed. 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 |
Quote:
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. |
Quote:
Code:
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.182 |
Quote:
Code:
bash-4.3# /usr/share/mkinitrd/mkinitrd_command_generator.sh /boot/vmlinuz-generic-4.4.182 |
Quote:
|
Quote:
|
Quote:
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:
ls -l /var/log/packages/glibc* Code:
ls -l /var/log/packages/gcc* Code:
cat /etc/slackpkg/mirrors | grep -v "^ *#" Code:
ls -l /boot/ |
Quote:
[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 |
Quote:
|
Quote:
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. |
Quote:
|
All times are GMT -5. The time now is 07:26 PM. |