Intel Skylake i5-6200U graphics driver in FreeBSD 14.5-RC1

escape · Sep 7, 2026

Computer has become slower in writing text in terminal. Characters are not rendered anymore as in the following image:

It looks like that the graphics driver does not work anymore. The OS version is 14.5-RC1.

As AI assisted, command glxinfo -B prints "llvmpipe" and "Accelerated: no" :

Bash:

...
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: llvmpipe (LLVM 19.1.7, 256 bits) (0xffffffff)
    Version: 26.1.3
    Accelerated: no
    ...

The computer has: CPU: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (2400.00-MHz K8-class CPU) as in dmesg(). Text "Intel Skylake" prints in multiple locations.

Intel Skylake i915 computers have had graphics driver support from graphics/drm-next-kmod as in URL . It has been important in what order the kernel modules were loaded. A good order was for example:

 kldload /boot/modules/i915kms.ko

kldload /boot/modules/drm.ko

kldload /boot/kernel/iic.ko

kldload /boot/kernel/linuxkpi_hdmi.ko

kldload /boot/modules/dmabuf.ko

kldload /boot/kernel/lindebugfs.ko

kldload /boot/modules/ttm.ko

This module seems to be outdated today and at least the handbook instructs to:

 pkg install drm-kmod

sysrc kld_list+=i915kms

This leads to the previously mentioned problem.

A working solution previously before update to 14.4 and 14.5-RC1 was to just:

 cd /usr/ports/graphics/drm-515-kmod

make reinstall

I've updated the ports -tree to the 14.5-RC1 and reinstalled the graphics/drm-515-kmod and graphics/drm-kmod and graphics/gpu-firmware-intel-kmod separately testing them after a reboot without good results, then run pkg update; pkg upgradewithout any significant change. The graphics/gpu-firmware-intel-kmod updated a new version of some firmware. It did not fix the problem. As in the link after the post, "Panel Shift Refresh" setting did not change anything either.

How to fix the Intel i5-6200U graphics driver?

Interesting how /boot/defaults/loader.conf has module_blacklist="drm drm2 radeonkms i915kms amdgpu if_iwlwifi if_rtw88 if_rtw89" in it.

escape

Some other intertesting links:
https://www.gaelanlloyd.com/blog/fix-freebsd-lag-issues-intel-i915/
https://[do not visit]_www_freebsdsoftware_org_[do not visit ]/graphics/gpu-firmware-intel-kmod-skylake/
(Forum adds the "do not visit" automatically - why, not known)

SirDice · Sep 7, 2026

escape said:
I've updated the ports -tree to the 14.5-RC1

Ports tree is the same for ALL versions of FreeBSD.

escape said:
(Forum adds the "do not visit" automatically - why, not known)

It's a fake website, avoid it.

C

Thread 'Please beware of [do not visit]_www_freebsdsoftware_org_[do not visit ] - it contains AI slop'

Aug 26, 2026

Just want to make FreeBSD users aware: The site [do not visit]_www_freebsdsoftware_org_[do not visit ] has a lot of "plausible-looking" information, but most of it is completely wrong. It seems to be an AI slop site.

For example: hxxp://[do not visit]_www_freebsdsoftware_org_[do not visit ]/blog/freebsd-gaming-2026.html

it says to "pkg install dxvk". There is no such package. There is also no package called "mesa-mesa-vulkan-intel".

The site is pure slop. Sadly, search results put it above the FreeBSD Handbook. Please make sure you get your documentation from the proper places.

escape · Sep 7, 2026

As just remembered, sometimes it was an issue to update to a RELEASE after the CURRENT. The graphics driver support dropped there as well, it could have been at FreeBSD 12 or older, not remembered anymore. Not a current issue. This is not some license issue?

SirDice · Sep 7, 2026

escape said:
sometimes it was an issue to update to a RELEASE after the CURRENT.

Major version upgrades are always problematic, especially when it comes to 'external' (from ports/packages) kernel modules. They need to be specifically compiled for your running kernel version. DRM drivers are notoriously finicky due to the fast paced development cycle of LinuxKPI in the FreeBSD kernel (the DRM drivers rely heavily on it). Minor version upgrades are less impacted, but could still pose problems with LinuxKPI features added. Lots of things changed between 15.0 and 15.1 for example. Not sure about the changes with regards to the legacy 14 branch though.

escape said:
The graphics driver support dropped there as well, it could have been at FreeBSD 12 or older, not remembered anymore.

