Board index Linux Setup

Slackware 2.3.0, bare boot -> child process XXX died with code ff00

Slackware 2.3.0, bare boot -> child process XXX died with code ff00

Post by Chris Me » Thu, 20 Jul 1995 04:00:00



I am trying to install Slackware 2.3.0 (kernel 1.2.8) onto my P90/PCI,
and I can't get past the starting gate.  I boot with the "bare"
bootdisk, and
a) before loading the filesystem, I am prompted to "insert the disk
containing the ramdisk", which seems strange because it is on the
same disk (I think), then
b) after loading the MINIX filesystem, the machine goes into this
state where I just keep getting the messages

"Child process N died with code ff00"

"Child process N+1 died with code ff00"

etc., with these messages coming at ~100 Hz.

A minimal but functional installation of an older Slackware (kernel ~1.1.50)
is already present on this machine, so I'm pretty sure I don't have any
debilitating hardware problems.

Any suggestions certainly appreciated.


 
 
 
Top

Slackware 2.3.0, bare boot -> child process XXX died with code ff00

Post by Dass Rami Patri » Thu, 20 Jul 1995 04:00:00



>I am trying to install Slackware 2.3.0 (kernel 1.2.8) onto my P90/PCI,
>and I can't get past the starting gate.  I boot with the "bare"
>bootdisk, and
>a) before loading the filesystem, I am prompted to "insert the disk
>containing the ramdisk", which seems strange because it is on the
>same disk (I think), then
>b) after loading the MINIX filesystem, the machine goes into this
>state where I just keep getting the messages
>"Child process N died with code ff00"
>"Child process N+1 died with code ff00"
>etc., with these messages coming at ~100 Hz.
>A minimal but functional installation of an older Slackware (kernel ~1.1.50)
>is already present on this machine, so I'm pretty sure I don't have any
>debilitating hardware problems.
>Any suggestions certainly appreciated.


that happened to me too, when they say insert ramdisk, give them the root
disk

rami dass


 
 
 
Top

1. slackware 2.3.0 boot problem (child #n died with code ff00)

This problem was already reported (at least once in July) but I
could not find any answer yet so I re-post it with few more details. I
booted my PC (which has only one 400MB DOS partition at this time out of
the WD 830MB total), with slackware 2.3.0 bare boot disk (the 1.2 M
version).
As I figured out it recognized my disks configuraions properly (at least
it knew the total size of the HD and the size of the two floppies) and
since I have no SCSI controllers, I pressed the ENTER key and let it do
the job.
It was loading ramdisk (linux version 1.2.8) and it issued:

   Partition Check:

     hda: hda1

   RAMDISK: 1274560 bytes, starting at 0x001f0200
   VFS: Insert ramdisk floppy and press ENTER

at this point I was surprised since I was expecting it to ask me to
switch to the root floppy. Anyway, recalling it was once loading ramdisk
from the floppy and since the boot diskette was still there, I pressed
ENTER. And indeed it started working saying:

   RAMDISK: Minix filesystem found at block 0
   RAMDISK: loading 1200 blocks into RAM disk .........................

and after few seconds, it hanged into this loop, prompting every few
milliseconds:

   child 1 died with code ff00
   child 2 died with code ff00
        .
        .
 Thanks Isaac.

P.S.

I have 16 M RAM (8+8) Vesa Local Bus PC.

2. Xandros

3. child xxx died with code ff00

4. How to get Network Bandwidth?

5. child xxx died with code ff00...

6. Howto send output to fb0

7. child process xxxx died with code ff00!

8. Technical info about Apollo Hard disk controllers

9. Linux won't boot- "child # died with code ff00" message

10. "child nnn... died with code ff00 loop on boot

11. 3.2 bare - died with code ff00 ?!! HELP

12. child (#) died with code ff00??????????????

13. child nnnnn died with code ff00 (n=1 to infinity)


All times are UTC
Board index