Hello You can try setting a different mode at the loader: get to the prompt (press 9) and play with 'gop list', 'gop set <n>' and 'gop get'. Maybe you can find a resolution that works fine?
If yes, try loading i915 in /etc/rc.conf, that's the recommended procedure. Loading i915 too early may blow up booting. You don't need to load drm explicitly, it's a prerequisite of i915 and will be loaded automatically. Best Peeter -- On Wed, May 19, 2021 at 12:50 AM Chuck Musser <[email protected]> wrote: > > Related (maybe) to this are these messages in dmesg: > > vgapci0: <VGA-compatible display> port 0x5000-0x503f mem > 0xe0000000-0xefffffff,0xf0000000-0xf03fffff irq 16 at device 2.0 on pci0 > [drm] pdev: vendor=0x8086 device=0x0126 rev=0x09 > [drm] svendor=0x17aa sdevice=0x21da irq=17 > WARN_ON(domain->wake_count == 0)error: [drm:pid0:gen6_gmch_probe] *ERROR* > Can't set DMA mask/consistent mask (-5) > [drm] Memory usable by graphics device = 2048M > [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [drm] Driver supports precise vblank timestamp query. > tunable drm.video.LVDS-1 is not set > tunable drm.video.VGA-1 is not set > tunable drm.video.HDMI-A-1 is not set > tunable drm.video.DP-1 is not set > tunable drm.video.HDMI-A-2 is not set > tunable drm.video.HDMI-A-3 is not set > tunable drm.video.DP-2 is not set > tunable drm.video.DP-3 is not set > RPM wakelock ref not held during HW access<4>RPM wakelock ref not held during > HW access<6>[drm] taking over the fictitious range 0xe0000000-0x10000000 > [drm] Initialized i915 1.6.0 20171023 for dev_name on minor 0 > kms console: xpixels 1366 ypixels 768 > WARNING !set->fb failed at > /usr/src/sys/dev/drm/drm/../drm_atomic_helper.c:2750 > WARNING state->crtc && !state->fb failed at > /usr/src/sys/dev/drm/drm/../drm_atomic.c:862 > [drm] DRM_I915_DEBUG_GEM enabled > drm0 on vgapci0 > > > > > They are labeled "WARNINGS", but maybe more serious?
