From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Description of problem:
Standard Dell Optiplex GX150 with 16MB ATI Rage AGP card installs
Fedora Core 2 without a problem. System behavior is expected
throughout the entire user experience until you logout of Gnome or
KDE. Upon logout the screen flickers, then blanks, then the Dell P991
monitor states that the Monitor is on, but that the input signal is
beyond the scan range. The system is frozen afterwards, no amount of
keyboard escape will work, Control-Alt-Backspace or
Control-Alt-Delete. The only path out is to press the power button and
force the power supply to turn off. Upon restart the system complains
about an unclean shutdown and prompts to fsck the root filesystem. The
entire experience up to this point is what I expect to see from Fedora
Core, it's only just past logout that it fails.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Login to X as user
3.Logout ----> Fail.
Actual Results: System unresponsive to keyboard input, montior states
"out of sync range"
Expected Results: Return to the graphical login screen for a new user
to log in. This screen does appear normally after a power-on, before
the first and last login for the machine.
Dell GX150 - 8ZQMQ11. Full install of Fedora Core 2 from FTP, selected
standard workstation install and added a small amount of extra
packages for exploration of distribution. Compeltely vanilla
first-time-install, auto-partition, remove all prior partitions, rpm
installation and system startup ran perfectly, with no faults.
I had almost the same problem with ATI Rage Pro Ultra 32 Mb video card
on FC2. But a few logouts were sucsesful.
in /etc/X11/Xorg.config all logouts are fine.
But Tuxracer became very slow. :-)
That did it! Thanks!
While disabling DRI may work around the problem, the video driver
should really be detecting an invalid configuration (if that is the
case) and disabling DRI itself, so we should try to reproduce at
I have both a Dell P991 monitor, and several ATI Rage 128 16Mb cards,
and can investigate this sometime in the future, and possibly fix it
or work around it in the driver.
Changing component to "xorg-x11" (We do not ship XFree86)
I have similar problems with ATI Radeon 9800Pro AGP on an ASUS AV333
(Via KT333 chipset) motherboard. System freezes on switching to a
virtual text console or shutting down X. The error is always reproducible.
I'm using FC2 with a 2.6.6 kernel, but had the same problem while
running a 2.6 kernel on FC1 also. The error occurs with all versions
of the 2.6 kernel, and also regardless of whether I use the radeon
driver bundled with X.org or ATi's binary only fglrx drivers (both
3.7.6 and 3.9.0 versions).
I've tried disabling DRI as mentioned above, but not had any success.
I've already posted a rather longish description of the same problem
I would be willing to turn DRI back on and test using the hardware I
have here if it would lead to a "real fix" versus a "shotgun fix".
I have a rage 128 that does this same exact thing. Has anyone heard
back from Mike Harris if he was able to dup this or fix it maybe?
I have the same problem with Rage 128 PF/PRO. Commenting
the Load "dri" line solves the problem, but I also had
success with changing /etc/X11/gdm/gdm.conf line
And I got accelerated 3d!
*** Bug 124873 has been marked as a duplicate of this bug. ***
*** Bug 122351 has been marked as a duplicate of this bug. ***
This seems to be related to SIGHUP'ing the server and DRI. I can
reproduce this with the FC2 kernel (2.6.5-1.358), but updating to any
newer kernel from FC2-updates or rawhide solves the problem.
Please try to install a newer kernel and see if that fixes it.
For me too, a newer kernel fixes the problem.
*** Bug 124677 has been marked as a duplicate of this bug. ***