I have recompiled like 3 times using different guides and the last time i used this guide

http://www.linuxquestions.org/questi...threadid=49035

it was similar to the others and I never got any errors the only problem I am having is when the computer boots it says

kernel panic - not syncing : VFS: unable to mount root FS on unknown-block (3, 5)

I remember a while back the first time i ever installed slack I had this issue because I cuz installed without picking a filesystem type (ext2,ext3,etc) It was my first install so yea.

I googled alot and all the things talk about ext3 and did i miss something and 2.6 only works with ext3 or is there some other round about things that you need for ext2.

The way I installed did the lilo for me and I did the first line for me and I added a second part so I could test two things at once.

heres the important part of my lilo conf:

image = /boot/vmlinuz
root = /dev/hda5
label = slack
read-only
image = /boot/vmlinuz-ide-2.4.29
root = /dev/hda5
label = slackold
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
image = /boot/vmlinuz.old
root = /dev/hda5
label = 2.6.10
read-only
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda2
label = windows
table = /dev/hda
# Windows bootable partition config ends

The second image with 2.4.29 works and the other 2 both give the same error seeing as one is a symlink to the other.

Here is my /boot:

root@tgo:~# ls -al /boot
total 15032
drwxr-xr-x 2 root root 4096 2005-07-13 19:34 ./
drwxr-xr-x 19 root root 4096 2005-07-13 18:17 ../
lrwxrwxrwx 1 root root 37 2005-05-24 10:14 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
-rw-r--r-- 1 root root 805590 2005-07-13 19:28 System.map
-rw-r--r-- 1 irc 1000 848420 2005-03-09 15:41 System.map-2.6.11-2
-rw-r--r-- 1 root root 1193693 2005-07-13 16:11 System.map-2.6.12
-rw-r--r-- 1 root root 805590 2005-01-22 15:07 System.map-generic-2.6.10
-rw-r--r-- 1 root root 607998 2005-01-20 22:24 System.map-ide-2.4.29
lrwxrwxrwx 1 root root 25 2005-07-13 18:16 System.old -> System.map-generic-2.6.10
-rw-r--r-- 1 root root 512 2005-05-24 10:39 boot.0300
-rw-r--r-- 1 root root 2537899 2005-07-13 16:11 bzImage-2.6.12
lrwxrwxrwx 1 root root 21 2005-07-13 18:16 config -> config-generic-2.6.10
-rw-r--r-- 1 irc 1000 51148 2005-03-09 15:23 config-2.6.11-2
-rw-r--r-- 1 root root 30763 2005-07-13 17:19 config-2.6.12
-rw-r--r-- 1 root root 50545 2005-01-22 15:07 config-generic-2.6.10
-rw-r--r-- 1 root root 41731 2005-01-20 22:24 config-ide-2.4.29
-rw-r--r-- 1 root root 5032 2004-05-21 02:19 diag1.img
-rw------- 1 root root 60416 2005-07-13 19:34 map
-rw-r--r-- 1 root root 1413268 2005-07-13 19:28 vmlinuz
-rw-r--r-- 1 irc 1000 1626047 2005-03-09 15:41 vmlinuz-2.6.11
-rw-r--r-- 1 root root 2537899 2005-07-13 16:52 vmlinuz-2.6.12
-rw-r--r-- 1 root root 1413281 2005-01-22 15:07 vmlinuz-generic-2.6.10
-rw-r--r-- 1 root root 1253760 2005-01-20 22:24 vmlinuz-ide-2.4.29
lrwxrwxrwx 1 root root 22 2005-07-13 18:16 vmlinuz.old -> vmlinuz-generic-2.6.10



As you can see I tried another version a while back but I got seriuos about it today and would like to figure this out.

2.6 supports ext2. there's nothing roundabout about it, you just have to select it in the filesystems section. i think it's the very first entry. what filesystem are you using?

I think it should be set right I did:

root@tgo:/usr/src/linux# less .config | grep EXT2
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set

so im thinking it should be ok?

What type is your root filesystem? ReiserFS? That's IIRC the default in Slackware.
If it's ReiserFS, you either
- compile ReiserFS support it into your kernel (that's what I did and it's done by Pat for kernel 2.4 but not for kernel 2.6)
- compile it as a module (you probably already did) and put it into an initrd (there's a file with a name like initrd.README with the 2.6.10 kernels from Slackware which explains how) AND you specify this initrd in your lilo.conf (something like initrd = /boot/initrd.gz)

I'd go for the first option, as you have some routine now in compiling kernels, although option 2 is faster to implement.