https://www.funtoo.org/api.php?action=feedcontributions&user=Azerthoth&feedformat=atomFuntoo - User contributions [en]2024-03-28T19:40:07ZUser contributionsMediaWiki 1.36.2https://www.funtoo.org/index.php?title=Package:VirtualBox&diff=16994Package:VirtualBox2016-10-22T09:15:34Z<p>Azerthoth: correcting gpasswd -a bob vboxguests to gpasswd -a bob vboxguest the group has no s</p>
<hr />
<div>{{Ebuild<br />
|Summary=A desktop virtualization package from Oracle Corporation that allows you to run a guest operating system (Linux, Windows or other) on your Linux system.<br />
|CatPkg=app-emulation/virtualbox<br />
}}<br />
'''VirtualBox''' is a free and open source [https://www.wikipedia.org/wiki/Virtualization virtualization] '[https://www.wikipedia.org/wiki/Hypervisor hypervisor]' for x86-based machines. VirtualBox can be installed and run on GNU/Linux and other Operating Systems.<br />
<br />
The [https://en.wikipedia.org/wiki/Virtual_machine virtual machines] provided by VirtualBox can be used to run a number of guest Operating Systems such as GNU/Linux, Windows, and others.<br />
<br />
VirtualBox is available for Funtoo Linux on the ''arch'' profiles '''x86-32bit''', '''x86-64bit''' and '''pure-64'''.<br />
<br />
VirtualBox Homepage: https://www.virtualbox.org<br />
<br />
== Glossary of Terms ==<br />
<br />
{{TableStart}}<br />
{{2ColHead|Term|Explanation}}<br />
{{2Col|'''''Host OS''''' |An install of Funtoo Linux on physical hardware. VirtualBox will be installed to and run from here.}}<br />
{{2Col|'''''Guest OS'''''|The Operating System that is run '''within a Virtual Machine''' provided by VirtualBox. The Guest OS could be Funtoo Linux, another GNU/Linux distribution, Windows, etc.}}<br />
{{2Col|'''''Guest Additions'''''|''Guest Additions'' is a collection of applications, libraries and kernel modules/drivers that are installed in your Guest OS. These provide support for graphics, networking, and other features such as file transfer and Guest access to real physical devices such as a USB flash drive.}}<br />
{{TableEnd}}<br />
<br />
== Host OS Installation ==<br />
VirtualBox can be installed onto your Host OS - Funtoo Linux - using one of two packages: {{c|app-emulation/virtualbox}} or {{c|app-emulation/virtualbox-bin}}. The latter "-bin" package is a binary (precompiled) copy of VirtualBox. Installing this may be preferable on machines with low computing power.<br />
<br />
For a typical install, run<br />
{{console|body=<br />
###i## emerge --ask app-emulation/virtualbox<br />
}}<br />
<br />
=== Assign VirtualBox Users ===<br />
<br />
Normal non-root users will not be able to use VirtualBox immediately after it has been installed. The Users that are to use VirtualBox must first become a member of the group {{c|vboxusers}}. For example, a user ''alice'' is added to {{c|vboxusers}}<br />
<br />
{{console|body=<br />
###i## gpasswd -a alice vboxusers<br />
}}<br />
<br />
If currently logged in the User added to {{c|vboxusers}} must first log out before the changes will have an effect.<br />
<br />
=== Load VirtualBox Kernel Modules ===<br />
<br />
VirtualBox requires one or more Linux kernel modules to be loaded on the Host OS (Funtoo Linux) in order to function. As of VirtualBox version 5 these are provided by the package {{c|app-emulation/virtualbox-drivers}} which is installed automatically (as a dependency) when you install app-emulation/virtualbox.<br />
<br />
As ''root '' load these modules in a terminal<br />
{{console|body=<br />
###i## modprobe vboxdrv<br />
###i## modprobe vboxnetadp<br />
###i## modprobe vboxnetflt<br />
}}<br />
<br />
Each time the Host machine (Funtoo Linux) is rebooted the modules will be unloaded. The modules can be loaded automatically during system startup via OpenRC (sys-app/openrc). To achieve this, edit the file {{f|/etc/conf.d/modules}} to contain the following line<br />
{{file|name=/etc/conf.d/modules|body=<br />
modules="vboxdrv vboxnetadp vboxnetflt"<br />
}}<br />
<br />
=== Starting VirtualBox ===<br />
VirtualBox can be started from a terminal.<br />
{{console|body=<br />
$##i## virtualbox<br />
}}<br />
<br />
In a Desktop Environment, VirtualBox may also be run from a menu entry. Look for the names "VirtualBox" or "Oracle xVM VirtualBox" under menu categories "System" and/or "Emulator".<br />
<br />
=== Funtoo Linux (Host OS) kernel updates ===<br />
The VirtualBox kernel modules are compiled for the kernel present on the Host, Funtoo Linux. Each time that the Host kernel is updated or changed, the VirtualBox kernel modules must also be rebuilt.<br />
<br />
As is typical for most kernel changes or updates, please run <br />
{{console|body=<br />
###i## emerge --ask @module-rebuild<br />
}}<br />
''before'' running VirtualBox under the new kernel.<br />
<br />
If you wish to check that the VirtualBox kernel drivers will be rebuilt in this way, please examine the file {{f|/var/lib/module-rebuild/moduledb}}. For example, using the command {{c|grep}}<br />
<br />
{{console|body=<br />
$##i## grep virtualbox /var/lib/module-rebuild/moduledb<br />
a:1:app-emulation/##r##virtualbox##!r##-modules-5.0.20<br />
}}<br />
<br />
== Guest OS Installation ==<br />
=== Install Guest Additions ===<br />
VirtualBox '''Guest Additions''' is a collection of applications, libraries and kernel modules/drivers that are installed in your Guest OS. These provide support for graphics, networking, and other features such as file transfer and Guest access to real physical devices such as a USB flash drive.<br />
<br />
==== Funtoo or Gentoo Linux Guests ====<br />
Following the successful installation of you Funtoo Linux ''Guest OS'' (that is within a Virtual Machine), install the package {{c|app-emulation/virtualbox-guest-additions}}.<br />
{{console|body=<br />
###i## emerge --ask app-emulation/virtualbox-guest-additions<br />
}}<br />
<br />
Next, add your Guest OS Users to the group {{c|vboxguest}}. For example, a user ''bob'' is added to {{c|vboxguests}}<br />
<br />
{{console|body=<br />
###i## gpasswd -a bob vboxguest<br />
}}<br />
<br />
Now add virtual-box-guest additions to the default runlevel of OpenRC.<br />
<br />
{{console|body=<br />
###i## rc-update add virtualbox-guest-additions default<br />
}}<br />
<br />
Without having to reboot you can now start virtualbox-guest-additions within the Funtoo Guest OS with the command<br />
{{console|body=<br />
###i## rc<br />
}}<br />
<br />
==== Other GNU/Linux Guests ====<br />
For other GNU/Linux, please refer to [https://www.virtualbox.org/manual/ch04.html#idp11274368 VirtualBox documentation].<br />
<br />
==== Microsoft Windows Guests ====<br />
VirtualBox Guest Additions are installed in a Windows Guest by mounting a virtual CD-ROM image (.iso) within the guest virtual machine.<br />
<br />
In your Host OS Funtoo Linux, confirm the version of VirtualBox installed:<br />
For {{c|app-emulation/virtualbox}}<br />
{{console|body=<br />
$##i## emerge --pretend --quiet app-emulation/virtualbox<br />
[##g##ebuild##!g## ##y##R##!y## ] ##g##app-emulation/virtualbox-5.0.20##!g##<br />
}}<br />
<br />
'''For VirtualBox versions 4.x (less than 5.0)'''<br />
<br />
Under the earlier chapter [[ Package:VirtualBox#Host_OS_Installation|Host OS Installation ]], install {{c|app-emulation/virtualbox}} (or {{c|app-emulation/virtualbox-bin}}) with the USE flag {{c|additions}} enabled. This will provide the ISO necessary for installing Guest Additions within a Microsoft Windows guest.<br />
<br />
'''For VirtualBox versions 5.0 and above'''<br />
<br />
From version 5.0 the USE flag {{c|additions}} has been removed from the package app-emulation/virtualbox. The Guest Additions ISO required for a Windows-based Guest OS is now provided in a separate package, {{c|app-emulation/virtualbox-additions}}. Install this manually<br />
{{console|body=<br />
###i## emerge --ask app-emulation/virtualbox-additions<br />
}}<br />
<br />
{{warning|The package app-emulation/'''virtualbox-additions''' installs the Guest Additions ISO on your Host OS (Funtoo Linux). This is what you mount in a VM with Windows as a Guest OS. The package app-emulation/'''virtualbox-guest-additions''' is different. This is the Guest Additions that you install ''inside of a VM'' that happens to be a Guest OS of Funtoo Linux or Gentoo Linux.<br />
<br />
The two packages perform different tasks so be sure to install the correct package!}}<br />
<br />
Mount the Guest Additions ISO {{f|/usr/share/virtualbox/VBoxGuestAdditions.iso}} inside of your Microsoft Windows guest. Within Windows, browse to and install VirtualBox Guest Additions.<br />
<br />
== Tips and Tricks ==<br />
=== Configure Video within Funtoo Linux Guests ===<br />
{{note|This section is being developed.}}<br />
For Funtoo, Gentoo and other GNU/Linux ''Guest OS'' the [https://ww.wikipedia.org/wiki/X_Window_System X Window System] can be optimized for running within a VirtualBox virtual machine.<br />
<br />
In a Funtoo Linux ''Guest OS'', modify the file {{f|/etc/portage/[[make.conf]]}} to include the following line<br />
{{file|name=/etc/portage/make.conf|body=<br />
VIDEO_CARDS="virtualbox"<br />
}}<br />
<br />
=== Providing USB2, USB3, VRDP and/or PXE Boot ROM to Guest OS ===<br />
{{note|This section is being developed.}}<br />
Accept PUEL licence<br />
<br />
emerge app-emulation/virtualbox-extpack-oracle<br />
<br />
== Troubleshooting ==<br />
=== EFI case ===<br />
latest releases of virtualbox have a volatile NVRAM and this makes an EFI guest boot troublesome. To workaround this following steps required:<br />
* remove any CD images (like systemrescuecd) from the VM settings<br />
* start the VM<br />
* wait for the countdown or press Esc immediately to reach the EFI shell<br />
* type <code>edit startup.nsh</code> to open the full-screen editor<br />
* enter <code>"fs0:\EFI\Funtoo Linux [GRUB]\grubx64.efi" </code> (including the double quotes, since the path contains spaces)<br />
* press <code>CTRL-s</code> (maybe twice) to save and confirm saving by pressing Enter<br />
* quit editor by pressing <code>CTRL-q</code><br />
* type <code>reset</code> to reboot the machine (or kill the VM and boot it using the GUI)<br />
* wait for the countdown or press Enter to immediately run the startup.nsh script<br />
EFI guests now should properly boot.<br />
reference reports: https://www.virtualbox.org/ticket/14279 and https://bugs.funtoo.org/browse/FL-2640<br />
<br />
[[Category:Ebuilds]]<br />
[[Category:Virtualization]]<br />
{{EbuildFooter}}</div>Azerthothhttps://www.funtoo.org/index.php?title=Building_a_Kernel_from_Source&diff=10705Building a Kernel from Source2015-06-30T21:03:28Z<p>Azerthoth: /* Configuring the kernel */ added make oldconfig if using an older kernel config file</p>
<hr />
<div>Setting up a proper kernel yourself - lean, mean and tailored to your hardware, is the challenge by which a linux user can graduate to becoming a Funtoo knight ;-)<br />
<br />
Even though many of us are using enterprise-ready kernels in datacenters, there is almost nobody who hasn't at least considered building a kernel for his laptop / PC.<br />
We are showing here how an intermediate Linux user can use an alternative to the standard beginners "genkernel" approach, to compile a custom kernel, in a relatively speedy and easy set up.<br />
<br />
== Minimum Requirements ==<br />
* '''Understand the command line'''<br />
* '''Know where the kernel files are located'''<br />
<br />
== Assumptions ==<br />
You start from an installed Funtoo system on the disk, or at least, you are on stage3 in a chrooted environment from a live cd, following somehow the Funto [[Installation (Tutorial)|Installation Tutorial]].<br />
<br />
== Less advanced version ==<br />
=== Emerging the kernel sources ===<br />
To begin, we have to figure out which kernel sources we will use. If you are unsure about which sources are available and what their benefits and drawbacks are, check out the [[Funtoo_Linux_Kernels| Kernels]] page.<br />
<br />
After you have made a decsion as to which kernel you want to install, emerge it:<br />
<console><br />
###i## emerge sys-kernel/[kernel-name]<br />
</console><br />
Portage will now go about installing the sources to ''/usr/src''. However, it is preferable to also create a symlink with eselect as such: <br />
<console><br />
###i## eselect kernel set 1<br />
</console><br />
You may use<br />
<console><br />
###i## eselect kernel list<br />
</console><br />
to display a list of kernels currently installed.<br />
<br />
Using the above command is useful, because it allows you to always be able to go to the directory "/usr/src/linux" and find your current working kernel and build files.<br />
The "/usr/src/linux" directory is simply a symlink to the kernel you selected with eselect, in the "/usr/src" directory.<br />
<br />
Note that portage can also set this up for you automatically, by setting the "symlink" USE flag for your kernel.<br />
<br />
=== Configuring the kernel ===<br />
Now that the kernel sources are on your system, you should configure them. To do this, change your directory to ''/usr/src/linux''<br />
<console><br />
###i## cd /usr/src/linux<br />
</console><br />
<br />
We are now in the kernel sources directory, next sanitize the sources:<br />
{{warning|this will delete your .config}}<br />
<console>###i## make clean && make distclean && make mrproper</console><br />
<br />
Copy configurations if you have previous configurations to copy:<br />
<console>###i## cp /boot/config-3.13.7 .config</console><br />
{{important|If the configuration you copy is for a kernel older than the one you are building you must<br />
<console><br />
###i## make oldconfig<br />
</console><br />
}}<br />
<br />
We can now run a script that allows us to modify the configuration. Run:<br />
<console><br />
###i## make menuconfig<br />
</console><br />
<br />
or<br />
<br />
<console><br />
###i## make nconfig<br />
</console><br />
<br />
{{kernelop||desc=here is where you insert kernel configs, or press / to search for kernel modules by name}}<br />
<br />
While you edit the sources, keep the following in mind:<br />
* To build something into your kernel, press y when you have it selected.<br />
* To exclude something from your kernel, press n when you have it selected.<br />
* To build something as a module, press m. <br />
<br />
<br />
Things that you may need to include in your kernel:<br />
<br />
as '''modules''':<br />
<br />
* Wireless/LAN drivers<br />
* Support for your graphics card<br />
* Support for your audio card<br />
* Support for USB devices<br />
<br />
<br />
as '''built in''':<br />
* scsi sata & or ata controllers<br />
* file system used<br />
<br />
{{note|1=<br />
Many pages on the wiki will tell you the kernel requirements for the application that they are about. Keep your eyes open for the blue background, white text sections of pages. Like on this one: [[uvesafb| uvesafb]]}}<br />
<br />
=== Building and installing the kernel sources ===<br />
After you finish configuring your kernel sources, you will need to build them. To build your sources, run the following:<br />
<console><br />
###i## make<br />
</console><br />
{{tip|1=<br />
You can add -j<number of processing cores + 1> after make to build the kernel more quickly.}}<br />
<br />
When the kernel and its modules finish building, install them:<br />
<console><br />
###i## make modules_install && make install<br />
</console><br />
Now that you have installed your kernel and modules, it is a good idea to install an [[Building_a_Kernel_from_Source#Initramfs| Initramfs]].<br />
* If your system has a separate ''/usr'' partition, is encrypted, or uses some other non-standard configuration, it will probably not boot without an initramfs.<br />
* If your system is unencrypted, with file system, and hard drive controllers compiled in rather than as modules, it will not need an initramfs.<br />
<br />
== Advanced version == <br />
=== Getting ready to start ===<br />
<br />
{{note|In this case we are building a kernel that is booting root in LVM over encrypted LUKS container.<br />
If you don't have this setup, don't worry, you just don't need all the modules, but everything else is similar.}}<br />
First, there is the decision which linux kernel sources we need.<br />
There are plenty of them in the repositories around, often it is not easy to distinguish between them.<br />
<br />
I would always trust my distribution of choice and take what is has to offer - and funtoo has a lot to offer!<br />
<br />
I really do recommend (especially if it is your first time) to build a debian-sourced genkernel like described in chapter 5 "Using Debian-Sources with Genkernel" in the [[Funtoo_Linux_Kernels| Funtoo Kernels Tutorial]].<br />
<br />
From there you should have a running system booting nicely from your own build (just little bit bloated) kernel. This is more than you can expect from any other ready to go distribution.<br />
<br />
{{note|1=<br />
We are using Red Hat's dracut in order to build a nice initramfs (containing all the necessary tools and extra drivers our kernel might need to start the system). Although dracut is the way to go, more sophisticated and not as buggy as gentoo's genkernel approach, more and more funtoo geeks start using slashbeast's better-initramfs, which we will cover at the end of this howto! So after having set up a genkernel from debian or gentoo sources we are going to build a kernel with either (or both) dracut or/and better-initramfs. So gentoo sources with genkernel is always my backup if anything is not working correctly on my system. For the slightly more geeky approach with my own initram I am using pf-sources, ck-sources or any other more or less heavily patched sources.}}<br />
<br />
Let's go!<br />
<br />
=== Kernel Sources ===<br />
The source you use on your system is up to you. For a laptop or desktop system, the following are recommended:<br />
* '''{{Package|sys-kernel/pf-sources}}'''<br />
* '''{{Package|sys-kernel/ck-sources}}'''<br />
* '''{{Package|sys-kernel/gentoo-sources}}'''<br />
* '''{{Package|sys-kernel/git-sources}}'''<br />
* '''{{Package|sys-kernel/sysrescue-std-sources}}'''<br />
* '''{{Package|sys-kernel/debian-sources}}'''<br />
{{note|If you are unsure of which sources you would like to use, emerge <code>gentoo-sources</code>. That's always a safe bet for a general system. For more information on available kernels, check out: [[Funtoo Linux Kernels]]}}<br />
<br />
Please see discussion page for listings of [[Talk:Building_a_Kernel_from_Source|sys-kernel]] <br /><br />
Please see http://www.funtoo.org/Package:Eix page for more commands to see more kernel-related information.<br />
<br />
=== Prerequisites ===<br />
<br />
=== Preparing the kernel ===<br />
<br />
We go now to the sources directory and enter the following commands to update the kernel's .config file:<br />
<console><br />
###i## cd /usr/src/linux/<br />
###i## make clean<br />
CLEAN .<br />
CLEAN arch/x86/kernel/acpi/realmode<br />
CLEAN arch/x86/kernel/cpu<br />
CLEAN arch/x86/kernel<br />
CLEAN arch/x86/vdso<br />
CLEAN arch/x86/lib<br />
CLEAN drivers/gpu/drm/radeon<br />
CLEAN drivers/net/wan<br />
CLEAN drivers/scsi/aic7xxx<br />
CLEAN drivers/tty/vt<br />
CLEAN drivers/video/logo<br />
CLEAN firmware<br />
CLEAN kernel<br />
CLEAN lib/raid6<br />
CLEAN lib<br />
CLEAN security/apparmor<br />
CLEAN security/selinux<br />
CLEAN usr<br />
CLEAN arch/x86/boot/compressed<br />
CLEAN arch/x86/boot<br />
CLEAN .tmp_versions<br />
CLEAN vmlinux System.map .tmp_kallsyms2.S .tmp_kallsyms1.o .tmp_kallsyms2.o .tmp_kallsyms1.S .tmp_vmlinux1 .tmp_vmlinux2 .tmp_System.map<br />
###i## zcat /proc/config.gz > /usr/src/linux/.config<br />
</console><br />
<br />
Next, we run <code>make localmodconfig</code>. You will get some questions which you can answer mostly with either M (compiled as a module) or Y (compiled directly into the kernel). If you are not sure what to choose, press enter, and the default option will be selected.<br />
<console><br />
###i## make localmodconfig<br />
Enable different security models (SECURITY) [Y/n/?] y<br />
Enable the securityfs filesystem (SECURITYFS) [Y/?] y<br />
Socket and Networking Security Hooks (SECURITY_NETWORK) [Y/?] y<br />
Security hooks for pathname based access control (SECURITY_PATH) [Y/?] y<br />
Low address space for LSM to protect from user allocation (LSM_MMAP_MIN_ADDR) [65536] 65536<br />
NSA SELinux Support (SECURITY_SELINUX) [Y/n/?] y<br />
NSA SELinux boot parameter (SECURITY_SELINUX_BOOTPARAM) [N/y/?] n<br />
NSA SELinux runtime disable (SECURITY_SELINUX_DISABLE) [N/y/?] n<br />
NSA SELinux Development Support (SECURITY_SELINUX_DEVELOP) [Y/n/?] y<br />
NSA SELinux AVC Statistics (SECURITY_SELINUX_AVC_STATS) [Y/n/?] y<br />
NSA SELinux checkreqprot default value (SECURITY_SELINUX_CHECKREQPROT_VALUE) [1] 1<br />
NSA SELinux maximum supported policy format version (SECURITY_SELINUX_POLICYDB_VERSION_MAX) [Y/n/?] y<br />
NSA SELinux maximum supported policy format version value (SECURITY_SELINUX_POLICYDB_VERSION_MAX_VALUE) [19] 19<br />
TOMOYO Linux Support (SECURITY_TOMOYO) [Y/n/?] y<br />
Default maximal count for learning mode (SECURITY_TOMOYO_MAX_ACCEPT_ENTRY) [2048] 2048<br />
Default maximal count for audit log (SECURITY_TOMOYO_MAX_AUDIT_LOG) [1024] 1024<br />
Activate without calling userspace policy loader. (SECURITY_TOMOYO_OMIT_USERSPACE_LOADER) [Y/n/?] y<br />
AppArmor support (SECURITY_APPARMOR) [Y/n/?] y<br />
AppArmor boot parameter default value (SECURITY_APPARMOR_BOOTPARAM_VALUE) [1] 1<br />
Integrity Measurement Architecture(IMA) (IMA) [Y/n/?] y<br />
EVM support (EVM) [N/y/?] (NEW)<br />
Default security module<br />
1. SELinux (DEFAULT_SECURITY_SELINUX)<br />
2. TOMOYO (DEFAULT_SECURITY_TOMOYO)<br />
3. AppArmor (DEFAULT_SECURITY_APPARMOR)<br />
> 4. Unix Discretionary Access Controls (DEFAULT_SECURITY_DAC)<br />
choice[1-4?]: 4<br />
warning: (ACPI_HOTPLUG_CPU) selects ACPI_CONTAINER which has unmet direct dependencies (ACPI && EXPERIMENTAL)<br />
warning: (MEDIA_TUNER) selects MEDIA_TUNER_TEA5761 which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_MEDIA && I2C && EXPERIMENTAL)<br />
#<br />
# configuration written to .config<br />
#<br />
warning: (GFS2_FS) selects DLM which has unmet direct dependencies (EXPERIMENTAL && INET && SYSFS && CONFIGFS_FS && (IPV6 || IPV6=n))<br />
warning: (IMA) selects TCG_TPM which has unmet direct dependencies (HAS_IOMEM && EXPERIMENTAL)<br />
warning: (MEDIA_TUNER) selects MEDIA_TUNER_TEA5761 which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_MEDIA && I2C && EXPERIMENTAL)<br />
warning: (ACPI_HOTPLUG_CPU) selects ACPI_CONTAINER which has unmet direct dependencies (ACPI && EXPERIMENTAL)<br />
</console><br />
<br />
Now comes the most adventurous part!<br />
<br />
=== Building the Kernel ===<br />
<console><br />
###i## make -j8 bzImage<br />
###i## make -j8 modules<br />
###i## make modules_install<br />
###i## make install<br />
</console><br />
<br />
== Initramfs ==<br />
{{warning|Make sure that you have built and installed your kernel sources / modules before building an initramfs.}}<br />
To get your initramfs up and running, check out the [http://www.funtoo.org/Initramfs Initramfs] page. After following all the directions on the page to get your initramfs set up, continue following the ones here.<br />
<br />
Update the <code>grub.cfg</code> with boot update, then reboot and see how it works!<br />
<console><br />
###i## boot-update -v<br />
###i## reboot<br />
</console><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Featured]]<br />
[[Category:Kernel]]</div>Azerthothhttps://www.funtoo.org/index.php?title=Package:NVIDIA_Linux_Display_Drivers&diff=10704Package:NVIDIA Linux Display Drivers2015-06-30T20:44:08Z<p>Azerthoth: </p>
<hr />
<div>{{Ebuild<br />
|Summary=NVIDIA accelerated graphics driver<br />
|CatPkg=x11-drivers/nvidia-drivers<br />
|Repository=Funtoo Overlay<br />
|Overlay=Funtoo<br />
}}<br />
== Introduction ==<br />
NVIDIA have proprietary graphics drivers for Linux under binary blob. The alternative open source driver is {{Package|x11-drivers/xf86-video-nouveau}}.<br />
<br />
{{warning|If you installed debian-sources with the binary USE flag you will need to blacklist the nouveau module<br />
<console> ###i## echo "blacklist nouveau" >> /etc/modprobe.d/blacklist </console>}}<br />
<br />
== Preparing to Install ==<br />
=== Hardware compatibility and driver versions ===<br />
Currently, there are five versions of meta NVIDIA Linux drivers, each of which supports a specific group of GPUs. To check the type of driver that is related to your video card, check out the official page of the NVIDIA [http://www.nvidia.com/object/IO_32667.html complete list of supported GPUs].<br />
<br />
If you have identified as your driver version 337.25, for example, you need the mask(s) driver(s) latest(s) to which you want to install.<br />
<br />
<console><br />
###i## echo “>x11-drivers/nvidia-drivers-340” >> /etc/portage/package.mask<br />
</console><br />
<br />
=== The required kernel options ===<br />
<br />
{{kernelop|desc=<br />
[*] Enable loadable module support<br />
}}<br />
{{kernelop|desc=<br />
[*] MTRR (Memory Type Range Register) support<br />
}}<br />
To we made a successful compilation of the legacy NVIDIA driver, we set before the removal of the native framebuffer drivers into the kernel in order to avoid conflicts for x86 and AMD64 processors, in this case.<br />
{{kernelop|desc=<br />
Device Drivers ---><br />
Graphics support ---> <br />
<*> Support for frame buffer devices ---><br />
<> NVIDIA Framebuffer Support<br />
<> NVIDIA Riva support<br />
}}<br />
<br />
{{tip|An alternative is to [[uvesafb|uvesafb]] framebuffer, or vesa framebuffer which can be installed in parallel with nvidia-drivers }}<br />
<br />
== Installation ==<br />
<br />
Upgrade and/or configure <code>VIDEO_CARDS</code> variable to <code>nvidia</code> in <code>/etc/[[make.conf]]</code>. This will serve to while you are installing the Server X, the correct version of nvidia-drivers to be provided for you.<br />
<console><br />
# ##i##nano /etc/make.conf<br />
VIDEO_CARDS="nvidia"<br />
</console><br />
<br />
{{note|Installing to the driver with the option in '''gtk''' use flags will make it installed the <code>media-video/nvidia-settings</code> which is a graphical tool for monitoring and various settings for your video card}}<br />
<br />
=== Emerging the package ===<br />
<console><br />
###i## emerge x11-drivers/nvidia-drivers<br />
</console><br />
<br />
When the installation is complete run '''modprobe''' nvidia module to read kernel memory.<br />
<br />
<console><br />
###i## lsmod | grep nvidia<br />
</console><br />
If an update before remove the old module<br />
<console><br />
###i## rmmod nvidia<br />
###i## modprobe nvidia<br />
</console><br />
<br />
=== Testing your Video Card ===<br />
To test your video card run the glxinfo program, which is part of the mesa-progs package. This will check if direct rendering is enabled.<br />
<console><br />
$ ##i##glxinfo | grep direct<br />
$ ##i## direct rendering: yes<br />
</console><br />
<br />
== Configuring ==<br />
=== Loading at boot ===<br />
To automate the loading of the module when you boot your system, add '''nvidia''' in modules variable.<br />
<console><br />
# ##i##nano /etc/conf.d/modules<br />
modules="nvidia"<br />
</console><br />
<br />
=== Integration with X Server ===<br />
When your X server is installed find, and there's <code>/etc/X11/xorg.conf</code> you can run the nvidia-xconfig which will set in xorg.conf to identify the video card among other possible configurations.<br />
<br />
<console>###i## nvidia-xconfig</console><br />
<br />
{{file|name=/etc/X11/xorg.conf|body=<br />
Section "Device"<br />
Identifier "nvidia"<br />
Driver "nvidia"<br />
VendorName "NVIDIA Corporation"<br />
BoardName "[Name] [Model]"<br />
EndSection<br />
}}<br />
<br />
=== Enabling NVIDIA Support ===<br />
Include the use flag in '''nvidia''' in <code>/etc/[[make.conf]]</code> so due to applications that make use of this advantage may withdraw.<br />
<console><br />
# ##i##nano /etc/make.conf<br />
USE="nvidia"<br />
</console><br />
<br />
=== Enabling OpenGL/OpenCL ===<br />
As a requirement, make sure that the Xorg server is not in use during this change. To enable OpenGL and OpenCL.<br />
<console><br />
###i## eselect opengl set nvidia<br />
###i## eselect opencl set nvidia<br />
</console><br />
<br />
[[Category:Video Cards]]<br />
[[Category:First Steps]]<br />
{{EbuildFooter}}</div>Azerthothhttps://www.funtoo.org/index.php?title=Package:NVIDIA_Linux_Display_Drivers&diff=10703Package:NVIDIA Linux Display Drivers2015-06-30T20:42:18Z<p>Azerthoth: </p>
<hr />
<div>{{Ebuild<br />
|Summary=NVIDIA accelerated graphics driver<br />
|CatPkg=x11-drivers/nvidia-drivers<br />
|Repository=Funtoo Overlay<br />
|Overlay=Funtoo<br />
}}<br />
== Introduction ==<br />
NVIDIA have proprietary graphics drivers for Linux under binary blob. The alternative open source driver is {{Package|x11-drivers/xf86-video-nouveau}}.<br />
<br />
{{note|If you installed debian-sources with the binary USE flag you will need to blacklist the nouveau module in /etc/modprobe.d/blacklist with the comment blacklist nouveau<br />
<console> ###i## echo "blacklist nouveau" >> /etc/modprobe.d/blacklist </console>}}<br />
<br />
== Preparing to Install ==<br />
=== Hardware compatibility and driver versions ===<br />
Currently, there are five versions of meta NVIDIA Linux drivers, each of which supports a specific group of GPUs. To check the type of driver that is related to your video card, check out the official page of the NVIDIA [http://www.nvidia.com/object/IO_32667.html complete list of supported GPUs].<br />
<br />
If you have identified as your driver version 337.25, for example, you need the mask(s) driver(s) latest(s) to which you want to install.<br />
<br />
<console><br />
###i## echo “>x11-drivers/nvidia-drivers-340” >> /etc/portage/package.mask<br />
</console><br />
<br />
=== The required kernel options ===<br />
<br />
{{kernelop|desc=<br />
[*] Enable loadable module support<br />
}}<br />
{{kernelop|desc=<br />
[*] MTRR (Memory Type Range Register) support<br />
}}<br />
To we made a successful compilation of the legacy NVIDIA driver, we set before the removal of the native framebuffer drivers into the kernel in order to avoid conflicts for x86 and AMD64 processors, in this case.<br />
{{kernelop|desc=<br />
Device Drivers ---><br />
Graphics support ---> <br />
<*> Support for frame buffer devices ---><br />
<> NVIDIA Framebuffer Support<br />
<> NVIDIA Riva support<br />
}}<br />
<br />
{{tip|An alternative is to [[uvesafb|uvesafb]] framebuffer, or vesa framebuffer which can be installed in parallel with nvidia-drivers }}<br />
<br />
== Installation ==<br />
<br />
Upgrade and/or configure <code>VIDEO_CARDS</code> variable to <code>nvidia</code> in <code>/etc/[[make.conf]]</code>. This will serve to while you are installing the Server X, the correct version of nvidia-drivers to be provided for you.<br />
<console><br />
# ##i##nano /etc/make.conf<br />
VIDEO_CARDS="nvidia"<br />
</console><br />
<br />
{{note|Installing to the driver with the option in '''gtk''' use flags will make it installed the <code>media-video/nvidia-settings</code> which is a graphical tool for monitoring and various settings for your video card}}<br />
<br />
=== Emerging the package ===<br />
<console><br />
###i## emerge x11-drivers/nvidia-drivers<br />
</console><br />
<br />
When the installation is complete run '''modprobe''' nvidia module to read kernel memory.<br />
<br />
<console><br />
###i## lsmod | grep nvidia<br />
</console><br />
If an update before remove the old module<br />
<console><br />
###i## rmmod nvidia<br />
###i## modprobe nvidia<br />
</console><br />
<br />
=== Testing your Video Card ===<br />
To test your video card run the glxinfo program, which is part of the mesa-progs package. This will check if direct rendering is enabled.<br />
<console><br />
$ ##i##glxinfo | grep direct<br />
$ ##i## direct rendering: yes<br />
</console><br />
<br />
== Configuring ==<br />
=== Loading at boot ===<br />
To automate the loading of the module when you boot your system, add '''nvidia''' in modules variable.<br />
<console><br />
# ##i##nano /etc/conf.d/modules<br />
modules="nvidia"<br />
</console><br />
<br />
=== Integration with X Server ===<br />
When your X server is installed find, and there's <code>/etc/X11/xorg.conf</code> you can run the nvidia-xconfig which will set in xorg.conf to identify the video card among other possible configurations.<br />
<br />
<console>###i## nvidia-xconfig</console><br />
<br />
{{file|name=/etc/X11/xorg.conf|body=<br />
Section "Device"<br />
Identifier "nvidia"<br />
Driver "nvidia"<br />
VendorName "NVIDIA Corporation"<br />
BoardName "[Name] [Model]"<br />
EndSection<br />
}}<br />
<br />
=== Enabling NVIDIA Support ===<br />
Include the use flag in '''nvidia''' in <code>/etc/[[make.conf]]</code> so due to applications that make use of this advantage may withdraw.<br />
<console><br />
# ##i##nano /etc/make.conf<br />
USE="nvidia"<br />
</console><br />
<br />
=== Enabling OpenGL/OpenCL ===<br />
As a requirement, make sure that the Xorg server is not in use during this change. To enable OpenGL and OpenCL.<br />
<console><br />
###i## eselect opengl set nvidia<br />
###i## eselect opencl set nvidia<br />
</console><br />
<br />
[[Category:Video Cards]]<br />
[[Category:First Steps]]<br />
{{EbuildFooter}}</div>Azerthothhttps://www.funtoo.org/index.php?title=Package:NVIDIA_Linux_Display_Drivers&diff=10701Package:NVIDIA Linux Display Drivers2015-06-30T20:29:51Z<p>Azerthoth: added note about debian-sources and nouveau</p>
<hr />
<div>{{Ebuild<br />
|Summary=NVIDIA accelerated graphics driver<br />
|CatPkg=x11-drivers/nvidia-drivers<br />
|Repository=Funtoo Overlay<br />
|Overlay=Funtoo<br />
}}<br />
== Introduction ==<br />
NVIDIA have proprietary graphics drivers for Linux under binary blob. The alternative open source driver is {{Package|x11-drivers/xf86-video-nouveau}}.<br />
<br />
{{note|If you installed debian-sources with the binary USE flag you will need to blacklist the nouveau module in /etc/modprobe.d/blacklist with the comment blacklist nouveau}}<br />
<br />
== Preparing to Install ==<br />
=== Hardware compatibility and driver versions ===<br />
Currently, there are five versions of meta NVIDIA Linux drivers, each of which supports a specific group of GPUs. To check the type of driver that is related to your video card, check out the official page of the NVIDIA [http://www.nvidia.com/object/IO_32667.html complete list of supported GPUs].<br />
<br />
If you have identified as your driver version 337.25, for example, you need the mask(s) driver(s) latest(s) to which you want to install.<br />
<br />
<console><br />
###i## echo “>x11-drivers/nvidia-drivers-340” >> /etc/portage/package.mask<br />
</console><br />
<br />
=== The required kernel options ===<br />
<br />
{{kernelop|desc=<br />
[*] Enable loadable module support<br />
}}<br />
{{kernelop|desc=<br />
[*] MTRR (Memory Type Range Register) support<br />
}}<br />
To we made a successful compilation of the legacy NVIDIA driver, we set before the removal of the native framebuffer drivers into the kernel in order to avoid conflicts for x86 and AMD64 processors, in this case.<br />
{{kernelop|desc=<br />
Device Drivers ---><br />
Graphics support ---> <br />
<*> Support for frame buffer devices ---><br />
<> NVIDIA Framebuffer Support<br />
<> NVIDIA Riva support<br />
}}<br />
<br />
{{tip|An alternative is to [[uvesafb|uvesafb]] framebuffer, or vesa framebuffer which can be installed in parallel with nvidia-drivers }}<br />
<br />
== Installation ==<br />
<br />
Upgrade and/or configure <code>VIDEO_CARDS</code> variable to <code>nvidia</code> in <code>/etc/[[make.conf]]</code>. This will serve to while you are installing the Server X, the correct version of nvidia-drivers to be provided for you.<br />
<console><br />
# ##i##nano /etc/make.conf<br />
VIDEO_CARDS="nvidia"<br />
</console><br />
<br />
{{note|Installing to the driver with the option in '''gtk''' use flags will make it installed the <code>media-video/nvidia-settings</code> which is a graphical tool for monitoring and various settings for your video card}}<br />
<br />
=== Emerging the package ===<br />
<console><br />
###i## emerge x11-drivers/nvidia-drivers<br />
</console><br />
<br />
When the installation is complete run '''modprobe''' nvidia module to read kernel memory.<br />
<br />
<console><br />
###i## lsmod | grep nvidia<br />
</console><br />
If an update before remove the old module<br />
<console><br />
###i## rmmod nvidia<br />
###i## modprobe nvidia<br />
</console><br />
<br />
=== Testing your Video Card ===<br />
To test your video card run the glxinfo program, which is part of the mesa-progs package. This will check if direct rendering is enabled.<br />
<console><br />
$ ##i##glxinfo | grep direct<br />
$ ##i## direct rendering: yes<br />
</console><br />
<br />
== Configuring ==<br />
=== Loading at boot ===<br />
To automate the loading of the module when you boot your system, add '''nvidia''' in modules variable.<br />
<console><br />
# ##i##nano /etc/conf.d/modules<br />
modules="nvidia"<br />
</console><br />
<br />
=== Integration with X Server ===<br />
When your X server is installed find, and there's <code>/etc/X11/xorg.conf</code> you can run the nvidia-xconfig which will set in xorg.conf to identify the video card among other possible configurations.<br />
<br />
<console>###i## nvidia-xconfig</console><br />
<br />
{{file|name=/etc/X11/xorg.conf|body=<br />
Section "Device"<br />
Identifier "nvidia"<br />
Driver "nvidia"<br />
VendorName "NVIDIA Corporation"<br />
BoardName "[Name] [Model]"<br />
EndSection<br />
}}<br />
<br />
=== Enabling NVIDIA Support ===<br />
Include the use flag in '''nvidia''' in <code>/etc/[[make.conf]]</code> so due to applications that make use of this advantage may withdraw.<br />
<console><br />
# ##i##nano /etc/make.conf<br />
USE="nvidia"<br />
</console><br />
<br />
=== Enabling OpenGL/OpenCL ===<br />
As a requirement, make sure that the Xorg server is not in use during this change. To enable OpenGL and OpenCL.<br />
<console><br />
###i## eselect opengl set nvidia<br />
###i## eselect opencl set nvidia<br />
</console><br />
<br />
[[Category:Video Cards]]<br />
[[Category:First Steps]]<br />
{{EbuildFooter}}</div>Azerthothhttps://www.funtoo.org/index.php?title=User:Azerthoth&diff=2341User:Azerthoth2013-01-27T02:17:58Z<p>Azerthoth: </p>
<hr />
<div>{{Person<br />
|Full name=Jim Cook<br />
|Email=azerthoth@gmail.com<br />
|Nick=Azerthoth<br />
|Geoloc=61.3454134, -149.5557101<br />
|Location name=Eagle River, Alaska, United States of America<br />
|Roles={{Role<br />
|Role type=User<br />
|Role desc=Forum moderator, IRC channel Op<br />
}}<br />
|Maintains=<br />
|Blogs=<br />
}}<br />
Thar be bears here!!!!</div>Azerthoth