Bug 18993 - [ i965 gem] glsl demo noise fails
Summary: [ i965 gem] glsl demo noise fails
Status: VERIFIED DUPLICATE of bug 15217
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Gordon Jin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-09 23:47 UTC by lin, jiewen
Modified: 2009-01-15 17:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
log (46.02 KB, application/octet-stream)
2008-12-09 23:47 UTC, lin, jiewen 		Details
conf (3.76 KB, application/octet-stream)
2008-12-09 23:48 UTC, lin, jiewen 		Details
screenshot (131.22 KB, image/png)
2008-12-09 23:51 UTC, lin, jiewen 		Details
View All

Description lin, jiewen 2008-12-09 23:47:36 UTC 
Created attachment 20979 [details]
log

System Environment:
--------------------------

--Platform: 965
--Architecture(32-bit,64-bit,compatiblity): 32-bit
--2D driver: (xf86-video-intel-2.6-branch)                                     
6ca0d7e6ff05bff2bb88bfae64c2d79ac115bd38
--3D driver: (intel-2008-q4)154a9e5317f890618932cea0129ef887e16baf84
--DRM:shipped with kernel 2.6.28-rc6 for-airlied
--libdrm: (master)c99566fb810c9d8cae5e9cd39d1772b55e2f514c
--Xserver: (server-1.6-branch)b268458eab2f213ec14dfe8013aa714c187e3aab
--Kernel: 2.6.28-rc6 for-airlied

Bug detailed description:
--------------------------
start X and noise, the display is not correct. Details could be got in the
attachment screenshot.

Reproduce steps:
----------------
1. xinit &
2. ./noise
Comment 1 lin, jiewen 2008-12-09 23:48:31 UTC 
Created attachment 20980 [details]
conf
Comment 2 lin, jiewen 2008-12-09 23:51:25 UTC 
Created attachment 20981 [details]
screenshot

On the pic, the left window is using software rendering(normal), and the right one is direct rendering.
Comment 3 Gordon Jin 2008-12-10 05:14:27 UTC 

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

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.