FreeBSD 12 (and before) indeed had an Intel and AMD graphics driver included. They've been removed with 13 onward and replaced with graphics/drm-kmod. But you might find references to it in old posts and/or howtos.

fahrenheit · Sep 7, 2026

escape like SirDice said, pre-release and the 3 months after are a funny period for external kmods..

Anyway some points, you don't need to install drm-kmod, that's just a meta package that installs drm-xyz-kmod and gpu-firmware-kmod. For 14.x you can use drm-515-kmod or drm-61-kmod and install the firmware for your card.
You also don't need to manually load the modules, just follow the handbook and do # sysrc kld_list+="i915kms", that will load the i915kms kernel module and all necessary modules (including linuxkpi and firmware modules), so you probably need to remove those modules from the blacklist.
Now, back to modules, the binary packages are probably broken right now, so may need to:

make sure /usr/src is synced with the releng/14.5 branch (i.e. # git fetch --all && git checkout releng/14.5) or, if using pkgbase, install FreeBSD-src-sys
make sure /usr/ports is synced to main (ie. # git checkout main && git pull)
# cd /usr/ports/graphics/drm-515-kmod (or # cd /usr/ports/graphics/drm-61-kmod)
# make package && pkg install work/pkg/*.pkg
# pkg install -r FreeBSD-ports-kmod gpu-firmware-intel-kmod-skylake (specifiying the repository is important because otherwise you may get the package for 14.0 from FreeBSD-ports, you have to make sure you have it correctly configured, see here and here). If the kmods repo for 14.5 does not have the firmware packages you may be able to use the 14.4 package otherwise install from ports (graphics/gpu-firmware-intel-kmod using the kabylake flavour)
To avoid issues testing, remove the i915kms module from /etc/rc.conf with # sysrc kld_list-="i915kms" and reboot (if you use a graphical login manager, I suggest disabling it's service also)
After rebooting, do a # kdload i195kms, if you don't get a kernel panic, you should be alright, re-enable i915kms on /etc/rc.conf (# sysrc kld_list+="i915kms") and the graphical login manager if you disabled it before.
On the other hand if this gets you a kernel panic, please say here and provide the output of dmesg from the boot that went sour and maybe we can help, otherwise check the drm-kmod github issues and/or bugzilla

If you are not using pkgbase, replace make package with make install.

Hope this helps.

edit: updated firmware package name to match hardware requirements.

fahrenheit · Sep 7, 2026

Ah, forgot to say, that if everything goes really south, you can still use X11 with either the scfb (uefi) or the vesa (bios/csm) driver and get a working graphical session. Just remember to disable compositing if you are using a DE that uses it.
You may also need to set the gop mode on the loader to match your screen resolution as the framebuffer drivers don't allow resizing.

escape · Tuesday at 10:29 AM

Is the kabylake driver different comparing to skylake driver? Are they compatible? Why are they in a different driver package?

An edit later: The old case about the 12-STABLE is found from this URL. The firmware refused to load. This time the firmware loaded and still the acceleration is not available. Here is another interesting case when using i386, URL (not relevant here, this one is x64) .

SirDice · Tuesday at 12:00 PM

escape said:
Is the kabylake driver different comparing to skylake driver? Are they compatible? Why are they in a different driver package?

The version of DRM dictates which graphics cards are supported. The DRM drivers depend on LinuxKPI support that's built into the FreeBSD kernel.

Thread 'Intel GPU support Matrix'

May 31, 2026

As the support for Intel GPUs (integrated or discreete) in FreeBSD is confusing (well, in general), here is an handy table for theoretical support as constructed from Linux Kernel LTS release code.

Please remember that:

Only FreeBSD 15.1/16 support DRM 6.12 (more specifically FreeBSD 15 after 1500509 and FreeBSD 16 after 1600018)
FreeBSD 14.x supports DRM 5.15 and 6.1
FreeBSD 15.0 support DRM 5.15, 6.1 and 6.6
FreeBSD 15.1 supports DRM 5.15, 6.1, 6.6 and 6.12
The currently available firmware package is 20260519
You have to have...

fahrenheit · Tuesday at 12:40 PM

escape actually your firmware should be skylake not kabylake. in doubt install the entire intel gpu firmware package, check which one is loaded and remove afterwards the ones not used.
and yes, the firmware package matters as the intel drm driver will try to load specific binary files for the hardware (if you wish you can check the i915_driver.c file on the drm-kmod repo for more information).

Erichans · Tuesday at 2:50 PM

escape said:
The OS version is 14.5-RC1

As FreeBSD 14.5-RELEASE Available has been officially announced, I'd upgrade now and have the "best available" version installed. It may not immediately solve your problems but you'll have a better known base.

escape · Wednesday at 11:26 PM

Upgrading to 14.5-RELEASEdid not have effect in glxinfo -B output. pkg update; pkg upgrade neither and reinstalling the kernel to the custom one before upgrading to 14.5-RC1 did not have any effect (possibly LinuxKPI and/or other) even if the /usr/ports packages were reinstalled. Problem continues. There are different directories /boot/modules and /boot/kernel and different timestamps in different files.

Erichans · Thursday at 9:20 AM

escape said:
Upgrading to 14.5-RELEASE ...

escape · Thursday at 9:59 AM

Bash:

$ pkg -vv | sed -nE -e '/^OSVERSION|^ABI/ p' -e '/^Repositories:/,$ p'
ABI = "FreeBSD:14:amd64";
OSVERSION = "1405000";
Repositories:
  FreeBSD: {
    url             : "pkg+https://pkg.FreeBSD.org/FreeBSD:14:amd64/quarterly",
    enabled         : yes,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }
  FreeBSD-kmods: {
    url             : "pkg+https://pkg.FreeBSD.org/FreeBSD:14:amd64/kmods_quarterly_5",
    enabled         : yes,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }
$ pkg query -x '[%R] %o %n %v' '(^drm-(51.-|6..?-)?kmod)|(.*-firmware-intel-.*)' | column -t
[unknown-repository]  graphics/drm-61-kmod              drm-61-kmod                          6.1.128.1405000_10
[unknown-repository]  graphics/drm-kmod                 drm-kmod                             20260508
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-alderlake    20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-battlemage   20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-broxton      20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-cannonlake   20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-dg1          20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-dg2          20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-elkhartlake  20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-geminilake   20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-icelake      20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-kabylake     20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-meteorlake   20260519.1405000
[FreeBSD-kmods]       graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-rocketlake   20260519.1405000
[unknown-repository]  graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-skylake      20260519.1405000
[FreeBSD]             graphics/gpu-firmware-intel-kmod  gpu-firmware-intel-kmod-tigerlake    20260519.1404000

fahrenheit · Thursday at 12:11 PM

escape can you provide the output of /var/log/messages?

escape · Thursday at 12:14 PM

Comparing to the logs with version 12-STABLE to the case the kernel logs reveal something like this:

Code:

Sep  7 00:22:21 n kernel: drmn0: <drmn> on vgapci0
Sep  7 00:22:21 n kernel: vgapci0: child drmn0 requested pci_enable_io
Sep  7 00:22:21 n syslogd: last message repeated 1 times
Sep  7 00:22:21 n kernel: [drm] Unable to create a private tmpfs mount, hugepage support will be disabled(-19).
Sep  7 00:22:21 n kernel: [drm] Got stolen memory base 0x8c000000, size 0x4000000
Sep  7 00:22:21 n kernel: drmn0: successfully loaded firmware image 'i915/skl_dmc_ver1_27.bin'
Sep  7 00:22:21 n kernel: drmn0: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
Sep  7 00:22:21 n kernel: lkpi_iic0: <LinuxKPI I2C> on drmn0
Sep  7 00:22:21 n kernel: iicbus3: <Philips I2C bus> on lkpi_iic0
Sep  7 00:22:21 n kernel: iic3: <I2C generic I/O> on iicbus3
Sep  7 00:22:21 n kernel: lkpi_iic1: <LinuxKPI I2C> on drmn0
Sep  7 00:22:21 n kernel: iicbus4: <Philips I2C bus>
Sep  7 00:22:21 n kernel:  on lkpi_iic1
Sep  7 00:22:21 n kernel: iic4: <I2C generic I/O> on iicbus4
Sep  7 00:22:21 n kernel: lkpi_iic2: <LinuxKPI I2C> on drmn0
Sep  7 00:22:21 n kernel: iicbus5: <Philips I2C bus> on lkpi_iic2
Sep  7 00:22:21 n kernel: iic5: <I2C generic I/O> on iicbus5
Sep  7 00:22:21 n kernel: sysctl_add_oid: can't re-use a leaf (hw.dri.debug)!
Sep  7 00:22:21 n kernel: lkpi_iic3: <LinuxKPI I2C> on drm1
Sep  7 00:22:21 n kernel: iicbus6: <Philips I2C bus> on lkpi_iic3
Sep  7 00:22:21 n kernel: iic6: <I2C generic I/O> on iicbus6
Sep  7 00:22:21 n kernel: lkpi_iic4: <LinuxKPI I2C> on drm2
Sep  7 00:22:21 n kernel: iicbus7: <Philips I2C bus> on lkpi_iic4
Sep  7 00:22:21 n kernel: iic7: <I2C generic I/O> on iicbus7
Sep  7 00:22:21 n kernel: [drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
Sep  7 00:22:21 n kernel: VT: Replacing driver "efifb" with new "fb".
Sep  7 00:22:21 n kernel: start FB_INFO:
Sep  7 00:22:21 n kernel: type=11 height=1440 width=2160 depth=32
Sep  7 00:22:21 n kernel: pbase=0xa0000000 vbase=0xfffff800a0000000
Sep  7 00:22:21 n kernel: name=drmn0 flags=0x0 stride=8640 bpp=32
Sep  7 00:22:21 n kernel: end FB_INFO

There are some texts, for example:

Code:

[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0 and
Unable to create a private tmpfs mount, hugepage support will be disabled(-19).

Is this something about the xorg.conf drivers? Edit later: huge pages error, URL.

Edit later, from Xorg.0.log

Code:

[    70.878] (II) config/udev: Adding drm device (/dev/dri/card0)
[    70.878] (II) xfree86: Adding drm device (/dev/dri/card0)
[    70.878] (II) Platform probe for /dev/dri/card0
[    70.878] (II) LoadModule: "modesetting"
[    70.878] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so

and

Code:

[    70.509] (EE) modeset(G0): drmSetMaster failed: Device busy
[    70.512] (II) UnloadModule: "modesetting"
[    70.512] (II) UnloadSubModule: "glamoregl"
[    70.512] (II) Unloading glamoreg

escape · Thursday at 12:41 PM

Version text
$ pciconf -lv
...
vgapci0@pci0:0:2:0: class=0x030000 rev=0x07 hdr=0x00 vendor=0x8086 device=0x1916 subvendor=0x1025 subdevice=0x111e
vendor = 'Intel Corporation'
device = 'Skylake-U GT2 [HD Graphics 520]'
class = display
subclass = VGA
...

fahrenheit · Thursday at 3:50 PM

escape said:

Comparing to the logs with version 12-STABLE to the case the kernel logs reveal something like this:

Code:

Sep  7 00:22:21 n kernel: drmn0: <drmn> on vgapci0
Sep  7 00:22:21 n kernel: vgapci0: child drmn0 requested pci_enable_io
Sep  7 00:22:21 n syslogd: last message repeated 1 times
Sep  7 00:22:21 n kernel: [drm] Unable to create a private tmpfs mount, hugepage support will be disabled(-19).
Sep  7 00:22:21 n kernel: [drm] Got stolen memory base 0x8c000000, size 0x4000000
Sep  7 00:22:21 n kernel: drmn0: successfully loaded firmware image 'i915/skl_dmc_ver1_27.bin'
Sep  7 00:22:21 n kernel: drmn0: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
Sep  7 00:22:21 n kernel: lkpi_iic0: <LinuxKPI I2C> on drmn0
Sep  7 00:22:21 n kernel: iicbus3: <Philips I2C bus> on lkpi_iic0
Sep  7 00:22:21 n kernel: iic3: <I2C generic I/O> on iicbus3
Sep  7 00:22:21 n kernel: lkpi_iic1: <LinuxKPI I2C> on drmn0
Sep  7 00:22:21 n kernel: iicbus4: <Philips I2C bus>
Sep  7 00:22:21 n kernel:  on lkpi_iic1
Sep  7 00:22:21 n kernel: iic4: <I2C generic I/O> on iicbus4
Sep  7 00:22:21 n kernel: lkpi_iic2: <LinuxKPI I2C> on drmn0
Sep  7 00:22:21 n kernel: iicbus5: <Philips I2C bus> on lkpi_iic2
Sep  7 00:22:21 n kernel: iic5: <I2C generic I/O> on iicbus5
Sep  7 00:22:21 n kernel: sysctl_add_oid: can't re-use a leaf (hw.dri.debug)!
Sep  7 00:22:21 n kernel: lkpi_iic3: <LinuxKPI I2C> on drm1
Sep  7 00:22:21 n kernel: iicbus6: <Philips I2C bus> on lkpi_iic3
Sep  7 00:22:21 n kernel: iic6: <I2C generic I/O> on iicbus6
Sep  7 00:22:21 n kernel: lkpi_iic4: <LinuxKPI I2C> on drm2
Sep  7 00:22:21 n kernel: iicbus7: <Philips I2C bus> on lkpi_iic4
Sep  7 00:22:21 n kernel: iic7: <I2C generic I/O> on iicbus7
Sep  7 00:22:21 n kernel: [drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
Sep  7 00:22:21 n kernel: VT: Replacing driver "efifb" with new "fb".
Sep  7 00:22:21 n kernel: start FB_INFO:
Sep  7 00:22:21 n kernel: type=11 height=1440 width=2160 depth=32
Sep  7 00:22:21 n kernel: pbase=0xa0000000 vbase=0xfffff800a0000000
Sep  7 00:22:21 n kernel: name=drmn0 flags=0x0 stride=8640 bpp=32
Sep  7 00:22:21 n kernel: end FB_INFO

There are some texts, for example:

Code:

[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0 and
Unable to create a private tmpfs mount, hugepage support will be disabled(-19).

Is this something about the xorg.conf drivers? Edit later: huge pages error, URL.

Edit later, from Xorg.0.log

Code:

[    70.878] (II) config/udev: Adding drm device (/dev/dri/card0)
[    70.878] (II) xfree86: Adding drm device (/dev/dri/card0)
[    70.878] (II) Platform probe for /dev/dri/card0
[    70.878] (II) LoadModule: "modesetting"
[    70.878] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so

and

Code:

[    70.509] (EE) modeset(G0): drmSetMaster failed: Device busy
[    70.512] (II) UnloadModule: "modesetting"
[    70.512] (II) UnloadSubModule: "glamoregl"
[    70.512] (II) Unloading glamoreg

Thanks for this.
The kernel drm module initialization is successful apparently (the driver and firmware loads), what is failing is the modesetting driver on X11.
Out of curiosity, and knowing that the intel X11 driver has issues, can you try forcing the use of the xf86-video-intel driver (example #1)?

Also, please install drm_info (pkg install drm_info), and before starting X, check if drm_info | grep Device says something?

If that doesn't work please open a ticket because there's obviously something broken.

escape · Thursday at 10:56 PM

There are multiple and old Xorg.log -files in /var/log. In 14.5-RELEASE -log is the only one printing modeset(G0): drmSetMaster failed: Device busy . For example 14.5-RC1 does not have this error. This could be a ghost hunt if the line frequently appears like this.

drm_info | grep Device prints the same hardware version as pciconf -lv: ├───Device: PCI 8086:1916 Intel Corporation Skylake-U GT2 [HD Graphics 520]

fahrenheit · Friday at 8:08 AM

escape said:
There are multiple and old Xorg.log -files in /var/log. In 14.5-RELEASE -log is the only one printing modeset(G0): drmSetMaster failed: Device busy . For example 14.5-RC1 does not have this error. This could be a ghost hunt if the line frequently appears like this.

drm_info | grep Device prints the same hardware version as pciconf -lv: ├───Device: PCI 8086:1916 Intel Corporation Skylake-U GT2 [HD Graphics 520]

Ok, so, the issue is not the drm driver (the output from dri_info confirms it loaded correctly).
So the issue ia either mesa or xorg.
Open a ticket or ask around on the x11 mailing list to get more eyes on the issue.

Erichans · Friday at 2:23 PM

escape said:
Edit later, from Xorg.0.log [...]

fahrenheit said:
[...] The kernel drm module initialization is successful apparently (the driver and firmware loads), what is failing is the modesetting driver on X11.

I agree what seems to be failing is the initialisation step of the Xorg modesetting driver. However, that might perhaps also be caused by a not fully correctly working i915kms; just the kldload-ing accompanied by the necessary firmware modules is not necessarily the same as the "drm" parts (as opposed to the Xorg parts) are functioning correctly for this CPU/GPU. In that case graphics/drm-61-kmod might not be functioning correctly for your Intel Core i5-5200U. OTOH, the problem could just as easily be somewhere else, as was suggested by fahrenheit, I'm not ruling that out.

Your Intel Core i5-5200U is from Release Date: Mar 1st, 2015; given that it's "moderately old", instead of graphics/drm-61-kmod, using graphics/drm-515-kmod seems a viable alternative, I suggest you give drm-515-kmod a try.

If you choose to do that, please save a copy of the Xorg log file when starting Xorg using graphics/drm-61-kmod. Then install graphics/drm-515-kmod. Verify, given:

Rich (BB code):

# pkg rquery -x '[%R] %o %n %v' '(^drm-(51.-|6..?-)?kmod)' | column -t | nl
     1  [FreeBSD]        graphics/drm-515-kmod  drm-515-kmod  5.15.160.1404000_10
     2  [FreeBSD]        graphics/drm-61-kmod   drm-61-kmod   6.1.128.1404000_10
     3  [FreeBSD]        graphics/drm-kmod      drm-kmod      20260508
     4  [FreeBSD-kmods]  graphics/drm-515-kmod  drm-515-kmod  5.15.160.1405000_11
     5  [FreeBSD-kmods]  graphics/drm-61-kmod   drm-61-kmod   6.1.128.1405000_11

that you have installed the version labelled with 1405000. If you install this by using pkg-install(8) you should get it from FreeBSD-ports-kmods (not from FreeBSD-ports). If you should choose to build it locally from source, then the installed package's repository will be shown as [unknown-repository] as is shown in your pkg query output in message #13.

When having used these two drm packages, please post (attach):

a full Xorg log file when using graphics/drm-61-kmod
a full Xorg log file when using graphics/drm-515-kmod

I'd be interested in comparing these. Having tried both graphics/drm-61-kmod and graphics/drm-515-kmod provides a broader context what might be failing when, and under what circumstances, in particular when filing a PR/ticket.

P.S.
I'd generally be hesitant to selectively install a sole specific intel firmware package, intended for a specific intel CPU/GPU. First it might not be easily evident what particular firmware package is required. In addition (what is not easily detected): there might be an additional other intel firmware package needed as was shown gpu-firmware-kmod for coffee lake (message #7 and follow-up).
As is shown in the output of message #13 there are fairly few intel-firmware packages.

escape · 2026-09-14T02:30:55+0100

I will get back to this later.

Is it possible based on the symptoms that the hardware could be broken? The laptop has opened itself from the corner and some thin connectors could be loose. At the same time there was an accident with a memory stick. There were read and write errors and the device was automatically unmounted often. The USB-stick was mounted in an outer device not in the laptop.

From updating to 14.5-RELEASE writing to the filesystem using a text editor there are additional requests: "the file has been modified elsewhere, do you wan't to save the file" and using mousepad: "file on disk has been changed, reload the file?". Not word by word. Is this - most likely timestamp problem - a release related problem? It isn't my hardware failing?

Espionage724 · 2026-09-14T03:12:40+0100

escape said:
Is this something about the xorg.conf drivers? Edit later: huge pages error, URL.

Edit later, from Xorg.0.log
[ 70.878] (II) LoadModule: "modesetting" [ 70.878] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.soand
[ 70.509] (EE) modeset(G0): drmSetMaster failed: Device busy [ 70.512] (II) UnloadModule: "modesetting" [ 70.512] (II) UnloadSubModule: "glamoregl" [ 70.512] (II)

I'd switch to Intel DDX (did this on i5-6400T iirc HD 530 and UHD 630):

Code:

pkg install xf86-video-intel

Code:

mkdir -p '/usr/local/etc/X11/xorg.conf.d' && ee '/usr/local/etc/X11/xorg.conf.d/10-graphics-custom.conf'

Code:

Section "OutputClass"
    Identifier "Intel (intel custom)"
    MatchDriver "i915"
    Driver "intel"
    Option "AccelMethod" "SNA"
    Option "DRI" "3"
EndSection

And check which one's used (one or the other will report a bunch of stuff with screen rates/driver settings/etc):

Code:

cat '/var/log/Xorg.0.log' | grep 'intel('

Code:

cat '/var/log/Xorg.0.log' | grep 'modeset('

Intel Skylake i5-6200U graphics driver in FreeBSD 14.5-RC1

escape

SirDice

Administrator

Thread 'Please beware of [do not visit]_www_freebsdsoftware_org_[do not visit ] - it contains AI slop'

escape

SirDice

Administrator

fahrenheit

fahrenheit

escape

SirDice

Administrator

Thread 'Intel GPU support Matrix'

fahrenheit

Erichans

escape

Erichans

escape

fahrenheit

escape

escape

fahrenheit

escape

fahrenheit

Erichans

escape

Espionage724