Heh, been there. After 2 days trying, I gave up, installed the base system using 2.2.17-reiserfs (from http://chao.ucsd.edu/debian/boot-floppies/), and upgraded to 2.4.x afterwards (add "deb http://people.debian.org/~bunk/debian potato main" to apt.sources, apt-get dist-upgrade). I think maybe syslinux, init or something in the boot disks is not compatible with 2.4.x. If you do find a fix, please email me. Hope that helped.
On Tue, 2001-11-20 at 02:31, Roman Mitz wrote: > Hi, I'm running into a problem here and wanted to see if anyone else saw > something like it before. > > I was following the instructions in "Technical information on the Boot > Floppies" to replace the Rescue Floppy Kernel, as I have a machine with a > promise raid controller I want to use for the root. I put 2.4.14 (with > the loop.c modification) on the disk. > > Bootup looks fine, it detects the controller and disks, etc. Everything > looks good until it goes to load the root ramdisk. It finds the > compressed image, says it mounts, and then gets "no init found". I > confirmed that this ramdisk works with a standard boot floppy. > > I tried several combinations of init= parameters, though those didn't > work, as expected. > > So, what simple thing am I missing? Thanks in advance for your input. > > Roman. > ------ > Director of Computing Resources > The Center for the Neural Basis of Cognition > > -- []'s Daniel Serodio <[EMAIL PROTECTED]>
