>>>>> "Srinivas" == Srinivas G <[EMAIL PROTECTED]> writes:

    Srinivas> Dear All,

    Srinivas> I have question regarding building the linux kernel in
    Srinivas> FC2 and later distributions. I have almost always faced
    Srinivas> a problem with building linux kernels in 2.6.x range in
    Srinivas> FC2 or later distributions.

    Srinivas> When I try to build the kernel, the recompilation
    Srinivas> process which takes enough amount of time finishes very
    Srinivas> without any errors.

    Srinivas> Today, I was trying to build 2.6.11.12 kernel over FC2.

    Srinivas> Now, I am getting the following error:

    Srinivas> Uncompressing Linux... OK, booting the kernel ()
    Srinivas> RAMDISK: incomplete write (-28 !=32768) 4194304 Kernel
    Srinivas> panic - Not syncing: VFS: Unable to mount rootfs on
    Srinivas> unknown-block (0,0)

A quick google search reveals that the RAMDISK error  means

#define ENOSPC          28      /* No space left on device */
 
Did you do a mkinitrd for the new kernel you built? Also, i would
check if the drives / fs modules for the root device are built into
the kernel.

details on what are the steps you followed to rebuild the kernel and
the corresponding configs from the boot loader might be of help.

-balaji


-- 
http://balajin.net/blog

BOFH excuse #5:

static from plastic slide rules


------------------------ Yahoo! Groups Sponsor --------------------~--> 
Most low income homes are not online. Make a difference this holiday season!
http://us.click.yahoo.com/5UeCyC/BWHMAA/TtwFAA/0XFolB/TM
--------------------------------------------------------------------~-> 

-----------------------------------------------
Next Meeting as on our Website: http://ilughyd.org.in
----------------------------------------------- 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ilughyd/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to