Difference between revisions of "Talk:GRUB"

From ArchWiki
Jump to navigation Jump to search
(GRUB Legacy: rm closed section)
m (Unsupported sections: rm closed section)
Line 146: Line 146:
::As there's no further comments, I've went ahead and merged the section. Now we can focus on the real work. :) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:51, 12 December 2014 (UTC)
::As there's no further comments, I've went ahead and merged the section. Now we can focus on the real work. :) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:51, 12 December 2014 (UTC)
=== <s>Unsupported sections</s> ===
Any unsupported or harmful section should be deleted. Users that want those instructions will find them anyway.
:Removed ''Install to partionless disk'': [https://wiki.archlinux.org/index.php?title=GRUB&diff=347954&oldid=347953] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:34, 3 December 2014 (UTC)
:Removed ''Manually creating grub.cfg'': [https://wiki.archlinux.org/index.php?title=GRUB&diff=347960&oldid=347954] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:38, 3 December 2014 (UTC)
::About these removals I was wondering, just wondering, if they're going a bit too far: the Arch Way is to present all the options and let the users decide for themselves, without hiding anything; "unsupported" doesn't have a precise meaning in Arch, and I'm afraid that deleting those sections will result, sooner or later, in somebody else re-adding something similar just because they're experimenting on it and want to share their discoveries; in general, if we delete this kind of "non-standard" observations systematically, we risk turning the wiki into a mere introduction (when not even duplication) to external manuals, perhaps inhibiting a bit the spirit of curiosity and experimentation that could instead be seen as one of the most important engines that has built this wiki through all these years. After all, those sections were properly introduced by warnings (well, a Note and a Warning to be exact), so it was very clear that anyone following them would take all responsibilities for any bad consequences. Any opinions about this? -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:17, 5 December 2014 (UTC)
:::If there's a particular demand for them, I'm fine with readding them (I admit being a bit brash), but IMO they don't belong in the main article. Maybe a separate "tips" page might be suited for them. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:10, 5 December 2014 (UTC)
::::I think removing them for now, and adding them later if necessary is the best course of action. No need to be in the main article. Probably best to very briefly mention them if necessary and say 'see [[Grub Legacy]]'.
::::--[[User:Stevenmw|Stevenmw]] ([[User talk:Stevenmw|talk]]) 16:17, 5 December 2014 (UTC)
:::::@Stevenmw But those sections were about GRUB 2, not GRUB Legacy, unless I'm missing something ^^
:::::@Alad I admit I'd like to see them restored, I don't know if they're enough for a separate article; maybe they can be put at the bottom of the "Advanced configuration" section, or in a new "Tips and tricks" section?
:::::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 03:18, 6 December 2014 (UTC)
:::::: Yeah, that's a good idea. --[[User:Stevenmw|Stevenmw]] ([[User talk:Stevenmw|talk]]) 10:52, 6 December 2014 (UTC)
:::::::Restored the sections, see [[#Advanced configuration]], closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:50, 7 December 2014 (UTC)
=== Others ===
=== Others ===

Revision as of 12:52, 12 December 2014

GRUB2 + Windows 7 TrueCrypt-encrypted partition

here is a link to my notes from my experience going thru this and Ubuntu Forum post which helped me a GREAT DEAL with this issue - below is a quick HOWTO ::

# ls -al /mnt/win7drive/Users/me/Documents/TrueCrypt\ Rescue\ Disk.iso
   -rwx------ 2 me users 1835008 Sep  5  2011 /mnt/win7/Users/me/Documents/TrueCrypt Rescue Disk.iso
# sudo cp /mnt/win7/Users/me/Documents/TrueCrypt\ Rescue\ Disk.iso /boot/
# mv /boot/TrueCrypt\ Rescue\ Disk.iso /boot/truecryptDesktop.iso
# pacman -S syslinux
# cp /usr/lib/syslinux/memdisk /boot/
# ls -alt /boot
   total 26388
   drwxr-xr-x  5 root root     4096 Jul 29 04:01 .
   -rw-r--r--  1 root root    26140 Jul 29 04:01 memdisk
   -rwx------  1 root root  1835008 Jul 29 03:59 truecryptDesktop.iso
            ....   ....
#mount | grep /boot
   /dev/sda3 on /boot type ext3 (rw,relatime,data=ordered)
# vi /etc/grub.d/40_custom

menuentry "Microsoft Windows 7 x64 Home Premium" {
   insmod part_msdos
   set root='(hd0,msdos3)'
   linux16 ($root)/memdisk iso raw
   initrd16 ($root)/truecryptDesktop.iso
# sudo grub-mkconfig -o /boot/grub/grub.cfg

--Fnord0 (talk) 17:59, 30 July 2012 (UTC)

Boot Arch iso from LVM (LVM hook in Arch iso?)

I added the following in /etc/grub.d/40_custom:

menuentry "archlinux-2013.03.01-dual.iso" --class iso {
    insmod loopback
    insmod iso9660
    insmod part_gpt
    insmod lvm
    insmod ext2
    set root='lvm/vg0-arch'
    set isofile='/home/jordy/data/isos/archlinux-2013.03.01-dual.iso'
    loopback loop $isofile
    linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCH_201303 img_dev=$root img_loop=$isofile earlymodules=loop
    initrd (loop)/arch/boot/x86_64/archiso.img

My / is on LVM, the iso boots, but it can't mount the loop device (the iso) because the LVM hook hasn't been run before that. Is there a way to fix this and enable the LVM hook in the iso (without modifying it)

jordz (talk) 22:34, 24 March 2013 (UTC)

Did you find an answer? Does this help https://www.archlinux.org/news/changes-to-lvm/ at all? --Stevenmw (talk) 11:01, 6 December 2014 (UTC)

How to create EFI directory?

According to GRUB#Check_if_you_have_GPT_and_an_ESP, 'On [the EFI partition], there should be a folder called "EFI".' How is this created? I followed the instructions:

parted /dev/sda print
Number [...] File system Name       Flags
 1           fat32       EFI System boot

First, the instructions result in a "fat32" file system, and not a "vfat" one (as described in GRUB#Check_if_you_have_GPT_and_an_ESP). AFAICT "fat32" is not a subclass of "vfat", so that should probably be changed. Second, this partition, when mounted, does not contain anything at all, and I could find no instructions on how the "EFI" directory is supposed to be created. I expect some tool other than mkdir is supposed to do this (and possibly more)?

Other articles have mentioned a directory "/boot/efi". I guess that's just a case of FAT file systems being case insensitive, or does it actually matter?

Is there something missing?

I tried this on a Virtual Machine and on two physical machines and i always end up with "EFI variables are not supported on this system"

This seems due to an bug that arch-chroot does not mount the efivars directory at all inside the chroot.

You have to run

# mount -t efivarfs efivarfs /sys/firmware/efi/efivars

or it will not work so this should be in the article.

Alpha sorting for kernel names without versions

When installing the "linux" and "linux-lts" kernels on a basic install, the /etc/grub.d/10_linux in 2.02-beta1 will try and use a numeric-oriented sorting routine that doesn't work well for kernels without any versions in the names of the files. I've submitted a feature request and patch for this upstream:

Forum discussion w/patch:

I solved this (and other problems) long ago… why nobody applied this patch to the Arch package is beyond me. felix (talk) 14:11, 8 August 2014 (UTC)
What is the current sate of this issue? --Stevenmw (talk) 10:56, 6 December 2014 (UTC)

EFI Single Standard?

As some firmware isn't fussy about the name of the directory after $esp/EFI/ - nor apparently the name of the efi stub contained within it - then logically bootx64.efi in $esp/EFI/boot should work for them as well.

For example, the standard Grub UEFI installation command:

# grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=grub --recheck --debug

Could possibly be changed to:

grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=boot --recheck --debug

To install to $esp/EFI/boot rather than $esp/EFI/grub. All that would be required then is to rename the efi stub, which again - logically - should work for all firmware.

Does anyone have any experience of this, or be willing to test? Unfortunatly my UEFI hardware only works with bootx64.efi in $esp/EFI/boot.

Did a bit more research, and $esp/EFI/boot/bootx64.efi is essentially used to set the "default" bootloader for most UEFI firmware, hence having a higher chance of detection. The negative of this is that it would cause issues where using multiple bootloaders... Carlduff (talk) 22:59, 24 September 2014 (UTC)

Suggested changes

This section should be used to discuss reasons behind suggested changes to the GRUB article. I'm slowly going through the discussions on the page. My goal is to address any concerns in these discussions and get them closed. Once closed, we can address all concerns relating to the article as it exists now and the current state of GRUB. The reason being several of these discussions are very old. --Stevenmw (talk) 15:17, 4 December 2014 (UTC)

I've read over the GRUB article a dozen times over the past couple of days. Just trying to weed out what is relevant information, and what should be removed all together or moved out of a section and into another one. I'm currently focusing on the preface. Could I please get feedback from other users on this? I'd likesome opinions on better organization, what is relevant, what could use better clarification, etc. Thanks.
--Stevenmw (talk) 14:55, 5 December 2014 (UTC)

GRUB is a highly used package, and the Arch wiki standard has risen a great deal over the years. I feel like this article could really use several small changes and even a small amount of restructuring. It could definitely use use clarification and rephrasing in certain areas,

Here is the course of action I am proposing;

  • First we go through this discussion page and address everything. We give people a chance to provide feedback. Then within a reasonable amount of time we slowly close the discussions. (Several haven't had a response in over a year, and by closing them we can start fresh and handle things a piece at a time.)
  • Then we start one master discussion where we can all discuss changes / concerns regarding this article.
  • Then we gradually roll out these changes in an order that best fits the changes we decided needed to happen.

This afternoon I will be starting at the top of this page and researching each concern / issue. I will slowly work my way down the page over the rest of the week. I encourage other Arch users to contribute to this page as it exists right now so we can address any concerns regarding open discussions and get them closed out so we can start from scratch.

After reading over the discussion rules page I realized I had a couple of violations when adding this discussion topic. I've corrected them.

--Stevenmw (talk) 18:23, 3 December 2014 (UTC)

I was the one who added the template, so thank you very much for the initiative. Improving GRUB was planned as part of the Beginners' guide merge, and a big gripe is how information is scattered throughout the article, with none distinction between essential and dubious (corner-case to dirty hack) approaches. Feel free to add to this list. -- Alad (talk) 18:25, 3 December 2014 (UTC)

Advanced configuration

GRUB#Basic configuration and GRUB#Advanced configuration should be merged and simplified where approriate. Remaining "advanced" topics should be brought in a Tips and tricks section, or separate page (depending on amount).

Title changed to GRUB#Tips and tricks, the section is large enough to move it to a separate page (if the current structure is acceptable). -- Alad (talk) 00:49, 7 December 2014 (UTC)
As there's no further comments, I've went ahead and merged the section. Now we can focus on the real work. :) -- Alad (talk) 12:51, 12 December 2014 (UTC)


  • Shorted the introduction at the top of the article by removing the definition of a bootloader, moved definition to the Preface section of the article
--Stevenmw (talk) 15:45, 4 December 2014 (UTC)
  • The MBR and EFI sections need a major overhaul / restructure. (will draft something out this weekend) --Stevenmw (talk) 15:52, 4 December 2014 (UTC)
  • Preface needs to be cleaned up with non-relevant information stripped and provide a better transition into the article. --Stevenmw (talk) 15:49, 5 December 2014 (UTC)
  • Possibly add setting up custom keyboard layout section as mentioned in a closed discussion. --Stevenmw (talk) 10:52, 6 December 2014 (UTC)
Keyboard layouts, if added, should be added to GRUB#Tips and tricks. -- Alad (talk) 00:51, 7 December 2014 (UTC)