[ATI][KMS][R300] Compiz boots to white screen with Mesa 7.6+git

Bug #411451 reported by Angel Guzman Maeso
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

Testing the new kms ppa of bryce for a ATI Mobility Radeon X600 (rv 380) on Karmic.

$ compiz --replace
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 (1440x900) to maximum 3D texture size (2048): Passed.
Checking for Software Rasterizer: Not present.
Checking for nVidia: not present.
Checking for FBConfig: present.
running under gnome seesion, checking for gnomecompat
Checking for Xgl: not present.
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12

The screen going to white and nothing happens.

Also the glxgears perfomance is worse (before 9500 fps, now 4000 fps).

ProblemType: Bug
Architecture: i386
CurrentDmesg:
 [ 205.430240] usbcore: registered new interface driver wacom
 [ 205.430245] wacom: v1.51:USB Wacom Graphire and Wacom Intuos tablet driver
 [ 205.657556] lib80211_crypt: registered algorithm 'WEP'
 [ 214.860011] eth4: no IPv6 routers present
 [ 776.692023] pan1: no IPv6 routers present
Date: Mon Aug 10 16:19:31 2009
DistroRelease: Ubuntu 9.10
MachineType: TOSHIBA 00000000000000000000
Package: xorg 1:7.4+3ubuntu5
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-5-generic root=UUID=590c22cb-5c99-4270-a154-4e6df62d1b4c ro locale=es_ES vga=792 radeon.modeset=1
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090805.ac3de85e-0ubuntu1
 libdrm2 2.4.12+git20090806.d74c67fb-0ubuntu1
 xserver-xorg-video-intel 2:2.8.0-0ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090805.bd03977e-0ubuntu2
SourcePackage: xorg
Uname: Linux 2.6.31-5-generic i686
dmi.bios.date: 03/16/2006
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.60
dmi.board.name: EBQ10
dmi.board.vendor: TOSHIBA
dmi.board.version: Null
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd03/16/2006:svnTOSHIBA:pn00000000000000000000:pvr0000000000000000:rvnTOSHIBA:rnEBQ10:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: 00000000000000000000
dmi.product.version: 0000000000000000
dmi.sys.vendor: TOSHIBA
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-5-generic

[lspci]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M24 [Radeon Mobility X600] [1002:5462]
     Subsystem: Toshiba America Info Systems Device [1179:ff04]

---
Architecture: i386
DistroRelease: Ubuntu 10.04
DkmsStatus:
 vboxnetflt, 3.1.8, 2.6.32-2-generic, i686: installed
 vboxnetadp, 3.1.8, 2.6.32-2-generic, i686: installed
 vboxdrv, 3.1.8, 2.6.32-2-generic, i686: installed
