[SOLVED] slackware 14.2 | upraded to new kernel and messed up the mkinitrd/lilo stuff.
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.
slackware 14.2 | upraded to new kernel and messed up the mkinitrd/lilo stuff.
Hey there everyone, it's been awhile, sorry to be annoying, but i started a new job and haven't been playing with my slackware box for awhile, anyhow i have forgot some steps because i upgraded my system with slackpkg -update then upgrade-all then i ran lilo and i forgot about the mkinitrd command, so i watched this video i remembered on youtube by la rathbone that explained it, and i don't know it must've been the wrong one, because i don't remember him messing it up, and i royaly flubbed it.
how to fix ? I have boot up stick so can get boot prompt, but how to get it all humming along again, I just wanna listen to music, it's so frustrating (((
It has been a quite while since I used slack. But, trust me, I ran into similar situation several times with Debian.
All I need to do is boot onto old kernel.
If any other package depends on new kernel, you are in trouble. In this case, go something like rescue mode, then install new kernel.
It is a kind of common mistake, it should not be hard to resolve.
hello, thans guys, tried these things, not chroot (not sure how to use that command)
but screen just goes black after post, might be a problem with the video drivers etc, i do recall actually now, seeing some error from running lilo i had never seen before saying there was issue with video drivers, could it be working i just can't see it because the monitor switches off ?
OK Scratch that, thankyou, it works!!!!!!! tried a different moniitor
(i have dual monitors and one isn't working due to Xorg not configured properly..)
Last edited by jhsdcsjdcvbdj; 09-22-2017 at 04:37 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.