LinuxQuestions.org
Visit Jeremy's Blog.
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 09-02-2018, 03:46 AM   #1
alpage2
LQ Newbie
 
Registered: Sep 2003
Location: North-East UK
Distribution: Mandrake 9.1
Posts: 15

Rep: Reputation: 0
153 kernel upgrade rendered 32 & 64 bit PCs unbootable


I had a 64-bit and a 32-bit PC - both quite old machines - ex-Vista and ex-WinXP - running nicely with the 144 kernel in the latest slackware, 14.2, and I had carried out the process to convert to the generic kernel, as described in the beginner's guide, here:

https://docs.slackware.com/slackware...generic_kernel

It worked with the 64-bit machine, but not the 32-bit, which I had to revert to the 'huge' kernel.

However, both were borked by the recent upgrade to the 153 kernel, in such a way as to make them unbootable. I am just looking for some pointers as to how I might go about recovering them, or will it simply be easier to do a reinstall of slackware 14.2. - and if so, will the latest installer downloads be now equipped with the 153 kernel?

Thanks in anticipation
Alan
 
Old 09-02-2018, 03:50 AM   #2
TommyC7
Member
 
Registered: Mar 2012
Distribution: Slackware, CentOS, OpenBSD, FreeBSD
Posts: 502

Rep: Reputation: Disabled
How did you upgrade them?

If you perhaps just forgot to run lilo, you can chroot into your system via the installation medium and run lilo after chrooting in.
 
Old 09-02-2018, 04:03 AM   #3
alpage2
LQ Newbie
 
Registered: Sep 2003
Location: North-East UK
Distribution: Mandrake 9.1
Posts: 15

Original Poster
Rep: Reputation: 0
Hi TommyC7

I upgraded by slackpkg update followed by slackpkg upgrade-all, and yes, I think I ran lilo in both cases, but thanks for the tip - I'll use chroot to make sure of that, and post back - possibly later today.

Thanks
Alan
 
Old 09-02-2018, 05:29 AM   #4
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,307
Blog Entries: 4

Rep: Reputation: Disabled
You didn't mention doing anything about the initrd, so here is a reminder: when you're upgrading a 'generic' kernel, you *must* make a new initrd before running lilo.
 
Old 09-02-2018, 05:46 AM   #5
alpage2
LQ Newbie
 
Registered: Sep 2003
Location: North-East UK
Distribution: Mandrake 9.1
Posts: 15

Original Poster
Rep: Reputation: 0
Many Thanks 55020

That could well be the problem for the 64-bit machine - I'll give that a try. Having never used the generic kernel before, I was not prepared for that.

Alan
 
  


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
Developers of CentOS- shameful absence of any testing, rendered systems unbootable v4r3l0v Linux - Desktop 34 12-28-2015 01:53 PM
removing raid 1 rendered server unbootable dime111 Linux - Software 7 09-09-2012 08:27 PM
upgrade problem - my box rendered unbootable fastestOS Slackware 6 12-17-2008 11:45 AM
Sid unbootable after kernel upgrade st1cky_rice Debian 7 12-18-2005 07:08 AM

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

All times are GMT -5. The time now is 12:33 PM.

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