WindowsXP duel boot with SuSe Linux, SuSe linux not booting?
 

Im duel booting suse linux with windows xp in the NFTS system and when i boot the system and i try to boot into linux.. the progressbar moves to halfway and stops for some reason, now when i try to boot into windows xp it works..

Heres what i get when trying to boot SuSe linux:

INIT: Id "1" respawning to fast: disabled for 5 minutes
INIT: Id "2" respawning to fast: disabled for 5 minutes
INIT: Id "3" respawning to fast: disabled for 5 minutes
INIT: Id "4" respawning to fast: disabled for 5 minutes
INIT: Id "5" respawning to fast: disabled for 5 minutes
INIT: Id "6" respawning to fast: disabled for 5 minutes
INIT: no more processes left in this runlevel

Im guessing thats why it freezes.. :D

Hi and Welcome to LinuxQuestions!

Has your SuSE installation ever worked? There seems to be a serious error with your installation. If you just installed it, may I suggest reinstalling.

I could give a detailed description of what is wrong, but if you are new to Linux that wouldn't be of much help to you.

Martin

Everytime i install SuSe linux i get that error message, and the install goes fine, also i have ran mandrake linux 9.X before so i know some about linux

im using my windowsxp for games and my suse linux for other stuff this problem has occured for the past 4 days i've tried to install it..

OK. When the Linux system boots, the first thing that's started is the kernel. The kernel configures all hardware and starts the file systems and stuff like that. After that, the kernel starts the first process, init. Init never quits (until you reboot, of course) and is among other things responsible for keeping text terminals and, if activated, the boot GUI running. Init also starts the boot process. Init is controlled by a configuration file, /etc/inittab that tells it which scripts to run.

In your case, it seems that the inittab file (or something else in the startup scripts) is broken. It's difficult to tell what is broken and it may be hard to repair too. One way to fix it would be to boot the system with a rescue floppy and compare the scripts with those of a working system. But it's really strange that this occurs immediately after installation. :scratch: I almost suspect that the CD you use for installation is damaged.

I hope that you get a little understanding of what's wrong even though I can't give much help. Had you been in Linköping, Sweden, then I would have grabbed my Tom's rescue floppy (http://www.toms.net/rb/) and come over to have a look, but from here it's kind of difficult.

Martin