LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-08-2018, 02:26 AM   #1
aihaike
Member
 
Registered: Feb 2006
Location: Paris, France
Distribution: Slackware, CentOS
Posts: 266

Rep: Reputation: 20
Question Unable to login after update


Dear all,

I'm running Slackware64 current and did an upgrade last night.
What I do is :
  1. slackokg check-updates
  2. slackpkg update
  3. slackpkg install-new
  4. 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.
 
Old 03-08-2018, 02:55 AM   #2
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,493

Rep: Reputation: 4336Reputation: 4336Reputation: 4336Reputation: 4336Reputation: 4336Reputation: 4336Reputation: 4336Reputation: 4336Reputation: 4336Reputation: 4336Reputation: 4336
Sounds like your kernel-modules package is missing. I'd check that first.
 
Old 03-08-2018, 03:13 AM   #3
aihaike
Member
 
Registered: Feb 2006
Location: Paris, France
Distribution: Slackware, CentOS
Posts: 266

Original Poster
Rep: Reputation: 20
Thanks, I'll give it a try.
 
Old 03-08-2018, 02:41 PM   #4
aihaike
Member
 
Registered: Feb 2006
Location: Paris, France
Distribution: Slackware, CentOS
Posts: 266

Original Poster
Rep: Reputation: 20
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 ?
 
Old 03-08-2018, 07:26 PM   #5
dTd
Member
 
Registered: Feb 2007
Location: CT, USA
Distribution: Slackware
Posts: 92

Rep: Reputation: 10
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
 
Old 03-08-2018, 08:43 PM   #6
dTd
Member
 
Registered: Feb 2007
Location: CT, USA
Distribution: Slackware
Posts: 92

Rep: Reputation: 10
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
 
Old 03-09-2018, 03:07 AM   #7
aihaike
Member
 
Registered: Feb 2006
Location: Paris, France
Distribution: Slackware, CentOS
Posts: 266

Original Poster
Rep: Reputation: 20
Thanks for your reply,

How do you reinstall the kernel only form the boot disk ?
 
Old 03-09-2018, 05:26 AM   #8
dTd
Member
 
Registered: Feb 2007
Location: CT, USA
Distribution: Slackware
Posts: 92

Rep: Reputation: 10
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.
 
Old 03-09-2018, 10:04 AM   #9
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 645
Blog Entries: 3

Rep: Reputation: 191Reputation: 191
Quote:
Originally Posted by aihaike View Post
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
 
1 members found this post helpful.
Old 03-09-2018, 01:32 PM   #10
th_r
LQ Newbie
 
Registered: May 2009
Posts: 12

Rep: Reputation: 0
hi

Check /boot/vmlinuz link
 
Old 03-09-2018, 10:08 PM   #11
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 5,073

Rep: Reputation: 2866Reputation: 2866Reputation: 2866Reputation: 2866Reputation: 2866Reputation: 2866Reputation: 2866Reputation: 2866Reputation: 2866Reputation: 2866Reputation: 2866
Quote:
Originally Posted by aihaike View Post
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!
 
1 members found this post helpful.
Old 03-10-2018, 02:50 AM   #12
aihaike
Member
 
Registered: Feb 2006
Location: Paris, France
Distribution: Slackware, CentOS
Posts: 266

Original Poster
Rep: Reputation: 20
Thumbs up

Thank you bassmadrigal,


That was the trick!
You just made my day.

Thank you all for your replies and your helps.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Unable to login to GUI after last update xorg.conf in ubuntu 12.04 sonicboy Ubuntu 6 06-08-2012 06:30 PM
Unable to login - Could not update ICEAuthority file sinnans Linux - Newbie 4 02-05-2010 10:08 PM
Unable to upgrade to ubuntu 7.10, update manager fails to update.... jonbvgood Linux - Software 2 02-05-2008 03:58 PM
Red Hat Update Agent freezing, unable to update (FC4) Malakye Fedora 1 12-09-2005 08:02 PM
Unable to logon on as non-root user after update as unable to set executable context pls198 Fedora 2 04-09-2004 11:41 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:52 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration