i have searched for this error and have found a lot but most of them state that the kernel was compiled and reiserfs support was not included (or some other fs), this is not my case

i installed 10.2 and used the 2.6.13 kernel, source, headers, modules and alsa-driver. everything went as planned

installed slapt-get and updated everything, again, no issues. pc reboots fine

changed my slapt-getrc to point to current, did a --dist-upgrade, everything went fine, reboot, no issues

here is where the problem lies and i am sure it is my fault but anyway...

i downloaded kernel-generic, -source, -headers, -modules (all 2.6.16.9) and alsa-driver from slackware.mirrors.tds.net/pub/slackware/slackware-current/testing/packages/linux-2.6.16.9/

then i removed the installed headers, source, modules, and alsa-driver. it would not let me remove kernel-generic or kernel-ide (said package does not exist) and then i installed all the packages listed above. ran lilo and just for good measure ran /sbin/lilo and rebooted

only one linux was listed in lilo menu and it started to boot but got the error
kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(3,2)

i have not compiled anything myself and i did have reiserfs support when i installed 10.2.
i have booted with disc 1 and at the prompt loaded bare.i root=/dev/hda2 noinitrd ro
but where to go from here?

The last couple of 2.6 kernels in slackware-current/testing do not include support for ext3 and reiser filesystems - instead these are built as modules and present in the kernel-modules package.

You will need to create an intrd (I hope you can still boot your old kernel?):

Add this line to the 2.6.16.9 section of /etc/lilo.conf
and re-run lilo:
Eric

well, i cant boot my old kernel, but i can get to the install using disc 1

i made initrd but where in lilo does the line go?

mine says
image = /boot/vmlinuz
root = /dev/hda2
label = Linux
read-only

nevermind, got it, put it after image = /boot/vmlinuz

thank you very much for your help. i hope now i can help the next guy that comes along

now off to fix my new nvidia error message

Make sure you use the latest Nvidia installer with that new kernel!

Eric

actually the error was while it was uninstalling, something about libglx.so not being a symbolic link. i hit ok and the install finished. i used the most recent driver from nvidia and it worked. im replying now in my new up to date CURRENT slackware install! woohoo!

thanks again Alien Bob! you da man!