Bug 22767 - Wrong colors in softwate rendering
Summary: Wrong colors in softwate rendering
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: unspecified
Hardware: PowerPC Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-14 12:24 UTC by Andrey Gusev
Modified: 2009-11-23 11:11 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Screen shot of glxgears (11.70 KB, image/png)
2009-07-14 12:25 UTC, Andrey Gusev
Details
glxgears in 15 bpp mode on big-endian architecture (6.69 KB, image/png)
2009-08-10 02:53 UTC, Andrew Randrianasulu
Details
glxinfo in 15 bpp mode (13.95 KB, text/plain)
2009-08-10 02:53 UTC, Andrew Randrianasulu
Details
glxinfo in 24 bpp mode (18.32 KB, text/plain)
2009-08-10 02:54 UTC, Andrew Randrianasulu
Details
x.org log (9.12 KB, text/plain)
2009-08-10 02:54 UTC, Andrew Randrianasulu
Details
xorg.conf (1.95 KB, text/plain)
2009-08-10 02:57 UTC, Andrew Randrianasulu
Details

Description Andrey Gusev 2009-07-14 12:24:59 UTC
I have wrong colors in software rendering. Most likely it is byteorder problem. Better looks screen shot. I tried nv and nouveau driver, both have same drawing. Related bugs:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/366755
http://bugs.freedesktop.org/show_bug.cgi?id=22017
My software:
Package: libgl1-mesa-glx
Version: 7.4.4-1
Versions of packages libgl1-mesa-glx depends on:
ii  libc6                         2.9-12     GNU C Library: Shared libraries
ii  libdrm2                       2.4.11-1   Userspace interface to kernel DRM 
ii  libx11-6                      2:1.2.1-1  X11 client-side library
ii  libxdamage1                   1:1.1.1-4  X11 damaged region extension libra
ii  libxext6                      2:1.0.4-1  X11 miscellaneous extension librar
ii  libxfixes3                    1:4.0.3-2  X11 miscellaneous 'fixes' extensio
ii  libxxf86vm1                   1:1.0.2-1  X11 XFree86 video mode extension l

Versions of packages libgl1-mesa-glx recommends:
ii  libgl1-mesa-dri               7.4.4-1    A free implementation of the OpenG

andrey@power-debian:~$ glxinfo 
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, 
    GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, 
    GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.4.4
OpenGL shading language version string: 1.20

My hardware:
0000:00:10.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 420] (rev a3) (prog-if 00 [VGA controller])
	Subsystem: nVidia Corporation Device 0008
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 248 (1250ns min, 250ns max)
	Interrupt: pin A routed to IRQ 48
	Region 0: Memory at 91000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at 98000000 (32-bit, prefetchable) [size=128M]
	Region 2: Memory at f1000000 (32-bit, prefetchable) [size=512K]
	Expansion ROM at 90000000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [44] AGP version 2.0
		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
		Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
Comment 1 Andrey Gusev 2009-07-14 12:25:47 UTC
Created attachment 27686 [details]
Screen shot of glxgears
Comment 2 Michel Dänzer 2009-07-15 04:41:34 UTC
> I tried nv and nouveau driver, both have same drawing.

If you were using the nouveau 3D driver as well, there is yet another bug in that which needs to be repported and tracked separately.
Comment 3 Andrew Randrianasulu 2009-08-10 02:51:33 UTC
Not sure if i hit same bug, but i have wrong colors in gears in X over fbdev on SGI O2.


I have mesa  self-compiled from git master, commit 483a7916d1c93d1edf125dc671dcfbff42a9fc5e. In 15 bpp mode i see strange colors in gears.

Comment 4 Andrew Randrianasulu 2009-08-10 02:53:05 UTC
Created attachment 28471 [details]
glxgears in 15 bpp mode on big-endian architecture
Comment 5 Andrew Randrianasulu 2009-08-10 02:53:43 UTC
Created attachment 28472 [details]
glxinfo in 15 bpp mode
Comment 6 Andrew Randrianasulu 2009-08-10 02:54:22 UTC
Created attachment 28473 [details]
glxinfo in 24 bpp mode
Comment 7 Andrew Randrianasulu 2009-08-10 02:54:46 UTC
Created attachment 28474 [details]
x.org log
Comment 8 Andrew Randrianasulu 2009-08-10 02:57:47 UTC
Created attachment 28475 [details]
xorg.conf
Comment 9 Michel Dänzer 2009-11-23 11:11:34 UTC
Fixed in Git commit 601edbef172f3106b9e4c0b96b24d8b5eea8d2a5 .  The fix should get into the upcoming 7.6.1 and 7.7 releases.


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.