[SOLVED] -Current Issue after upgrade-all

yakiza · 10-10-2019, 03:15 PM

Hello everyone,

I am running Slackware -current and after doing a slackpkg upgrade-all and rebooting I am not able to use my peripherals,I tried putting my ssd on my laptop it booted i was able to type but my ethernet card was not recognize, no interfaces where shown with ifconfig -a. I did not do any changes to the kernel or the gcc. When it boots and it requests me to login i get the following "Warning/error":

Quote:

This system is currently not set up to build kernel modules.
Please install the new Linux kernel "header" files matching the current kernel for adding new hardware support system.

linuxtinker · 10-10-2019, 11:11 PM

Did do a slackpkg install-new, and a slackpkg clean-system ?

willysr · 10-10-2019, 11:33 PM

did you make an initrd if you are using generic kernel?

rogan · 10-11-2019, 01:42 AM

If I understand correctly, you did a upgrade on one computer, then took out the drive and plugged it in your laptop.
The only reason for that not to work is because udevd writes "persistent rules" i.e. your network card will not work.
Just remove /etc/udev/rules.d/70-persistent-net.rules, reboot and your network should work fine (but see below).

Regarding your initial problems; Did you rerun lilo after the upgrade? If you didn't, all that's going to work is
what the "huge" kernel supports, so network is out of the question, usb connected stuff and a multitude of other things also.

In this case your easiest option is to just run lilo as root (provided you get to login) and shove that ssd back
in the original computer.

yakiza · 10-11-2019, 05:26 AM

Quote:

Originally Posted by linuxtinker

Did do a slackpkg install-new, and a slackpkg clean-system ?

No I did not do the above I just did upgrade-all.

Quote:

did you make an initrd if you are using generic kernel?

I did not do the above either, I didnt know i have to do this? And also not sure if I am using the generic when I installed i did the full recommended install What ever that installs

Quote:

If I understand correctly, you did a upgrade on one computer, then took out the drive and plugged it in your laptop.
The only reason for that not to work is because udevd writes "persistent rules" i.e. your network card will not work.
Just remove /etc/udev/rules.d/70-persistent-net.rules, reboot and your network should work fine (but see below).

Regarding your initial problems; Did you rerun lilo after the upgrade? If you didn't, all that's going to work is
what the "huge" kernel supports, so network is out of the question, usb connected stuff and a multitude of other things also.

I believe you misunderstood me a bit, I did the upgrade-all and when I rebooted my pc my peripherals such as keyboard were not working, because I did not had a second keyboard I put my ssd in my laptop to see(check/test) if the keyboard will work there and it did but unfortunately not my network card. This is the reason I've put it on my laptop.

On my PC when I boot i get to the login page the only issue is my keyboard doesnt work so I cant log in at all

rogan · 10-11-2019, 05:31 AM

did you run lilo after the upgrade all

yakiza · 10-11-2019, 05:40 AM

Quote:

Originally Posted by rogan

did you run lilo after the upgrade all

No, I didnt know I had to.
Also using elilo

yakiza · 10-11-2019, 05:52 AM

I have a bootable USB and I know I can format my root partition as I have a different partition for my /Home but id like to salvage my installed applications.
I did try and do $ Huge.s root="/dev/sda2" (sda2) is my slackware partition.
But not sure what to do after that, I suppose I can mount the partition chroot, but then what?

rogan · 10-11-2019, 06:29 AM

