Help>>What happened to lilo???

staus · 08-11-2016, 09:51 PM

Just ran the current August 11 update with the 4.4.17 kernel, and now I'm using a rescue disk. Slackware will no longer boot up.
Looks like grub is being pushed, but I prefer lilo still.
Any ideas how to fix the lost lilo? Or just fix grub?

Richard Cranium · 08-11-2016, 10:04 PM

You're going to have to expand on what you had before the update and what you had after the update.

Lilo is still there in -current on August 11. I happen to use grub2 on my testbed machine, but I can clearly see that lilo is still there. So how did you apply the latest update?

cwizardone · 08-11-2016, 10:17 PM

Just installed the 4.4.17 kernel, edited the lilo.conf accordingly, ran lilo, and rebooted. So far everything is working perfectly.

staus · 08-11-2016, 10:33 PM

I screwed up by looking at the rescue disk /boot directory. I reran lilo as chroot, and still no boot up, even though the slackware /boot directory looks normal.

Richard Cranium · 08-11-2016, 11:19 PM

Did you do the chroot with the binds required for /sys, /proc, and /dev?

Bertical · 08-12-2016, 04:19 AM

I'm on a rescue disk also as UEFI boot seems broken. Ran eliloconfig after this mornings updates. Get to "Loading linux .. done" and system hangs.

Bertical · 08-12-2016, 05:26 AM

Update: It does eventually boot, after a delay of around 50 seconds.

hyperhead · 08-12-2016, 05:28 AM

Have a look at this, I had a similar problem last week.

http://www.linuxquestions.org/questi...em-4175586154/