INFORMATICS

All of our EVGA power supplies are manufactured to conform to ATX standards. The ATX specification has different ratings for voltage and wattage, depending on the connector that is used. In a typical configuration, where a graphics card is directly installed into a PCIe slot on a motherboard, that PCIe slot is specified to deliver 75 watts.

PCIe risers and adapters do not conform to ATX standards. Using these types of adapters can result in damage to any system components.

The ATX standard for SATA or Molex connections is rated for 54 watts. Each SATA/Molex connector provides three 12v pins at 1.5 amps each, for a total of 4.5 amps. 12 volts, times 4.5 amps, equals 54 watts able to be provided by a SATA/Molex connector.

Some PCIe risers do not conform to ATX specifications. As ATX specifications require the PCIe slot to supply 75 watts, a PCIe riser may potentially overdraw the SATA/Molex connector by 21 watts. Please confirm that any risers you use meet ATX specifications before use. Risers that do not meet ATX specifications are not recommended for use with any EVGA power supplies or graphics cards.

If multiple graphics cards are needed to be installed in a system, it is recommended that they are installed directly into the PCIe slot on the motherboard.

The maximum power consumption of the connectors:

The PCI Express slot of the motherboard can provide up to 75 watts to the graphics card.
6-pin power connector can provide up to 75 watts.
8-pin power connector can provide up to 150 watts.

Repository installation

# dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
# dnf install https://rpms.remirepo.net/enterprise/remi-release-8.rpm



EPEL stand for Extra Packages for Enterprise Linux.
EPEL repository is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, 
including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Enterprise Linux(OEL).

Extra Packages for Enterprise Linux (EPEL) - (See http://fedoraproject.org/wiki/EPEL) provides rebuilds of Fedora packages for EL6 and EL7. Packages should not replace base, although there have been issues around point releases in the past. You can install EPEL by running yum --enablerepo=extras install epel-release. The epel-release package is included in the CentOS Extras repository that is enabled by default. Support available on Freenode in #epel, on mailing lists, and its issue tracker. If you are willing to help test EPEL updates before they are pushed to stable, you can enable the epel-testing repository on your development/testing servers. Enabling epel-testing on production systems is not a good idea.

Remi repository is a yum repository maintained by a French dude – Remi Collet. This post describe the basic steps to prepare and install the additional 
CentOS packages with EPEL and Remi Repository into CentOS 6.

Remi Repository - (See http://rpms.remirepo.net/) Remi Collet maintains a large collection of RPMS, including latest versions of PHP etc. 
He's also got an FAQ at http://blog.remirepo.net/pages/English-FAQ . 
Note that this is a collection of repos, and using the -safe series will ensure that nothing from the base CentOS Linux distro is overwritten or replaced. 
However, be aware that this repo does not play nicely with other third party repos - for example, 
Remi's packages contain Obsoletes: lines for packages from both IUS and Webtatic repos and thus will automatically replace them with the .remi version. 
This may not be the desired behaviour and you should be careful with enabling this repo for that reason.

About 'enabled' and 'disabled' repository configuration files

Please read man 5 yum.conf, particularly the discussion of enabled=0 versus enabled=1 . A line containing one of these options is recommended for each repository in each .conf file in the  /etc/yum.repos.d/  directory. This allows the administrator to more clearly specify whether a repository is or is not used for packages. After any edits of these files, in order to clear any cached information, and to make sure the changes are immediately recognized, as root run:

# yum clean all 



After modifying the repository file with new entries, proceed and clear the DNF / YUM cache as shown.

# dnf clean all
OR
# yum clean all

To confirm that the system will get packages from the locally defined repositories, run the command:

# dnf repolist
OR
# yum repolist