Date: Sun, 18 Jul 2010 21:51:00 +0300 From: Andrey Kosachenko <andrey.kosachenko@gmail.com> To: freebsd-x11@freebsd.org Subject: Re: intel driver Message-ID: <4C434D14.8050501@gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, On 22.06.2010 17:27, Robert Noland wrote: > I was hoping that the 2.9.1 driver would work on the Ironlakes without > drm support, but I've had multiple failure reports. A lot of work is > required to try and de-linuxify and get newer drivers working. (Read GEM > and KMS kernel support) I don't have an Ironlake to test with which > complicates matters even further, on top of my current time constraints. > It is quite possible that the current failure is something simple, but I > really can't say for sure at the moment. I'd like to revive this since the issue is topical for the 'happy' owners of IGDNG. I observed the same issue as the Jaap Boender. Additional data can be found bellow: Xorg.0.log: http://pastebin.org/402959 dmesg: http://pastebin.org/402960 pciconf -lv: http://pastebin.org/402963 I've also noticed that guys from linux world stuck with similar issu some time ago and they told that this simple patch fixed it for them: http://people.canonical.com/~hzhang/554569/i915-fix-ironlake-edp-panel-setup-v2.patch So, I'm not sure, but it could be connected somehow with embedded Display Port (eDP) timings handling. And that made me think that there is a slight chance to get it worked with intel-2.9.1 driver (w/o acceleration but it is way better then vesa anyway). Unfortunately due to the lack of knowledge I could not find relevant piece of code in freebsd's sources to give it a try. Could smb. point me where it is worth to dig (i.e. prove/decline that it will/won't work). Thanks in advance. --- WBR, Andrey Kosachenko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C434D14.8050501>