Re: Virtualbox 3D accel broken in xf86-video-nouveau 1.0.3

[Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

On Tue, Oct 30, 2012 at 01:30:53PM -0500, Pouar wrote:
>    On 10/30/2012 01:28 PM, Pouar wrote:
> 
>    On 10/28/2012 01:21 PM, Pouar wrote:
> 
>    On 10/28/2012 01:18 PM, Emil Velikov wrote:
> 
>      On Sun, 28 Oct 2012 01:15:54 -0000, Pouar wrote:
> 
>      there's a regression in the xf86-video-nouveau driver that came up
>      in
>      1.0.3 that causes the desktop to bounce around in virtualbox
>      whenever
>      using HW acceleration in cinnamon and gnome 3, but not in fallback
>      or
>      cinnamon 2d, only happens in virtualbox and not the host, I've
>      confirmed
>      it was the graphics driver on the host because it happened with the
>      1.0.3 driver but not the 1.0.2.
>      anyone else having this problem? I'm using GeForce GTX 560 Ti
> 
>      Hi Pouar
>      Can you open a bug, following these instructions [1]
>      Ideally you can try bisecting the issue - there are only 10 changes
>      that may have caused the issue
>      Cheers
>      Emil
>      [1] [1]http://nouveau.freedesktop.org/wiki/Bugs
> 
>      I just did
> 
>    --
>    Pouar
> 
>      by I just did I meant the bug report, not the bisecting, I have zero
>      experience with driver programming, much less graphics driver
>      programming, so I wouldn't know what to look for, I signed up for
>      this mailing list to keep track of the different driver issues and
>      bugs and their progress

You don't need to have any experience in driver programming to bisect this bug.

git clone git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau/
cd xf86-video-nouveau/
./autogen.sh
make

If you can compile successfully, do:

1) git bisect start xf86-video-nouveau-1.0.3 xf86-video-nouveau-1.0.2
2) make && sudo rm /usr/lib/xorg/modules/drivers/nouveau_drv.so && sudo cp src/.libs/nouveau_drv.so /usr/lib/xorg/modules/drivers
3) Restart X. Try to reproduce the bug.
4) If you can't reproduce it - do "git bisect good", if you can - do "git bisect bad".
5) Go to 2). After ~4 compiles it will tell you about first bad commit - this
is what we want to see.

Marcin