Hey, Op 23-05-12 21:09, Sven Joachim schreef: > On 2012-05-23 20:47 +0200, Maarten Lankhorst wrote: > >> Op 23-05-12 17:34, Sven Joachim schreef: >>> On 2012-05-23 10:31 +0200, Maarten Lankhorst wrote: >>> >>>> commit c20b687c6f92abb63eb019c1778cb5b465ac1b57 >>>> Author: Maarten Lankhorst <m.b.lankho...@gmail.com> >>>> Date: Wed May 23 10:08:34 2012 +0200 >>>> >>>> Add 02-drm-nouveau-newabi.patch to build with old libdrm >>> This does not really describe the patch accurately, rather the >>> new libdrm_nouveau is pulled into the source tree and the driver >>> ges statically linked with it. >>> >>>> + awful hack to remove dependency on libdrm_nouveau >>> Awful hack indeed, and it does not work for me. See the attached log >>> file, where the driver fails to initialize acceleration and the X server >>> crashes. >>> >> The failing line seems to be this: >> >> (EE) NOUVEAU(0): Failed to allocate scratch buffer: -22 >> >> aka EINVAL >> >> Is there anything in dmesg that indicates where it comes from? > No. The message only appears once in the driver's source, though; so I > conclude that nouveau_bo_new() must have returned 0 and nouveau_bo_map() > returned -EINVAL at the beginning of NVAccelCommonInit(). > Nah, both could have failed. It would be interesting to know which of the 2 failed, and where.
3 probable candidate calls that would fail: drmCommandWriteRead in abi16_bo_init called from nouveau_bo_new mmap in nouveau_bo_map drmCommandWrite in nouveau_bo_wait called from bo_map. ~Maarten -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fbd38c8....@canonical.com