SEO

I'm trying to find a version of linux I can live with. I must have
tried a dozen in the last month. I have an old Slackware 8.1 cdrom, so
I installed that. BTW: I am dual-booting XP/Linux.

The installed seemed to go okay, until the end. I chose to have
slackware install lilo in the MBR. Slackware said it couldn't do that,
so I choose the floppy. Slackware is the only linux distro that gave
me a problem with this.

When I went to boot, I just got a lot of: "99 99 99 99 99 99 99" etc.
I have a 60 GB HDD. I got that warning about there being over 1024
cylinders.

No harm done. I did an fdisk /mbr to get back to where I was before
the attempted install. I backed up my disk first anyway.

Still, I was dissapointed, I was hoping for good install. I ordered
slackware 9.1 from ebay for practically nothing. Will I have the same
problem?

walterbyrd wrote:
> When I went to boot, I just got a lot of: "99 99 99 99 99 99 99" etc.
> I have a 60 GB HDD. I got that warning about there being over 1024
> cylinders.

lilo has a readme somewhere in /usr/doc/lilo-<version>, which should tell
you what this error means. (there's a list of error codes in there
somewhere.)

> Still, I was dissapointed, I was hoping for good install. I ordered
> slackware 9.1 from ebay for practically nothing. Will I have the same
> problem?

i know older lilo's have problems with large hard disks, but i'm not sure
if slack 8.1 has a lilo that old. i suspect, though, that 9.1 should give
you less trouble.

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

walterbyrd@iname.com wrote :

> When I went to boot, I just got a lot of: "99 99 99 99 99 99 99" etc.
> I have a 60 GB HDD. I got that warning about there being over 1024
> cylinders.

The warning probably doesn't have anything to do with your problem.

Usually the 99 99 error is because you've got an relict of an old LILO
from a previous Linux install present in your MBR and Slackware defaults
to install LILO in /dev/hda1 or wherever your Linux is located. Then the
old bootloader is looking for a kernel it cant find because it doesn't
exist anymore.

Boot from the floppy you created during your Slackware install and edit
/etc/lilo.conf and find a line like this:
boot = /dev/hda1 (or wherever you installed Slackware)
and change it to
boot = /dev/hda
and then run /sbin/lilo -v

Then reboot and hopefully Slackware is up running.
--
Thomas O.

This area is designed to become quite warm during normal operation.

"Thomas Overgaard" <thover@post2.tele.dk> wrote in message
news:dq61k1-bo1.ln1@news.inet.tele.dk...
>
> walterbyrd@iname.com wrote :
>
> > When I went to boot, I just got a lot of: "99 99 99 99 99 99 99" etc.
> > I have a 60 GB HDD. I got that warning about there being over 1024
> > cylinders.
>
> The warning probably doesn't have anything to do with your problem.
>
> Usually the 99 99 error is because you've got an relict of an old LILO
> from a previous Linux install present in your MBR and Slackware defaults
> to install LILO in /dev/hda1 or wherever your Linux is located. Then the
> old bootloader is looking for a kernel it cant find because it doesn't
> exist anymore.
>
> Boot from the floppy you created during your Slackware install and edit
> /etc/lilo.conf and find a line like this:
> boot = /dev/hda1 (or wherever you installed Slackware)
> and change it to
> boot = /dev/hda
> and then run /sbin/lilo -v
>
> Then reboot and hopefully Slackware is up running.

I'm still hanging onto lilo for my boot manager probably
due to the fact that I actually understand it, mostly, mostly!
I do read a lot of stuff saying grub is more capable of doing
more advanced things but I guess I don't need them since I
don't find myself seeking out grub. Anyone else sticking with
lilo? The config file for grub to me at least seems a little
too cryptic.

Scott Eberl wrote:
> don't find myself seeking out grub. Anyone else sticking with
> lilo?

nah, i use yaboot. ;-)

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

Scott Eberl wrote:

>. Anyone else sticking with
> lilo?

Yes!

Never had troubles with it, and being curious I run it through managing
few OS's, the DOS(es), Linux(es) and Windows98(s) variety on two drives
with hiding and unhiding partitions. It worked.
The practicality of this is questionable but we are in computers for
playing games, aren't we?

Have fun

