Mandrake respawning error

computergirl · 03-21-2002, 08:17 PM

This is my first time installing Linux so this may be a dumb question but.... the problem is I installed Mandrake 8.1 and everything went fine, I thought and when it rebooted for the first time I got a message saying

Init: Id "x" respawning too fast:diabled for 5 minutes

I waited the 5 min. and it just keeps doing the same thing. I read the user guide and can't find anything. Here are my specs if you need them:
AMD Duron 800 mhz
320 mg RAM
DSL service
Nvidia Vanta LT Display adapter
Onboard Soundmax Soundcard
Dual Booted with XP home
Thank You in advance, any help would be greatly appreciated.

rshaw · 03-21-2002, 10:09 PM

sounds like mandrake didn't detect your video adapter correctly. start the install again and choose expert update as the installation class. then click on <configure x> as soon as it will let you. if your card is not listed, try models from the same manufacturer, or if all else fails choose a generic vesa or frame buffer device. test each selection when it offers.

computergirl · 03-22-2002, 09:59 AM

I reinstalled, thank you the tip worked, but now I'm having another problem when it went to reboot I got a msg back saying loading Linux EBDA too big (something like that). So, I went back here and checked the forum and saw the advice of creating a boot partition so I did that only I had to reinstall to do it. Then when it went to reboot again I got another message saying

Kernel Panic: no init found. Try passing init=option to kernel

I pretty sure the error was caused by creating the boot partition but I don't know how to fix it. I'm just about ready to give up, if I have to reinstall again it will be the 5th time.
Thank you
Also I did try checking google first as well as the forum but none of it helped.

shintu · 04-01-2003, 11:13 PM

I've been running into the same error with a rebuild of Slackware 8 (EBDA too big). I tried everything out there with no luck. Until I finally tried changing back each thing I had changed since my last build. My problem seems to have stemmed from the fact that I was booting from the first sector on my root partition. In my previous installation I was booting from the master boot section. I used liloconfig to reinstall lilo with this setup and it fixed my problem.