well if you ever aren't quite sure what a package is called you can try:

rpm -qa | grep xfs (or whatever you think it might be)

to see...

Now, I wouldn't go uninstalling XFree86 if I were you...but if you decide to remove XFree-86-xfs, you need to use the -nodeps option because many packages depend on it. However, if you're just planning to uninstall and reinstall that package, it shouldn't affect much.

after reinstalling XFree86-xfs.blah, I can now get to graphical login and actually login. But, as soon as I login with anybody but root, it gives me an error that your session lasted for less than 10 seconds. Login as root works fine..

Any suggestions...

if ur gettin an error about default font, and flashing screens, then ur space is used up, go into windows and use a partition magic, and delete some files, i think its xsession-errors file in the /root/ or wotever directory, mine wus 600mb + and i had to delete it,

sorry if you have already figured this out but,

enabling swap space
sh -2.05a#

your there, it's not hung. That's the command line prompt

/bump

I am encountering this same problem with a fairly new RH9 installation. The problem started after I asked the system to reboot rather than shutdown. After completing the "stopping" sequence the system hung with the hard drive lights on solid. This system is a dual processor Pent II "DK440LX - Intel MB" with 2 SCSI drives and 2 IDE CDROMs. It has a 384M of memory and is setup for KDE and development. What I am stuck at is how to "intercept" or interrupt the booting process and take control to prevent the system from entering runlevel 5. If I can get to a text log in then I can apply some of the suggestions here but currently I am in a start - crash loop which I can only exit by pressing CTRL+ALT+DEL at the TEXT login screen (it appears for a couple of seconds compared to the random garbage graphical screen for like 15 secs). The CTRL+ALT+DEL sets runlevel to 6 and the system "stops" the loaded processes and then restarts the whole text / garbage graphics loop again. I can intercept the GRUB screen but I didn't append the proper information to make linux rescue or linux single work yet.

So in summary, is there a way to overide the runlevel init during the booting process? Will go search more but not sure what correct keywords are.

(Linux for about a year and had this problem 2 times now - reinstalled to fix the last one but there has to be a better less drastic solution.)

I've been through h*!@ tonight with this problem. I finally got xf86config to work with a cold booted 600mhz. Had to keep rebooting and trying different xconfig settings....finally one worked. I couldn't boot into the init 3 until I shut off the computer for about a minute. Finally got startx to work...now, my mouse don't work. Computer wouldn't boot into init 3 to get xf86config to work until I shut it off for awhile....