Tech Support > Operating Systems > Linux / Variants > Unable to start X- After trying to upgrade KDE to 3.1.1
Unable to start X- After trying to upgrade KDE to 3.1.1
Posted by SRIKANTH NS on July 18th, 2003


Hi All,
I use a triple boot PC (Win 98/RH7.3/MDK 9.1) at home.
The specs are Intel Celeron 900 MHZ, 128 MB RAM
Intel 815 M/B (16 MB Shared RAM), Samsung 15" Monitor (56V).
I was trying to upgrade KDE in RH7.3 with a local magazine (PCQuest July
issue , India) CD to KDE 3.1.1. I copied the all the rpm's to a directory
and started installing them as per directions in the mag.
rpm -Uvh qt-*.rpm --nodeps --force
rpm -Uvh arts-*.rpm --nodeps --force
rpm -Uvh quanta*.rpm --nodeps --force
rpm --kde-*.rpm --nodeps --force

During all the above except for the last (kde*.rpm) there was indication
that installation was going on. During installation of KDE rpms some error
message came and I did not note it down.
Since errors came I tried uninstalling them in the reverse order
rpm -e quanta, then arts , then qt. But error message was that those
packages were not installed.
After working for some more time, I shut down the PC.
Today morning I booted into Redhat, but the monitor was blinking madly.
After about two minutes, error message was
"INIT: Id "x" respawning too fast. Disabled for 5 minutes"

I waited. It started blinking again.

I rebooted into mandrake. There GUI login was there . No problem. Booting
into windows also was normal.

So hardware problems, graphics card driver corruption are ruled out.(I
think)
I checked up XF86Config-4 file, no changes have taken place.
Again booting into redhat gave one more error message in addition to the
earlier one
"gpmops( ) invoked from gpm.c(164)"

What can be done to remedy the situation?

TIA,

Srikanth


Posted by Brand-X on July 18th, 2003


On Fri, 18 Jul 2003 06:28:42 +0530, SRIKANTH NS wrote:

<snip>

That flickering and trying unsuccessfully to go into graphical mode
happened to me when I was using 7.3 and it couldn't probe my video card
correctly. You'll need to run Xconfigurator and see if it can probe your
video card and screen correctly and set your resolution. Although if you
say that XF86Config is unchanged it seems unlikely that this is the
problem, I'd still give it a go to be sure, its in usr/X11R6/bin/

HTH

Adam
--
"He took a duck in the face at 250 knots"



Posted by Vwakes on July 18th, 2003


On Fri, 18 Jul 2003 SRIKANTH NS wrote:

I hope you had a -Uvh or -Ivh there.

I don't know who to believe now ;-) Check again.

rpm -q qt
rpm -q quanta
rpm -q arts
rpm -qa |grep kde

Check the version and see if they are upgraded.

How about booting into Gnome or other non-kde X?

Yep. It should. You haven't touched anything else. You must not have
even mounted other partitions I assume. Anyway..

Just install correctly. First don't use --nodeps or --force unless you
know what you are doing. Apparently you don't. If you install a package
just check if it was installed or not before jumping to install other
packages. Keep notes of what you are doing so that It would save hours
later.

Do you know how many KDE pkgs were there before and how many
you were trying to upgrade and what were those?

If you want to get your system back, get back your RH CD's and
using package manager install kde, arts, etc., again. Force it, here it
is ok.

And, while upgrading KDE don't use KDE. Same goes with qt, arts, etc.
Better get into a console mode, runlevel 3. It's safer that way.

GL.
V.


Similar Posts