<quote?> pkg_postinst_os() { if use kernel_linux then linux-mod_pkg_postinst elog "Having in-kernel DRM modules installed can prevent x11-drm modules from being" elog "loaded. It can also lead to unknown symbols in x11-drm modules, which would" elog "be seen during the installation. If you experience any of those problems," elog "please ensure that the in-kernel DRM modules are not installed." elog "This can be done with the following:" elog " cd ${KERNEL_DIR}" elog " make modules modules_install" elog "This should allow the x11-drm modules to load and function normally." </quote> But running "make modules modules_install" effectively reinstalls all kernel modules from the sourcetree and kills kernel modules installed by Gentoo packages ... so exactly the opposite. Yes, it will result in only the "vanilla" modules being installed and zaps x11-drm module ... so there no clash anymore. Because I use too new kernel it probably does not make sense for me to have x11-base/x11-drm package installed. Hope I can uninstall it and nothing depends on it. ;-)
It would zap x11-drm's modules if they were installed under the usual location (/lib/modules/KV/kernel/drivers/char/drm). However, the package installs them into /lib/modules/KV/x11-drm instead. This ensures that full kernel module rebuilds do not zap the package's modules. Unfortunately, this requires that there be no modules installed by the kernel, because it would then prefer the kernel's modules over the x11-drm modules when the user tries to load them. I hope that clarifies things for you. Please reopen if you're seeing behavior that contradicts me. Thanks.
Yes, now it is clear. It would be nice if the einfo() would at least link to your explanation in comment #1.