GdmLog: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: /home/shakaran/.gtkrc-2.0:8: Unable to find include file: ".themes/nautilus/nautilus.rc"
MachineType: TOSHIBA 00000000000000000000
Package: mesa (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-2-generic root=UUID=590c22cb-5c99-4270-a154-4e6df62d1b4c ro locale=es_ES splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-2.2-generic
Tags: lucid lucid
Uname: Linux 2.6.32-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy kvm lpadmin netdev plugdev powerdev sambashare scanner video
dmi.bios.date: 03/16/2006
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.60
dmi.board.name: EBQ10
dmi.board.vendor: TOSHIBA
dmi.board.version: Null
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd03/16/2006:svnTOSHIBA:pn00000000000000000000:pvr0000000000000000:rvnTOSHIBA:rnEBQ10:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: 00000000000000000000
dmi.product.version: 0000000000000000
dmi.sys.vendor: TOSHIBA
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-2-generic

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :
Bryce Harrington (bryce)
affects: xorg (Ubuntu) → mesa (Ubuntu)
Bryce Harrington (bryce)
description: updated
Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

With the yesterday [1] update the glxgears performance is back, but I dont have compiz yet.

[1] https://lists.ubuntu.com/archives/karmic-changes/2009-August/006499.html

Bryce Harrington (bryce)
Changed in mesa (Ubuntu):
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

You've got a lot of extraneous settings in your xorg.conf which may be influencing the behavior here. Please move your xorg.conf aside and re-test and see if you get the same behavior.

Also btw there is newer mesa available in xorg-edgers, so it would be good if you would test that, as it's got a ton of ati fixes included.

Changed in mesa (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

I dont have xorg.conf file anymore (because you said that I remove in other report).

I using the last update of mesa 7.6.0~git20090817.7c422387-0ubuntu1 and compiz works, but it is useless because it is extremely slow. If I move a window to the other corner of screen it cost 2 o 3 seconds to wait.

Also I get a fatal error with compiz if metacity composite is enabled with Ubuntu Tweak:
$ compiz --replace
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: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Checking screen 1Comparing resolution (1440x900) to maximum 3D texture size (2048): Passed.
Checking for Software Rasterizer: Not present.
Checking for nVidia: not present.
Checking for FBConfig: present.
running under gnome seesion, checking for gnomecompat
Checking for Xgl: not present.
/usr/bin/compiz.real (core) - Error: Could not acquire compositing manager selection on screen 0 display ":0.0"
/usr/bin/compiz.real (core) - Fatal: No manageable screens found on display :0.0

If I disable, then works, but I get a warning video:
$ compiz --replace
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: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Checking screen 1Comparing resolution (1440x900) to maximum 3D texture size (2048): Passed.
Checking for Software Rasterizer: Not present.
Checking for nVidia: not present.
Checking for FBConfig: present.
running under gnome seesion, checking for gnomecompat
Checking for Xgl: not present.
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format

Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

I tested with the lastest updates of mesa, same behaviour. Do you need something more for remove incomplete status?

Revision history for this message
Bryce Harrington (bryce) wrote :

Your Xorg.0.log when running without the xorg.conf would be good to see.

We'll focus this bug on the white screen issue. We don't really care about fps in glxgears.

Changed in mesa (Ubuntu):
status: Incomplete → Confirmed
summary: - [ATI][KMS][Karmic][R300] Compiz dont work with Mesa 7.6
+ [ATI][KMS][R300] Compiz boots to white screen with Mesa 7.6+git
Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

The white screen issue is gone. But Compiz is unusable (extremely slow move with windows and flickering). I will make a video if you need it. I attach my Xorg.0.log.

Revision history for this message
Dominik (dominalien) wrote :

I am also experiencing this issue on R200 hardware.

In Jaunty, when enabling compositing, the system looks for 3 instances of texture_from_pixmap in the output from glxinfo. It's there.

On Karmic, there are only 2 instances of this in glxinfo output. Compositing in KDE is horribly slow, in Gnome a bit better (I think) but still slow and interestingly, in both KDE and Gnome enabling compositing causes the wallpaper to go all black.

Revision history for this message
Dominik (dominalien) wrote :

Just to be clear: this is with stock ati drivers from the repos.

Revision history for this message
Twisted Lucidity (lucidlytwisted) wrote :

I have an ATI Radeon Mobility 9000 (rv250) and have noted a serious drop in performance with Compiz in Karmic.
The whole setup seems sluggish and the Benchmark utility (not a rigorous test, I know) reports 11fps when it used to be 100+fps under Jaunty (an basic Intel chipset system I have reports around 30fps).
The ATI system is a fresh install, the Intel is an upgrade.
Happy to provide any logs or configs...not sure if the upgrade Intel system still has an xorg.conf, I'll need to check (not sure if it would make any difference anyway).

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Suspecting this is fixed in lucid. If not, reopen.

Changed in mesa (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Angel Guzman Maeso (shakaran) wrote :
Download full text (6.0 KiB)

This bug is not fixed. Now appear:
$ compiz --replace
WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!
WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug!

And the screen is deeply slow. 3 seconds for move a pixel in a window. Also, I have support for Open GL 1.4 for the moment.

$ 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_import_context, GLX_EXT_texture_from_pixmap,
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
    GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control,
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
    GLX_SGIX_visual_select_group
client glx vendor string: Mesa Project and 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_MESA_copy_sub_buffer,
    GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method,
    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
OpenGL vendor string: DRI R300 Project
OpenGL renderer string: Mesa DRI R300 (RV380 5462) 20090101 x86/MMX/SSE2 TCL
OpenGL version string: 1.5 Mesa 7.7.1-DEVEL
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program,
    GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture,
    GL_ARB_occlusion_query, GL_ARB_point_parameters, GL_ARB_provoking_vertex,
    GL_ARB_shadow, GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp,
    GL_ARB_texture_compression, GL_ARB_texture_cube_map,
    GL_ARB_texture_env_add, GL_ARB_texture_env_combine,
    GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3,
    GL_MESAX_texture_float, GL_ARB_texture_mirrored_repeat,
    GL_ARB_texture_rectangle, GL_ARB_transpose_matrix,
    GL_ARB_vertex_array_bgra, GL_ARB_vertex_buffer_object,
    GL_ARB_vertex_program, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra,
    GL_EXT_blend_color, GL_EXT_blend_equation_separate,
    GL_EXT_blend_func_separate, GL_EXT_blend_logic_op, GL_EXT_blend_minmax,
    GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_convolution,
    GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord,
    GL_EXT_gpu_program_parameters, GL_EXT_histogram, GL_EXT_multi_draw_arrays,
    GL_EXT_packed_d...

Read more...

Changed in mesa (Ubuntu):
status: Fix Released → New
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Angel,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 411451

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 411451 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/411451

Changed in mesa (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in mesa (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Angel Guzman Maeso (shakaran) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Angel Guzman Maeso (shakaran) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : GdmLog1.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : GdmLog2.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : Lspci.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : Lsusb.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : PciDisplay.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : ProcModules.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : UdevDb.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : UdevLog.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : XorgLog.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : XorgLogOld.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : Xrandr.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : glxinfo.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : monitors.xml.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : setxkbmap.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : xdpyinfo.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote : xkbcomp.txt

apport information

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

Restoring bug status with new information attached

Changed in mesa (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

Sorry for delay.

Trying with compiz now, I have some white flickers when starts and then it is ok. The performace is some better, but it also is slow.

By other way, I have some fatal warnings when init compiz:

$ compiz --replace
WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!
WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug!

This is a bug wih glXCreatePixMap implementation.

Revision history for this message
Vikram Dhillon (dhillon-v10) wrote : Re: [Ubuntu-x-swat] [Bug 411451] Re: [ATI][KMS][R300] Compiz boots to white screen with Mesa 7.6+git

On Sat, May 29, 2010 at 12:02:07AM -0000, Angel Guzman Maeso wrote:
> Sorry for delay.
>
> Trying with compiz now, I have some white flickers when starts and then
> it is ok. The performace is some better, but it also is slow.
>
> By other way, I have some fatal warnings when init compiz:
>
> $ compiz --replace
> WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!
> WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug!
>
> This is a bug wih glXCreatePixMap implementation.
>
> --
> [ATI][KMS][R300] Compiz boots to white screen with Mesa 7.6+git
> https://bugs.launchpad.net/bugs/411451
> You received this bug notification because you are a member of Ubuntu-X,
> which is subscribed to mesa in ubuntu.
>

Bryce, would it make sense to report this upstream? or will this issue be fixed here then.

--
Regards,
Vikram Dhillon

Revision history for this message
Oibaf (oibaf) wrote :

This was probably fixed since the switch to r300 gallium driver. Reopen if it's still an issue.

Changed in mesa (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.