LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   12.0 Lilo Failed Install (http://www.linuxquestions.org/questions/slackware-14/12-0-lilo-failed-install-569749/)

tzman 07-16-2007 06:56 AM

12.0 Lilo Failed Install
 
Hmm, I have downloaded both the cd and dvd images with no errors and all checksum tests passed. Both images created without error (I have done this before) and both do boot. Now the weird part, both give the same error when lilo attempts to install, Lilo can not be written to disk, please use a boot floppy to...whatever.

What has changed, because I fell back to 11.0 and no issues, lilo installed and I could boot into Slack.

What has changed in lilo between 11.0 and 12.0 and how do we fix the issue?

Road_map 07-16-2007 07:00 AM

What is your partition table? Did you try "expert" option to install LILO?

tzman 07-16-2007 07:54 PM

Partition table is the same for Slackware 11.0

/dev/hda1 (set for swap)
/dev/hda2 (the rest of the drive)

Yes, this is very lazy, but has been very effective, especially when your drive is over 10 gb.

I have always used expert mode to install lilo.

One more item, I never write to the MBR.

Been using Slackware since almost the 1st release, 199x something, and this is one of the few times that I have seen the lilo install fail.

Road_map 07-17-2007 04:38 AM

Quote:

Originally Posted by tzman
Yes, this is very lazy, but has been very effective, especially when your drive is over 10 gb.

I have 2 harddisk of 80 GB, Slackware 12.0 is on third partition on primary master harddisk, Slackware 11.0 is on fourth partition on primary slave harddisk, but I have no problem installing LILO.

Quote:

Originally Posted by tzman
One more item, I never write to the MBR.

You should try to install LILO to the MBR.

tzman 07-18-2007 07:55 PM

That would be difficult since I also boot about 3 other flavors of linux with a boot manager (GAG, see freshmeat.net) that lives on the MBR and REALLY would not like to loose change that.

Like I said, has anyone found out if lilo has changed? I am asking because 11.0 and older ALL install to root partition without a problem, at least back to 9.0

Vincent_Vega 07-18-2007 08:46 PM

If you're a seasoned Slack user and run multiple distros, it might benefit you to take a serious look at grub. Hands down a better way to boot your multi-OS system.

tzman 07-19-2007 01:13 AM

Hmm, interesting...
 
How do you boot a linux partition/installation without a boot sector/loader installed/activated, pretty tricky.

Also note, Grub is not distributed with Slackware.

I have also posted the original issue to the Slackware team at www.slackware.com which basically is:

What has changed with lilo between Slackware versions 11.0 and 12.0?

MannyNix 07-19-2007 01:34 AM

grub-0.97-i486-3 in extra/grub

ftp://slackware.mirrors.tds.net/pub/slackware/slackware-12.0/extra/grub

or Slackbuild + source:
ftp://slackware.mirrors.tds.net/pub/slackware/slackware-12.0/extra/source/grub

tzman 07-19-2007 09:11 AM

OK.

How do you install a package when you can't boot up the system? Floppy boot is not available with 12.0, at least not directly, and I do not have a thumb drive to boot from.

All fine suggestions, but useless until you get your system to boot, at least so far.

titopoquito 07-19-2007 09:51 AM

Boot from the CD or DVD. There is an example how to boot up your install. I think it should be something like "hugesmp.s root=/dev/hda2 rdinit= ro" in your case if I remember right. This boots up your installed system although it takes the kernel from CD/DVD. Then you can (un)install and modify what you like.

tzman 07-20-2007 06:28 AM

Thanks, that may be the ticket, at least to get 12.0 working.

I am still wondering what changed in lilo to prevent it from installing during the system install. It is a very frustrating and unnecessary change.

Lockywolf 07-20-2007 06:31 AM

maybe you just set too long name for the system?

tzman 07-20-2007 01:38 PM

Same name used as on previous version installs. Like I said, never been an issue before.

gegechris99 07-20-2007 04:48 PM

Quote:

Originally Posted by tzman
Thanks, that may be the ticket, at least to get 12.0 working.

I am still wondering what changed in lilo to prevent it from installing during the system install. It is a very frustrating and unnecessary change.

For one thing, Slackware 12.0 comes with lilo 22.8 whereas Slackware 11.0 comes with lilo 22.7.1.

To know what changed between those versions, boot from CD and then read file:

/usr/doc/lilo-22.8/CHANGES

I'm not technical enough to understand the changelog but you may find what you're looking for.

Cheers

tzman 07-21-2007 09:34 AM

Thanks for the excellent suggestion.

I reviewed the changelogs and sure enough they changed lilo 2.8 to default install to the MBR. Betting they did not check the code to install elsewhere when chosen.

Thanks to all for your suggestions, will get 12.0 working yet.


All times are GMT -5. The time now is 11:50 AM.