Oh,thank goodness...it works!!!!!!!!! But in fact,I have to thank maze@cela.pl. :-) I follow his (or her) instruction,and examine my .config,then found that I forget to set RAMFS,initrd support...what a stupid man I am! Now it works well.
And,also thanks Jim Perrin.You are right.Usually,I will not rebuild a kernel on RedHat series and etc,but on Debian(Most of time I use Debian).But as you said,I "honestly feel some burning pull "to rebuild my own kernel.(I will not run it as a production server.)And if I failed,I will think "oh,there's something I don't know,I have to hurdle it!",or else I can't fall asleep.This feeling is terrible.
Aha,tonight I will have a sweet sleep. Thanks again.
--- Maciej �enczykowski maze@cela.pl:
Ok, so it looks like your kernel is missing one or more of the following: a) hard disk hardware device drivers b) partition drivers (very unlikely, only if non-MSDOS disklabels) c) file system drivers for the root filesystem
or possibly it's been setup for initrd operation and d) initrd support is lacking in the kernel e) the initrd file system (ramfs tmpfs or whatever) is lacking f) the initrd is screwed up...
What are the grub.conf entries for the kernel? does it reference an initrd? does it boot/how does it screw up if the initrd for this new kernel is commented out?
On Tue, 23 Aug 2005, cpp fire wrote:
Oh,sorry,I did not describe it clearly. When booting the system,it stops with these words: "kernel panic:VFS:Unable to mount root fs on unknown-block(0,0)"
Maybe it's what you want. Thank you!
___________________________________________________________ �Ż����G���䣭�й���һ���������ʼ�ɧ�ų������� http://cn.mail.yahoo.com