|
Bugzilla – Full Text Bug Listing |
| Summary: | X.Org does not properly handle X700 Mobility screen resolutions | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | William Beebe <wbeebe> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Xorg log
xorg configuration file SAX2 xorg configuration file. SAX2 based Xorg log. |
||
|
Description
William Beebe
2005-08-28 20:21:53 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. Created attachment 47914 [details]
Xorg log
Xorg.0.log that was requested.
Created attachment 47916 [details]
xorg configuration file
xorg.conf file that was requested.
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. Created attachment 48023 [details]
SAX2 xorg configuration file.
Created attachment 48027 [details]
SAX2 based Xorg log.
Hmm ... nothing obvious I could find. 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. 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. reopen to close as duplicate. *** This bug has been marked as a duplicate of 115283 *** |