OK here's a brief background to my current situation, then onto the specifics. I am new to linux and am using FC3. I was installing an NVIDIA graphics driver and the instructions told me to change inittab to boot to "3" instead of "5" in order to bypass X. I did so (keeping an original copy of my inittab) and installed the driver successfully.

Upon rebooting there were no problems. I changed my inittab back to the original so as to boot into X again and came up with this error right after it found the physical drives:

"Enforcing mode requested but no policy loaded. Halting Now.
Kernel panic - not syncing: Attempted to kill init!"

and nothing further happens. I'm not sure what happened here and I would rather not have to reinstall the whole blasted thing, as this is not windows and can probably be fixed an easier way.

Your help is appreciated, thank you.

Fortentas

ok I just changed my xorg.conf file according to the instructions (I'm booting into rescue mode via my install disk) by changing

Driver "nv" to Driver "nvidia"
and
removing Load "dri" ('Load "GLCore"'was not there and 'Load "glx"' was there already)

This changed nothing in the boot process and it is still failing.


Also, if you need any clarification just reply and I'll get it out as soon as possible. Thanks

Can you provide the boot messages leading up to the "Enforcing moderequested..." lines.

The reinstall is most likely the easiest way. However, the best way is to grab a good livecd and fix it yourself. This will teach you a great deal about linux commands and the boot proccess.

In this case I recommend SystemRescueCD.

Thanks for the tip, I was using the rescue mode on the FC install disk which allowed me to access it.

After reading some other threads I tried changing selinux to permissive instead of enable and that seemed to do the trick. I'm not sure why selinux was having problems though.

as for the lines leading up to it, it was (paraphrasing) locating physical Volumes, found VolGroup00 and lists the physical volumes. then it loaded Enforcing mode (which I found was related to selinux) and that's apparently where my trouble began.

In any case if anyone knows why this happened I'd still like to know, as I'm trying to build my linux knowledge.