Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I am a spanish speaker so excuse me for my bad english.

I am learning how to compile slackware kernel, so I have downloaded linux-3.2.7.tar.bz2 from http://www.kernel.org

Conditions:

  • Slackware installed on a vmware virtual machine.
  • Host o.s windows 7.
  • Slackware root filesystem: ext4
  • Slackware old kernel: 2.6.37.6
  • Slackware partitions: sda1 for swapping, sda2 for the kernel.

Basically I have followed the following steps:

#cd /usr/src
#tar jvxf linux-3.2.2.tar.bz2
#mv /usr/src/linux /usr/src/linux.old 
#ln -s /usr/src/linux-3.2.2 /usr/src/linux
#cd linux-3.2.2
#make mrproper
#cp /usr/src/linux-2.6.37.6/.config /usr/src/linux-3.2.2/.config
#make menuconfig

Load an alternate configuration file: .config INCLUDED (OPTION Y):

ATA/ATAPI/MFM/RLL support (DEPRECATED) (at Device drivers)
SCSI generic support (at Device drivers)
second extended support (at filesystems)
ext3 journaling (all)
ext4 (all)
ext4 (at filesystems)
JBD (ext4) debuggin support
JBD2 (ext4) debugging support
ReiserFS support
XFS filesystem support
"compile kernel with debug info" (at kernel hacking)

make dep
make clean
make bzImage
make modules
make modules_install
mv /boot/System.map /boot/System.map.old
cp /usr/src/linux/System.map /boot/System.map-3.2.2
ln -s /boot/System.map-3.2.2 /boot/System.map
mv /boot/vmlinuz /boot/vmlinuz.old
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-3.2.2
ln -s /boot/vmlinuz-3.2.2 /boot/vmlinuz
nano -w /etc/lilo.conf

ADDED THE FOLLOWING LINES:

image=/boot/vmlinuz.old
label = oldSlack
root = /dev/sda2
read-only

#lilo
#lilo -q
#shutdown -r now

When kernel 3.2.2 is booting, it stops showing the following:

VFS: Cannot open root device "802" or unknown-block(8,2)
Please append a correct "root=" boot option
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-bloc(8,2)

I hate this message because I have recompiled the kernel many times, and after hours of compilation I always get this message. :(

Can anyone help me to understand what I am doing bad or why is that error?

share|improve this question

1 Answer 1

up vote 0 down vote accepted

NOTE: I am not familiar with Linux 3.

I can guess right now, wrong path cause this problem while executing lilo command. Lilo installed mbr somewhere else.

1st: Stop recompiling your kernel because i think it even didn't start booting.

2nd: Check again path for boot files, and paths when executing lilo. Read about lilo -r switch

 system=sda2
 mbr=sda
 lilo -F -r /mnt/$system -b /dev/$mbr -C /etc/lilo.conf

Show output:

/sbin/sfdisk -d /dev/sda
ls -all /boot/
lilo
dmesg

I would suggest you to use L switch:

cp -L /usr/src/linux/System.map /boot/System.map-3.2.2
cp -L /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-3.2.2

Are you sure, Linux is boting?

share|improve this answer
    
Thanks for answering, this is what I have gotten: dl.dropbox.com/u/107789289/ERROR-PANIC.png I have done the same steps in a virtual box virtual machine and it has worked, now I am trying on vmware and it doesnt work –  adrian4aes Oct 7 '12 at 17:38

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.