Hi,
This is what i get when I boot into my newly complied
RAMDISK: cramfs filesystem found at block 0
RAMDISK: image to big! (35512/8192 blocks)
RAMDISK: Coundn't find valid RAM disk image starting at 0.
VFS: Cannot open root-device "hda4" or unknown-block (0,0)
Please append a correct "root= " boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block (0,0)
libin@debian:~$ ls -l /boot/
total 42644
lrwxrwxrwx 1 root root 12 2005-12-01 14:04 config -> config-2.6.8
-rw-r--r-- 1 root root 44853 2005-05-16 13:16 config-2.4.27-2-386
-rw-r--r-- 1 root root 44888 2005-12-01 14:04 config-2.6.8
drwxr-xr-x 2 root root 4096 2005-12-01 14:37 grub
-rw-r--r-- 1 root root 3780608 2005-11-29 19:46 initrd.img-2.4.27-2-386
-rw-r--r-- 1 root root 36364288 2005-12-01 14:06 initrd.img-2.6.8
lrwxrwxrwx 1 root root 16 2005-12-01 14:04 System.map ->
System.map-2.6.8-rw-r--r-- 1 root root 542191 2005-05-16 14:08
System.map-2.4.27-2-386
-rw-r--r-- 1 root root 827171 2005-12-01 14:04 System.map-2.6.8
lrwxrwxrwx 1 root root 13 2005-12-01 14:04 vmlinuz -> vmlinuz-2.6.8
-rw-r--r-- 1 root root 816590 2005-05-16 14:08 vmlinuz-2.4.27-2-386
-rw-r--r-- 1 root root 1173395 2005-12-01 14:04 vmlinuz-2.6.8
These are the entries in /boot/grub/boot
title Debian GNU/Linux, kernel 2.6.8 (*new*)
root (hd0,3)
kernel /boot/vmlinuz-2.6.8 root=/dev/hda4 ro
initrd /boot/initrd.img-2.6.8
savedefault
boot
title Debian GNU/Linux, kernel 2.4.27-2-386 (boot properly)
root (hd0,3)
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda4 ro
initrd /boot/initrd.img-2.4.27-2-386
savedefault
boot
Regarding the "root= ", I got this error, the previous time I compiled,
so please help me find the correct "root= " option ( I am a newbie )
First, let me list you parttion table
debian:/home/libin# fdisk -l /dev/hda
Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 510 4096543+ b W95 FAT32
/dev/hda2 511 2806 18442620 f W95 Ext'd (LBA)
/dev/hda3 2807 3698 7164990 7 HPFS/NTFS
/dev/hda4 3699 4865 9373927+ 83 Linux
/dev/hda5 511 1275 6144831 b W95 FAT32
/dev/hda6 1276 1659 3084448+ b W95 FAT32
/dev/hda7 1660 2806 9213246 b W95 FAT32
Secondly, I saw something after i do a "make bzImage", notice the "root
device is (3,4)". What is this?
Root device is (3, 4)
Boot sector 512 bytes.
Setup is 4831 bytes.
System is 1140 kB
Kernel: arch/i386/boot/bzImage is ready
here is also one more root stuff i got. Also explain what is this. I
found this in /usr/share/initrd-tools/linuxrc
libin@debian:~$ cat /proc/sys/kernel/real-root-dev
772
Lastly, regarding the huge size, I didnt change much in the config of
the stock 2.6.8 kernel, just some stuff like kernel hacking features,
then the NTFS write support and Suspend options in Power Management (I
think that is it, AFAIR). Any reason why it did make aan image this huge?
Thanks in Advance
Libin Varghese
Email: libinv@xxxxxxxxx
*******************************************************************
Experts arose from their own urgent need to exist. - Murphy's laws
When the software itches you, scratch the Code. - Libin Varghese :D
*******************************************************************
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
