Bug 488 - Screen keeps refreshing if Xconfigurator is set to wrong monitor freq.
Screen keeps refreshing if Xconfigurator is set to wrong monitor freq.
Product: Red Hat Linux
Classification: Retired
Component: Xconfigurator (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1998-12-15 16:25 EST by isingh
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1998-12-16 12:03:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description isingh 1998-12-15 16:25:43 EST
I had installed my Linux 5.1 couple of months back and was
working on it smoothly. I also had Xwindows installed and
console login used to comeup automatically on reboot. But
then yesterday I ran Xconfigurator to set some monitor
and mistakenly set the monitor refresh rates to wrong
Now if I reboot, the console login pops up (not the Xwindows
and then the screen keeps on refreshing not allowing me to
start Xwindows or login.  Cntrl+Alt+Del works which just
the machine. Because I have lot of stuff already on the
hard drive, I can't reinstall Linux because it would
format the drive.
Comment 1 David Lawrence 1998-12-16 12:03:59 EST
You need to boot the machine into single user mode but typeing at the
lilo prompt

LILO boot: linux single

This will eventually get you to a BASH# prompt where you need to use a
text editor to edit the /etc/inittab file. Change the number 5 to
number 3 in the line


This will allow the system to reboot without trying to run the X
login. Then rerun Xconfigurator to set the monitor to correct
specifications. If you feel everything is again set correctly then you
can change the 3 back to a 5 and reboot the machine.

Note You need to log in before you can comment on or make changes to this bug.