User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729) I'm having a lot of trouble using X on this computer with the xorg-ATI driver (described in summary), so it was suggested to me on the user's list to try using the vesa driver instead. So I had even worse luck doing that. Below is the screen output. Attached is the log file. ------------ [William@localhost ~]$startx xauth: creating new authority file /home/William/.serverauth.1566 X.Org X Server 1.6.3.901 (1.6.4 RC 1) Release Date 2009-8-25 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.18-164.el5 ppc Current Operating System: Linux localhost.localdomain 2.6.30.10-105.fc11.ppc #1 Thu Dec 24 16:28:20 UTC 2009 ppc Kernel Command line: root=/dev/mapper/VolGroup-lv_root ro rhgb quiet Build Date: 09 September 2009 11:36:55AM Build ID: xorg-x11-server 1.6.4-0.1.fc11 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implememented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 11 10:37:12 1976 (==) Using config file: "/etc/X11/xorg.conf" Backtrace: 0: /usr/bin/X(xorg_backtrace+0x50) [0x101014e0] 1: /usr/bin/X(xf86SigHandler+0xd8) [0x10085fc8] 2: [0x100364] 3: /usr/lib/xorg/modules//libint10.so(LockLegacyVGA+0x50) [0xf241c30] 4: /usr/lib/xorg/modules//libint10.so(xf86ExtendedInitInt10+0x1e0) [0xf245f30] 5: /usr/lib/xorg/modules//libvbe.so(VBEExtendedInit+0x320) [0xf281760] 6: /usr/lib/xorg/modules/drivers//vesa_drv.so [0xf2a9f24] 7: /usr/bin.X(InitOutput+0x5bc) [0x1006a6cc] 8: /usr/bin/X(main+0x224) [0x10021bb4] 9: /lib/libc.so.6 [0xf7f343c] 10: /lib/libc.so.6 [0xf7f35e0] Fatal server error: Caught signal 7. Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.o.log" for additional information. giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. Reproducible: Always Steps to Reproduce: 1. In text mode as root, run this command: system-config-display --noui --set-driver=vesa 2. startx 3. Look at the crappy output shown above. Actual Results: X couldn't start and it provides a lot of crash information. Expected Results: X should start
Created attachment 387136 [details] My Xorg.0.log file showing the VESA driver failure.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.