I just installed CentOS 5 on a Sony Vaio V505 (PCG-V505DC2P) and it worked perfectly. A full yum update also worked fine.
The user made various changes to it over the weekend, and how I'm faced with trying to undo endless "INIT: Id "x" respawning too fast: disabled for 5 minutes" error messages.
I've spent half the day googling various answers. init 5 will not do anything. startx and xinit do work, but don't provide the proper window manager nor X window sessions.
Now that I think of it, after the first yum update, the system defaulted to a tty, and I had to CNTL-Alt-F7 to switch to the X display.
I also tried to install the ATI video driver, but that claimed an error in the end.
I tried to comment out x:5:respawn... at #Run xdm in runlevel 5 at the end of /etc/inittab then initiate init 5 from a tty session, but that didn't do any good.
Ideas would be most appreciated.
Thanks.
Scott
Ouch! I hope you are charging $150/hr to fix the laptop of this clueless user?
Have you looked in the system logs to see what errors are being written?
This error message has several causes, some of which can be easy to track down - others not. You could spend the time tracking the cause down, but I suspect you will find more than 1 problem, since you have no idea what this idiot has done to the system. One idea from left field is they might have modified the security settings and PAM is kicking the user out before it can login.
So I recommend instead, you simply wipe the sytem and reinstall CentOS5, and tell the user not to touch anything they don't know about.
Now that I think of it, after the first yum update, the system defaulted to a tty, and I had to CNTL-Alt-F7 to switch to the X display.
Uhh sorry, didnt read this properly. That there is where this problem has started. An update has broken the system. Maybe its the default radeon drivers.
I had a similar problem on a couple of our Linux boxes. This happened right after we installed Sybase.
The culprit was, the /etc/ld.so.conf file was empty. The Sybase installation erased these files for some reason. I put back the entries in the file and everything was OKAY.
Here is how my /etc/ld.so.conf file looks like
/lib /usr/lib /usr/X11R6/lib /usr/kerberos/lib /usr/local/lib /usr/X11R6/lib /usr/lib/qt-3.1/lib /usr/lib/mysql
-
DamianS -
Prasad Pillarisetti -
Scott Ehrlich