Bug 22657 - [945GME] Compiz fails at high resolutions (2048x1152)
Summary: [945GME] Compiz fails at high resolutions (2048x1152)
Status: RESOLVED DUPLICATE of bug 22076
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Jesse Barnes
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-07 04:43 UTC by Matthias Blaicher
Modified: 2009-07-16 13:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg log, with switching resolution and active compiz. (439.86 KB, text/plain)
2009-07-07 04:43 UTC, Matthias Blaicher
no flags Details
Xorg log, in UMS and modedebug (201.76 KB, text/plain)
2009-07-08 01:11 UTC, Matthias Blaicher
no flags Details

Description Matthias Blaicher 2009-07-07 04:43:12 UTC
Created attachment 27452 [details]
Xorg log, with switching resolution and active compiz.

I am using Ubuntu 9.04 with the xorg-edgers PPA and a vanilla mainline Kernel 2.6.30 with active KMS from the Kernel PPA on an Asus EEE 901. According to the intel specs I set the virtual resolution to 2048x1536. I have an 23" LCD monitor with 2048x1152 pixels.

I now deactivated the internal LCD with the Ubuntu Display Prefrences and activated the Samsung LCD. It changes the resolution, but Compiz only show a screen with an artefact background with a normal moving mouse cursor. Reverting the display settings back to internal LCD or using smaller resolutions on the external display brings compiz back to live.

When I start compiz, it says:

mabl@dogmatix:~$ DISPLAY=:0 compiz
Checking for Xgl: not present. 
xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log 
Detected PCI ID for VGA: 
Checking for texture_from_pixmap: present. 
Checking for non power of two support: present. 
Checking for Composite extension: present. 
Checking screen 1Comparing resolution (2048x1152) to maximum 3D texture size (2048): Passed.
Checking for Software Rasterizer: Not present. 
Checking for nVidia: not present. 
Checking for FBConfig: present. 
Checking for Xgl: not present. 
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format


There seem to be no error messages on xorg.log. I used tail -f on the syslog and xorg logs, but the log is quiet.

mabl@dogmatix:~$ uname -a
Linux dogmatix 2.6.30-020630-generic #020630 SMP Wed Jun 10 09:45:40 UTC 2009 i686 GNU/Linux
Comment 1 Gordon Jin 2009-07-07 18:46:03 UTC
This should be supported. But I don't have monitor with 2048 resolution (our 24# is 1920x1200) to validate this.

How about if disable compiz?
Comment 2 MaLing 2009-07-07 22:31:38 UTC
(In reply to comment #1)
> This should be supported. But I don't have monitor with 2048 resolution (our
> 24# is 1920x1200) to validate this.
> How about if disable compiz?

Could you please try in UMS mode, then upload log file with modedebug option on?

Thanks
Ma Ling
Comment 3 Matthias Blaicher 2009-07-08 01:11:35 UTC
Created attachment 27489 [details]
Xorg log, in UMS and modedebug
Comment 4 Matthias Blaicher 2009-07-08 01:12:46 UTC
> How about if disable compiz?
Works like a charm without it. Quiet astonished how well it runs. 

> Could you please try in UMS mode, then 
> upload log file with modedebug option on?

I assume UMS stands for Userspace Mode Setting, right? So I deactivated KMS,
set the modedebug option and started the system without an external monitor
connected. I then connected the monitor and deactivated the internal LCD. =>
Same result, mostly black screen with some artefacts and a normal mouse cursor. 
Comment 5 Michael Fu 2009-07-08 18:30:50 UTC
Gordon, this doesn't sounds like a modesetting bug. you could either leave it for ma ling to figure out later or give it to jesse or eric for quick fix. you decide.
Comment 6 Gordon Jin 2009-07-08 18:57:58 UTC
agree this is not modeset bug. Jesse, could you take a look?
Comment 7 jayprakash 2009-07-16 13:34:52 UTC
Duplicate of bug https://bugs.freedesktop.org/show_bug.cgi?id=22076

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


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.