Please send me mail if you have any ideas about this
sad, sad story.
I have a LILO boot problem...
System: P133 Advanced/EV board, NCR 53C825 PCI SCSI ctrlr,
96 MB RAM, SCSI boot disk sda, SCSI cdrom. This system has
been running *only* Linux for about 2.5 years, through a
few new RH releases. It had 32 MB until just last week :-)
Recently I added 2 4GB IDE drives, which have been working
fine for about 3 weeks.
Then I added 2 32MB SIMMS to bring the memory complement
up to 96MB. But Linux only saw 64 MB. I left that
little problem for later...
Then I got brave and tried installing an Evergreen Spectra
333 CPU upgrade. Evergreen expects this upgrade to work
on my Intel motherboard.
The upgrade required replacement of the old AMI BIOS with
MR BIOS. Did that, and things seemed to go on working just
fine. Then I made the classic error of doing 2 things
at once :-(
I asked an Intel hw hacker about the memory issue and on his
advice I modified lilo.conf to add append="mem=96m" and also
shut down to install the new CPU. When I rebooted with the
new CPU I got as far as
and that was it.
I thought the Evergreen CPU didn't work. So...
put the old CPU back in and rebooted:
and that was it :-(
I tried booting RH install diskette in the thought that I
could just reinstall the OS on the boot disk. RH installer
can't find the cdrom device on the SCSI bus.
After a few iterations trying to get RH to see the CDROM,
the boot behaviour changed to
[something, probably some portion of LILO, goes by
too fast to read] 01 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 01 01 01 01 01 01....
you get the idea. The 01 text is just pouring onto the
screen at max scroll speed.
So... ummm... I don't have a rescue diskette... I just
upgraded to RH 5.1 recently and didn't get around to making
it yet [yes, this is very embarrassing].
Does anyone understand (a) what 01 01 01 01 means
(b) why I can't see my CDROM any more
(c) how I can ever get this crate booted again
I tried typing in "linux single root=/dev/sda1" at the
boot prompt on the RH install disk but that, obviously,
didn't work... it does mount the ext2 fs on the SCSI disk,
which gives me *hope* that the disk is still alive; but
I can't get a shell at all.
Is there a simple hardware diag package on floppy disk that
I could run to find out at least how much of my system
is still alive?
The NCR SCSI card is alive enough to report SCSI ID strings
during initialization. The rest of the system is alive
enough that MR BIOS shows correct settings for memory
size, CPU vendor and ID, etc. There are really only 3
I can no longer boot from my SCSI boot disk
I can no longer even SEE my SCSI CDROM from RH installer
so I can't reinstall
and one "operator error"
I don't have a rescue disk [stupid me!]
Is my LILO problem due to the append statement I added
or due to the death of my scsi controller, and how can
I tell? And is there any way to get this thing booted
without its own special custom rescue disk?
:De Clarke, Software Engineer UCO/Lick Observatory, UCSC:
:Web: www.ucolick.org | ones people hate, and the ones people don't use.--JO: