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 unthinkingly hit "return" after updating Slackware Current instead of typing "lilo". I have a backup kernel, so all I have to do to fix things is boot to the backup kernel, login as root, type "lilo", reboot, and carry on normally. _BUT_ I took advice to change to graphic login "because it's so much easier", and the cursor is now visible but unresponsive after boot so I cannot login. I'm looking for advice from someone who really knows the system -- suggestions on how to fix my system without reinstalling from scratch would be appreciated.
You can boot from the install DVD, mount your root partition in a chroot, and then run lilo. See this post for a step-by-step guide (in your case skip generating an initrd and and editing lilo.conf if you don't need to do that):
I have from time to time made that error, and the fix was not difficult. It should be readily possible to fix your system. What do you have to boot the computer: a) an 'emergency boot disk' on a USB flash-drive, made back at the time the OS was installed; or b) a USB flash-drive with "usbboot.img" properly installed; or c) something else? (Note: usbboot.img would come from a repository containing slackware-current/usb-and-pxe-installers.)
But when I re-booted after very specifically instructing the /etc/lilo.conf file to use the advised vmlinuz-huge-4.4.186 kernel, the reboot refused to accept keyboard input when the login: prompt appeared
Using the steps outlined in https://www.linuxquestions.org/quest...6/#post5558235, is it still possible to do a regressive install with a prior kernel (e.g., kernel-huge-4.4.172 or the original kernel-huge-4.4.12) and recover functionality without having to completely re-install Slackware 14.2 ?
_BUT_ I took advice to change to graphic login "because it's so much easier", and the cursor is now visible but unresponsive after boot so I cannot login. I'm looking for advice from someone who really knows the system -- suggestions on how to fix my system without reinstalling from scratch would be appreciated.
You mean you change init level to 4? Try Alt+Ctl+F1(or F2 to F6) and try login in text console.
If this it also broken, you can try add
Code:
init=/bin/bash
to lilo commandline (at boot time). However this boot system in very, VERY, crude mode. There are no startup scripts run, an you must everything do manually (mounting, set $PATH, etc). But if you are novice in Linux this maybe little to hard for you. If so better try "montagdude" advice.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.