i wonder if there is some problem with the initrd.img created by 3.4 after a hd-install.

i believe it is the cause of the rather annoying msg i reported earlier http://www.knoppix.net/forum/viewtopic.php?t=11246

and is also discussed in

http://www.knoppix.net/forum/viewtopic.php?p=47833

i wonder if this is related to the fact that the initrd.img file is customized for boot from cd.
once my hd-installed knoppix boots, i notice that doing a df shows a /dev/root.old mounted as /initrd (fs-type ext2 which matches the cmd in mkinitrd.conf -- i don't have any ext2 file systems in my system, so it must be in ram). shouldn't this have been unmounted (and the ram freed) once the system has booted?

i tried to recreate a initrd.img file for the 2.4.26 kernel using a combo of fabianx's suggestion as well as another by norbert tretkowski (in the mkinitrd.conf file, set root to /dev/hda1 instead of probe) but using this initrd.img file doesn't work (as others have reported in these forums as well). seems like something special is necessary to recreate the initrd.img file used by knoppix. if anyone can shed light on this, would appreciate it.

my setup: i am running knoppix 3.4 off the hard-disk (beginner install using knoppix-installer) and added "nohwsetup" and "nofstab" as additional bootparameters in lilo.conf (to disable the tedious hw-detection and fstab creation everytime i reboot). i am only interested in the 2.4.26 kernel (and, in fact, intend to remove the 2.6 kernel from my system once i have a 2.4.26 system booting exactly the way i want it).