Date: Sat, 23 Oct 2010 18:05:46 +0300 From: Andrey Kosachenko <andrey.kosachenko@gmail.com> To: freebsd-x11@freebsd.org Subject: Re: Fw: Deignoring ports/x11-drivers/xf86-video-intel29 Message-ID: <4CC2F9CA.5040501@gmail.com> In-Reply-To: <4CC2F98F.7030307@gmail.com> References: <4CBDD30E.3030803@pcbsd.org> <20101020013910.e2ad077c.daniel.bilik@neosystem.cz> <20101020020557.477cd211.daniel.bilik@neosystem.cz> <4CC1B43C.6010809@pcbsd.org> <4CC2F98F.7030307@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23.10.2010 18:04, Andrey Kosachenko wrote: > Hi, > > On 22.10.2010 18:56, Kris Moore wrote: > >> Well, your patches work. I just had to modify the intel-legacy Makefile >> to use autoconf:267 not 268, since 268 is broken in ports :) >> >> After that it compiled / installed fine. Working is another matter >> though... On my newer Pineview laptop X will startup with the intel >> driver, and run for about 5 seconds before going to a corrupted screen. >> Chris Wilson the original author had posted something last month about a >> buffer issue he was working on, its possible that is the culprit here, >> but I'm not certain. Tried legacy driver in question here (against ironlake chip): it is also compiled/installed. However as soon as X starts blank screen appears and seems only reboot allows to get laptop functional. I.e. there is no way to kill X or to switch to another console (though machine is available via network connection). Even after logging in remotely and killing X screen remains blank. Turning DRI off (Option DRI "false", commenting out dri, dri2, glx) didn't help. There is nothing suspicious in logs. -- WBR, Andrey Kosachenko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CC2F9CA.5040501>