First boot into linux with the CDrom. Go to /usr/src/linux (if that is where your kernel is) and run 'make bzlilo'. Then check in Yast-System Config-Lilo Config that your kernel boots on /boot/vmlinuz. Then run '/sbin/lilo'. Reboot and see if it works. Jostein
===== Original Message From "Carley, Jason (Hong Kong)" <jason_carley@hk.ml.com> ===== Well I haven't yet gotten around to fixing my network problems. I am now trying to get my system to boot from either a disk or LILO on the hard drive.
It is an Abit KT-7 and the Drive is a slave (for historical reasons) behind a CDROM drive on the 1st IDE controller (not the RAID controllers which have a seperate windows installation on them).
I get the famous LI response from the bootloader. Now after looking this up in the docs and being told that it relates to disk geometry I am stumped. I am booting to a /boot all within the 1024 limit. The drive is properly detected and boots under other OSs. I get exactly the same problem whether I am using LILO on a boot disk or the hard drive. I even tried a reinstall using default partitioning in case something I did stuffed up the booting ability from the hard drive.
It boots fine from the Disk 1 CDROM.
Any help greatly appreciated.
Regards,
Jason.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Jostein Berntsen writes:
First boot into linux with the CDrom.
Go to /usr/src/linux (if that is where your kernel is) and run 'make bzlilo'. Then check in Yast-System Config-Lilo Config that your kernel boots on /boot/vmlinuz. Then run '/sbin/lilo'. Reboot and see if it works.
Jostein
I believe Win2k like WinNT has its own boot manager (it will always write over lilo, and likewise lilo will write over it). There is a program that will create an image that can booted from WinNT's boot manager and I assume there is one for Win2k by now. However if you are not able to let Win2K rewrite its boot manager I am not sure what you could do now but reinstall Win2k. It should not affect your linux install. Here is document which might help: ftp://metalab.unc.edu/pub/linux/docs/HOWTO/mini/Linux+NT-Loader
===== Original Message From "Carley, Jason (Hong Kong)" <jason_carley@hk.ml.com> ===== Well I haven't yet gotten around to fixing my network problems. I am now trying to get my system to boot from either a disk or LILO on the hard drive.
It is an Abit KT-7 and the Drive is a slave (for historical reasons) behind a CDROM drive on the 1st IDE controller (not the RAID controllers which have a seperate windows installation on them).
I get the famous LI response from the bootloader. Now after looking this up in the docs and being told that it relates to disk geometry I am stumped. I am booting to a /boot all within the 1024 limit. The drive is properly detected and boots under other OSs. I get exactly the same problem whether I am using LILO on a boot disk or the hard drive. I even tried a reinstall using default partitioning in case something I did stuffed up the booting ability from the hard drive.
It boots fine from the Disk 1 CDROM.
Any help greatly appreciated.
Regards,
Jason.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- Jesse Marlin Intec Telecom Systems Software Engineer Main 404-705-2800 Ph 404-705-2912 Fax 404-705-2805 Email jesse.marlin@intec-telecom-systems.com
participants (2)
-
Jesse Marlin -
Jostein Berntsen