Bug 113697 - X.Org does not properly handle X700 Mobility screen resolutions
Summary: X.Org does not properly handle X700 Mobility screen resolutions
Status: RESOLVED DUPLICATE of bug 115283
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Beta 3
Hardware: x86 SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-28 20:21 UTC by William Beebe
Modified: 2005-09-06 06:34 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Xorg log (40.29 KB, text/plain)
2005-08-28 22:25 UTC, William Beebe 		Details
xorg configuration file (19.16 KB, text/plain)
2005-08-28 22:26 UTC, William Beebe 		Details
SAX2 xorg configuration file. (6.80 KB, text/plain)
2005-08-29 14:52 UTC, William Beebe 		Details
SAX2 based Xorg log. (43.01 KB, text/plain)
2005-08-29 14:53 UTC, William Beebe 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description William Beebe 2005-08-28 20:21:53 UTC 
System is a Gateway M680XL notebook with an ATI Mobility X700. Normal resolution
under Windows XP is 1680 x 1050 on a 17" screen. During second stage
installation of SuSE 10 Beta 3 the installation program properly detected the
graphics chip and allowed me to select the 1680 x 1050 resolution. However, when
the system finally attempted to boot into my account, the screen was totally black.

I downloaded the latest ATI driver for Linux, installed it, and used fglrxconfig
to create an xorg.conf file that finally allowed me to see the graphics screen.
Unfortunately the resolution is at 1280 x 1024.
Comment 1 Stefan Dirsch 2005-08-28 21:20:44 UTC 
Probably I cannot help about the ATI "fglrx" driver, but for the radeon driver 
I would need your /var/log/Xorg.0.log and /etc/X11/xorg.conf to have a look at 
it.
Comment 2 William Beebe 2005-08-28 22:25:59 UTC 
Created attachment 47914 [details]
Xorg log

Xorg.0.log that was requested.
Comment 3 William Beebe 2005-08-28 22:26:38 UTC 
Created attachment 47916 [details]
xorg configuration file

xorg.conf file that was requested.
Comment 4 Stefan Dirsch 2005-08-29 04:18:46 UTC 
Sorry, but these are the config and log files for the "fglrx" driver. Please 
reconfigure your gfx card with SaX2 "sax2 -r -a" to use the radeon driver 
instead and attach the new config and log files.
Comment 5 William Beebe 2005-08-29 14:52:07 UTC 
Created attachment 48023 [details]
SAX2 xorg configuration file.
Comment 6 William Beebe 2005-08-29 14:53:17 UTC 
Created attachment 48027 [details]
SAX2 based Xorg log.
Comment 7 Stefan Dirsch 2005-08-29 15:12:06 UTC 
Hmm ... nothing obvious I could find.
Comment 8 Matthias Hopf 2005-08-29 15:34:35 UTC 
The installation system uses the Vesa driver, which uses the BIOS for mode
setting. In your case (and probably in your case only) this works better than
the one from the radeon driver.

The radeon driver calculates modelines with the general timing formula (gtf),
but several LCDs need different timing information. Unluckily, I don't remember
how to calculate them. I have seen a laptop once that didn't work with gtf, but
worked with the other timing formula.

The fglrx driver is currently broken WRT modelines. That is, it cannot use
irregular / unusual settings like your 1680x1050 ATM.
Comment 9 Stefan Dirsch 2005-08-29 21:24:45 UTC 
Due to lack of this specific hardware we unfortunately cannot investigate this 
any further ATM. Setting to LATER therefore. What you can try is to use 
another color depth or resolution.
Comment 10 Stefan Dirsch 2005-09-06 06:34:32 UTC 
reopen to close as duplicate.
Comment 11 Stefan Dirsch 2005-09-06 06:34:56 UTC 

*** This bug has been marked as a duplicate of 115283 ***