Then you probably won't notice that much increase in performance. But anyway you will learn a lot about linux (and your computer) in the process.

I think your file system error is because the kernel does not have in-kernel support for the filesystem you are using, and it cannot load the modules as it cannot read the filesystem where the modules are located. This can be solved with mkinitrd (if you know how to do, that is. Unfortunately I cannot help you on that one), but also by compiling in-kernel support for the filesystem for your /boot and base directories ( / /etc /usr/ and the other system directories). It is usually a good idea to use a well supported FS for these (ETX2 or EXT3).

dude...
u made the bzImage by compiling the kernel... rite..
u copied the file from arch/i386/boot to ur boot folder..
in the same way copy the system.map to ur boot folder
and then mkinitrd.........
this ll create the initrd for the new kernel...
u have to create a new initrd for the new bzImage u created ..

and can u tell me the command u used till now..

I agree with you that it is good to learn what's happening in our system.

I suppose you are right, I use Reiserfs, as it seems that I was given the impression that this is a faster FS (I guess I am wrong here), and even with the default kernel, it says something like can't find ext3 filesystem during bootup.

Thanks for the clarification.

As mentioned in the last page, this is what I typed and what the system prints out.

I still can't figure out the initrd part. But by leaving out the initrd part I am able to get to the commancd prompt, though I still can't start X.

I would post the error message later.

add a softlink in lib/modules to the directory where u compiled the kernel...