Grub customizer manjaro linux установка

Настройка порядка загрузки систем в Manjaro Linux 19 XFCE

Всем привет! В этом материале мы рассмотрим возможность изменять порядок загрузки операционных систем в Manjaro Linux 19 XFCE в тех случаях, когда на компьютере установлено две и более систем, например, Windows 10 и Manjaro Linux 19.

Напомню, в прошлых материалах мы уже подробно рассмотрели процесс установки Manjaro Linux 19 на компьютер рядом с Windows 10, а также процесс настройки раскладки клавиатуры в Manjaro уже после установки системы.

Сегодня, как было уже отмечено, мы рассмотрим настройки, с помощью которых мы можем управлять порядком загрузки операционных систем, так как по умолчанию после установки Manjaro Linux 19 данный порядок настроен так, что при включении компьютера, если в загрузочном меню ничего не выбрать, будет загружаться та система, в которую Вы загружались последний раз. Например, если Вы загрузились в Windows 10, то в следующий раз по истечении периода ожидания, т.е. если также ничего не выбрать в загрузочном меню, будет загружаться все та же Windows 10.

Данное поведение загрузчика некоторых пользователей может и не устраивать. Однако существуют настройки, с помощью которых мы можем принудительно указать операционную систему, которая должна загружаться каждый раз по умолчанию, не зависимо от того, какая система была загружена последней.

Итак, давайте начнем.

Настройка загрузчика GRUB в Manjaro Linux 19

В качестве примера давайте разберем ситуацию, когда у нас на компьютере установлено две системы Windows 10 и Manjaro Linux 19, и по умолчанию у нас загружается операционная система, которая была загружена последней, однако допустим, мы хотим, чтобы по умолчанию всегда загружалась Windows 10.

Чтобы это реализовать, необходимо выполнить настройку загрузчика GRUB из операционной системы Manjaro Linux. Для этого сделаем несколько простых шагов.

Шаг 1 – Определяем и запоминаем индекс системы в загрузочном меню

Первое, что нам необходимо сделать, это определить и запомнить индекс или точное название той системы, которую мы хотим указать по умолчанию.

Узнать индексы операционных систем в загрузчике можно из конфигурационных файлов, этот вариант обычно используют продвинутые пользователи Linux, однако мы обычные пользователи и этот способ мы использовать не будем.

Заметка! Книга для начинающих пользователей Linux – «Linux для обычных пользователей». В ней я максимально простым языком рассказываю про основы Linux и как пользоваться этой операционной системой без командной строки.

В нашем случае проще простого определить порядковый номер системы в загрузочном меню, которое появляется при включении компьютера. Однако здесь стоит учитывать тот факт, что номер индекса начинается с нуля, а также то, что все подпункты, если такие есть, также нужно учитывать.

И таким образом, у первого пункта будет индекс 0, у второго 1 и так далее.

В моем случае, как Вы можете наблюдать на скриншоте ниже, у Manjaro Linux индекс 0, у дополнительных параметров загрузки Manjaro Linux индекс 1, а у Windows 10 индекс 2.

Поэтому, я запоминаю цифру 2 и перехожу ко второму шагу.

Шаг 2 – Указываем операционную систему по умолчанию

Далее загружаемся в Manjaro Linux и выполняем несколько простых команд в терминале Linux. Для этого запускаем терминал, «Меню -> Эмулятор терминала».

Сначала для указания операционной системы по умолчанию выполняем следующую команду.

Где, 2 – это индекс системы, которую мы хотим сделать системой по умолчанию (для выполнения команды необходимо будет ввести свой пароль).

Шаг 3 – Сохраняем настройки

Операционная система по умолчанию указана, однако нам еще нужно сохранить настройки и переконфигурировать загрузчик. Для этого выполняем еще одну команду

Шаг 4 – Проверяем порядок загрузки операционных систем

