Hi all:
After a long research I just finished installing my new 2.6.8 kernel. I
did it using the tutorial from this site:

http://www.digitalhermit.com/linux/K...ild-HOWTO.html

It seems very complete and fool proof. Everything went fine but when I
boot to the new lilo 2.6.8 entry it boots for a little whille and then I
get the following message:

Kernel panic: VFS: unable to mount root fs on unknown-block(3,7)

After that message the computer locks up. As far as I know I did not get
any errors during the installation. Luckily the old kernel still boots.
But I am still in a dire need to fix this kernel issue because I need to
tackle some video card and wireless card issues. So then I can move on
with my engineering school project.

I am using Slackware 10 on a sony vgn s150 notebook. Please let me know
what extra info you need and the command or file to get it from, I am a
total newbie.

Please advise.

Sonoman wrote:
> After that message the computer locks up. As far as I know I did not get
> any errors during the installation. Luckily the old kernel still boots.
> But I am still in a dire need to fix this kernel issue because I need to
> tackle some video card and wireless card issues. So then I can move on
> with my engineering school project.
>

The first two things that come to mind are:

1) Are you sure that you have the correct filesystem built into the
kernel. (not modules)

2.) double check your lilo, make sure it points to the correct partition.


--
Ezra Vandervort

Linux, Because rebooting is for adding new hardware ...

Ezra Vandervort wrote:
> Sonoman wrote:
>
>> After that message the computer locks up. As far as I know I did not
>> get any errors during the installation. Luckily the old kernel still
>> boots. But I am still in a dire need to fix this kernel issue because
>> I need to tackle some video card and wireless card issues. So then I
>> can move on with my engineering school project.
>>
>
> The first two things that come to mind are:
>
> 1) Are you sure that you have the correct filesystem built into the
> kernel. (not modules)

This may be the issue here, I am using reiserfs. How do I check? How do
I correct it?

>
> 2.) double check your lilo, make sure it points to the correct partition.

This should not be the problem I think because I am using the same
partition as before. Now I have two linux entries on lilo, both point to
the same partition /dev/hda7 which as far as I know is fine because the
older kernel boots fine to it.

>
>

I had the same problem with newly compiled 2.6.8.1 kernel, but had it
rectified after some modifications in the config.
As I don't know exactly which modif has done the trick, you'll find
below a quick paste of the "diff .config .config.old" result.
===============
< CONFIG_BLK_DEV_LOOP=y ---> CONFIG_BLK_DEV_LOOP=m
< CONFIG_BLK_DEV_RAM=y ---> CONFIG_BLK_DEV_RAM=m
< CONFIG_BLK_DEV_INITRD=y
< CONFIG_BLK_DEV_IDECD=y ---> CONFIG_BLK_DEV_IDECD=m
< CONFIG_BLK_DEV_IDEPNP=y ---> # CONFIG_BLK_DEV_IDEPNP is not set
< CONFIG_BLK_DEV_OFFBOARD=y ---> # CONFIG_BLK_DEV_OFFBOARD is not set
< CONFIG_BLK_DEV_HPT366=y ---> CONFIG_BLK_DEV_HPT366=m
< CONFIG_BLK_DEV_PIIX=y ---> CONFIG_BLK_DEV_PIIX=m
< CONFIG_EXT2_FS_XATTR=y ---> # CONFIG_EXT2_FS_XATTR is not set
< CONFIG_FS_MBCACHE=y
< CONFIG_MINIX_FS=y ---> # CONFIG_MINIX_FS is not set
< CONFIG_ROMFS_FS=m ---> # CONFIG_ROMFS_FS is not set
< CONFIG_AUTOFS_FS=y ---> # CONFIG_AUTOFS_FS is not set
< CONFIG_DEVFS_DEBUG=y ---> # CONFIG_DEVFS_DEBUG is not set
< CONFIG_DEVPTS_FS_XATTR=y ---> # CONFIG_DEVPTS_FS_XATTR is not set
< # CONFIG_DEVPTS_FS_SECURITY is not set
< CONFIG_SYSV_FS=y ---> # CONFIG_SYSV_FS is not set
< CONFIG_PARTITION_ADVANCED=y ---> # CONFIG_PARTITION_ADVANCED is not
set
===============