Problems trying to run X on Intel DH77DF System

Kevin Oberman kob6558 at gmail.com
Tue May 29 04:38:48 UTC 2012


On Sun, May 27, 2012 at 10:19 AM, Bob Willcox <bob at immure.com> wrote:
> On Sun, May 27, 2012 at 10:02:42AM -0700, Kevin Oberman wrote:
>> On Sat, May 26, 2012 at 10:35 AM, Bob Willcox <bob at immure.com> wrote:
>> > Hi All,
>> >
>> > I have a new Intel DH77DF mini-ITX motherboard with a Core i5 3550 CPU and am
>> > having trouble getting X to run. This is on a 9-STABLE system just updated
>> > today via cvsup. There appear to be two obvious problems: the first is that X
>> > will no longer start (it used to with about a two week older 9-stable build);
>> > and the second is that once I attempt to start X I seem to lose the console.
>> > I'm left with a blue screen and am unable to switch to any other console
>> > (neither Alt-Fx nor Ctl-Alt-Fx do anything). The system is, however, still
>> > running as I can login via the network.
>> >
>> > My 'uname -a' output is this:
>> >
>> > FreeBSD yoda 9.0-STABLE FreeBSD 9.0-STABLE #4: Fri May 25 20:36:02 CDT 2012 ? ? bob at yoda:/usr/obj/usr/src/sys/YODA ?amd64
>> >
>> > I have attached my dmesg output, a copy of my xorg.conf file, and the output
>> > of 'pciconf -vl'.
>> >
>> > Anyone have any idea of what's going wrong, or what I can do to get X to work
>> > on this system?
>>
>> Are you using the KMS driver  (WITH_NEW_XORG)?
>
> I suspect not. Should I set that in /etc/make.conf?
>
>> Can you provide the Xorg.log?
>
> Attached.
>
>>
>> As far as vty switching, that is yet to be implemented with KMS.
>
> Hmm, ok. I can live without that...just a pain.

Well, vty switching with KMS is not an issue as you are not running
the Intel-KMS driver. You are running the VESA driver and, from you
logs, I suspect that VESA is broken on that system. I would suggest
trying to start X with no xorg.conf, though. It often is the best
choice these days. In any case, you probably do not want
"AllowEmptyInput" "Off".  See Warren Block's excellent write-up at
http://www.wonkity.com/~wblock/docs/html/aei.html. It explains the
correct thing to do, depending on whether you run hald or not.

Try re-building Xorg drivers, xorg-server, graphics/libGL,
graphics/libGLU graphics/libglut and graphics/libdrm with
WITH_NEW_XORG=YES
WITH_KMS=YES
added to /etc/make.conf. Hopefully I didn't miss anything here.Take a
look at the FreeBSD wiki page on the Intel GPU support project at
http:wiki.freebsd.org/Intel_GPU, but it is rather old and currently
being re-written, so a fair amount of the information is no longer
relevant (like getting various versions of code as they are now
committed to ports) and get the kernel patches for 9-Stable from
https://docs.google.com/open?id=0BxbPi2OX4_B-bFd6djZYeU9uYVE

Further instructions on the patch are in
http://osdir.com/ml/freebsd-x11/2012-04/msg00052.html.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6558 at gmail.com


More information about the freebsd-stable mailing list