LinuxQuestions.org - ? Configuring GRUB on Debian/sarge to boot Knoppix from HDD?

I am new to Debian and LInux, and to speed up the learning process, and check configurations on Knoppix when in doubt I have installed Knoppix on a different partion of the HDD, but I can not configure GRUB to boot Knoppix:

no matter what options I append to the kernel it starts booting and ends up with the same error:
--------------------------
[COLOR=blue]
#RAMDISK: Compressed image found at block 0
#RAMDISK: incomplete write (-28 !=32768) 4194304
#Kernel Panic: VFS: Unable to mount root fs on hda5
[ /COLOR]
--------------------------

here is my GRUB configuration menu.lst:

---------------------------
[COLOR=blue]
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda7 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,2)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=al
## ## End Default Options ##

title Debian GNU/Linux, kernel 2.4.26-1-386
root (hd0,2)
kernel /vmlinuz-2.4.26-1-386 root=/dev/hda7 vga=791
initrd /initrd.img-2.4.26-1-386
savedefault
boot

title Debian GNU/Linux, kernel 2.4.26-1-386 (recovery mode)
root (hd0,2)
kernel /vmlinuz-2.4.26-1-386 root=/dev/hda7 vga=791 single
initrd /initrd.img-2.4.26-1-386
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1

title Slackware
root (hd0,5)
kernel /boot/vmlinuz root=/dev/hda6 vga=791

title Knoppix
root (hd0,4)
kernel /boot/vmlinuz-2.4.27 root=/dev/hda5 vga=791
initrd /boot/initrd.img-2.4.27
savedefault
boot

title Knoppix-2.6.7
root (hd0,4)
kernel /boot/vmlinuz-2.6.7 root=/dev/hda5 vga=791 append="ramdisk_size=100000 lang=de apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce "
initrd /boot/initrd.img-2.6.7
savedefault
boot

title MS Windows 2003 ES
root (hd0,0)
savedefault
makeactive
chainloader +1
[ /COLOR]
----------------------------------------------

and the Knoppix lilo.conf on the root partition is as follows:

----------------------------------
[COLOR=blue]
# /etc/lilo.conf - See: 'lilo(8)' and 'lilo.conf(5)',
# --------------- 'install-mbr(8)', '/usr/share/doc/lilo/',
# and '/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run 'lilo' after you make changes to this |
# | conffile, '/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run 'lilo'. |
# | |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81

#disk=/dev/sda
# bios=0x80

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda5

# Specifies the device that should be mounted as root. ('/')
#
root=/dev/hda5

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using 'compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact

# Default menu for Debian. (Using the images from debian-bootscreen)
# from Philipp Wolfer <phil@newswriter.org>.
bitmap=/usr/share/lilo/debianlilo.bmp
bmp-colors=1,,0,2,,0
bmp-table=120p,173p,1,15,17
bmp-timer=254p,432p,1,0,0

# Install the specified file as the new boot sector.
# LILO supports built in boot sectory, you only need
# to specify the type, choose one from 'text', 'menu' or 'bitmap'.
# new: install=bmp old: install=/boot/boot-bmp.b
# new: install=text old: install=/boot/boot-text.b
# new: install=menu old: install=/boot/boot-menu.b or boot.b
# default: 'menu' is default, unless you have a bitmap= line
# Note: install=bmp must be used to see the bitmap menu.
# install=menu
# install=bmp
install=bmp

# Specifies the number of _tenths_ of a second LILO should
# wait before booting the first image. LILO
# doesn't wait if DELAY is omitted or if DELAY is set to zero.

# delay=20

# Prompt to use certaing image. If prompt is specified without timeout,
# boot will not take place unless you hit RETURN
prompt
timeout=50

# Specifies the location of the map file. If MAP is
# omitted, a file /boot/map is used.
map=/boot/map

# Specifies the VGA text mode that should be selected when
# booting. The following values are recognized (case is ignored):
# NORMAL select normal 80x25 text mode.
# EXTENDED select 80x50 text mode. The word EXTENDED can be
# abbreviated to EXT.
# ASK stop and ask for user input (at boot time).
# <number> use the corresponding text mode. A list of available modes
# can be obtained by booting with vga=ask and pressing [Enter].
vga=normal

# You can set a password here, and uncomment the 'restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an 'append'
# statement in 'lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like 'Linux init=/bin/sh',
# and thus becoming 'root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use 'install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM 'install-mbr(8)'.
#
# password=tatercounter2000

# You can put a customized boot message up if you like. If you use
# 'prompt', and this computer may need to reboot unattended, you
# must specify a 'timeout', or it will sit there forever waiting
# for a keypress. 'single-key' goes with the 'alias' lines in the
# 'image' configurations below. eg: You can press '1' to boot
# 'Linux', '2' to boot 'LinuxOLD', if you uncomment the 'alias'.
#
# message=/boot/bootmess.txt
# prompt
# single-key
# delay=100
# timeout=100

# Kernel command line options that apply to all installed images go
# here. See: The 'boot-prompt-HOWO' and 'kernel-parameters.txt' in
# the Linux kernel 'Documentation' directory.
#
# append=""
# Boot up Linux by default.
#
default="Linux"

image=/boot/vmlinuz
label="Linux"
initrd=/boot/initrd.img
append="ramdisk_size=100000 lang=de apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce "
read-only
image=/boot/vmlinuz-2.4.27
label="Linux(2.4)-1"
initrd=/boot/initrd.img-2.4.27
append="ramdisk_size=100000 lang=de apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce "
read-only

image=/boot/vmlinuz-2.6.7
label="Linux(2.6)-2"
initrd=/boot/initrd.img-2.6.7
append="ramdisk_size=100000 lang=de apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi nomce "
read-only

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the 'other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
# other=/dev/hda1
# label="WinXP/2K(hda1)"
[ /COLOR]
------------

I do not have any problems booting Slackware or MS Win2003, just Knoppix, and it is the same problem no matter, what Knoppix kernel I boot???

the file system of the Debian /boot (/dev/hda3) is ReiserFS, this may have sth to do with the problem??? (my intuition tells me) but aty this point it looks like sth in the configuration is to blame.

If you have any clues, please, tell me!??

10x in advance!