Чтобы проверить загрузчик, перезагружаем компьютер, и в загрузочном меню ничего не выбираем, в нашем случае должна по умолчанию загружаться Windows 10, несмотря на то, что мы только что использовали Manjaro Linux.

У меня все сработало, по умолчанию загружается Windows 10.

Если по каким-либо причинам Вы хотите вернуть настройки, которые были, т.е. сделать так, чтобы загружалась операционная система, которая загружалась последней, необходимо выполнить все те же команды в терминале Manjaro Linux, только вместо «2» указать параметр «saved».

На сегодня это все, надеюсь, материал был Вам полезен, пока!

Источник

GRUB/Tips and tricks

Contents

Alternative installation methods

Install to external USB stick

Assume your USB stick’s first partition is FAT32 and its partition is /dev/sdy1

Optionally backup configuration files of grub.cfg :

To have grub write its EFI image to esp/EFI/BOOT/BOOTX64.efi , which the boot firmware will be able to find without any UEFI boot entry, use —removable when you run grub-install .

Install to partition or partitionless disk

To set up grub to a partition boot sector, to a partitionless disk (also called superfloppy) or to a floppy disk, run (using for example /dev/sdaX as the /boot partition):

You need to use the —force option to allow usage of blocklists and should not use —grub-setup=/bin/true (which is similar to simply generating core.img ).

grub-install will give out warnings like which should give you the idea of what might go wrong with this approach:

Without —force you may get the below error and grub-setup will not setup its boot code in the partition boot sector:

With —force you should get:

The reason why grub-setup does not by default allow this is because in case of partition or a partitionless disk is that GRUB relies on embedded blocklists in the partition bootsector to locate the /boot/grub/i386-pc/core.img file and the prefix directory /boot/grub . The sector locations of core.img may change whenever the file system in the partition is being altered (files copied, deleted etc.). For more info, see https://bugzilla.redhat.com/show_bug.cgi?id=728742 and https://bugzilla.redhat.com/show_bug.cgi?id=730915.

The workaround for this is to set the immutable flag on /boot/grub/i386-pc/core.img (using chattr command as mentioned above) so that the sector locations of the core.img file in the disk is not altered. The immutable flag on /boot/grub/i386-pc/core.img needs to be set only if GRUB is installed to a partition boot sector or a partitionless disk, not in case of installation to MBR or simple generation of core.img without embedding any bootsector (mentioned above).

Unfortunately, the grub.cfg file that is created will not contain the proper UUID in order to boot, even if it reports no errors. see https://bbs.archlinux.org/viewtopic.php?pid=1294604#p1294604. In order to fix this issue the following commands:

Now, install linux , then:

Generate core.img alone

To populate the /boot/grub directory and generate a /boot/grub/i386-pc/core.img file without embedding any GRUB bootsector code in the MBR, post-MBR region, or the partition bootsector, add —grub-setup=/bin/true to grub-install :

