Yikes! X is borked. Help!
dk
Yesterday I installed a new graphics card (GeForce 6200) which went
fine. Worked for several hours afterwards, before shutting machine down
for the night.
This morning, all was working well, again for several hours. Then, when
waking up the machine after a period of inactivity, the screensaver
image briefly appeared and then the machine froze. Completely frozen
solid, only option was to power down.
Upon rebooting, the machine allowed me to log into KDE before freezing
again (part way through drawing a background image - though that may be
coincidence). Locked solid again. Next reboot, it froze on the login
screen (ie, before going to KDE).
So I rebooted and selected runlevel 3. That's fine. But any attempt to
start X (including any attempt to run Sax2) results in the machine
freezing solid. So I figure that X may be borked somehow.
/etc/X11/xorg.conf is fine - as it was yesterday, not corrupted.
Where else could I start looking? Any advice? Your thoughts would be
appreciated.
Marcel Cox
Your message was not posted to the official Novell news
server or crossposted to a non novell.* newsgroup.
While your news server might show the Novell support
newsgroups, Novell has no official connection with other news
servers, and the message you posted will probably never
propagate to the official Novell server. The SysOps only see
messages on the Novell server and for that reason,
you will probably never get a reply to your
message posted here.
I suggest you post your message directly to the official
novell news server named support-forums.novell.com. The
Novell news server is freely accessible both through HTTP
and NNTP. See http://support.novell.com/forums for details.
This message was posted automatically. Please do not reply
to it.
Marcel Cox
Novell Support Forums SysOp
ERACC
> Where else could I start looking? Any advice? Your thoughts would be
> appreciated.
Reads like a physical hardware problem. Bad video card perhaps. Try
replacing with a known good one. It is also possible the machine is not in
a "hard" lockup and could be accessed via ssh from another PC on your LAN.
In that case you could ssh in and kill X from a remote box. Of course if
it /is/ a physical hardware problem then the system might actually be in a
hard lockup. Only way to know would be to try ssh from another box.
Gene (e-mail: gene \a\t eracc \d\o\t com)
--
Mandriva Linux release 2006.0 (Official) for i586
09:03:24 up 6 days, 22 min, 16 users, load average: 0.08, 0.09, 0.09
ERA Computers & Consulting - http://www.eracc.com/ <- get VOIP here!
eComStation, Linux, FreeBSD, OpenServer & UnixWare preloads & sales