Hello, On 9/22/05, Libin Varghese <libinv@xxxxxxxxx> wrote: > Hi, > After compiling the 2.6.0 kernel, copied the image to /boot and > renamed it to vmlinuz-2.6.0 . I add the kernel image in the grub > configuration file (grub.conf) as follows > > <grub.conf> > title Linux 2.6.0 > root (hd0, 8) > kernel /vmlinuz-2.6.0 ro root=LABEL=/ rhgb > </grub.conf> Why not compile 2.6.13.2 instead of 2.6.0 ? http://www.kernel.org/ And what environment are you using for compilation? (kernel 2.4 environment or 2.6 environment) By the way, can you find error messages before the following line? > VFS: cannot open root device "LABEL=/" or unknown-block (0,0) This line is the result of ignoring previous errors. So lines before this line are very important. "Fawad Lateef <fawadlateef@xxxxxxxxx>" wrote: > I always found that building 2.6.x kernel on 2.4.x kernel, EXT2 and > EXT3 (or which ever the type of your boot partition) must be set to Y > in the kernel configuration else kernel won't able to load the module > of file-system and hence unable to mount that ........... but the > error which i found in loading file-system module is : unable to load > ext3.o or AFAIR something like that .... So file-system setting to Y > in kernel config might not work in your case, but plzz do give it a > try if already not did so .... Yes, selecting built-in for ext2 and ext3 may help. In kernel 2.4, modules are "*.o" , while in kernel 2.6 modules are "*.ko" . I think this causes mkinitrd for 2.4 environment cannot found "*.ko" , resulting initrd.img without appropreate drivers. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
