[SOLVED] Unable to login after update

aihaike · 03-08-2018, 02:26 AM

Dear all,

I'm running Slackware64 current and did an upgrade last night.
What I do is :

slackokg check-updates
slackpkg update
slackpkg install-new
slackpkg upgrade-all

It usually works smoothly but now I can't use usb devices (keyboard, mouse) and it's not connected to my network.
At the end of the upgrading process I was asked to overwrite some files, and well I did.
I remember about rc.M, rc.inet1, rc.inet2.
I do not notice any error at boot time (runlevel 3).

My plan is to create a boot usb stick from an other current machine and replace the config files.
I'm not sure which one I should consider though and why this happened.
I need you guys to guide me.
Thanks.

volkerdi · 03-08-2018, 02:55 AM

Sounds like your kernel-modules package is missing. I'd check that first.

aihaike · 03-08-2018, 03:13 AM

Thanks, I'll give it a try.

aihaike · 03-08-2018, 02:41 PM

Volkerdi,

It didn't solve the issue.
I noticed /lib/modules contains the kernel 4.14.23, and that everything in /boot point to this kernel as well. However the machine still boot on kernel 4.14.18.
During the upgrade, it's been requesting to run lilo but not elilo.
Do you think that may be the cause of the problem?
How to run elilo from boot disk and have an effect on the desktop ?

dTd · 03-08-2018, 07:26 PM

Got this issue as well just now, upgraded all kernel* packages, mkinitrd and lilo as per usual, no modules can't login. Wondering how to now correct it

dTd · 03-08-2018, 08:43 PM

Well, what I did was burn the -current install iso, boot from it using the huge.s , then installed the huge kernel which I noticed uses a different symlink in /boot than just vmlinuz, seeing that I also installed the generic-smp and modules and added both entries to lilo.conf. Now both kernels seem to boot fine. Not exactly sure why it couldn't find the modules on the first attempt. This system has been on slackware current, updated as it updates since kernel 3.10.11. Updated with slackpkg for everything but kernels and this has been the first hitch in all that time. Good work guys and gals

aihaike · 03-09-2018, 03:07 AM

Thanks for your reply,

How do you reinstall the kernel only form the boot disk ?

dTd · 03-09-2018, 05:26 AM

When you boot from the install disk, there are instructions on how to you might boot your system in the very first lines of text that go something like:
Boot: huge.s root=/dev/sda1 initrd= ro

If /dev/sda1 is your /root partition, or /boot partition if that's separate, this will boot up your linux install using the huge kernel which has all the modules compiled inside so the modules package isn't required. Once you've done that, mount the cd and install packages as you like using installpkg. What seemed to be different on my system is that inside /boot vmlinuz used to point to the kernel whereas now it's vmlinuz-generic-smp which does, so you need to edit the pertinent section of lilo.conf to match before running lilo. I hope that's clear enough.

coralfang · 03-09-2018, 10:04 AM

Quote:

Originally Posted by aihaike

Thanks for your reply,

How do you reinstall the kernel only form the boot disk ?

Mount your disk somewhere and chroot into it;

Code:

# mount /dev/sda1 /mnt
# chroot /mnt /bin/bash
# slackpkg reinstall kernel*
# /sbin/lilo

Then reboot.

If you have lvm/luks, follow this:
https://docs.slackware.com/howtos:sl...oot_from_media

th_r · 03-09-2018, 01:32 PM

hi

Check /boot/vmlinuz link

bassmadrigal · 03-09-2018, 10:08 PM

Quote:

Originally Posted by aihaike

Volkerdi,

It didn't solve the issue.
I noticed /lib/modules contains the kernel 4.14.23, and that everything in /boot point to this kernel as well. However the machine still boot on kernel 4.14.18.
During the upgrade, it's been requesting to run lilo but not elilo.
Do you think that may be the cause of the problem?
How to run elilo from boot disk and have an effect on the desktop ?

If you're running a UEFI system, you'll need to re-run eliloconfig to add the new kernel to the EFI partition and allow you to boot from it. If you're running a BIOS based system (or using legacy booting), you'd need to run lilo to save the location of the new kernel to the MBR.

With a lilo system, follow coralfang's instructions. If this is a UEFI system using elilo, and since you're running into issues with peripherals with this, you'll need to boot off the install media, mount your main drive and your EFI partitions, bind mount a few system mounts, chroot into the main partition, and then run eliloconfig. Adjust the drive designators as necessary.

Code:

mount /dev/sda2 /mnt/
mount /dev/sda1 /mnt/EFI/
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
eliloconfig
exit
reboot

This should add your new kernel to the correct location in the EFI partition and then allow you to boot up with the new kernel.

Good luck!

aihaike · 03-10-2018, 02:50 AM

Thank you bassmadrigal,

That was the trick!
You just made my day.

Thank you all for your replies and your helps.