In the post compilling messages about of xf86-driver-intel and mesa is asked to activate KMS support in the kernel. Such a procedure can't be done for DRM_I915_KMS because the kernel lack this option. Tested in a 4.7.8-1~bpo8+1 kernel.
is this problem in combination of x11-drivers/xf86-video-intel or just with the kernel source? Which exact kernel source do you use to build?
(In reply to Jonas Stein from comment #1) > is this problem in combination of x11-drivers/xf86-video-intel > or just with the kernel source? Which exact kernel source do you use to > build? Hi, Jonas. The KMS kernel support messages are displayed for both mesa and x11-drivers/xf86-video-intel media-libs/mesa in the post compiling messages of emerge. The kernel was a debian-sources-4.7.8-1~bpo8+1
Additional info. Base system: OS amd64 desktop For each packages below (version and USE flags). -mesa media-libs/mesa-12.0.3 "bindist d3d9 gles1 gles2 openmax osmesa vaapi valgrind xvmc vdpau" -xf86-video-intel x11-drivers/xf86-video-intel-2.99.917-r2 "xvmc uxa"
Created attachment 451947 [details] xf86-video-intel postinst message
Order of facts. Two days ago I've upgraded the packages in my box and there came a mesa and xf86-video-intel postinst message related to activating KMS support over the kernel for intel machines. I made the possible changes required in the kernel such as the CONFIG_DRM_I915 and recompiled the kernel. Next, after recompiling mesa again using the modified kernel (debian-sources-4.7.8-1~bpo8+1). The postinst message of mesa is gone whereas the one from xf86-video-intel still remains.
(In reply to Lambd0x from comment #2) > (In reply to Jonas Stein from comment #1) > > is this problem in combination of x11-drivers/xf86-video-intel > > or just with the kernel source? Which exact kernel source do you use to > > build? > > Hi, Jonas. The KMS kernel support messages are displayed for both mesa and > x11-drivers/xf86-video-intel media-libs/mesa in the post compiling messages > of emerge. Mesa doesn't check any Kconfig options. I think you're mistaken about that. The highest stabilized version of xf86-video-intel (2.99.917_p20160621-r1) and all higher (unstable) versions have the following code: pkg_postinst() { if linux_config_exists && \ kernel_is -lt 4 3 && ! linux_chkconfig_present DRM_I915_KMS; then echo ewarn "This driver requires KMS support in your kernel" ewarn " Device Drivers --->" ewarn " Graphics support --->" ewarn " Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->" ewarn " <*> Intel 830M, 845G, 852GM, 855GM, 865G (i915 driver) --->" ewarn " i915 driver" ewarn " [*] Enable modesetting on intel by default" echo fi [...] } The kernel commit that removed DRM_I915_KMS is fd930478fb797e4cbaa799d9ddd970e9a1fa1b4a, and git tag --contains=... says it first appeared in v4.3, so that all seems right. I don't know what problem you're having... (In reply to Lambd0x from comment #3) > -xf86-video-intel > x11-drivers/xf86-video-intel-2.99.917-r2 > "xvmc uxa" Ah, this is your problem. The version you're using does not contain the -lt 4 3 in pkg_postinst(). I'm not sure *why* you're using that version since something newer was stabilized September 17th. Resolved: Use latest stable.
Matt, mesa had the same messages before the kernel editings that I've described above. So this postinst message issued by xf86-video-intel-2.99.917-r2 is solved by the later versions I see. I tried to unmask the last stable version: xf86-video-intel-2.99.917_p20160621-r1 but my system won't upgrade it due to a few other dependencies such as x11-drivers/xf86-input-mouse-1.9.1:0/0::gentoo/ and +3. Guess once is released a new ebuild for this a package then portage will eventually update the intel driver to the latest stable and solve the postinst message. Thanks.
(In reply to Lambd0x from comment #7) > Matt, mesa had the same messages before the kernel editings that I've > described above. You'll have to show me the code. Mesa (since we moved the ebuilds to Git) has never had the string "linux_chkconfig_present". > So this postinst message issued by xf86-video-intel-2.99.917-r2 is solved by > the later versions I see. > > I tried to unmask the last stable version: > xf86-video-intel-2.99.917_p20160621-r1 > but my system won't upgrade it due to a few other dependencies such as > x11-drivers/xf86-input-mouse-1.9.1:0/0::gentoo/ and +3. Guess once is The -mouse (and -keyboard) driver is very old and essentially deprecated. In fact, as far as I understand so are -evdev and -synaptics. You should update to use xf86-input-libinput. While we're on the topic of deprecated drivers... so is xf86-video-intel. :) When xorg-server-1.19 hits the tree, VIDEO_CARDS="i965 intel" will not require it to be installed -- instead relying on xorg-server[glamor] and its built-in modesetting driver. You can get the same effect today by adding the following entries to package.use: x11-base/xorg-server glamor x11-base/xorg-drivers -video_cards_intel
Unfortunately I can't show u the logs form portage because I just activated them one day after the incident. I'll change the drivers as you also suggested. tks.