Red Hat Bugzilla – Bug 131694
Black screen during install FC2 on ACER Altos G310
Last modified: 2007-11-30 17:10:48 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7)
Description of problem:
While starting a graphical installation, which is the default, the
screen turns black and no installation is possible. In this situation
the monitor does not show an out of range information.
The graphical card gets probed as "VESA driver (generic)". The monitor
gets properly probed as "Compaq S700 Color Monitor". At the point
where the graphical screen is started the screen turns black.
I have tried several boot options:
# linux nofb
# linux skippdcc
# linux resolution=1024x768 (and others)
# linux noapic acpi=off
The text installation does run successfuly, however after a boot the
console is not useable, not even the text-console => ALT+Shift+F[1-6]
The monitor shows an error: "Signal out of Sync (32,5kHz 40Hz)"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.start machine from CD#1 (Fedora FC2)
3.skip testing the CD
Actual Results: Always get a black screen.
Expected Results: It should start with the graphical interface to
continue the graphical installation process. At least the text-console
should be available.
I was able to remotely log into the machine (ssh) and ran the
following command: Xorg -configure
The resulting config file contains weird information:
#DisplaySize 330 250 # mm
ModelName "COMPAQ S700"
HorizSync 30.0 - 70.0
HorizSync 876034368.0 - 0.0 (??)
VertRefresh 50.0 - 0.0 (??)
When running the test: X -xf86config /home/fdb/xorg.conf.new
it complains with:
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 6 08:43:41 2004
(++) Using config file: "/home/fdb/xorg.conf.new"
Parse error on line 51 of section Monitor in file /home/fdb/xorg.conf.new
The HorizSync keyword must be followed by a list of numbers or
(EE) Problem parsing the config file
(EE) Error parsing the config file
Fatal server error:
no screens found
Strange thing is that the /etc/X11/xorg.conf - file seems to contain
correct information for the screen:
VendorName "Monitor Vendor"
ModelName "Compaq S700 Color Monitor"
DisplaySize 330 250
HorizSync 30.0 - 70.0
VertRefresh 50.0 - 160.0
Please run the following command:
After this, try to start the X server, and attach your X server
log and config file to the bug report using the bugzilla file
Thanks in advance.
Created attachment 103626 [details]
file :: /usr/share/system-config-display/xconf.py
This is the file the command "system-config-display --reconfig"
I ran the command, it returned this error:
[mail: ~] root# system-config-display --reconfig
Traceback (most recent call last):
File "/usr/share/system-config-display/xconf.py", line 412, in ?
NameError: name 'hardware_state' is not defined
Created attachment 103627 [details]
TAR file containing "grub.conf" and "xorg.conf" files
The files have been modified; I am not completely sure which part makes it
work, however with these 2 files I got a working graphical environment
Please attach non-compressed files so they can be viewed in a web
browser. Thanks in advance.
Created attachment 103816 [details]
grub.conf boot file
By request the text version of "grub.conf"
Created attachment 103817 [details]
By request the text version of xorg.conf
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core 3, which can be obtained from:
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.