Stanislaw
Slack user from Ulladulla.

Scott Eberl wrote :

> I'm still hanging onto lilo for my boot manager probably
> due to the fact that I actually understand it, mostly, mostly!

Same here. I'm stuck with lilo because i think i understand it,
mostly.

And I don't feel like doing experiments with something as vital as the
bootloader.
--
Thomas O.

This area is designed to become quite warm during normal operation.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Trim your posts.

In alt.os.linux.slackware, Scott Eberl dared to utter,
> Anyone else sticking with
> lilo?

I am. Other than yaboot for booting linux on a PPC machine, LILO's the
only boot loader I ever use. On some RedHat boxen I have to admin I am
using grub though, because that's what they were installed with. Really
though, I don't use grub because I never play with booting them.
They're all on UPS and pretty much never need to be rebooted.

In what little I've done with grub I liked it, but didn't find it
superior to LILO. grub has the nice ability to fail back to the boot
loader if something goes wrong, edit the boot parameters, and try
again. IME though, that's mostly worthless. Installing a bootloader is
a pretty trivial task these days. I never run into problems with LILO,
and as such I've never bothered replacing a single LILO MBR with grub.
I'm sure Pat still puts LILO in Slackware for the same reasons: LILO is
proven and there is no real need to replace it with something less
proven but more shiney.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAb235L3KiNGOqr6ERAvroAJ9loCAHgMzJIK8fUqK/G36tVH7ZCQCfQCnh
tlavmy8ddYYtnEw1q0c+2Cg=
=Kmzt
-----END PGP SIGNATURE-----

pgp trash troll delete

Guy Macon

Alan Hicks <alan@lizella.network> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Trim your posts.

> In alt.os.linux.slackware, Scott Eberl dared to utter,
> > Anyone else sticking with
> > lilo?

> I am. Other than yaboot for booting linux on a PPC machine, LILO's the
> only boot loader I ever use. On some RedHat boxen I have to admin I am
> using grub though, because that's what they were installed with. Really
> though, I don't use grub because I never play with booting them.
> They're all on UPS and pretty much never need to be rebooted.

> In what little I've done with grub I liked it, but didn't find it
> superior to LILO. grub has the nice ability to fail back to the boot
> loader if something goes wrong, edit the boot parameters, and try
> again. IME though, that's mostly worthless. Installing a bootloader is
> a pretty trivial task these days. I never run into problems with LILO,
> and as such I've never bothered replacing a single LILO MBR with grub.
> I'm sure Pat still puts LILO in Slackware for the same reasons: LILO is
> proven and there is no real need to replace it with something less
> proven but more shiney.

> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)

> iD8DBQFAb235L3KiNGOqr6ERAvroAJ9loCAHgMzJIK8fUqK/G36tVH7ZCQCfQCnh
> tlavmy8ddYYtnEw1q0c+2Cg=
> =Kmzt
> -----END PGP SIGNATURE-----

I repartitioned my hdd and started all over with Win2k on the first
partition, and slackware 9.1 on the second partition. Had the same
problem with lilo. I booted from my floppy, ran liloconfig, and it
works. The only problems I have now are 1) my scroll wheel on my mouse
won't work. 2) gnucash won't install.


Thomas Overgaard <thover@post2.tele.dk> wrote in message news:<dq61k1-bo1.ln1@news.inet.tele.dk>...
> walterbyrd@iname.com wrote :
>
> > When I went to boot, I just got a lot of: "99 99 99 99 99 99 99" etc.
> > I have a 60 GB HDD. I got that warning about there being over 1024
> > cylinders.
>
> The warning probably doesn't have anything to do with your problem.
>
> Usually the 99 99 error is because you've got an relict of an old LILO
> from a previous Linux install present in your MBR and Slackware defaults
> to install LILO in /dev/hda1 or wherever your Linux is located. Then the
> old bootloader is looking for a kernel it cant find because it doesn't
> exist anymore.
>
> Boot from the floppy you created during your Slackware install and edit
> /etc/lilo.conf and find a line like this:
> boot = /dev/hda1 (or wherever you installed Slackware)
> and change it to
> boot = /dev/hda
> and then run /sbin/lilo -v
>
> Then reboot and hopefully Slackware is up running.