• Filehippo - Download Free Software
• Hd Movies Point - Download Free Hd Movies

Root # emerge -ask -newuse sys-boot/os-prober The GRUB2 (and optionally ) installations do not automatically enable the boot loader. These only install the software on the operating system, but to install the boot loader to the system itself (so that it is used when booting the system), additional steps need to be taken, which are covered in the section. Configuration There are two important aspects to the configuration of GRUB2:. Installation of GRUB2 software as the boot loader of the system. Configuration of the GRUB2 boot loader. The installation of GRUB2 software is specific to the type of system, and is covered in.

First we cover the configuration of the boot loader itself. Main configuration file The grub-mkconfig script is used to generate a grub configuration. It uses the scripts under /etc/grub.d/. together with the /etc/default/grub configuration file to generate the final /boot/grub/grub.cfg - the only configuration file used by GRUB2 itself. File Format Edits recommended? Description /usr/sbin/grub-mkconfig POSIX shell script No Installed as part of the:2 package.

Run this script to generate /boot/grub/grub.cfg after configuring the files described below. /boot/grub/grub.cfg GRUB2 shell script No The file generated by grub-mkconfig. This file is evaluated by GRUB2's built-in script interpreter and doesn't necessarily support all POSIX commands or syntax. See the in the GRUB manual for supported features. Be aware that modifications to this file won't persist to the next time grub-mkconfig is run. /etc/grub.d/. POSIX shell scripts Maybe Each script under /etc/grub.d/.

that has its execute bit set is evaluated in sequence, and the stdout is concatenated to form the final /boot/grub/grub.cfg (or whatever file is given to the grub-mkconfig -o option). These scripts use the current system shell and therefore can use any supported syntax. Ideally they should be POSIX-compatible scripts, and the output script must be compatible with the GRUB2 interpreter. It may be necessary to disable or add scripts.

For instance, to add menu items that couldn't be automatically generated. /boot/grub/custom.cfg GRUB2 shell script Maybe The /etc/grub.d/41custom script will reference this file to be read in at boot time if it exists. This file provides a place to add additional entries or commands and does not require regeneration of the main grub.cfg file.

/etc/default/grub POSIX shell script Yes In most cases this is the only file that should be modified directly. It is mainly used to assign variables used by the scripts in /etc/grub.d to generate a working configuration file. See or the for supported variables. GRUB2 does not require the administrator to manually maintain a boot option configuration (as is the case with boot loaders such as and ). Instead it can generate its configuration file ( /boot/grub/grub.cfg) using the grub-mkconfig command. This utility will use the scripts in /etc/grub.d/ and the settings in /etc/default/grub.

Warning If grub-mkconfig does not report any found entries then no entries were found. In this case GRUB2 will offer no boot selections when upon system restart which may be a tricky, time consuming situation to resolve. Make sure the output is satisfactory before restarting the system. Setting configuration parameters The following variables in /etc/default/grub are the most common ones to set to control how GRUB2 will function: Variable Explanation Default value GRUBDEFAULT Defines the default menu entry selected on boot. May be a numeric index, a menu title, or 'saved'. Defaults to first detected entry. GRUBTIMEOUT Delay (in seconds) before booting default menu entry.

Set to 0 to boot immediately or -1 to wait indefinitely. The default is 5 seconds.

