Hello Dennis,
I had this exact same problem on a newer HP Pavilion. Up2date hung up the
machine and I had to cycle power. Then I got the same error you did. In my
case I am running Fedora Core 1 which I installed from 3 CDs made from a
Fedora mirror site. At the system console I examined all 3 CDs for anything
X related. I found lots of Xfree86 rpms on each CD. So I simply mounted each
CD, went into the /cd/Fedora/RPM directories, and did something like:
$
$rpm -i X*.rpm
I got some media errors on the third CD, and some complained that the package
was already installed. Upon rebooting, I did get something of an X window
setup. I was running KDE, which came up, but there was no text asking for
Login or Password. I logged in anyway and was able to get some menus to
run, but was still missing text/fonts in some menus. Too weird. Being lost
now, I decided to try up2date again, even though I couldn't read the gui.
Once it finished, I rebooted and KDE came back fine.
I hope this helps.
Bill Mott
Systems Administrator
Office of Treasury Technology
New Jersey State Treasury
609-943-4685
-----Original Message-----
From: Dennis King [mailto:d_r_king@xxxxxxxxx]
Sent: Tuesday, March 09, 2004 4:07 PM
To: fedora-list@xxxxxxxxxx
Subject: INIT: id "x" respawning too fast, disabled for 5 minutes
I just ran up2date, which downloaded a bunch of XFree86 RPM's. The
install process hung on me for some reason (minimal software running
at the time, I was working on a PHP/MySQL script while the updates
were running on a different desktop). I had to force quit up2date
because all my applications were hanging, I could hardly navigate
among windows, which redrew every 10 seconds.
On reboot, the error message "INIT: id 'x' respawning too fast,
disabled for 5 minutes" now comes up. The GNOME GUI doesn't launch,
only the commannd line. I logged into the command line and ran rpm -i
/var/spool/up2date/XF*rpm as root to see if some packages had not
been installed, but there has been no changed. My hardward is an HP
Pavillion that is probably 4 years old now (sorry I'm not at home now
and can't provide the exact model number). I saw a similar bug in the
Redhat knowledgebase regarding 7.3, but there was no solution
offered, the user had had to reinstall 7.2, I think.
Any suggestions on getting my computer back? I'm afraid I'll have to
copy content to floppies and install something new.
Thanks,
Dennis
__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you're looking for faster
http://search.yahoo.com
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
