Bug#522956: firmware-matrox: g200-warp firmware from firmware-linux kills system on 3d-acceleration
On Saturday 11 April 2009 04:10:25 Ben Hutchings wrote:
> On Tue, 2009-04-07 at 19:21 +0300, David Baron wrote:
> > Package: firmware-linux
> > Version: 0.16?
> > Severity: critical
> > Justification: breaks the whole system
> >
> > As of 2.6.29 kernels, this (nonfree?) code is broken out of the kernel's
> > driver and loaded from this package. The mga driver for Matrox g200 mila
> > card worked before when this separate firmware was not necessary.
>
> Sorry about this. No-one has previously reported the results of the
> patch to separate Matrox firmware so it may not have been tested before
> it was included in the 2.6.29 package.
>
Happens to the best of us.
I do not know whether this info is of help but this is from Xorg.0.log:
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
> > Now, any attempt to start a 3d-accelerated app (i.e. games like chromium
> > or ppracer) will freeze the entire system. Only logged error will be x
> > existed suddenly or such.
>
> If you have another computer on the local network, can you try enabling
> netconsole and capturing kernel messages up to the crash?
Unfortunately, I do not have this capability
> What happens if you uninstall the firmware? The result should be a
> fallback to software rendering.
This is what happens.
Reply to: