RE: [newbie] People who get LI at boot up rather than LILO BOOT:
no I have had that problem and what it was is that you didn't have the complete download of the product check the image size and see if it is the same as the site size? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, February 25, 2000 7:04 AM To: [EMAIL PROTECTED] Subject: [newbie] People who get LI at bootup rather than LILO BOOT: This is almost certainly a problem with hard drive geometry. You should open up your PC and look at the label glued onto it, and make a note of the number of cyliners, heads and sectors. If you want a dual-boot machine, and the windows part already works OK, then you don't need to mess with the BIOS. If this is not the case, have a look at the BIOS, and try setting LBA as the hard disk addressing mode. If this still doesn't work, boot linux from a boot floppy, edit /etc/lilo.conf and add this line append = "hd=cyl,hds,sctrs" where cyl is the number of cylinders, hds is the number of heads and sctrs is the number of sectors printed on your disk. You might find the LILO mini HOWTO and the BOOTDISK HOWTO useful, Steve Flynn IBM MVS Operations Analyst
RE: [newbie] People who get LI at boot up rather than LILO BOOT:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Actually when the LI pops up it usually means that the /boot part of Linux is no install within the first 1024 cylinder of the hard drive. Take a look the docs and it will probably point you on how to fix this. I personally have a tripe boot system with a 25Gb hard drive and I created a boot disk instead of LILO due to the fact linux is installed on the last 10Gb which means LILO won't be able to boot to it. This is a normal problem, but can be fixed with some work and planning. At 10:45 AM 2/25/2000 -0800, you wrote: no I have had that problem and what it was is that you didn't have the complete download of the product check the image size and see if it is the same as the site size? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, February 25, 2000 7:04 AM To: [EMAIL PROTECTED] Subject: [newbie] People who get LI at bootup rather than LILO BOOT: This is almost certainly a problem with hard drive geometry. You should open up your PC and look at the label glued onto it, and make a note of the number of cyliners, heads and sectors. If you want a dual-boot machine, and the windows part already works OK, then you don't need to mess with the BIOS. If this is not the case, have a look at the BIOS, and try setting LBA as the hard disk addressing mode. If this still doesn't work, boot linux from a boot floppy, edit /etc/lilo.conf and add this line append = "hd=cyl,hds,sctrs" where cyl is the number of cylinders, hds is the number of heads and sctrs is the number of sectors printed on your disk. You might find the LILO mini HOWTO and the BOOTDISK HOWTO useful, Steve Flynn IBM MVS Operations Analyst -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.2 for non-commercial use http://www.pgp.com iQA/AwUBOLbf2D80MyC4YemsEQKYWACgoaMyv3yX90YePlnFoiLP0inPjq8AoISt zW6UJc5yoFwBpW2BLvpGN2OH =13oV -END PGP SIGNATURE-
Re: [newbie] People who get LI at boot up rather than LILO BOOT:
I'm still a bit puzzle about this "LI" freeze on bootup instead of LILO BOOT. This is on a lin/win box dual boot using lilo... It just happened for the second time and I can't figure out why. I had to boot with a floppy and reinstall LILO. But before it was done installing lilo, it stopped with an error of "Partition entry not found". To fix lilo.conf , I had to change label=windows to label=dos because my hda1 fat32 is labeled "dos". Here's where I'm confused: Why did lilo work with the old lilo.conf and then suddenly not work and freeze on bootup? And then, why did it work okay after I reinstalled lilo with the correct "label" entry in lilo.conf? What caused lilo to suddenly decide not to accept the "label" entry for hda1 in the old lilo.conf? Seve -Original Message- From: Kennedy D. Rivers [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Date: Friday, February 25, 2000 11:40 AM Subject: RE: [newbie] People who get LI at boot up rather than LILO BOOT: no I have had that problem and what it was is that you didn't have the complete download of the product check the image size and see if it is the same as the site size? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, February 25, 2000 7:04 AM To: [EMAIL PROTECTED] Subject: [newbie] People who get LI at bootup rather than LILO BOOT: This is almost certainly a problem with hard drive geometry. You should open up your PC and look at the label glued onto it, and make a note of the number of cyliners, heads and sectors. If you want a dual-boot machine, and the windows part already works OK, then you don't need to mess with the BIOS. If this is not the case, have a look at the BIOS, and try setting LBA as the hard disk addressing mode. If this still doesn't work, boot linux from a boot floppy, edit /etc/lilo.conf and add this line append = "hd=cyl,hds,sctrs" where cyl is the number of cylinders, hds is the number of heads and sctrs is the number of sectors printed on your disk. You might find the LILO mini HOWTO and the BOOTDISK HOWTO useful, Steve Flynn IBM MVS Operations Analyst
Re: [newbie] People who get LI at boot up rather than LILO BOOT:
I have had this happen a ouple of times, I guess after making some changes. All I had to do was bott from a floppy and run liloconf, reboot and everything was fine. Cheers john Montgomery
Re: [newbie] People who get LI at boot up rather than LILO BOOT:
Sevatio Octavio wrote: I'm still a bit puzzle about this "LI" freeze on bootup instead of LILO BOOT. This is on a lin/win box dual boot using lilo... the "LI" thing is in the doc's IIRC "man lilo" "man lilo.conf(ig?) "/usr/doc/lilo" I've had it several times when I fscked a Kernel compile or Installed a new distro. Just boot off a floppy rerun lilo (check etc/lilo.conf(ig)1st) -WBD
Re: [newbie] People who get LI at boot up rather than LILO BOOT:
fat file is gone and you need to low level format your hard drive and set headers again for the hard drive. Pmagic is great!! for this!
