Bug 25746

Summary: r300g: Software fallback doesn't work running GL apps
Product: DRI Reporter: Laurent carlier <lordheavym>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: medium    
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
glxinfo output with gallium none

Description Laurent carlier 2009-12-21 11:07:33 UTC
Created attachment 32224 [details]
glxinfo output with gallium

When i try to run glxgears with gallium r300 driver and a rs880 chipset:
libGL: OpenDriver: trying /home/lordh/tstdri/tls/r600_dri.so
libGL: OpenDriver: trying /home/lordh/tstdri/r600_dri.so
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/lordh/.drirc: No such file or directory.
Mesa: Mesa 7.8-devel DEBUG build Dec 21 2009 09:22:08
Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable
Mesa: Initializing x86-64 optimizations
Mesa: 3Dnow! detected
*********************************WARN_ONCE*********************************
File radeon_tcl.c function radeon_run_tcl_render line 499
Rendering was 96 commands larger than predicted size. We might overflow  command buffer.
***************************************************************************
drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info.

--dmesg--
Forbidden register 0x1C14 in cs at 1
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
---------

--lspci--
01:05.0 VGA compatible controller: ATI Technologies Inc Device 9710 (prog-if 00 [VGA controller])
---------

All is from git (libdrm, xf86-video-ati, mesa) and up to date, with KMS running.
Comment 1 Corbin Simpson 2010-03-19 16:36:29 UTC
You were running r600, not r300g, and this bug's been fixed in the meantime. Closing as INVALID.

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.