[SOLVED] No boot after editing vmlinuz symbolic link to point to 3.3.45 generic

(subject should read: 3.2.45 generic")

Can't get slack14 64-bit to boot after I changed the symbolic link that had been pointing to "huge-3.2.45" so that it now points to "generic-3.2.45".

How do I get inside slackware to tinker? and what tinkering is to be done?
do I change link back to "huge"?

(I have a usb start-up but when i use it i can't find any of my files; it's like a fresh install)

Thanks
(still bogged down in the peat-moss bog flats surrounding mount slackware)

The "generic" kernel contains very little in terms of storage drivers, so you'll need an initrd.

Boot from the DVD and follow the instructions on the boot screen for booting your installed system. Basically, you tell the "huge.s" kernel not to use the installation initrd and mount a hard drive partition as a root FS instead.

Once your system is booted, log in and run /usr/share/mkinitrd/mkinitrd_command_generator.sh. It will tell you what parameters to use with the mkinird command to generate an initrd with the right kernel modules.

For getting in see http://docs.slackware.com/howtos:sla...oot_from_media

It looks like you have been updating your Slackware 14.0 install to the latest kernel (should be 3.2.45 NOT the 3.3.45 in your post).
Did you create an initrd.gz using mkinitrd before trying to reboot to the generic kernel?
If so, did you add an entry to /etc/lilo.conf?
If so, did you run lilo?

It you have the huge kernel in /boot, it is probably best to change the symlink back to pointing to the huge kernel and run lilo (after doing the chroot) to recover your ability to boot.

Originally Posted by allend For getting in see http://docs.slackware.com/howtos:sla...oot_from_media It looks like you have been updating your Slackware 14.0 install to the latest kernel (should be 3.2.45 NOT the 3.3.45 in your post). Did you create an initrd.gz using mkinitrd before trying to reboot to the generic kernel? If so, did you add an entry to /etc/lilo.conf? If so, did you run lilo? It you have the huge kernel in /boot, it is probably best to change the symlink back to pointing to the huge kernel and run lilo (after doing the chroot) to recover your ability to boot.

I didn't install lilo when i installed slackware (grub2 on MBR picks up slackware after upgrade-grub in mint) but i'm beginning to suspect that the problem you've been helping me with (patchy gui) could stem from having installed slack AFTER installing Mint, and that I might be advised to go for fresh install of both, but this time, starting first with slack, installing lilo in MBR and when i come to install mint, installing grub2 in mint's /boot partition.

What do you think?

I don't think that this is a problem with Lilo or Grub, but since you give us no clue at all which errors you get when you try to boot Slackware this is just a shot in the dark. Have you created an initrd, which is mandatory when using the generic kernel?
Which error messages do you get?