You can then chainload GRUB’s core.img from GRUB Legacy or syslinux as a Linux kernel or as a multiboot kernel (see also Syslinux#Chainloading).

GUI configuration tools

• grub-customizer — GTK customizer for GRUB or BURG

https://launchpad.net/grub-customizer || grub-customizer

Visual configuration

In GRUB it is possible, by default, to change the look of the menu. Make sure to initialize, if not done already, GRUB graphical terminal, gfxterm, with proper video mode, gfxmode, in GRUB. This video mode is passed by GRUB to the linux kernel via ‘gfxpayload’ so any visual configurations need this mode in order to be in effect.

Setting the framebuffer resolution

GRUB can set the framebuffer for both GRUB itself and the kernel. The old vga= way is deprecated. The preferred method is editing /etc/default/grub as the following sample to set width (pixels) x height (pixels) x color depth:

Multiple resolutions can be specified, including the default auto , so it is recommended that you edit the line to resemble GRUB_GFXMODE=desired_resolution,fallback_such_as_1024x768,auto . For more information, refer to the GRUB gfxmode documentation. The gfxpayload property will make sure the kernel keeps the resolution.

If this method does not work for you, the deprecated vga= method will still work. Just add it next to the «GRUB_CMDLINE_LINUX_DEFAULT=» line in /etc/default/grub for example: «GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash vga=792» will give you a 1024×768 resolution.

915resolution hack

Sometimes for Intel graphic adapters neither # hwinfo —framebuffer nor videoinfo will show you the desired resolution. In this case you can use the 915resolution hack. This hack will temporarily modify video BIOS and add needed resolution. See 915resolution’s home page. The package can be found here: 915resolution AUR

First you need to find a video mode which will be modified later. For that we need the GRUB command shell:

Next, we overwrite the Mode 30 with 1440×900 resolution:

Lastly we need to set GRUB_GFXMODE as described earlier, regenerate grub.cfg and reboot to test changes.

Background image and bitmap fonts

GRUB comes with support for background images and bitmap fonts in pf2 format. The unifont font is included in the grub package under the filename unicode.pf2 , or, as only ASCII characters under the name ascii.pf2 . Run pacman -Ql grub | grep pf2 to get the file paths.

Image formats supported include tga, png and jpeg, providing the correct modules are loaded. The maximum supported resolution depends on your hardware.

Make sure you have set up the proper framebuffer resolution.

Edit /etc/default/grub like this:

Re-generate grub.cfg to apply the changes. If adding the splash image was successful, the user will see «Found background image. » in the terminal as the command is executed. If this phrase is not seen, the image information was probably not incorporated into the grub.cfg file.

If the image is not displayed, check:

• The path and the filename in /etc/default/grub are correct
• The image is of the proper size and format (tga, png, 8-bit jpg)
• The image was saved in the RGB mode, and is not indexed
• The console mode is not enabled in /etc/default/grub
• The command grub-mkconfig must be executed to place the background image information into the /boot/grub/grub.cfg file
• The grub-mkconfig scripts will not quote the file name in grub.cfg so make sure it does not contain spaces

Theme

Here is an example for configuring Starfield theme which was included in GRUB package.

Re-generate grub.cfg to apply the changes. If configuring the theme was successful, you will see Found theme: /usr/share/grub/themes/starfield/theme.txt in the terminal.

Your splash image will usually not be displayed when using a theme.

Menu colors

You can set the menu colors in GRUB. The available colors for GRUB can be found in the GRUB Manual. Here is an example:

Hidden menu

One of the unique features of GRUB is hiding/skipping the menu and showing it by holding Esc when needed. You can also adjust whether you want to see the timeout counter.

Edit /etc/default/grub as you wish. Here are the lines you need to add to enable this feature, the timeout has been set to five seconds and to be shown to the user:

GRUB_TIMEOUT is how many seconds before displaying menu.

Disable framebuffer

Users who use NVIDIA proprietary driver might wish to disable GRUB’s framebuffer as it can cause problems with the binary driver.

To disable framebuffer, edit /etc/default/grub and uncomment the following line:

Another option if you want to keep the framebuffer in GRUB is to revert to text mode just before starting the kernel. To do that modify the variable in /etc/default/grub :

Booting ISO9660 image file directly via GRUB

GRUB supports booting from ISO images directly via loopback devices, see Multiboot USB drive#Using GRUB and loopback devices for examples.

Password protection of GRUB menu

If you want to secure GRUB so it is not possible for anyone to change boot parameters or use the command line, you can add a user/password combination to GRUB’s configuration files. To do this, run the command grub-mkpasswd-pbkdf2 . Enter a password and confirm it:

Then, adjust permissions on /etc/grub.d/40_custom such that only root can read it and add the following to this file:

where password is the string generated by grub-mkpasswd_pbkdf2 .

Regenerate your configuration file. Your GRUB command line, boot parameters and all boot entries are now protected.

This can be relaxed and further customized with more users as described in the «Security» part of the GRUB manual.

Password protection of GRUB edit and console options only

Adding —unrestricted to a menu entry will allow any user to boot the OS while preventing the user from editing the entry and preventing access to the grub command console. Only a superuser or users specified with the —user switch will be able to edit the menu entry.

The factual accuracy of this article or section is disputed.

In order to make Linux entries —unrestricted , the CLASS variable in the beginning of /etc/grub.d/10_linux can be modified.

Hide GRUB unless the Shift key is held down

In order to achieve the fastest possible boot, instead of having GRUB wait for a timeout, it is possible for GRUB to hide the menu, unless the Shift key is held down during GRUB’s start-up.

In order to achieve this, you should add the following line to /etc/default/grub :

Then create the file /etc/grub.d/31_hold_shift containing [1], make it exectuable, and regenerate the grub configuration:

Combining the use of UUIDs and basic scripting

If you like the idea of using UUIDs to avoid unreliable BIOS mappings or are struggling with GRUB’s syntax, here is an example boot menu item that uses UUIDs and a small script to direct GRUB to the proper disk partitions for your system. All you need to do is replace the UUIDs in the sample with the correct UUIDs for your system. The example applies to a system with a boot and root partition. You will obviously need to modify the GRUB configuration if you have additional partitions:

Multiple entries

Disable submenu

If you have multiple kernels installed, say linux and linux-lts, by default grub-mkconfig groups them in a submenu. If you do not like this behaviour you can go back to one single menu by adding the following line to /etc/default/grub :

Recall previous entry

GRUB can remember the last entry you booted from and use this as the default entry to boot from next time. This is useful if you have multiple kernels (i.e., the current Arch one and the LTS kernel as a fallback option) or operating systems. To do this, edit /etc/default/grub and change the value of GRUB_DEFAULT :

This ensures that GRUB will default to the saved entry. To enable saving the selected entry, add the following line to /etc/default/grub :

This will only work if /boot is not a btrfs, because grub cannot write to btrfs. But it will generate a misleading error message: «sparse file not allowed. Press any key to continue.».

Changing the default menu entry

To change the default selected entry, edit /etc/default/grub and change the value of GRUB_DEFAULT :

Using menu titles :

Grub identifies entries in generated menu counted from zero. That means 0 for the first entry which is the default value, 1 for the second and so on. Main and submenu entries are separated by a > .

The example above boots the third entry from the main menu ‘Advanced options for Arch Linux’.

Boot non-default entry only once

The command grub-reboot is very helpful to boot another entry than the default only once. GRUB loads the entry passed in the first command line argument, when the system is rebooted the next time. Most importantly GRUB returns to loading the default entry for all future booting. Changing the configuration file or selecting an entry in the GRUB menu is not necessary.

Play a tune

You can play a tune through the PC-speaker while booting (right before the menu appears) by modifying the variable GRUB_INIT_TUNE . For example, to play Berlioz’s extract from Sabbath Night of Symphonie Fantastique (bassoon part) you can add the following:

This section is being considered for removal.

You can add a menu entry to play each of these common GRUB_INIT_TUNE samples by creating the following file and then re-running grub-mkconfig .

For information on this, you can look at info grub -n play .

Manual configuration of core image for early boot

If you require a special keymap or other complex steps that GRUB is not able to configure automatically in order to make /boot available to the GRUB environment, you can generate a core image yourself. On UEFI systems, the core image is the grubx64.efi file that is loaded by the firmware on boot. Building your own core image will allow you to embed any modules required for very early boot, as well as a configuration script to bootstrap GRUB.

Firstly, taking as an example a requirement for the dvorak keymap embedded in early-boot in order to enter a password for an encrypted /boot on a UEFI system:

Determine from the generated /boot/grub/grub.cfg file what modules are required in order to mount the crypted /boot . For instance, under your menuentry you should see lines similar to:

Take note of all of those modules: they will need to be included in the core image. Now, create a tarball containing your keymap. This will be bundled in the core image as a memdisk:

Now create a configuration file to be used in the GRUB core image. This is in the same format as your regular grub config, but need contain only a few lines to find and load the main config file on the /boot partition:

Finally, generate the core image, listing all of the modules determined to be required in the generated grub.cfg , along with any modules used in the early-grub.cfg script. The example above needs memdisk , tar , at_keyboard , keylayouts and configfile .

The generated EFI core image can now be used in the same way as the image that is generated automatically by grub-install : place it in your EFI partition and enable it with efibootmgr , or configure as appropriate for your system firmware.

UEFI further reading

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

Below is other relevant information regarding installing Arch via UEFI.

Alternative install method

This article or section needs expansion.

Usually, GRUB keeps all files, including configuration files, in /boot , regardless of where the EFI System Partition is mounted.

If you want to keep these files inside the EFI System Partition itself, add —boot-directory=esp to the grub-install command:

This puts all GRUB files in esp/grub , instead of in /boot/grub . When using this method, make sure you have grub-mkconfig put the configuration file in the same place:

Configuration is otherwise the same.

UEFI firmware workaround

GRUB standalone

This section assumes you are creating a standalone GRUB for x86_64 systems (x86_64-efi). For 32-bit (IA32) EFI systems, replace x86_64-efi with i386-efi where appropriate.

It is possible to create a grubx64_standalone.efi application which has all the modules embedded in a tar archive within the UEFI application, thus removing the need to have a separate directory populated with all of the GRUB UEFI modules and other related files. This is done using the grub-mkstandalone command (included in grub ) as follows:

Then copy the GRUB config file to esp/EFI/grub/grub.cfg and create a UEFI Boot Manager entry for esp/EFI/grub/grubx64_standalone.efi using efibootmgr.

Technical information

The GRUB EFI file always expects its config file to be at $/grub.cfg . However in the standalone GRUB EFI file, the $ is located inside a tar archive and embedded inside the standalone GRUB EFI file itself (inside the GRUB environment, it is denoted by «(memdisk)» , without quotes). This tar archive contains all the files that would be stored normally at /boot/grub in case of a normal GRUB EFI install.

Due to this embedding of /boot/grub contents inside the standalone image itself, it does not rely on actual (external) /boot/grub for anything. Thus in case of standalone GRUB EFI file $==(memdisk)/boot/grub and the standalone GRUB EFI file reads expects the config file to be at $/grub.cfg==(memdisk)/boot/grub/grub.cfg .

Hence to make sure the standalone GRUB EFI file reads the external grub.cfg located in the same directory as the EFI file (inside the GRUB environment, it is denoted by $ ), we create a simple /tmp/grub.cfg which instructs GRUB to use $/grub.cfg as its config ( configfile $/grub.cfg command in (memdisk)/boot/grub/grub.cfg ). We then instruct grub-mkstandalone to copy this /tmp/grub.cfg file to $/grub.cfg (which is actually (memdisk)/boot/grub/grub.cfg ) using the option «boot/grub/grub.cfg=/tmp/grub.cfg» .

This way, the standalone GRUB EFI file and actual grub.cfg can be stored in any directory inside the EFI System Partition (as long as they are in the same directory), thus making them portable.

Speeding up LUKS decryption in GRUB

Upon boot GRUB may in some cases take a long time to verify the password. This can be due to a high PBKDF iteration count, which you can check as follows:

The problem is that the iteration count for a given keyslot is generated when the key is added to ensure a balance between being high enough to protect against brute force attacks and low enough to allow for fast key derivation by estimating the capabilities of your computer. However, when GRUB is started, it might not have the same computational resources at hand, thus being vastly slower.

If your password provides enough entropy to counter common attacks by itself, you can lower this number:

A minimum of 1000 iterations is recommended as per RFC 2898, but you should aim for higher values if you can (The cost for an attacker as well as the time for key derivation scale linearly).

Источник