Bug#500495: Error "fire_buffer: DRM_VIA_PCICMD returned -22" on startup

[Sylvain Beucler <beuc@debian.org>]

On Tue, Jun 29, 2010 at 03:42:30PM +0100, Julien Cristau wrote:
> On Tue, Oct 21, 2008 at 20:23:21 +0200, Sylvain Beucler wrote:
> 
> > Hi,
> > 
> > I confirm that this is a S3 UniChrome:
> > 00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
> > 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)
> > 
> > So apparently I do have 3D support on this box... which I probably
> > didn't have in Etch :)
> > 
> > 
> > FYI, I retried with Driver "openchrome" :
> > 
> > $ titanion 
> > do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
> > Try adjusting the vblank_mode configuration parameter.
> > Load bgm: ttn1.ogg
> > Load bgm: ttn3.ogg
> > Load bgm: ttn2.ogg
> > Load SE: shot.wav
> > Load SE: explosion1.wav
> > Load SE: explosion2.wav
> > Load SE: explosion3.wav
> > Load SE: tractor.wav
> > Load SE: flying_down.wav
> > Load SE: player_explosion.wav
> > Load SE: flick.wav
> > Load SE: extend.wav
> > fire_buffer: DRM_VIA_CMDBUFFER returned -22
> > 
> > 
> > The error is less verbose, and is slightly different (previous was:
> > <some hex dump>
> > fire_buffer: DRM_VIA_PCICMD returned -22
> > )
> > 
> Does this still happen with mesa 7.7 or 7.8 and a recent kernel?

Hi,

Thanks for getting back to me.

Unfortunately I don't have time to spend on this oldish bug report at
the moment, especially since I use a modified hardware configuration.

Considering that most 3D apps just crash when the 3D card doesn't meet
all their requirements, and since this S3 card is very basic, I guess
we can close the bug as wontfix.

-- 
Sylvain