I am sure this is my fault. I had never compiled a kernel before, and with
the world conspiring to keep me away from my lfs test box for more than 10
minutes at a time, it had taken quite a long time to get LFS done.
Granted, it was my first time. I took the kernel settings as they were,
compiled and installed. I then took the LFS book advice and tried to set
up some of the BLFS stuff installed like Lynx. I didn't get that far
though, because Firefox locked up again, forcing me to reboot. So I booted
into my FC4 (on hda1... LFS is on hdb1), set up the FC4 Grub to load LFS,
and then rebooted.

Voila, LFS! I was thrilled. The command prompt was screwed up, but that
was my fault. And it was this very fact that thrilled me. I knew why my
command prompt was screwed up (same thing double-typed), and I was happy.
It was screwed up because I screwed it up, and wow, was that cool. I
fiddled a little and then shutdown.

When I came back two days later and tried to boot, my Abit MB's LED POS
error panel says C1 and then shuts off. No boot. I look it up on the
internet and read all about that debacle with the bursting Taiwanese
capacitors, so I checked the MB. No problems. I did the component-reinsert
thing to be sure everything was properly attached. No go. Then, just to be
sure, I used jumpers to clear the CMOS, and what do you know, it boots,
but the boot up complains that the settings are funny, and my P4 1.5 is
being listed as an 800. After reloading default settings in BIOS and
setting the BIOS to recognize CPU speed as 1.5, it works just fine.
However, I have not yet rebooted LFS.

So can I assume that I missed something in the kernel compile that in some
code that rewrote my CMOS upon booting up LFS?

Please note that I am not trying to save this LFS install. I intend to
start over again from scratch anyway, since that was my maiden voyage. I
just did not expect the LFS to render my machine unbootable.


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to