The attached patch makes anaconda stop neutering DRI/DRM (at least it should.) It does it by including the DRI userspace modules (from mesa) and the kernel DRM drivers. Why do this? To be more like the 'normal' installed system. Heck, if DRI's going to fail, the system's just going to blow up on the first boot anyway. Furthermore, there are cards/chips that do 2D accel via the 3D pipeline. Plus, if we want to actually disable it in anaconda, we should do it explicitly, not by accident as a consequence of some files not being there. Caveats: - listing the kernel drivers explicitly is a hack - this doesn't pull libGL onto the second stage. Assuming nothing dlopens() it, that shouldn't be a problem Bill
diff --git a/scripts/mk-images b/scripts/mk-images index 9791067..34bcb1a 100755 --- a/scripts/mk-images +++ b/scripts/mk-images @@ -110,7 +110,8 @@ LVMMODS="dm-mod dm-zero dm-snapshot dm-mirror dm-multipath dm-round-robin dm-emc RAIDMODS="md raid0 raid1 raid5 raid6 raid456 raid10 linear" CRYPTOMODS="sha256_generic cbc aes_generic blkcipher crc32c" PCMCIASOCKMODS="yenta_socket i82365 tcic pcmcia" -INITRDMODS="$USBMODS $FIREWIREMODS $IDEMODS $SCSIMODS $FSMODS $LVMMODS $RAIDMODS $CRYPTOMODS $COMMONMODS $PCMCIASOCKMODS =scsi =net" +DRMMODS="drm i810 i830 i915 mga nouveau r128 radeon savage sis tdfx via" +INITRDMODS="$USBMODS $FIREWIREMODS $IDEMODS $SCSIMODS $FSMODS $LVMMODS $RAIDMODS $CRYPTOMODS $COMMONMODS $PCMCIASOCKMODS $DRMMODS =scsi =net" . $(dirname $0)/buildinstall.functions diff --git a/scripts/upd-instroot b/scripts/upd-instroot index 62e4e50..242f3a8 100755 --- a/scripts/upd-instroot +++ b/scripts/upd-instroot @@ -612,6 +612,7 @@ usr/share/X11/locale usr/share/X11/rgb* usr/share/X11/xkb usr/$LIBDIR/xserver/SecurityPolicy +usr/$LIBDIR/dri usr/$LIBDIR/xorg/modules usr/bin/chattr* usr/bin/gdialog
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
