Funtoo Graphics Mix-Ins
gfxcard-intel gfxcard-intel-classic gfxcard-intel-iris
gfxcard-nouveau gfxcard-nvidia gfxcard-nvidia-legacy
gfxcard-amdgpu gfxcard-radeon, gfxcard-older-ati gfxcard-ancient-ati
gfxcard-panfrost gfxcard-raspi4 gfxcard-vmware gfxcard-kvm
- This mix-in enables all DRI-based Intel integrated graphics, including support for Vulkan and video acceleration where available. Do an
emerge libva-intel-driverafterwards to ensure you have full video acceleration support.
- This mix-in enables support for modern Radeon cards, Southern Islands -- GFX Core 6 (see this x.org reference) and greater. Includes Vulkan and video acceleration where available. Drivers are built for both the Gallium framework (modern replacement for DRI framework) and DRI framework. Glamor is used to accelerate 2D operations.
- This mix-in enables support for modern Radeon cards, R600 through Northern Islands -- GFX Core 4 and 5 (see this x.org reference). Drivers are built for the Gallium framework (modern replacement for DRI framework) as well as DRI framework. Glamor is used to accelerate 2D operations.
- Use this mix-in to enable support for R300 up to (but not including) R600 Radeon cards -- -- GFX Core 3 (see this x.org reference). DRI as well as Gallium-based drivers are enabled.
- Use this mix-in to enable support pre-R300 cards -- GFX Core 1 and 2 (see this x.org reference). These drivers are DRI-based.
- Use this to enable support for proprietary NVIDIA drivers. You will also need to
emerge nvidia-kernel-modules, blacklist
nouveauand add yourself to the
videogroup. See this documentation for more details. Note that Funtoo now has two catpkgs for NVIDIA proprietary graphics --
nvidia-kernel-modules-- to aid the use of NVIDIA acceleration on containers.
- Proprietary NVIDIA drivers like above, but the legacy version of the driver that supports older hardware. See https://www.nvidia.com/en-us/drivers/unix/ and browse the specific driver version that
emergeis installing to get detailed compatibility information.
- Use this mix-in to enable support for Open Source nouveau drivers.
- This contains the bare minimum settings for all Funtoo Linux flavors.
- The core flavor includes the minimal flavor, plus reasonable settings, and is used for the official stage3 downloads.
- In the future, the server flavor will include the core flavor, plus specific settings designed for servers. At the moment, it is equivalent to the core flavor.
- The workstation flavor is a minimal desktop system. It includes the core flavor, plus these mix-ins: X, audio, dvd, media and console-extras.
- The desktop flavor includes the common settings for any full-featured desktop system. It includes the workstation flavor plus printing support. The user is expected to further customize their system with a desktop environment of choice, such as KDE, GNOME, or XFCE, possibly by using a mix-in.
- USE and package.use settings required to merge GNOME. Designed to be used with desktop or workstation flavor.
- USE and package.use settings required to merge Cinnamon. Designed to be used with desktop or workstation flavor.
- USE and package.use settings required to merge KDE Plasma 5. Designed to be used with desktop or workstation flavor.
- USE and package.use settings required to merge LXDE. Designed to be used with desktop or workstation flavor.
- USE and package.use settings required to merge LXQT. Designed to be used with desktop or workstation flavor.
- USE and package.use settings required to merge MATE. Designed to be used with desktop or workstation flavor.
- USE and package.use settings required to merge XFCE. Designed to be used with desktop or workstation flavor..
Addt'l Mix-ins available
- Increases hardness
- Enables SELinux support.
- Enables vmware guest additions.
- Enables Wayland alternative to X11.
I have multiple machines that I maintain but I want to use a central system to manage them.
I also maintain several systems in separate partitions on some machines.
The multiple machine problem is managad by building a 'thumb' drive with complete installation scripts:
- Boot a standard distribution disk
- Mount the 'thumb' drive
- Run a script from the 'thumb' drive for that machine and partition to set up the system.
- Configuring the network
- Assuring the correct partitions exist
- Some of the partitions will be for 'foreign' systems by microsoft, apple, red hat and so on...
- Creating/Cleaning up the file system on selected partions
- External identification
- Partition labels
- Internal identification - special files in 'root', starting with 'blank'
- ' LABEL=...'
- ' UUID=...'
- ' DEVICE=...' (must be verified/reset during 'boot')
- External identification
- Standard mount points and build 'fstab' entries
- from a machine configuration file on the thumb drive
- include an 'own root' symbolic link for consistancy of reference
- an 'onboot' directory tree to maintain access to directories under mount points
- Initial file population - copy selected files from the 'thumb' drive
- 'sync' the system to current levels
- 'chroot' to the newly installed system partition and run more scripts from the 'thumb' drive
- incomplete at this time
- NOTE: This process may be interupted/aborted by errors at different points and has to allow for correction/restart.
Multiple system partitions use pieces from the multiple machine solution using 'chroot'.
Help building tools
Can you guys/gals identify hook points where the above outline could make use of the profile system?
Could the profile system be extended to allow easy configuration for multiple system?