Description of problem:
X seam not to start since I only get a black screen.
I have a asus notebook with a radeon mobilety.
I also have a external vga port and a s-video port.
What apear to be x failing to start proper and just turn the lcd display black
is that the ATI drivers used for ati cards in fedora only reconise the vga
outpot, once I connect a vga display to the port I have picture there, but not
on my lcd.
It's easy to fix by instaling the driver from livnea repos, but this result in
not being able to use beryl without instaling xgl since direct rendering won't
work on livna drivers if I type Option Composite "Enable" in my xorg.conf file.
It allways have to be Option Composite "False"
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:

Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below (please, only with
open source drivers; we don't want any fglrx stuff here).
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.

As I say the problem by not reciving signal on the LCD is solved by using the
fglrx drivers. Keep in mind that the Signal to the VGA is ok all the time.
My nootbook has a radeon mobilety where I can send signal both to the onboard
LCD and a external VGA screen.
When installing the fglrx drivers (since you don't recomend installig the
native ATI drivers) direct rendering wont work when I type:
Section "Extensions"
Option "Composite" "Enable"
EndSection
the xorg.conf direct rendring will only work if composite is
Section "Extensions"
Option "Composite" "False"
EndSection
This is a huge problem if I want to use beryl.

It seams like I no longer has the xorg file from the time befour I started
using fglrx driver, but it seam to be a problem with everyone using ati
mobility and fedora, but seam like nobody else but me tryed to conect a display
on the vga output. If I remember corectly it worked with no problem on fc4.

Created attachment 157188[details]
My modefyed xorg.conf
I upgraded to Fedora 7 today and the bug seam to still be there.
I installed and once starting xorg the laptops LCD go black.
I conect a external CRT scren to the VGA output and a picture apear at once.
I open my xorg.conf and replace the text I with the old file I used in FC6 only
changing the driver in the file from fglrx into radeon.
I logged out and restarted xorg and now a picture apear on both the LCD and the
CRT on my external VGA

(In reply to comment #10)
> (In reply to comment #7)
> > I logged out and restarted xorg and now a picture apear on both the LCD and
the
> > CRT on my external VGA
>
> Does it mean, that this bug has been actually fixed in FC7?
No the problem is still there, the xorg has to be modefyed to show picture on
the nootebooks internal LCD, if not modefyed it will only show picture on the
VGA output on the back off the notebook.

Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.
Setting status to NEEDINFO, and awaiting information from the reporter.
[This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or
Gecko. If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]

Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
information.
Closing as INSUFFICIENT_DATA.
{This is mass-closing of all obsolete bugs; if this bug was in your opinion
closed by mistake, please, reopen it with additional information; thanks a lot
and I am sorry for bothering you in such case.}