Haswell GPU and/or display issues?

Sun Sep 18 23:33:16 UTC 2016

On Sun, Sep 18, 2016 at 6:34 AM, Tyler Stachecki <stachecki.tyler at gmail.com>
wrote:

> Hi,
>
> I am currently giving FreeBSD 11 RC3 a test drive and can't get X11 to
> play ball.
>
> At first, Xorg reported that it couldn't find a display. I found that
> only Haswell GT1 and GT2 PCI IDs are present, so I added a PCI ID
> entry for my GPU (Haswell GT3). I assume it's supported and just
> missing entries?
>
> After adding PCI IDs for my GPU (Haswell GT3 mobile/Iris 5100), I was
> able to get the kernel to get drm to start spitting out some output.
> However, when running 'X -configure' or 'X -config', my display blacks
> out and becomes unresponsive. The display remains unresponsive even
> when I try to drop back to a VTY with ctrl+alt+fX.
>
> I noticed the bug in the wiki regarding resolutions above Full HD and
> have tried lowering my resolution to 1080p or lower to no avail.
>
> Any suggestions?
> Tyler
>
> [...]
>

> Xorg log:
> [    23.410]
> X.Org X Server 1.17.4
> Release Date: 2015-10-28
> [    23.410] X Protocol Version 11, Revision 0
> [    23.410] Build Operating System: FreeBSD 11.0-RC2 amd64
> [    23.410] Current Operating System: FreeBSD green 11.0-RC3 FreeBSD
> 11.0-RC3 #1 r305893: Sun Sep 18 12:22:45 EDT 2016
> root at green:/usr/obj/usr/src/sys/GENERIC amd64
> [    23.410] Build Date: 13 September 2016  07:19:21PM
> [    23.410]
> [    23.410] Current version of pixman: 0.34.0
> [    23.410] Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [    23.410] Markers: (--) probed, (**) from config file, (==) default
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [    23.410] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 18
> 12:35:10 2016
>

> [...]
>

> [    23.415] (==) ModulePath set to "/usr/local/lib/xorg/modules"
> [    23.415] (II) The server relies on devd to provide the list of
> input devices.
> If no devices become available, reconfigure devd or disable AutoAddDevices.
> [...]
>

> [    23.431] (II) LoadModule: "vesa"
> [    23.431] (WW) Warning, couldn't open module vesa
> [    23.431] (II) UnloadModule: "vesa"
> [    23.431] (II) Unloading vesa
> [    23.431] (EE) Failed to load module "vesa" (module does not exist, 0)
> [    23.431] (II) intel: Driver for Intel(R) 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, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
> GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics,
> HD Graphics 2000, HD Graphics 3000, HD Graphics 2500,
> HD Graphics 4000, HD Graphics P4000, HD Graphics 4600,
> HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100,
> HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200
>

> [...]
>

> [    25.550] (II) intel(0): EDID for output HDMI1
> [    25.559] (II) intel(0): EDID for output DP1
> [    25.564] (II) intel(0): EDID for output HDMI2
> [    25.573] (II) intel(0): EDID for output DP2
> [    25.573] (II) intel(0): Output eDP1 connected
> [    25.573] (II) intel(0): Output HDMI1 disconnected
> [    25.573] (II) intel(0): Output DP1 disconnected
> [    25.573] (II) intel(0): Output HDMI2 disconnected
> [    25.573] (II) intel(0): Output DP2 disconnected
> [    25.573] (II) intel(0): Using exact sizes for initial modes
> [    25.573] (II) intel(0): Output eDP1 using initial mode 2560x1440
> [    25.573] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0)
> unless otherwise stated.
> [    25.573] (II) intel(0): Kernel page flipping support detected, enabling
> [    25.573] (==) intel(0): DPI set to (96, 96)
> [    25.573] (II) Loading sub module "fb"
> [    25.573] (II) LoadModule: "fb"
> [    25.573] (II) Loading /usr/local/lib/xorg/modules/libfb.so
>

> [...]
>

> [    27.554] (**) sysmouse: (accel) keeping acceleration scheme 1
> [    27.554] (**) sysmouse: (accel) acceleration profile 0
> [    27.554] (**) sysmouse: (accel) acceleration factor: 2.000
> [    27.554] (**) sysmouse: (accel) acceleration threshold: 4
> [    27.554] (II) sysmouse: SetupAuto: hw.iftype is 4, hw.model is 0
> [    27.554] (II) sysmouse: SetupAuto: protocol is SysMouse
> [    27.605] (II) config/devd: adding input device Mouse (/dev/psm0)
> [    27.605] (II) Using input driver 'mouse' for 'Mouse'
> [    27.605] (**) Mouse: always reports core events
> [    27.605] (**) Option "Device" "/dev/psm0"
> [    27.605] (==) Mouse: Protocol: "Auto"
> [    27.605] (**) Mouse: always reports core events
> [    27.656] (==) Mouse: Emulate3Buttons, Emulate3Timeout: 50
> [    27.656] (**) Mouse: ZAxisMapping: buttons 4 and 5
> [    27.656] (**) Mouse: Buttons: 5
> [    27.656] (**) Option "config_info" "devd:psm0"
> [    27.656] (II) XINPUT: Adding extended input device "Mouse" (type:
> MOUSE, id 8)
> [    27.656] (**) Mouse: (accel) keeping acceleration scheme 1
> [    27.656] (**) Mouse: (accel) acceleration profile 0
> [    27.656] (**) Mouse: (accel) acceleration factor: 2.000
> [    27.656] (**) Mouse: (accel) acceleration threshold: 4
> [    27.672] (II) Mouse: SetupAuto: hw.iftype is 3, hw.model is 0
> [    27.672] (II) Mouse: SetupAuto: protocol is PS/2
> [    27.875] (II) Mouse: ps2EnableDataReporting: succeeded
> [    28.394] (II) AIGLX: Suspending AIGLX clients for VT switch
> [    33.203] (WW) config/devd: devd socket is lost
> [    33.204] (EE) config/devd: fail to connect to devd
> [    33.235] (II) config/devd: terminating backend...
> [    33.235] (II) UnloadModule: "mouse"
> [    33.235] (II) UnloadModule: "mouse"
> [    33.235] (II) UnloadModule: "kbd"
> [    33.239] (II) Server terminated successfully (0). Closing log file.
>
> Several potential issues, but the most obvious is that devd does not
appear to be working. Is devd running? If not, why not? if so, is there an
issue with the /etc/devd.conf file? Is it current? If it's not current, it
may not have the required devices to work with yo9ur hardware. But it can't
even find the keyboard or mouse and those shold be pretty much unchanged
since devd came into existence.

This could be the cause of other odd things in the Xlog, so get this fixed
and see if things work better.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683