Re: Funky Display Output:

To: Chavdar Ivanov <ci4ic4%gmail.com@localhost>, "John D. Baker" <jdbaker%consolidated.net@localhost>
Subject: Re: Funky Display Output:
From: Ron Georgia <netverbs%gmail.com@localhost>
Date: Tue, 30 Apr 2019 08:34:06 -0400
All,
When I switched to using modesetting the tearing issue went away; however the display was a little grainy and there was a lot of "lag" in the video when doing things like moving a window (like when I used to use Window 3.1.1 on my 286 6MHz beast of a machine). I changed the driver to intel and, as stated before, set Option "TearFree" to "true" and "AccelMethod" to "sna"

I do not see any performance hits with those settings. I need to dig into what those really do, since I found those settings on the web, maybe Arch Linux or something. As a refresher here are some snippets of my dmesg, in case that will help someone else with similar hardware.
========================================================
$ dmesg | grep 915
[ 11702.721326] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35
[ 20965.874027] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)urtwn0: autoconfiguration error: timeout waiting for firmware readiness
[ 239105.050842] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35
[ 239242.105019] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/drm_edid.c:1148)drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 113
[ 239250.238323] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)syncing disks... done
[     1.073974] i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 5912 (rev. 0x04)
[     5.915292] uhid1 at uhidev1 reportid 23: input=0, output=0, feature=1
[     7.915232] wsmouse1 at ums1 mux 0
[     8.766356] i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0)
[     8.919713] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:636)i915_firmware_load_error_print] *ERROR* failed to load firmware i915/kbl_dmc_ver1.bin (0)
[     8.993574] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:651)i915_firmware_load_error_print] *ERROR* The driver is built-in, so to load the firmware you need to
[     9.135295] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_guc_loader.c:560)guc_fw_fetch] *ERROR* Failed to fetch GuC firmware from i915/kbl_guc_ver9_14.bin (error -2)
[     9.260212] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -5 (ignored)
[     9.400418] intelfb0 at i915drmkms0


$ dmesg | grep intelfb0
[     9.400418] intelfb0 at i915drmkms0
[     9.430463] intelfb0: framebuffer at 0xffffb30259d9c000, size 1920x1080, depth 32, stride 7680
[    10.051376] wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0

$ dmesg | grep -i error
[ 11702.721326] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35
[ 20965.874027] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)urtwn0: autoconfiguration error: timeout waiting for firmware readiness
[ 239105.050842] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35
[ 239242.105019] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/drm_edid.c:1148)drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 113
[ 239250.158191] kern error: Raw EDID:
[     1.073974] acpiec0 at acpi0 (H_EC, PNP0C09-1)acpiec0: autoconfiguration error: unable to evaluate _GPE: AE_NOT_FOUND
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout0
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout1
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout2
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout3
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout4
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout5
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout6
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout7
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout8
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout9
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout10
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout11
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout12
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout13
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout14
[     1.073974] acpivga0: autoconfiguration error: unknown output device acpiout16
[     3.802183] autoconfiguration error: wd1: wedge named 'EFI System' already existed, using 'bc92f848-2ea5-47d7-9a93-b90d68f2cbbc'
[     8.388931] WARNING: 18 errors while detecting hardware; check system log.
[     8.919713] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:636)i915_firmware_load_error_print] *ERROR* failed to load firmware i915/kbl_dmc_ver1.bin (0)
[     8.993574] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:651)i915_firmware_load_error_print] *ERROR* The driver is built-in, so to load the firmware you need to
[     9.135295] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_guc_loader.c:560)guc_fw_fetch] *ERROR* Failed to fetch GuC firmware from i915/kbl_guc_ver9_14.bin (error -2)
[     9.260212] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -5 (ignored)


========================================================

