This error message:
Code:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2 filesystem (and not
swap or ufs or something else), then the superblock is corrupt, and you
might try running e2fsck with an alternate superblock:
ef2csk -b 8193 <device>
An error occurred during the root filesystem check
You will now be given a chance to log into the system in single user mode to
fix the problem
If you are using the ext2 filesystem, running e2fsck -v -y <partition> might
help.
It only happens with Slack with generic kernel and initrd. Custom kernel without initrd works, as well as huge kernel. Debian with initrd also works. So, problem is with my initrd for generic kernel.
This error message is the same whether lilo.conf is this:
Code:
image = /boot/vmlinuz-generic-smp-2.6.33.4-smp
initrd = /boot/initrd.gz
root= /dev/sdb1
append="i915.modeset=1"
label = Slack-generic
read-only
or
Code:
image = /boot/vmlinuz-generic-smp-2.6.33.4-smp
initrd = /boot/initrd.gz
root="UUID=480f7a86-d229-4809-92aa-e4e3a19a734e"
append="i915.modeset=1"
label = Slack-generic
read-only
So UUID works just as partition name, problem is probably my initrd.
append="i915.modeset=1" solved problem with X.
Edit:
Since my Lenovo now boots fast with lilo and I am able to use both OS's, I can mark this thread as solved. initrd is problem of it's own. Thank you all for your help and time!