In x11-drivers/xf86-video-intel29, there is the following patch explicitly mentioning i915kms.ko.
--- src/intel_device.c.orig 2014-08-31 10:47:52 UTC
+++ src/intel_device.c
@@ -401,8 +401,8 @@ static int intel_open_devicelegacy(c
pci->domain, pci->bus, pci->dev, pci->func);
ret = drmCheckModesettingSupported(id);
if (ret) {
if (xf86LoadKernelModule("i915"))
if (ret || 1) {
if (xf86LoadKernelModule("i915kms"))
ret = drmCheckModesettingSupported(id);
if (ret)
return -1;
I speculate those currently running master will somewhat accidentally have an non-updated i915kms.ko still in /boot/kernel, but what about those who install DragonFly from scratch after the install image gets updated? And will the eventual update of the above patch still also test for i915ims.ko as well as i915.ko?
For lastest master, the kernel module i915kms.ko was renamed to i915.ko
http://lists.dragonflybsd.org/pipermail/commits/2015-November/458660.html
In x11-drivers/xf86-video-intel29, there is the following patch explicitly mentioning i915kms.ko.
--- src/intel_device.c.orig 2014-08-31 10:47:52 UTC +++ src/intel_device.c @@ -401,8 +401,8 @@ static int intel_open_devicelegacy(c pci->domain, pci->bus, pci->dev, pci->func);
I speculate those currently running master will somewhat accidentally have an non-updated i915kms.ko still in /boot/kernel, but what about those who install DragonFly from scratch after the install image gets updated? And will the eventual update of the above patch still also test for i915ims.ko as well as i915.ko?