It could be a number of things that went horribly wrong.
And you may be better off asking the kernel gurus.
But my best guess would be corupted memory unloading.
{ I'm no kerel hacker }
try building the most vanilla kernel you can and try boot that.
If the problem still persists try downloading a cvs snapshot of
the 2.6 kernel and try again.
why are you so interested in the 2.6-test kernels, if I may ask?
--- "Matthew K. Lee" <[EMAIL PROTECTED]> wrote:
> Ok,
>
> I finally got the kernel to compile by removing stuff that it didn't
> like. But I can't get it to boot. I tried all the methods (initrd,
> bzImage, etc.) but no luck. Here's what it does...
>
> Loading 2.6.0-test2....................
> Uncompressing Linux... Ok, booting the kernel.
>
> [And then nothing....]
>
> When I rebooted back into my normal kernel, the file system load
> failed.
> There were a bunch of inode errors and empty inodes. The system
> dropped
> me into a shell, and told me to reboot (which I did.) The normal
> kernel
> came back up ok.
>
> What have I done wrong with my kernel compile?? Something seems
> dreadfully unhappy.
>
> Thanks,
>
> Matthew Lee
> [EMAIL PROTECTED]
>
>
=====
Ted Katseres
------------------------------------------------
------ C , C++, Java or Cobol -------
------ Linux doesn't care -------------
------------------------------------------------
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
