Bug 20019 - [KMS] Framebuffer timing problems on G31
Summary: [KMS] Framebuffer timing problems on G31
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Jesse Barnes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-09 09:45 UTC by Pantelis Koukousoulas
Modified: 2017-07-24 23:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
get-edit | parse-edid output (2.04 KB, text/plain)
2009-02-10 11:14 UTC, Pantelis Koukousoulas
no flags Details
xrandr -q --verbose under modesetting (6.57 KB, text/plain)
2009-02-11 01:47 UTC, Pantelis Koukousoulas
no flags Details
xrandr -q --verbose without KMSb (3.90 KB, text/plain)
2009-02-11 01:48 UTC, Pantelis Koukousoulas
no flags Details
A patch that fixes the problem for me (1.10 KB, patch)
2009-03-10 12:23 UTC, Pantelis Koukousoulas
no flags Details | Splinter Review

Description Pantelis Koukousoulas 2009-02-09 09:45:51 UTC
When using KMS on a G31, the timings seem incorrect which results into a display like this: (forgive lousy ascii art, hope it renders ok):

               ---------------------------------------------
               |                                           |
  Starting serv|ice foo..                                 [|OK]
               |                                           |
               ...                                        ...
               |___________________________________________|

I.e., lots of text is invisible on the edges of the screen. Unfortunately, the monitor's auto-set doesn't help this situation much.

I 'll be happy to provide any additional information that might be of use.

lspci excerpt:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [
8086:27d0] (rev 01)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 [
8086:27d2] (rev 01)


xrandr -q --verbose excerpt (on the same machine with another kernel)

Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1680 x 1680
VGA connected 1680x1050+0+0 (0x3c) normal (normal left inverted right x axis y axis) 4
74mm x 296mm
        Identifier: 0x3b
        Timestamp:  74803
        Subpixel:   unknown
        Clones:
        CRTC:       0
        CRTCs:      0 1
        EDID_DATA:
                00ffffffffffff001e6d6256992d0300
                011201036a2f1e78ead425a455499b27
                135054a76b80950f950081808140714f
                0101010101017c2e90a0601a1e403020
                3600da281100001a21399030621a2740
                68b03600da281100001c000000fd0038
                4b1c530f000a202020202020000000fc
                004c32323557000a202020202020001a
  1680x1050 (0x3c)  119.0MHz +HSync -VSync *current +preferred
        h: width  1680 start 1728 end 1760 total 1840 skew    0 clock   64.7KHz
        v: height 1050 start 1053 end 1059 total 1080           clock   59.9Hz
  1680x1050 (0x3d)  146.2MHz -HSync +VSync
        h: width  1680 start 1784 end 1960 total 2240 skew    0 clock   65.3KHz
        v: height 1050 start 1053 end 1059 total 1089           clock   60.0Hz
Comment 1 Pantelis Koukousoulas 2009-02-10 11:14:48 UTC
Created attachment 22770 [details]
get-edit | parse-edid output
Comment 2 Pantelis Koukousoulas 2009-02-11 01:47:52 UTC
Created attachment 22798 [details]
xrandr -q --verbose under modesetting
Comment 3 Pantelis Koukousoulas 2009-02-11 01:48:48 UTC
Created attachment 22799 [details]
xrandr -q --verbose without KMSb
Comment 4 Pantelis Koukousoulas 2009-03-10 12:23:29 UTC
Created attachment 23733 [details] [review]
A patch that fixes the problem for me
Comment 5 Pantelis Koukousoulas 2009-03-12 08:58:14 UTC
Since the attached patch hit mainline, I 'm closing the bug. Thanks airlied for picking up the patch and pushing to Linus :)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.