Need help untangling Xorg behavior on Haswell board, KMS, etc. etc.

[John Reynolds]

On 7/19/2013 9:15 PM, Kevin Oberman wrote:
>
> Did you define WITH_KMS in /etc/make.conf? Did you build libdrm with 
> the KMS option?
yes, i did have that in there. I should have reported that. I'm pretty 
sure that libdrm was built with this option because at one point I just 
said screw it and blew away all packages and just started over to make 
sure I had ALL good components of Xorg 7.7. But I will double check.
>
> There have been reports of issues with Haswell GPUs, so it still may 
> not work with the current KMS code, but it is worth a try. (And it 
> would be appreciated if you could report the results.)
With my little "tester" account (as I don't want to inadvertently hose 
my own .kde4 setup or anything else) I was able to launch into KDE 
earlier this afternoon. But ... apparently it was not using the intel 
driver, but fell back to VESA.
>
> If all else fails, you can use VESA, but it will be very slow and may 
> have other issues.
Yes, upon further inspection, what I thought was "success" I think was a 
fall-back to using VESA. In my Xorg.0.log:

[ 17861.411] (II) intel: Driver for Intel Integrated Graphics Chipsets: 
i810,
         i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
         E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
           ....
         Haswell CRW Server (GT1), Haswell CRW Server (GT2),
         Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
         Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
         Iris(TM) Pro Graphics 5200, ValleyView PO board

So it did load the driver and at least print this out, but later on in 
the file after a bunch of:

[ 17861.959] drmOpenDevice: node name is /dev/dri/card0
[ 17861.959] Failed to change owner or group for file /dev/dri! 2: No 
such file or directory
[ 17861.959] Failed to change owner or group for file /dev/dri/card0! 2: 
No such file or directory
[ 17861.959] drmOpenDevice: open result is -1, (No such file or directory)
[ 17861.959] Failed to change owner or group for file /dev/dri/card0! 2: 
No such file or directory
[ 17861.959] drmOpenDevice: open result is -1, (No such file or directory)
[ 17861.959] drmOpenDevice: Open failed
[ 17861.959] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 17861.959] drmOpenDevice: node name is /dev/dri/card0

I see

[ 17861.961] (II) VESA(0): initializing int10
[ 17861.962] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 17861.964] (II) VESA(0): VESA BIOS detected
[ 17861.964] (II) VESA(0): VESA VBE Version 3.0
[ 17861.964] (II) VESA(0): VESA VBE Total Mem: 262080 kB
[ 17861.964] (II) VESA(0): VESA VBE OEM: Intel(R) HSW Mobile/Desktop 
Graphics Chipset Accelerated VGA BIOS
[ 17861.964] (II) VESA(0): VESA VBE OEM Software Rev: 0.0
[ 17862.017] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[ 17862.017] (==) VESA(0): RGB weight 888
[ 17862.017] (==) VESA(0): Default visual is TrueColor
[ 17862.017] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 17862.017] (II) Loading sub module "ddc"
[ 17862.017] (II) LoadModule: "ddc"
[ 17862.017] (II) Module "ddc" already built-in
[ 17862.017] (II) VESA(0): VESA VBE DDC supported
[ 17862.017] (II) VESA(0): VESA VBE DDC Level 2
[ 17862.017] (II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
[ 17862.029] (II) VESA(0): VESA VBE DDC read successfully
....

I don't know if this was simply a fall-back or if my xorg.conf file is 
telling it to use vesa. As I was saying, I used the file generated by 
Xorg -configure and it set things up for two monitors and it has two 
"Device" sections, one that uses the "intel" driver and one that uses 
"vesa." I have not tried using no configuration file just yet.

So, are there developers with the Haswell boards and it's just a matter 
of time before kinks get worked out? Do you suggest using no xorg.conf file?

Also, as reported once I go into X via 'startx' on a console there's no 
coming back out. If I try it is a hard wedge. I know that's being 
currently worked on. If there's any kernel module or kernel config 
option or something that I need to have in order to even remotely have a 
chance at making this GPU work, please let me know. As of this moment 
I'm just running GENERIC/amd64, but I plan on recompiling things going 
forward.

-jr