На 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.