The general recommendation is to enable compatibility mode for UEFI when installing
and just use the normal boot sector for lilo. This (almost) always works fine and
all you have to do after a kernel upgrade is to rerun lilo.
I you're using elilo you must have done a UEFI install and I don't have much experience
with that, but if I remember correctly (it's been years now) you just copy the newly
installed kernel, overwriting the old, to the UEFI partition (probably mounted at /boot/UEFI
or some such) and reboot.
So plug your ssd in the laptop and try that. There's absolutely no need for a reinstallation.

gegechris99 · 10-11-2019, 06:34 AM

Quote:

Originally Posted by yakiza

But not sure what to do after that, I suppose I can mount the partition chroot, but then what?

If you are using elilo, you would need to do the following after a kernel upgrade and it's highly probable that there was a kernel upgrade when you upgraded -current:

Quote:

Upgrading your kernel

This task is now much easier than it used to be. All you really need to do is copy vmlinuz onto the ESP on top of the old kernel. No need to edit any configs or add any boot entries, unless you want to. Note that you can edit the config in place and ELILO will pick up the changes on next boot, no need to run any commands like with the old lilo.

It's recommended that you read the source article in Slackware Documentation Project:

source: https://docs.slackware.com/howtos:slackware_admin:linux_kernel_options_for_uefi_and_elilo?s[]=elilo

I use Grub2 on my UEFI-enabled machine so I cannot go further in helping you set up elilo correctly after a kernel upgrade.

colorpurple21859 · 10-11-2019, 07:15 AM

Your still using the old kernel that is in your /boot/efi/EFI/Slackware, with elilo, anytime the kernel is upgraded will need to copy the new kernel(/boot/vmlinuz) to /boot/efi/EFI/Slackware???/(not sure of the name of slackware directory. I use grub, so I don't have to worry about this after a kernel upgrade. Try running eliloconfig and reboot.

Alien Bob · 10-11-2019, 07:16 AM

Quote:

Originally Posted by yakiza

I have a bootable USB and I know I can format my root partition as I have a different partition for my /Home but id like to salvage my installed applications.
I did try and do $ Huge.s root="/dev/sda2" (sda2) is my slackware partition.
But not sure what to do after that, I suppose I can mount the partition chroot, but then what?

The welcome screen of the installer mentions this command to load your Slackware installation on the hard disk:

Code:

huge.s root=/dev/sda1 rdinit= ro

Note the "rdinit= ro" at the end, you do not mention this but you should addd it. Also note that there's a SPACE between "rdinit=" and "ro"!
This will either only work if your installation is not broken, but from what I read it is currently broken.

What I think happened here:
* You have configured a Slackware-current mirror in /etc/slackpkg/mirrors (you do not mention 32bit or 64bit but that did not break your installation)
* You ran "slackpkg update" followed by "slackpkg upgrade-all". This goes against the recommendations for users of slackware-current (you should have run "slackpkg install-new" inbetween to avoid breakage). But this too will probably not have broken your computer this time. Read https://docs.slackware.com/slackware:current and other documentation to understand the dangers of running -current as a newbie.
* Then you left your elilo configuration un-changed and rebooted.

What happened then:
* The computer booted according to what elilo told it. That is: to boot the older kernel which is present in /boot/efi/EFI/Slackware/ as installed by eliloconfig. This is a "huge" kernel which contains all the modules built-in that are needed to access the root partition (storage and USB hardware drivers, filesystem drivers) but the huge kernel does not contain drivers for keyboards (those are compiled as separate modules).
* The kernel finished booting and then loaded the root filesystem on your harddisk (your actual Slackware installation).
* The Slackware init system starts executing its rc scripts, which enables hardware probes (through UDEV) and then UDEV is supposed to load the kernel modules from /lib/modules/<kernel_version> to activate your computer's hardware like keyboard, network, display, mouse etc.
* UDEV looks in /lib/modules/<kernel_version> Where 'kernel_version' is the version of that older kernel in /boot/efi/EFI/Slackware but that directory no longer exists... it was replaced by the newer kernel-modules package as /lib/modules/<new_kernel_version> but that directory does not match the running kernel.
* The result is that your keyboard, mouse, network etc are not working after boot.

Solution: Fix your elilo configuration.

What you need to do:
* Boot from a Slackware installation medium.
* At the root prompt, enter the following commmands to 'chroot' into your Slackware installation:

Code:

mount /dev/sda1 /mnt
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
chroot /mnt /bin/bash

See also https://docs.slackware.com/howtos:sl...t_from_media?s[]=mount&s[]=bind&s[]=proc#chrooting
* Inside that chroot, fix your elilo. In your case (you never touched elilo after initial installation and you are not using a generic kernel), the easiest way is to simply run

Code:

eliloconfig

and follow the prompts.
* Then run "exit" to exit the chroot environment
* Finally reboot, all should be OK now.

garpu · 10-11-2019, 07:19 AM

I always have two working kernels in /boot/efi/EFI/Slackware. There's no reload--just copy the kernel, initrd.gz file, and make sure that there's an entry for it in elilo.conf. The syntax should be familiar, if you've edited lilo.conf.

Alien Bob · 10-11-2019, 11:00 AM

Quote:

Originally Posted by garpu

I always have two working kernels in /boot/efi/EFI/Slackware. There's no reload--just copy the kernel, initrd.gz file, and make sure that there's an entry for it in elilo.conf. The syntax should be familiar, if you've edited lilo.conf.

Considering the apparent experience levels of the OP, I tried to keep the instructions as simple as possible. But indeed, he should definitely consider switching to a generic kernel, generate an initrd, and always keep one working kernel in elilo.conf.

rogan · 10-12-2019, 04:06 AM

I think the bind mounting sequence in the tutorial should begin with mounting a root device at /mnt/
In his case : mount /dev/sda2 /mnt/