GRUBCMDLINELINUX Parameters to be passed on the kernel command line for all Linux menu entries. For instance, to support hibernation, users will need to add GRUBCMDLINELINUX='resume=/dev/sdXY' with /dev/sdXY being the swap partition. GRUBCMDLINELINUXDEFAULT Parameters to be passed on the kernel command line for non-recovery Linux menu entries. GRUBDEVICE The initial root device (i.e.

The kernel's root= parameter). Set this to override the grub-mkconfig command's root device auto-detection. For example, GRUBDEVICE=/dev/ram0 will force root=/dev/ram0 to be used in the kernel command line. For a more complete list, please refer to the sub-page. After modifying the parameters, regenerate the GRUB2 configuration file with grub-mkconfig. Enabling or disabling configuration scripts The directory /etc/grub.d/ contains the scripts that grub-mkconfig uses to generate a grub.cfg file.

By default the contents of this directory should be similar to the following. Root # grub-install /dev/sda Installation finished. No error reported. Grub-install accepts a -target option to set the CPU architecture and system platform. If unspecified, grub-install will attempt to guess the proper values; on an amd64/ x86 system it will use i386-pc by default.

Filehippo - Download Free Software

Grub-install also accepts a -boot-directory option to tell the GRUB2 installer which directory to look for GRUB2's boot files. This defaults to the current /boot but is useful when trying to move a root partition.

Partitioning for BIOS with MBR Be sure to leave enough free space before the first partition. Starting the first partition at sector 2048 leaves at least 1 MiB of disk space for the master boot record. It is recommended (but not mandatory) to create an additional partition for GRUB called the BIOS boot partition. This partition just needs to be defined, but not formatted.

It is only needed if the system is later migrated to the GPT partition layout. When sticking with MBR, this is not needed. If the were followed, this BIOS boot partition will already be available.

BIOS with GPT. Root # grub-install /dev/sda Installation finished. No error reported. Grub-install accepts a -target option to set the CPU architecture and system platform. If unspecified, grub-install will attempt to guess the correct values; on an amd64/ x86 system it will use i386-pc by default. Grub-install also accepts a -boot-directory option to tell the GRUB2 installer which directory to look in for GRUB2's boot files. This defaults to the current /boot but is useful when trying to move a root partition.

Partitioning for BIOS with GPT When a GPT partition table is present on the system, a small BIOS boot partition with type EF02 (which is different from the EFI System Partition (ESP) which has type EF00) will need to be available. 1 MiB will be enough to work, but 2-4 MiB is a safer option.

This BIOS boot partition will hold the stage 2 of the bootloader. BIOS boot partitions do not need to be formatted with a filesystem; the grub-install command will overwrite any existing filesystem with one of its own. Important The BIOS boot partition is not the same partition that is commonly mounted at /boot. The /boot and BIOS boot are different partitions and should be handled separately.

The BIOS boot partition should not be regularly mounted on the system (i.e., it should not be defined in /etc/fstab). The /boot partition can be regularly mounted with no issues and therefore can be present in the /etc/fstab file. To set a partition as a BIOS partition use the command-line tool parted by typing (change 1 to the number of the partition to mark as a BIOS boot partition!). (parted) set 1 biosgrub on With 's cgdisk utility, this is accomplished by setting the partition type to 0xEF02 and giving it a label of gptbios. An EFI System Partition is not required, but it would be sensible to make sure that the BIOS boot partition is large enough to be converted to one, should the system motherboard later be upgraded to an UEFI board. The following is the output of pressing the p key using the gdisk utility on a GPT-partitioned disk with both a BIOS boot 0xEF02 partition and an EFI 0xEF00 partition. Root # gdisk /dev/sdc GPT fdisk (gdisk) version 0.8.1 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT.

Root # parted /dev/sdc GNU Parted 3.0 Using /dev/sdc (parted) print. Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 424GB 424GB Linux LVM lvm 2 424GB 456GB 32.2GB Microsoft basic data 3 456GB 499GB 42.9GB Microsoft basic data 4 499GB 500GB 807MB ext2 Linux filesystem 5 500GB 500GB 1049kB BIOS boot partition biosgrub 6 500GB 500GB 8396kB EFI System boot (parted) Creating partitions in gdisk is straightforward for users familiar with the fdisk partitioning utility. After starting gdisk, type n (for new) in the main menu, provide beginning and end sectors (if needed), and set the partition type to EF00 for an EFI system partition. Users who have followed the will already have the proper partitioning layout set up. UEFI with GPT Make sure that the /boot location is available - if this uses a separate partition, make sure that it is mounted.

Root # grub-install -efi-directory=/boot/efi Installation finished. No error reported. The above command assumes the vfat (ESP) is mounted at /boot/efi.

If the ESP is mounted directly at /boot, use -efi-directory=/boot. Grub-install also accepts a -target option to set the CPU architecture and system platform. If unspecified, grub-install will attempt to guess the proper values; on an AMD64 UEFI-booted system it will use x8664-efi by default. Grub-install also accepts a -boot-directory option to tell the GRUB2 installer which directory to look for GRUB2's boot files. This defaults to /boot but is useful when trying to move a root partition. Partitioning for UEFI with GPT For UEFI GPT boot using GRUB2, the system must have a dedicated EFI partition containing a FAT filesystem.

The EFI partition can replace having a /boot partition on /dev/sda1 by having a /boot/efi partition on /dev/sda1. This is to say a successful UEFI boot scenario using GRUB2 can operate with two partitions total (three total if a swap partition is needed): a root partition and an EFI partition. Using this configuration, the /boot folder will be located in the root / partition (at /boot) and the EFI partition will mount in the boot folder (at /boot/efi).

For further clarification, see the example file below. /dev/sda1 /boot/efi vfat noauto,noatime 1 2 /dev/sda2 none swap sw 0 0 /dev/sda3 / ext4 noatime 0 1 Generating a 100MB partition for /boot/efi should provide plenty of space for holding multiple.efi files (multiple entries will most likely not be needed; most systems will only use one). Create the partition using the partitioning. The gdisk and parted tools fit nicely for this purpose. When using the gdisk utility, be sure to use type EF00.

Proceed to create a FAT filesystem on the EFI system partition using mkfs.fat and add it to /etc/fstab by following the example below. Important In order for GRUB2 to install properly, the EFI directory must be mounted and the efivars kernel module must be loaded before the grub-install command will complete successfully. Alternative: using the default UEFI firmware location If the system's UEFI firmware fails to find GRUB2's EFI bootloader file, using the default boot loader location should provide a working solution. This circumvents the boot menu managed by and thus offers reduced functionality, but is less error prone. To do this, verify the EFI partition is mounted at /boot/efi then copy the file grubx64.efi located at /boot/efi/EFI/gentoo/grubx64.efi to /boot/efi/EFI/BOOT/BOOTX64.EFI.

This example assumes a 64-bit UEFI system, adjust accordingly for 32-bit UEFI systems. Extended features GRUB2 has many features that make it a very powerful boot loader. It supports:. Booting from UEFI platforms. Booting from GPT partitioned drives without needing a hybrid MBR (hybrid MBR can enabled as needed for compatibility or portability).

Booting from a formatted /boot partition. Booting from a ZFS pool. Booting directly from a raid set without needing an for early mount setup. Booting directly from logical volume management (such as ). Booting with support for DM-RAID (RAID 0, 1, 4, 5, 6, 9 and 10). Booting from encrypted devices (LUKS).

Hd Movies Point - Download Free Hd Movies

Some specific features are explained in more detail next. Chainloading GRUB2 was built with a truly improved chainload mode when compared to GRUB Legacy. To chainload another boot loader, use the chainloader option. # Set resolution and color depth GRUBGFXMODE =1366x768x32 # Keep resolution when loading the kernel GRUBGFXPAYLOADLINUX =keep # Set a background image GRUBBACKGROUND = '/boot/grub/bg.png' # Use a custom font, converted using grub-mkfont utility GRUBFONT = '/boot/grub/fonts/roboto.pf2' # Set the menu colors GRUBCOLORNORMAL = 'light-blue/black' GRUBCOLORHIGHLIGHT = 'light-cyan/blue' Troubleshooting Most of the issues can be resolved by ensuring that the partition layout is correct. Make sure enough space is available before the first partition of the disk, or optionally make sure that a BIOS boot partition is available. Also verify that /boot/grub/grub.cfg was correctly generated with grub-mkconfig, or generate one with a custom menu entry. For more GRUB2 troubleshooting, please refer to the sub-article.

Motherboard firmware not finding the.EFI file Some motherboard manufacturers seem to only support one location for the.EFI file in the EFI System Partition (ESP). If this seems to be the case, simply move GRUB's default file to the /efi/boot/ location. First, make sure the ESP is mounted.

Presuming the ESP is mounted at /boot/efi (as suggested in the ), execute. Root # grub-install -efi-directory=/boot/efi -removable Installation finished. No error reported. This should aid the motherboard firmware in loading the GRUB executable. Reboot the system to see if the firmware now correctly loads GRUB. Os-prober and UEFI in chroot The utility is used to discover alternate installs, such as Microsoft Windows.

To function properly, it needs to have access to information from the live environment's udev to test for the EFI System Partition. Run these commands in the host environment to provide the required files (example shows Gentoo mounted on /mnt/gentoo like in the ). Root # grub-mkconfig -o /boot/grub/grub.cfg Generating grub.cfg. Found linux image: /boot/kernel-3.3.8-gentoo Found initrd image: /boot/initramfs-genkernel-x8664-3.3.8-gentoo Found linux image: /boot/kernel-3.2.12-gentoo Found initrd image: /boot/initramfs-genkernel-x8664-3.2.12-gentoo done Note that GRUB2 only needs to be reconfigured, not reinstalled to the boot drive's Master Boot Record (MBR).

On the other hand, when GRUB2 itself has been upgraded it does need to be reinstalled on the boot drive, but usually does not need to be reconfigured. See also There are a few specific GRUB2 resources available:. In the use of GRUB2 to boot other boot loaders is described. This is important to read when dual-booting systems, or when GRUB2 needs to be configured to boot ISO files. In the necessary steps are documented on how to install and use GRUB2 on more advanced storage situations, such as software RAID, logical volumes or encrypted file systems. In an exhaustive list of GRUB2 configuration variables, as used by /etc/default/grub, is documented. In a list of common GRUB2 errors (with their solutions) is presented.

In the use of a mixed MBR/GPT setup is documented, as well as how to use such hybrid partition layout with GRUB2. External resources For more information, please see:.

FEATURES OF THIS APP:. Customize your game graphics like a pro. 1080 Resolution: Change the resolution of the game. HDR Game Graphic: Unlock the HDR graphics on low end devices. Extreme FPS: Unlock the Extreme FPS level.

Style: Change graphics style setting. Shadow: Enable and disable shadow. 4xMSAA: Enable and disable Anti Aliasing. Zero Lag Mode + Battery Efficient.Plus version: Optimized game configuration. Memory Boost.Plus version: Boost up the game performance.

“This app is developed for specific game” SCREENSHOTS GOOGLE PLAY LINK THANKS.