I upgrade kernel to 2.6.31-gentoo and try run module-rebuild but x11-base/x11-drm build failed CC [M] /var/tmp/portage/x11-base/x11-drm-20090805/work/drm/linux-core/drm_proc.o /var/tmp/portage/x11-base/x11-drm-20090805/work/drm/linux-core/drm_memory.c: In function ‘agp_remap’: /var/tmp/portage/x11-base/x11-drm-20090805/work/drm/linux-core/drm_memory.c:286: error: ‘struct agp_memory’ has no member named ‘memory’ make[2]: *** [/var/tmp/portage/x11-base/x11-drm-20090805/work/drm/linux-core/drm_memory.o] Error 1 make[2]: *** Waiting for unfinished jobs.... /var/tmp/portage/x11-base/x11-drm-20090805/work/drm/linux-core/drm_proc.c: In function ‘drm__vma_info’: /var/tmp/portage/x11-base/x11-drm-20090805/work/drm/linux-core/drm_proc.c:589: warning: format ‘%08lx’ expects type ‘long unsigned int’, but argument 5 has type ‘phys_addr_t’ make[1]: *** [_module_/var/tmp/portage/x11-base/x11-drm-20090805/work/drm/linux-core] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.31-gentoo' make: *** [modules] Error 2
Created attachment 203787 [details] build.log build.log
drm.git kernel modules have been unmaintained for several kernel releases now. A statement should be added to the ebuild discouraging users from using x11-drm with newer kernels.
(In reply to comment #2) > drm.git kernel modules have been unmaintained for several kernel releases now. > A statement should be added to the ebuild discouraging users from using x11-drm > with newer kernels. > I'm also experiencing a build fail emerging x11-drm-20070314 on a 2.6.30-gentoo-r4 kernel: * Building DRM in /var/tmp/portage/x11-base/x11-drm-20070314/work/drm/linux-core... make -j2 M=/var/tmp/portage/x11-base/x11-drm-20070314/work/drm/linux-core LINUXDIR=/usr/src/linux 'DRM_MODULES= mga.ko r128.ko savage.ko' modules sh ../scripts/create_linux_pci_lists.sh < ../shared-core/drm_pciids.txt make -C /usr/src/linux SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules make[1]: Entering directory `/usr/src/linux-2.6.30-gentoo-r4' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/x11-base/x11-drm-20070314/work/drm/linux-core/drm_auth.o In file included from /var/tmp/portage/x11-base/x11-drm-20070314/work/drm/linux-core/drmP.h:83, from /var/tmp/portage/x11-base/x11-drm-20070314/work/drm/linux-core/drm_auth.c:36: /var/tmp/portage/x11-base/x11-drm-20070314/work/drm/linux-core/drm_os_linux.h:62: error: conflicting types for ‘irqreturn_t’ include/linux/irqreturn.h:16: error: previous declaration of ‘irqreturn_t’ was here make[2]: *** [/var/tmp/portage/x11-base/x11-drm-20070314/work/drm/linux-core/drm_auth.o] Error 1 make[1]: *** [_module_/var/tmp/portage/x11-base/x11-drm-20070314/work/drm/linux-core] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo-r4' make: *** [modules] Error 2 * Portage could not build the DRM modules. If you see an ACCESS DENIED error, * this could mean that you were using an unsupported kernel build system. * Only 2.6 kernels at least as new as 2.6.6 are supported. * * ERROR: x11-base/x11-drm-20070314 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 4038: Called src_compile_os * environment, line 4072: Called src_compile_linux * environment, line 4061: Called die_error * environment, line 1182: Called die * The specific snippet of code: * die "Unable to build DRM modules." * The die message: * Unable to build DRM modules. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-base/x11-drm-20070314/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-base/x11-drm-20070314/temp/environment'. * x11-drm-20070314 is marked as a stable package on the x86 architecture, and on two PCs of mine (one with VT82C598 [Apollo MVP3] chipset and another with a VT82C693A/694x [Apollo PRO133x] chipset, both with ATI Rage128 AGP card) the x11-drm-20090805 driver, though it compiles all right, causes a kernel crash and a following reboot by the hangcheck_timer module, I believe.
Maybe we should just remove the ebuild and teach pple to use in-kernel modules.
+1, x11-drm looks like a dead end to me. Everyone is working directly in the kernel now, not just Intel. Bryan, what say you? Thanks
This is not entirely correct, mach64 drm is only available via x11-drm and not in the kernel. But all other drivers could be dropped.
At the moment I'd to update the x11-drm snapshot, restore 2.6.31 compat and remove all the VIDEO_CARDS except for mach64. This works for the immediate future for mach64 users. All other users will get an error advising them to remove the package and use in-kernel modules. FreeBSD support should be dropped as that, too, has stagnated since March and I don't know if it even works with FBSD/Gentoo. However, the mach64 driver hasn't been touched in years (and may still have security vulnerabilities?) and the DRM git@fdo is probably going to be abandoned completely (outside of libdrm and the utils). I've got no experience with mach64 hardware, but it's probably a good idea to kill x11-drm once and for all after the aforementioned snapshot. We can move the DRM test utils to a new snapshot package as was done in the x11 overlay. Any thoughts?
Sounds good to me.
Actually the security issues of the mach64 driver have been fixed some time ago already. However not much has happened since then. http://lists.freedesktop.org/archives/xorg/2006-October/019137.html
IMHO, we should be able to just not care about mach64 drm anymore. xf86-video-mach64 works just fine without a drm module (unlike -intel these days) and I honestly doubt there are many people who except working 3D on such antiquated hardware. @Bryan, so feel free to do that one last snapshot if you really want to, but I definitely won't blame you if you just leave it die now :) Thanks
I would go with killing it too.
Ok then. I've masked x11-drm for removal in 30 days. I'll close this bug after that.
x11-base/x11-drm has now been removed from the tree.
