Bug 26719 - [810] Resolution keeps to 800x600 only
Summary: [810] Resolution keeps to 800x600 only
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.5 (2009.10)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-23 13:31 UTC by Timofonic
Modified: 2012-07-22 09:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (18.90 KB, text/plain)
2010-02-23 13:34 UTC, Timofonic
no flags Details
Xorg log (20.22 KB, text/plain)
2010-02-23 13:34 UTC, Timofonic
no flags Details

Description Timofonic 2010-02-23 13:31:56 UTC
Bug description:

Since 2.10, I'm unable to use the Intel driver properly. Resolution keeps to 800x600 only.

I was able to use a 1920x1200 resolution under this configuration (I didn't believe it the first time!).

I know this is a somewhat old version of the Intel Graphics chip, but I'm unable to get newer hardware right now and this system works quite stable so I can recycle it in different tasks in the future.

A dev from the IRC channel said me UMS for this chip wasn't removed, but in practical sense it seems to not work properly.

Please say me what info do I need to submit for helping in matching the bug and solving it.

System environment: 
-- chipset: intel 810e
-- system architecture: 32-bit
-- xf86-video-intel: 2.10
-- xserver: 1.7.5
-- mesa: 7.7
-- libdrm: 2.4.18
-- kernel: 2.6.32
-- Linux distribution: Archlinux
-- Machine or mobo model: Dell OptiPlex GX110. Pentium III 733 MHz 128MB RAM
-- Display connector: VGA

Reproducing steps:

Additional info:

% xrandr
Screen 0: minimum 640 x 480, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
   800x600        60.0*    56.0  
   640x480        60.0
Comment 1 Timofonic 2010-02-23 13:34:08 UTC
Created attachment 33512 [details]
dmesg
Comment 2 Timofonic 2010-02-23 13:34:41 UTC
Created attachment 33513 [details]
Xorg log
Comment 3 Timofonic 2010-02-23 13:35:54 UTC
% xrandr --verbose
Screen 0: minimum 640 x 480, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 (0x69) normal (normal) 0mm x 0mm
        Identifier: 0x68
        Timestamp:  889624
        Subpixel:   unknown
        Clones:    
        CRTC:       0
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter: 
  800x600 (0x69)   28.8MHz *current
        h: width   800 start    0 end    0 total  800 skew    0 clock   36.0KHz
        v: height  600 start    0 end    0 total  600           clock   60.0Hz
  800x600 (0x6a)   26.9MHz
        h: width   800 start    0 end    0 total  800 skew    0 clock   33.6KHz
        v: height  600 start    0 end    0 total  600           clock   56.0Hz
  640x480 (0x6b)   18.4MHz
        h: width   640 start    0 end    0 total  640 skew    0 clock   28.8KHz
        v: height  480 start    0 end    0 total  480           clock   60.0Hz
Comment 4 Timofonic 2010-02-23 13:50:44 UTC
Forgot to mention it also fails under 2.9 and the actual Xorg version.

% lspci | grep VGA
00:01.0 VGA compatible controller: Intel Corporation 82810E DC-133 (CGC) Chipset Graphics Controller (rev 03)
Comment 5 Gordon Jin 2010-02-23 17:21:33 UTC
So what's the working version? Is this a kernel regression?
Comment 6 Eugeni Dodonov 2011-09-08 15:56:38 UTC
This issue is affecting a hardware component which is not being actively worked on anymore.

Moving the assignee to the dri-devel list as contact, to give this issue a better coverage.
Comment 7 Chris Wilson 2012-07-22 09:48:11 UTC
(==) intel(0): Will alloc AGP framebuffer: 8192 kByte
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(II) intel(0): Monitor0: Using default hsync range of 31.50-37.90 kHz
(II) intel(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz

8 MiB: 1920x1080x4 just fits in (a few hundred bytes to spare).  However, 1920x1200 does not. So you will need to increase Option "VideoRam" "16384".

The second problem is that your monitor does not offer a 1920x1200 mode, so you will need to add that modeline to your xorg.conf. (Or check to see if a more recent xserver adds it back for). And if it did, it will be out of range of the default monitor settings so you will need to specify those above as well.

All in all, I think the issue is that the sanity checks became slightly more paranoid and for the default fb allocation to be reduced. I don't think this is an outright bug per se, and the only fix would be to move i810 to KMS/GEM so that we can actually allocate and manage memory dynamically.


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.