Re: Funky Display Output:
On Tue, 30 Apr 2019, Ron Georgia wrote: > 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 mention "modesetting" because that is the only thing that works for the machines I have (i82G41TY-, i82Q45-, i82946GZ-based). Using 'Driver "intel"' with 'Option "TearFree" "true"' and 'Option "AccelMethod" "SNA"' does not produce a usable display on these machines. > 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. I do see some performance impact, although in my case that could partly be due to running over NFS (machines have netbsd-8 only on local disk). If the server is busy, things lag. I am seeing the same kind of error messages logged to the console. I thought there was a pattern to them, but was just contradicted as I pasted this: [ 162875.7671473] kern error: [drm:(/x/current/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe A FIFO underrun [ 163245.8965324] kern error: [drm:(/x/current/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 Still, seems to be usually one of the first followed by two or more of the second, although not necessarily. Sometimes several of the first will occur before the second. So far, the only machines I have that do not have a problem using 'Driver "intel"' use actual i82915 devices or i82810e devices. For those, setting 'Option "TearFree" "false"' has no adverse effect and saves a performance penalty. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: Funky Display Output:
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 0xb30259d9c000, 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:
Re: Funky Display Output:
На 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 0xa100448a1000, 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 0xc7013e284000, 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" # [] 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.
Re: Funky Display Output:
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 0xa100448a1000, 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. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: Funky Display Output:
On Sat, 13 Apr 2019, John D. Baker wrote: > I suppose as an outlier data point, the intel driver works fine on an > ancient i82810e-based system with no DRM/KMS nor UMS at all. A machine with a real i82915 device works fine without any tweaks required, albeit I am not sure now if I updated this machine before or after "TearFree" was defaulted to "on". I threw together a minimal "xorg.conf" and set it both ways and it seemed to make no difference in the display--it was working well regardless. I suppose I'll keep it set to "false" to avoid the memory/perfomance penalty. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: Funky Display Output:
While wrestling with another problem that my custom kernel has that GENERIC doesn't, I double-checked the Xorg/intel behavior while running GENERIC. The behavior is the same: the intel driver with "TearFree" on with or without "AccelMethod" "SNA" is only marginally improved but still doesn't draw properly. Using "Driver" "modesetting" works very well. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: Funky Display Output:
I suppose as an outlier data point, the intel driver works fine on an ancient i82810e-based system with no DRM/KMS nor UMS at all. The machine does need an "xorg.conf", but only to define the limits of the CRT monitor--no "Device" section. I did have to tweak the "Display" subsection to keep it from using a bogus virtual size that was larger than what the CRT supported. 1600x1200x16 is nice. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: Funky Display Output
I think it's the kernel too. I have a reduced way of reproducing it. env LIBGL_ALWAYS_SOFTWARE=1 glmark2 (from pkgsrc) will be visibly corrupt. env LIBGL_ALWAYS_SOFTWARE=1 ktruss -i glmark2 > /dev/null or a second glmark2 instance seemed to make it go away. I think this difference means it might be under-synchronizing. tearing should become worse with a second glmark2 instance or with more load. instead it becomes better. Anyway, I enabled tearfree by default, so the visible effects should be gone, but the bug isn't.
Re: Funky Display Output:
On both of the intel-graphics machines I've tried so far: i915drmkms0 at pci0 dev 2 function 0: Intel 82G41 Integrated Graphics Device (re v. 0x03) Intel product 2e33 (miscellaneous display, revision 0x03) at pci0 dev 2 function 1 not configured i915drmkms0 at pci0 dev 2 function 0: Intel 82Q45 Integrated Graphics Device (re v. 0x03) Intel 82Q45 Integrated Graphics Device (miscellaneous display, revision 0x03) at pci0 dev 2 function 1 not configured setting: Options "TearFree" "true" Options "AccelMethod" "SNA" improved things but the display still exhibited "tearing" and dropouts/glitches throughout the screen. Only using Driver "modesetting" worked and works very well. I'm using the 82G41 system with it as I write this. Guess my stuff is too old again. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: Funky Display Output
With these two settings now kdm, xdm and slim work as expected; previously the username and the password echo did not show properly. Now my Intel graphics works rather well. I get hangs only when I run some of the xscreensaver demos in full screen mode, rendering the mouse/keyboard unresponsive - but the power off button brings orderly shutdown. On Fri, 12 Apr 2019 at 14:11, Ron Georgia wrote: > > Update: > Using "modesetting" did clear up the issue. > Keeping the Driver as "intel" and setting "TearFree" to "true" with > "AccelMethod" set to "sna" also worked. > Not sure how this email group looks on adding links to emails. I found some > info on TearFree and sna on askubuntu and the Archlinux wiki. > > Here's a good resource for explaining a little about TearFree and sna. > (archlinux wiki, search intel_graphics#Tearing) > > > On 4/12/19, 5:08 AM, "Benny Siegert" wrote: > > I don't think this is related to xf86. I started seeing these issues > when upgrading my kernel to the latest version while keeping all the > userland as is. So I assume it is related to an updated Intel kernel > driver. > > I haven't tried but perhaps the "NoTear" option to the Xorg intel > driver would help? > > On Thu, Apr 11, 2019 at 11:39 PM matthew green wrote: > > > > i am fairly sure the new display glitches you are seeing are > > related to the newer xf86-video-intel driver. > > > > can people who are seeing issues not related to GL/Mesa try > > forcing the "modesetting" driver instead? see if that makes > > things go away? i am probably going to revert the driver in > > -current until someone fixes the new one, and perhaps make > > the new one optional since it works better for me on > > kabylake, but it would be nice to know if modesetting helps > > fix some problems. > > > > thanks. > > > > > > .mrg. > > > > -- > Benny > > > --
Re: Funky Display Output
Update: Using "modesetting" did clear up the issue. Keeping the Driver as "intel" and setting "TearFree" to "true" with "AccelMethod" set to "sna" also worked. Not sure how this email group looks on adding links to emails. I found some info on TearFree and sna on askubuntu and the Archlinux wiki. Here's a good resource for explaining a little about TearFree and sna. (archlinux wiki, search intel_graphics#Tearing) On 4/12/19, 5:08 AM, "Benny Siegert" wrote: I don't think this is related to xf86. I started seeing these issues when upgrading my kernel to the latest version while keeping all the userland as is. So I assume it is related to an updated Intel kernel driver. I haven't tried but perhaps the "NoTear" option to the Xorg intel driver would help? On Thu, Apr 11, 2019 at 11:39 PM matthew green wrote: > > i am fairly sure the new display glitches you are seeing are > related to the newer xf86-video-intel driver. > > can people who are seeing issues not related to GL/Mesa try > forcing the "modesetting" driver instead? see if that makes > things go away? i am probably going to revert the driver in > -current until someone fixes the new one, and perhaps make > the new one optional since it works better for me on > kabylake, but it would be nice to know if modesetting helps > fix some problems. > > thanks. > > > .mrg. -- Benny
Re: Funky Display Output
On Thu, Apr 11, 2019 at 11:01:52PM -0500, John D. Baker wrote: > On the two intel-graphics machines I've tried now, I have the same > problem I originally mentioned in: > > http://mail-index.netbsd.org/current-users/2019/04/11/msg035551.html Just to make sure it is clear: the xdm glitches are not related to any driver, but started happening with the last xdm import. Martin
Re: Funky Display Output
On Thu, 11 Apr 2019, Chavdar Ivanov wrote: > Please don't be so quick reverting the Intel driver. With today's > build my laptop is working very well, I have no visible effects, > glmark2 executes as expected with the exception of the crash upon > exit, Kde4 was previously crashing on testing the gl capability, now > everything works. Great work, in two words. On the two intel-graphics machines I've tried now, I have the same problem I originally mentioned in: http://mail-index.netbsd.org/current-users/2019/04/11/msg035551.html although subsequently I've been using 'startx' rather than add the complication of 'xdm'. Graphical elements "draw" very slowly, disparate portions appear throughout the drawing region until complete (mostly). Keyboard/mouse response is normal, it just takes a while to see when graphical elements change/text is drawn, etc. The background outside of a window stayed black, but if a window was moved, the correct background color(s) appeared in the region vacated. The second machine has: [...] i915drmkms0 at pci0 dev 2 function 0: Intel 82Q45 Integrated Graphics Device (rev. 0x03) Intel 82Q45 Integrated Graphics Device (miscellaneous display, revision 0x03) at pci0 dev 2 function 1 not configured [...] 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] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 intelfb0 at i915drmkms0 intelfb0: framebuffer at 0xa000ad077000, size 1024x768, depth 32, stride 4096 wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0 wsmux1: connecting to wsdisplay0 > On Thu, 11 Apr 2019, 22:39 matthew green, wrote: > > > i am fairly sure the new display glitches you are seeing are > > related to the newer xf86-video-intel driver. > > > > can people who are seeing issues not related to GL/Mesa try > > forcing the "modesetting" driver instead? see if that makes > > things go away? i am probably going to revert the driver in > > -current until someone fixes the new one, and perhaps make > > the new one optional since it works better for me on > > kabylake, but it would be nice to know if modesetting helps > > fix some problems. Noting what Chavdar said above, I built -current again today and saw no change but I might not have all the latest. I've since updated again (as of about 201904120355Z) and will build and try again. So, there is a driver whose name is "modesetting"? As in: Section "Device" Identifier "foo" Driver "modesetting" EndSection During the attempts to use X on intel-graphics machines, dmesg was spammed with (last msgbuf's worth): [ 107.835093] 0001576c : [ 107.835093] 00015770 : 0720 [ 107.835093] 00015774 : [ 107.835093] 00015778 : 0720 [ 107.835093] 0001577c : [ 107.835093] 00015780 : 0720 [ 107.835093] 00015784 : [ 107.835093] 00015788 : 0720 [ 107.835093] 0001578c : [ 107.835093] 00015790 : 0720 [ 107.835093] 00015794 : [ 107.835093] 00015798 : 0720 [ 107.835093] 0001579c : [ 107.835093] 000157a0 : 0720 [ 107.835093] 000157a4 : [ 107.835093] 000157a8 : 0720 [ 107.835093] 000157ac : [ 107.835093] 000157b0 : 0720 [ 107.835093] 000157b4 : [ 107.835093] 000157b8 : 0720 [ 107.835093] 000157bc : [ 107.835093] 000157c0 : 0720 [ 107.835093] 000157c4 : [ 107.835093] 000157c8 : 0720 [ 107.835093] 000157cc : [ 107.835093] 000157d0 : 0720 [ 107.835093] 000157d4 : [ 107.835093] 000157d8 : 0720 [ 107.835093] 000157dc : [ 107.835093] 000157e0 : 0720 [ 107.835093] 000157e4 : [ 107.835093] 000157e8 : 0720 [ 107.835093] 000157ec : [ 107.835093] 000157f0 : 0720 [ 107.835093] 000157f4 : [ 107.835093] 000157f8 : 0720 [ 107.835093] 000157fc : [ 107.835093] 00015800 : 0720 [ 107.835093] 00015804 : [ 107.835093] 00015808 : 0720 [ 107.835093] 0001580c : [ 107.835093] 00015810 : 0720 [ 107.835093] 00015814 : [ 107.835093] 00015818 : 0720 [ 107.835093] 0001581c : [ 107.835093] 00015820 : 0720 [ 107.835093] 00015824 : [ 107.835093] 00015828 : 0720 [ 107.835093] 0001582c : [ 107.835093] 00015830 : 0720 [ 107.835093] 00015834 : [ 107.835093] 00015838 : 0720 [ 107.835093] 0001583c : [ 107.835093] 00015840 : 0720 [ 107.835093] 00015844 : [ 107.835093] 00015848 : 0720 [ 107.835093] 0001584c :
Re: Funky Display Output
Please don't be so quick reverting the Intel driver. With today's build my laptop is working very well, I have no visible effects, glmark2 executes as expected with the exception of the crash upon exit, Kde4 was previously crashing on testing the gl capability, now everything works. Great work, in two words. On Thu, 11 Apr 2019, 22:39 matthew green, wrote: > i am fairly sure the new display glitches you are seeing are > related to the newer xf86-video-intel driver. > > can people who are seeing issues not related to GL/Mesa try > forcing the "modesetting" driver instead? see if that makes > things go away? i am probably going to revert the driver in > -current until someone fixes the new one, and perhaps make > the new one optional since it works better for me on > kabylake, but it would be nice to know if modesetting helps > fix some problems. > > thanks. > > > .mrg. >
re: Funky Display Output
i am fairly sure the new display glitches you are seeing are related to the newer xf86-video-intel driver. can people who are seeing issues not related to GL/Mesa try forcing the "modesetting" driver instead? see if that makes things go away? i am probably going to revert the driver in -current until someone fixes the new one, and perhaps make the new one optional since it works better for me on kabylake, but it would be nice to know if modesetting helps fix some problems. thanks. .mrg.
Re: Funky Display Output
I have on occasion similar behaviour on my HP Envy laptop using the 530 graphics, it is rather weird. I also get the messages about not being able to load the two microcode files, even if I have placed them in the right location. On Thu, 11 Apr 2019 at 21:31, Ron Georgia wrote: > > My monitor is acting a little funky. When I call up something like wireshark > or firefox and start scrolling the content inside the active window looks > like a satellite TV during a storm. When the window repaints it is choppy > (albeit colorful). If I let it sit long enough it settles out. This is new > since updating to NetBSD 8.99.37. I also pulled down the latest “sets” from > HEAD and installed that (and survived etcupate). Here’s a little info. > > $ uname -a > NetBSD clement.ronverbs.dev 8.99.37 NetBSD 8.99.37 (GENERIC) #0: Wed Apr 10 > 16:15:11 UTC 2019 > mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 > > From dmesg: > [ 1.074128] acpivga0 at acpi0 (GFX0): ACPI Display Adapter > [ 1.074128] acpivga0 at acpi0 (GFX0): ACPI Display Adapter > [ 1.074128] acpiout0 at acpivga0 (DD01, 0x0100): ACPI Display Output > Device > [ 1.074128] acpiout1 at acpivga0 (DD02, 0x0002): ACPI Display Output > Device > [ 1.074128] acpiout2 at acpivga0 (DD03, 0x0300): ACPI Display Output > Device > [ 1.074128] acpiout3 at acpivga0 (DD04, 0x0301): ACPI Display Output > Device > [ 1.074128] acpiout4 at acpivga0 (DD05, 0x0302): ACPI Display Output > Device > [ 1.074128] acpiout5 at acpivga0 (DD06, 0x0303): ACPI Display Output > Device > [ 1.074128] acpiout6 at acpivga0 (DD07, 0x0304): ACPI Display Output > Device > [ 1.074128] acpiout7 at acpivga0 (DD08, 0x0305): ACPI Display Output > Device > [ 1.074128] acpiout8 at acpivga0 (DD09, 0x0009): ACPI Display Output > Device > [ 1.074128] acpiout9 at acpivga0 (DD0A, 0x000a): ACPI Display Output > Device > [ 1.074128] acpiout10 at acpivga0 (DD0B, 0x000b): ACPI Display Output > Device > [ 1.074128] acpiout11 at acpivga0 (DD0C, 0x000c): ACPI Display Output > Device > [ 1.074128] acpiout12 at acpivga0 (DD0D, 0x000d): ACPI Display Output > Device > [ 1.074128] acpiout13 at acpivga0 (DD0E, 0x000e): ACPI Display Output > Device > [ 1.074128] acpiout14 at acpivga0 (DD0F, 0x000f): ACPI Display Output > Device > [ 1.074128] acpiout15 at acpivga0 (DD1F, 0x0400): ACPI Display Output > Device > [ 1.074128] acpiout16 at acpivga0 (SKC0, 0xca00): ACPI Display Output > Device > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout0 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout1 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout2 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout3 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout4 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout5 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout6 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout7 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout8 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout9 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout10 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout11 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout12 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout13 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout14 > [ 1.074128] acpivga0: autoconfiguration error: unknown output device > acpiout16 > > > $ dmesg | grep drm > [ 1.074128] i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product > 5912 (rev. 0x04) > [ 7.396444] kern info: [drm] Memory usable by graphics device = 4096M > [ 7.433053] kern info: [drm] Supports vblank timestamp caching Rev 2 > (21.10.2013). > [ 7.470040] kern info: [drm] Driver supports precise vblank timestamp > query. > [ 7.505493] kern info: [drm] failed to find VBIOS tables > [ 7.540399] i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0) > [ 7.606755] kern info: [drm] failed to retrieve link info, disabling eDP > [ 7.706904] 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) > [ 7.780586] 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 > [ 7.922289] kern error: >
Funky Display Output
My monitor is acting a little funky. When I call up something like wireshark or firefox and start scrolling the content inside the active window looks like a satellite TV during a storm. When the window repaints it is choppy (albeit colorful). If I let it sit long enough it settles out. This is new since updating to NetBSD 8.99.37. I also pulled down the latest “sets” from HEAD and installed that (and survived etcupate). Here’s a little info. $ uname -a NetBSD clement.ronverbs.dev 8.99.37 NetBSD 8.99.37 (GENERIC) #0: Wed Apr 10 16:15:11 UTC 2019 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 >From dmesg: [ 1.074128] acpivga0 at acpi0 (GFX0): ACPI Display Adapter [ 1.074128] acpivga0 at acpi0 (GFX0): ACPI Display Adapter [ 1.074128] acpiout0 at acpivga0 (DD01, 0x0100): ACPI Display Output Device [ 1.074128] acpiout1 at acpivga0 (DD02, 0x0002): ACPI Display Output Device [ 1.074128] acpiout2 at acpivga0 (DD03, 0x0300): ACPI Display Output Device [ 1.074128] acpiout3 at acpivga0 (DD04, 0x0301): ACPI Display Output Device [ 1.074128] acpiout4 at acpivga0 (DD05, 0x0302): ACPI Display Output Device [ 1.074128] acpiout5 at acpivga0 (DD06, 0x0303): ACPI Display Output Device [ 1.074128] acpiout6 at acpivga0 (DD07, 0x0304): ACPI Display Output Device [ 1.074128] acpiout7 at acpivga0 (DD08, 0x0305): ACPI Display Output Device [ 1.074128] acpiout8 at acpivga0 (DD09, 0x0009): ACPI Display Output Device [ 1.074128] acpiout9 at acpivga0 (DD0A, 0x000a): ACPI Display Output Device [ 1.074128] acpiout10 at acpivga0 (DD0B, 0x000b): ACPI Display Output Device [ 1.074128] acpiout11 at acpivga0 (DD0C, 0x000c): ACPI Display Output Device [ 1.074128] acpiout12 at acpivga0 (DD0D, 0x000d): ACPI Display Output Device [ 1.074128] acpiout13 at acpivga0 (DD0E, 0x000e): ACPI Display Output Device [ 1.074128] acpiout14 at acpivga0 (DD0F, 0x000f): ACPI Display Output Device [ 1.074128] acpiout15 at acpivga0 (DD1F, 0x0400): ACPI Display Output Device [ 1.074128] acpiout16 at acpivga0 (SKC0, 0xca00): ACPI Display Output Device [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout0 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout1 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout2 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout3 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout4 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout5 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout6 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout7 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout8 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout9 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout10 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout11 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout12 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout13 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout14 [ 1.074128] acpivga0: autoconfiguration error: unknown output device acpiout16 $ dmesg | grep drm [ 1.074128] i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 5912 (rev. 0x04) [ 7.396444] kern info: [drm] Memory usable by graphics device = 4096M [ 7.433053] kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 7.470040] kern info: [drm] Driver supports precise vblank timestamp query. [ 7.505493] kern info: [drm] failed to find VBIOS tables [ 7.540399] i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0) [ 7.606755] kern info: [drm] failed to retrieve link info, disabling eDP [ 7.706904] 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) [ 7.780586] 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 [ 7.922289] 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) [ 8.057422] 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) [ 8.187625] intelfb0 at i915drmkms0 [ 9.299264] kern info: [drm] RC6 on [ 11189.535402] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start]
