RE: [SLE] HELP (again :-/) ?hardware err???
-----Original Message----- From: Michael Bartosh [SMTP:bartosh@ocean.tamu.edu] Sent: Friday, March 10, 2000 4:55 AM At 9:05 PM -0600 3/2/00, Michael Bartosh wrote:
On boot, after all POSTs go ok, lilo is dying. I have gotten something saying CRC error. Otherwise, it does this:
LI-
and freezes.
This is a sudden predicament. I was rebooting and poof- it fails to come up. So I am htinking hardware error... but I can boot therescue CD just fine, and I can mount and manipulate the /, /usr and /var partitions perfectly.
Or- it did once. It is no longer...
Ideas?? Help-
Well, turns out I an make it boot off of some floppies. Like a freesh Suse one. Which wouldn't be bad for a temporary solution- after I boot into the installer I can chose 'bboot installed system, and most everything works-- except my 3com 509 for some reason (works ine in my notmal srtup) and that kernel doesn't have any IPMasq on.
So I tried to be smart.
dd if=/dev/fdo of=/tmp/file.img (switch disks) dd if=/tmp/file.img of=/dev/fd0
mount floppy, replace the old ram disk w/ the one I usually boot from and the kernel w/ my own home brewed (that works fine afaik) but poof- reboot, and it's
LI
again
IIRC LI is an indication that lilo cannot find the kernel image. If I understand lilo correctly, it looks for the kernel at a very specific position on the disk, if it has changed, lilo gets lost. (Or I could be wrong and its a different problem, no matter). Try booting your system as you describe with the install floppys and use Yast to create a boot floppy. See if that floppy will boot. I seem to remember that you can also recompile your kernel using # make bzdisk (instead of bzImage or bzlilo) I think that's right, double check the docs to be sure as I don't have access to a linux box right now (again I could be wrong). If you can get to a bootable system floppy, you're halfway there. Good luck, Tim -- 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/Doku/FAQ/
At 9:05 PM -0600 3/2/00, Michael Bartosh wrote:
On boot, after all POSTs go ok, lilo is dying. I have gotten something saying CRC error. Otherwise, it does this:
LI-
and freezes.
This is a sudden predicament. I was rebooting and poof- it fails to come up. So I am htinking hardware error... but I can boot therescue CD just fine, and I can mount and manipulate the /, /usr and /var partitions perfectly.
Or- it did once. It is no longer...
Ideas?? Help-
Well, turns out I an make it boot off of some floppies. Like a freesh Suse one. Which wouldn't be bad for a temporary solution- after I boot into the installer I can chose 'bboot installed system, and most everything works-- except my 3com 509 for some reason (works ine in my notmal srtup) and that kernel doesn't have any IPMasq on.
So I tried to be smart.
dd if=/dev/fdo of=/tmp/file.img (switch disks) dd if=/tmp/file.img of=/dev/fd0
mount floppy, replace the old ram disk w/ the one I usually boot from and the kernel w/ my own home brewed (that works fine afaik) but poof- reboot, and it's
LI
again
Hmmm. I don't seem to have got this message through the list yet... Anyway, when you manage to boot up off a floppy, check your /etc/lilo.conf file to make sure it's correct and run /sbin/lilo to reinstall LILO. (Note that if you are mounting your hard drive through the floppy, then it might turn out as /mnt/etc/lilo.conf or /mnt/sbin/lilo...) If you can rerun the LILO command that will hopefully get things fixed ;-) Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- 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/Doku/FAQ/
I reran lilo to no avail, and used Yast when the command manually did not work. lilo.conf matches previous archived versions. The current pattern is that installer kernels seem to boot, and non installer kernels or even LILO does not. ie even trying to boot off ot the floppy resulting from make bzimage fails. -mab On Fri, 10 Mar 2000, Chris Reeves wrote:
At 9:05 PM -0600 3/2/00, Michael Bartosh wrote:
On boot, after all POSTs go ok, lilo is dying. I have gotten something saying CRC error. Otherwise, it does this:
LI-
and freezes.
This is a sudden predicament. I was rebooting and poof- it fails to come up. So I am htinking hardware error... but I can boot therescue CD just fine, and I can mount and manipulate the /, /usr and /var partitions perfectly.
Or- it did once. It is no longer...
Ideas?? Help-
Well, turns out I an make it boot off of some floppies. Like a freesh Suse one. Which wouldn't be bad for a temporary solution- after I boot into the installer I can chose 'bboot installed system, and most everything works-- except my 3com 509 for some reason (works ine in my notmal srtup) and that kernel doesn't have any IPMasq on.
So I tried to be smart.
dd if=/dev/fdo of=/tmp/file.img (switch disks) dd if=/tmp/file.img of=/dev/fd0
mount floppy, replace the old ram disk w/ the one I usually boot from and the kernel w/ my own home brewed (that works fine afaik) but poof- reboot, and it's
LI
again
Hmmm. I don't seem to have got this message through the list yet...
Anyway, when you manage to boot up off a floppy, check your /etc/lilo.conf file to make sure it's correct and run /sbin/lilo to reinstall LILO. (Note that if you are mounting your hard drive through the floppy, then it might turn out as /mnt/etc/lilo.conf or /mnt/sbin/lilo...)
If you can rerun the LILO command that will hopefully get things fixed ;-)
Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
-- 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/Doku/FAQ/
participants (3)
-
bartosh＠ocean.tamu.edu -
chris.reeves＠iname.com -
tduggan＠dekaresearch.com