Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Calling glxgears gives: > glxgears drmRadeonCmdBuffer: -22 (exiting) [drm] Initialized radeon 1.24.0 20060225 on minor 0 [drm] Setting GART location based on new memory map [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs [drm] Setting GART location based on new memory map [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs [drm:r300_emit_3d_load_vbpntr] *ERROR* Offset failed range check (k=0 i=2) while processing 3D_LOAD_VBPNTR packet. [drm:r300_emit_packet3] *ERROR* r300_emit_raw_packet3 failed [drm:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet3 failed [drm] Setting GART location based on new memory map [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs glxinfo: OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI R300 20040924 x86/MMX/SSE2 TCL OpenGL version string: 1.3 Mesa 6.5 Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.6.0-1 kernel 2.6.16-1.2141 glx-utils-6.5-4 How reproducible: always. run given kernel, start glxgears. Steps to Reproduce: 1. 2. 3. Actual results: glxgears gives error. Expected results: glxgears works as expected. Additional info: Xorg.log: gives no error, everything looks fine. kernel from development.
can you dupe this to #188228
Same problem with: mesa-libGLU-devel-6.4.2-6 mesa-libGL-devel-6.5-4 mesa-libGL-6.5-4 mesa-libGLU-6.4.2-6 xorg-x11-drv-ati-6.6.0-1 kernel-2.6.16-1.2147self_FC5
Created attachment 128115 [details] Xorg.log with named packages Xorg.log with named packages
No work here?
Is this fixed for MESA and R300 graphic hw?
Will this be fixed in the mesa libraries? I think it's no a problem from the kernel?
Please can anybody fix this..
Same problem in kernel-2.6.16-1.2122_FC5: (WW) RADEON(0): [dri] limiting video memory to one aperture of 65536K (WW) RADEON(0): [dri] detected radeon kernel module version 1.22 but 1.23 or newer is required for full memory mapping. Please use radeon kernel module 1.24 in kernels lower than -2147 (rawhide).
See also bug #188228. With: - kernel 2.6.16..2208 (radeon drm: "Initialized radeon 1.24.0 20060225..") - mesa-6.5 update with cvs sources from may 26, 2006 - xorg-x11-drv-ati-6.6.0-1 this works for me. Looks like mesa from RawHide doesn't contain the latest cvs code. R300 Chipset, ATI Technologies Inc M24 1P [Radeon Mobility X600], device id 0x3150.
With latest kernel/mesa/xorg updates from rawhide glgears *IS* working for me, I seem to have issues with compiz not decorating windows like a windowmanager should, but I have wibbly tooltips and a spinning cube desktop, will report thesde elsewhere ...
Hi Please give full version/ package name that you use. Please try to give output of glxgears and xengine with Xorg.conf. Try to use DRI/DRM with video overlay (xosd) with running ant-demo from xscreensaver.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
With this kernel and/ or mesa-6.5.1 this is not a problem any more for me.