Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#16 Can't boot: "Id "1" respawning too fast"

closed-invalid
nobody
None
5
2002-08-16
2001-05-24
Anonymous
No

Hi,

I've just installed Debian 2.2-m68k (aka. potato) on my LC 630 with 36
MB of RAM with Penguin 18 and the kernel which comes with Debian 2.2

All went right except when I want to boot the installed system. I get:
...
INIT: Entering runlevel: 2
Starting system log daemon: syslogd klogd
Starting internet superserver: inetd
INIT: Id "1" respawning too fast: disabled for 5 minutes

And if I wait 5 minutes the last lines appairs again and again.

So, I can't boot. Any idea to allow me to boot? (another kernel? some
kernel args to add?)

Thanks in advance for your help,

Julien

Discussion

  • Logged In: NO

    Hi Julian,

    I've had the same problem that you described.

    So far about the only way to get around this until
    you can pick apart the init/booting scripts and repair
    this problem is:
    1.) After you see the annoying message and you listen to the
    drive stop thrashing, hit <Ctrl - Left Arrow> keys on the
    keyboard.

    2.) You will see a prompt. Type in 'root' and hit return.

    3.) Now you will be logged in as root. Type in 'init 1'
    This will put the machine into a sysadmin. single user
    mode, and will kill alot of background processes.

    4.) your machine will stop showing that annoying 'respawn
    too fast message', and the harddrive will stop thrashing
    every 5 minutes. Grab your trusty Unics/Linux manual
    and camping equipment.

    I don't know why the 'respawn too fast' occurs yet,
    but I'm digging into it. init scripts probably need to be
    modified as a fix. The install config under Penguin-18
    is minimal and funky. BTW, the whole port to MAC-68k boxes
    is in the tinkertoy phase, IMHO. Not exactly Caldera
    eDesktop install on an x86 box.
    But hey, where's the challenge in that!?
    BTW, on my Centris 610 Mac the clock setting on boot
    to Linux is goofy too.
    Nice thing about Linux/Unics, theres always a work around
    for about every problem or bug.

    let me know what you come up with.
    If I fix this problem, or atleast avert it I'll post it.

    Bill. wdborgen@yahoo.com

     
  • Logged In: YES
    user_id=278639

    I've got the same problem on my LC475. It was solved by
    manual upgrade of proccessor (MC68LC040 -> MC68040).

     
  • gaspra
    gaspra
    2001-10-31

    Logged In: YES
    user_id=334181

    Had the same Problem with my Performa 475. After reading fivans Message in this thread i changed the
    MC68LC040 to a MC68040 which also solved the Problem for me.

     
  • Logged In: NO

    Yes I expereince the same prblem, heres what i found. The reason is goes in a cycle is because
    getty isnt working since as it says while booting up /dev/ttys0,1,2 , etc.. are not configured and
    also tries to access them in a PC fashion through thei IRQ's or something. Now I have an LC475
    and I know its not the cpu bug since i tried NetBsd and I would get segmentation faults every
    time i ran ls or ping, Here i was able to complete the installation run text editors configure my
    network try ping tracert , etc.. and in general the system didnt ever give me a problem. Still I
    cant boot since I havent figured a solution out yet, any help would be welcomed.

     
  • Logged In: NO

    Yes I expereince the same prblem, heres what i found. The reason is goes in a cycle is because
    getty isnt working since as it says while booting up /dev/ttys0,1,2 , etc.. are not configured and
    also tries to access them in a PC fashion through thei IRQ's or something. Now I have an LC475
    and I know its not the cpu bug since i tried NetBsd and I would get segmentation faults every
    time i ran ls or ping, Here i was able to complete the installation run text editors configure my
    network try ping tracert , etc.. and in general the system didnt ever give me a problem. Still I
    cant boot since I havent figured a solution out yet, any help would be welcomed.

     
  • Raylynn Knight
    Raylynn Knight
    2002-08-16

    • summary: Can't boot: "Id "1" respawning too fast" --> Can't boot: "Id "1" respawning too fast"
    • status: open --> closed-invalid
     
  • Raylynn Knight
    Raylynn Knight
    2002-08-16

    Logged In: YES
    user_id=92395

    Some mask revisions of MC68LC040 have a bug which prevents f-line
    trap handler (which catches attempts to execute FPU instructions and
    invokes the emulator) from properly working.

    The bug even prevents SoftwareFPU, an FPU emulator for MacOS,
    from working on some LC040 Macintoshes.

    There is absolutely no software fix for this problem. You must replace
    the CPU chip with a newer, fixed one. In some cases, you can do it
    yourself by getting a 68040 chip, whereas you cannot do it yourself in
    other cases.

    The list of known good or bad mask revisions of the LC040 chip is not
    currently known.