From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.4.2)
Description of problem:
driver did not detect my external connected monitor (Samsung
SyncMaster 180T) and used default settings instead, which results in a
uglx 640x480 resolution. My laptop is an IBM Thinkpad T30.
The same hardware works well with Fedora Core 1 and 2. It also works
fine with the vesa driver under RHEL 3.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install radeon driver
2. good luck :-)
Actual Results: 640x480 resolution
Expected Results: 1280x1024 resolution
RHEL 3 and Fedora Core 1 ship the exact same "radeon" driver.
You mention: 1. install radeon driver
Are you installing a 3rd party radeon driver?
I have used the XFree86 OSS driver, not the commercial ATI driver. The
VESA driver works well. Than Ngo tested it on Fedora Core 2 (sorry -
not Core 1 !!!). He and Thomas Woerner can also provide you with
further infos. Than made some testing and said, that he has an idea,
where the problem could be. Maybe it makes sense, if you talk
directely to him :-)
We also tried another TFT display (V7 17 inch) and this display works
well in 1280x1024 with the radeon driver. The Samsung display returns
a max horiz. frequenzy of 31khz. (according to the log files) to the
driver, The driver ignores all XF86Config settings and only starts in
640x480, not using the 1280x1024 resolution set in the config file.
Fedora Core 2 contains xorg-x11 which is a newer X release than
what is shipped/supported in RHEL3. Please attach a copy of the
X server log file from a failed startup attempt, and a copy of the
X config file.
I've also CC'd Than for comment.
If this problem remains, please update the bug report as per the
requests in comment #3 above. If the problem no longer occurs,
please update the report with status info so we can close it
Thanks in advance.
Setting status to "NEEDINFO", awaiting requested information.
my idee was just to disable some patches in XFree86-4.3.0-62.EL, which
could cause this problem. But it did not work. Problem still shows up :(
This problem is assumed to be fixed in RHEL3 with all updates
applied, as the required information requested in comment #3
has not been supplied. Closing bug as "ERRATA" for RHEL3, however
if this problem still persists in RHEL3 with all updates applied,
please attach the information requested in comment #3 above,
and we will review the issue again and investigate.
Thanks in advance.