Description of problem:
X crashes and locks up upon startup with current Rawhide when using i810 driver.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot in runlevel 3
2. type startx
system locks up with gray vertical stripes on screen. Alt-Fn does nothing.
starts with the DE of my choice displaying a nice image from the Western US
System works with the following:
attachment contains xorg.conf, Xorg.0.logs for working system and updated
Created attachment 297265 [details]
xorg.conf, Xorg.0.logs for working system and updated (crashing) system
Created attachment 297285 [details]
xorg.conf from the attachment 297265 [details]
Created attachment 297286 [details]
Xorg.0.log.crashed from the attachment 297265 [details]
Created attachment 297287 [details]
Xorg.0.log.good from the attachment 297265 [details]
I am seeing very similar symptoms, though in my case it fails most of the time
but has worked on occasions. The same machine running Fedora 7 works reliably.
Added notes: after getting X to work using the fbdev driver, I am sometimes able
to get X to work using the intel driver (I run Xorg -configure to get a new
1. Updated to today's Rawhide:
2. Rebooted system
3. Got rid of /etc/X11/xorg.conf and ran system-config-display which gave me the
following (after selecting generic LCD 1680x1050) replacement:
# Xorg configuration created by system-config-display
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
ModelName "LCD Panel 1680x1050"
HorizSync 31.5 - 65.5
VertRefresh 56.0 - 65.0
Viewport 0 0
4. Ran startx. Lo and behold, the system comes up with a 1680x1050 screen, sound
works, but Print and Ctrl-Print do not work
I have a similar problem on a different bug because of different symptoms. I
found that I needed to do a power reboot after the update to the driver before
doing the startx thing.
It is still broken for me - I can't get 1280x1024 though some resolutions do
work, eg. 1024x768 and 800x600. Curiously, I can get 1280x1024 by having a
resolution that works in /etc/X11/xorg.conf, then using the gnome tools to set
it to 1280x1024.
Actually, 1024x768 also fails occasionally.
Created attachment 298075 [details]
With the following addition to the "Device" section of xorg.conf, the current
Rawhide Xorg server and i810 driver have worked for me every single time (i.e.,
both times) I've rebooted.
Option "NoAccel" "True"
Actually, xorg-x11-drv-i810-2.2.1-14.fc9 from koji seems a lot more stable so
far at resolutions that I previously had problems with.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.