On 4/29/19, 5:05 PM, "Chavdar Ivanov" <ci4ic4%gmail.com@localhost> wrote:

    
    На 2019-04-29 в 18:34, John D. Baker написа:
    > I managed to fire up another machine w/intel graphics I have.  It uses:
    >
    > [...]
    > i915drmkms0 at pci0 dev 2 function 0: Intel 82946GZ Integrated Graphics Device (rev. 0x02)
    > [...]
    > kern info: [drm] Memory usable by graphics device = 512M
    > kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    > kern info: [drm] Driver supports precise vblank timestamp query.
    > kern info: [drm] failed to find VBIOS tables
    > i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0)
    > kern info: [drm] initialized overlay support
    > intelfb0 at i915drmkms0
    > intelfb0: framebuffer at 0xffffa100448a1000, size 1024x768, depth 32, stride 4096
    > wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0
    >
    >
    > It, too, requires the "modesetting" driver for Xorg to work.
    >
    It is a bit of a conundrum. I have got:
    
    ...
    
    i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 191b (rev. 0x06)
    kern info: [drm] Memory usable by graphics device = 4096M
    kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    kern info: [drm] Driver supports precise vblank timestamp query.
    i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0)
    kern error:
    [drm:(/home/sysbuild/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:636)i915_firmware_load_error_print]
    *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0)
    kern error:
    [drm:(/home/sysbuild/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:651)i915_firmware_load_error_print]
    *ERROR* The driver is built-in, so to load the firmware you need to
    kern error:
    [drm:(/home/sysbuild/src/sys/external/bsd/drm2/dist/drm/i915/intel_guc_loader.c:560)guc_fw_fetch]
    *ERROR* Failed to fetch GuC firmware from i915/skl_guc_ver4.bin (error -2)
    kern error:
    [drm:(/home/sysbuild/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw]
    *ERROR* Failed to initialize GuC, error -5 (ignored)
    intelfb0 at i915drmkms0
    intelfb0: framebuffer at 0xffffc7013e284000, size 1920x1080, depth 32,
    stride 7680
    kern info: [drm] RC6 on
    wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation),
    using wskbd0
    
    ...
    
    I get those weird effects only with /etc/rc.d/gdm and /etc/rc.d/kdm (I
    haven't tried xdm yet). After that, when I login, using the intel
    driver, everything seems to be working OK, I have no tear-offs or other
    obvious problems. I get also:
    
    ...
    
    [   628.319] (II) Initializing extension GLX
    [   628.579] (II) AIGLX: Loaded and initialized i965
    [   628.579] (II) GLX: Initialized DRI2 GL provider for screen 0
    [   628.579] (II) Initializing extension XFree86-VidModeExtension
    [   628.580] (II) Initializing extension XFree86-DGA
    [   628.580] (II) Initializing extension XFree86-DRI
    [   628.580] (II) Initializing extension DRI2
    
    and the 3D acceleration is reasonable for an Intel driver - glmark2
    returns anything between 1300 and 2400, blender and flightgear work
    well. I don't know why the log above reports those two microcode files
    fail loading - they are in the right place under /libdata/firmware/i915
    and even if this is important.
    
    If I switch to modesetting driver, the effects disappear, but I get:
    
    ...
    
    [  1442.234] (II) AIGLX: Screen 0 is not DRI2 capable
    [  1442.252] (II) IGLX: Loaded and initialized swrast
    [  1442.252] (II) GLX: Initialized DRISWRAST GL provider for screen 0
    [  1442.252] (II) Initializing extension XFree86-VidModeExtension
    [  1442.253] (II) Initializing extension XFree86-DGA
    [  1442.253] (II) Initializing extension XFree86-DRI
    [  1442.253] (II) Initializing extension DRI2
    
    
    and glmark2 returns a mere 38. So I am happy to put up with a few
    effects during login only. BTW with modesetting I cannot start kde4
    properly at all, it works very well with the Intel driver. I have also
    
     Option     "AccelMethod"        "sna"
     Option     "VSync" "true"               # [<bool>]
     Option     "TearFree"            "true"
    
    in my /etc/X11/xorg.conf file.
    
    
    I still have other problems on occasion - e.g. some of the Xscreensaver
    GL demos hang Xorg when ran full screen (-root) in a weird way - I can
    still ssh to the laptop, but the keyboard is not active, the screen gets
    all black with a cursor in the top left, poweroff from the remote shell
    does not complete and I get a panic.  Still, it is usable.
Follow-Ups:
- Re: Funky Display Output:
  - From: John D. Baker
References:
- Funky Display Output
  - From: Ron Georgia
- re: Funky Display Output
  - From: matthew green
- Re: Funky Display Output
  - From: Benny Siegert
- Re: Funky Display Output
  - From: Ron Georgia
- Re: Funky Display Output
  - From: Chavdar Ivanov
- Re: Funky Display Output:
  - From: John D. Baker
- Re: Funky Display Output:
  - From: John D. Baker
- Re: Funky Display Output:
  - From: Chavdar Ivanov
Prev by Date: Re: intelfb0 at i915drmkms0
Next by Date: Re: patch for build.sh to guess native MACHINE_ARCH
Previous by Thread: Re: Funky Display Output:
Next by Thread: Re: Funky Display Output:
Indexes:
Home | Main Index | Thread Index | Old Index