hi

I installed the 2.6.10 generic from the testing on the cd. I created a symlink from /boot/vmlinuz-generic-2.6.10 to /usr/src/linux-2.6.10 and edited lilo to include this.

in my excitement i forgot to update lilo and rebooted, I can now not access it as I am getting a kernel panic error.

my 2nd slackware cd doesn't seem to act as a boot disk. I have a knopix disk, how can I get access again fix lilo and look for kernel problem.

all i did t install 2.6 was
Then did upgradepkg for alsa

The first cd of slack 10.1 or the 2nd cd of slack 10.0 will work.
do this.

Boot up slackware 10.1 with disk 1, and then login as root
mkdir /mnt/slack
mount /dev/hdaX /mnt/slack #replacing /dev/hdaX with the actual partition
chroot /mnt/slack
/sbin/lilo

reboot

Mount your Slack partition with write prviledges.
Then chroot into where you have it mounted in Knoppix.

Next you should just need to run 'lilo' from the command line.

# su
# mount -o remount,rw /mnt/<partitionname>
# chroot /mnt/<partitionname>
# lilo

Why did you do this? You created a symlink from a kernel image to a directory.
Remove the symlink, and remove the entry from /etc/lilo.conf, and make an entry such as:
where root = /dev/hda2 corresponds to your root partition, and not mine.

Quote:

in my excitement i forgot to update lilo and rebooted, I can now not access it as I am getting a kernel panic error. my 2nd slackware cd doesn't seem to act as a boot disk.

Boot with CD1 and at the boot: prompt type "bare.i root=/dev/hda2 noinitrd ro" and, again, substitute your root partition for hda2, which is mine on this comp I'm building. Then su to root and run "lilo" and you're good. That's after you fix that symlink error and edit /etc/lilo.conf.

Quote:

Then did upgradepkg for alsa

Hope that works better for you than it does for me. The 2 times I used those packages to upgrade ALSA I lost sound.

How can I remove the symlink, most post seem to be reomoving the package with "rm" rather than removing a symlink.

Follow Xian's instructions, then just navigate to /boot and remove the symlink using 'rm' (you may want to fix all of the symlinks before running lilo though).

Also, as good practice, always leave an entry for a working kernel in /etc/lilo.conf and don't uninstall the old kernel immediately, in case the new one doesn't work out.

In your first post you stated:
To see that symlink issue:
That output is from a default installation of Slackware -current,
where I've not compiled a new kernel. I have tried using Pat's
kernels (i.e. ./slackware-current/testing/packages/linux-2.6.12.3/ )
but they cause problems for me. For one, they clobbered the
original kernel sources in /usr/src/ so that I can't recompile the
Nvidia drivers without pointing the driver to the new source ...
The new kernel sources should not be in /usr/src per
Linus Torvalds email dated Thu Jul 27 2000 and his README file
that comes with the kernel sources.
Second, that kernel didn't have proper support for USB devices;
and I prefer to roll my own kernels anyway, so that I can remove
modules for hardware that I don't have.

When you get that /boot/ output, look at the symlink you created.
It will be the ouput on the other side of the -> and I would assume
from your first post that it would look something like this:
I don't know what made you decide to do that, but it's just wrong.
If you were following a kernel build guide, throw it away and use
Kwan Lowe's Kernel Build HOW-TO
or Jesper Juhl's quick 2.6 guide for Slackware
but note in Juhl's guide do not create the symlink for System.map.

If you need help or just confirmation, please post the output of:
$ ls -al /boot/
$ cat /etc/lilo.conf

So would you use.

rm /boot/vmlinuz-generic-2.6.10 /usr/src/linux-2.6.10

or

rm -ls /boot/vmlinuz-generic-2.6.10 /usr/src/linux-2.6.10

I don't know how you linked it...you didn't post the output I asked for.
Also, you might want to post "ls -al /usr/src/linux/"

OK will do, at work at the moment.

Ok everything is back how it should be . I reinstalled. I installed the 2.6.10 from testing and edited lilo as above on reboot 2.6.10 failed due to kernel panic, the worse part is that 2.4 also did not work due to kernel panic.

The error for both was
Kernel panic - not syncing : VFS : unable to mount root fs on unknown-block

I went in as sugggested before
mkdir /mnt/slack
mount /dev/hda6 /mnt/slack
chroot /mnt/slack

I did /sbin/lilo I get an error this time that says
Warning 'proc/partitions' does not exist disk scan bypassed.

I am not sure if that is the error bringing it down. As a side I cannot get nano to work as the editor i tried "source /etc/profile" to let me use it but alas only vim which I can't get much done with.

That's ok, as long as it says "Added Linux (or whatever you named it)"

It has added the new slack-2.6.10 and I still have the 2.4 kernel called slacware, but bothe are having the kernel panic error.

Fact is, that the kernel(s) that you are trying to boot have no support for ReiserFS (that's your file-systemtype or not ?)

Does the "generic" kernel have support voor ReiserFS ? (i assume it does but it never hurts to ask).

Hmmz, I just did a "make menuconfig" on the 2.6.11.11 kernel and ReiserFS is enabled, but as a module by default. To boot correctly it has to be included in the kernel. Maybe that's the problem.

are you able to post your /etc/lilo.conf file here? to me it sounds like you got the path mixed up