Reboot after "BIOS Data Check Successful" using 2.6 kernel
Ok, I've been Googling for two hours now and I've come up with scratch. Here's the situation:
I had a Linux-based firewall running kernel v2.6.9. Something odd happened to it; the CPU and hard drive blew up almost simultaneously. After a little hardware fighting, I bought a new motherboard and CPU from Newegg (a tiny little low-power 800MHz deal) and pulled a hard drive out of the Bin (which I then ran through badblocks). All of the hardware checks out and everything is running smoothly under the default kernel installed by Slackware 10.0.
So then I downloaded the Linux v18.104.22.168 kernel sources and compiled a kernel from those, since my firewall uses a number of things which aren't exactly available by default. Now, when I reboot, the screen displays
I've tried the following things, all gleaned from searching on this forum or on Google:
* Disabled ACPI in the BIOS
* Started kernel with option "acpi=off"
* Reinstalled LILO and double-checked my lilo.conf
* Rebuilt the kernel, in the event that some damage was done somewhere
* Double-checked the System.map file generated by the kernel compile
None of this did any good. Also, I don't have a DVI port, which is what half of the posts out there seem to be about.
From what I've learned, it seems that this sort of problem appears whenever someone has a problem very early in the Linux bootup process. However, this error has been reported many, many times against machines which were recently upgraded to various versions of kernel 2.6.
My machine runs fine on kernel 2.4.26. Before the old hard drive and CPU gave up on me, it worked fine with 2.6.9. I'm currently downloading 2.6.10 to see if that produces a different result, but I get the feeling it'll wind up rebooting on the same message.
Does anyone have any suggestions? I'll entertain all of them, as I'm completely stumped. The contents of any of the files on the drive are available upon request.
My lilo.conf reads:
It took a bit of doing, but I managed to fix this without intervention from the forum. It turns out that these symptoms can be created by compiling the Linux kernel for an incompatible processor family. For example, in my case, I had compiled the kernel for the VIA C3-2 processor family when in fact this board has a VIA V3-1 in it. This probably wouldn't have been a problem if I were more experienced with compiling Linux for different types of machines.
Cheers, all... hopefully someone else will search this result and benefit from it. ;)
yes, i do
|All times are GMT -5. The time now is 07:21 PM.|