You are not logged in.
Recently I have switched from BIOS-GPT to UEFI-GPT my existing arch linux installation.
I was using GRUB 2 before and now I am using gummiboot boot manager in order for booting up in UEFI mode.
I have installed gummiboot successfully, and created the correct entry in /boot/loader/entries and configured correctly /boot/loader/loader.conf pointing to the correct entry (default) in /boot/loader/entries.
When I restart my machine a black screen appears an gummiboot menu does not appear (timeout is configured in loader.conf) even if I press space bar during the boot.
Also, after installing gummiboot in the new EFI partition recently created, the files vmlinuz-linux, initramfs-linux-fallback.img and initramfs-linux.img do not exist in /boot (ESP partition). Why?
Do I have to copy manually from the old /boot partiton? Why gummiboot installer does not copy or created them automatically?
Could some help me?
Offline
Without seeing your partition layout and your gummiboot configs, we can only take you at your word that they are configured correctly...
Not an Installation issue, moving to NC.
Offline
Without seeing your partition layout and your gummiboot configs, we can only take you at your word that they are configured correctly...
Not an Installation issue, moving to NC.
HDD Layout:
/dev/sdx1 -----> BIOS boot
/dev/sdx2 -----> Microsoft basic data <--- old /boot GRUB2
/dev/sdx3 -----> Linux LVM
/dev/sdx4 -----> EFI system <--- Current /boot
And my /dev/sdx3 which is a Linux LVM partition contains below logical volumes:
---> VolGroup00-lvolswap
---> VolGroup00-lvolhome
---> VolGroup00-lvolroot <----- This is my root
---> VolGroup00-lvolvar
gummiboot config
/boot/loader/loader.conf has the following content:
timeout 3
default 64f986c181c745629a2a95072bba9422-*
/boot/loader/entries/64f986c181c745629a2a95072bba9422-archlinux.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/mapper/VolGroup00-lvolroot rw
Last edited by toni (2014-11-09 17:49:09)
Offline
https://wiki.archlinux.org/index.php/Gu … figuration
Note what the default value is supposed to point to... You may want to rename that file to something a lot more readable, like arch.conf.
Offline
https://wiki.archlinux.org/index.php/Gu … figuration
Note what the default value is supposed to point to... You may want to rename that file to something a lot more readable, like arch.conf.
:
First of all, many thanks for all your support. I agree, I have changed the names. So my new gummiboot configuration files are below:
gummiboot config
/boot/loader/loader.conf has the following content:
timeout 3
default arch
/boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/mapper/VolGroup00-lvolroot rw
Now the name is more readable but it continues with the same behaviour: no working, after restart machine... black screen without showing gummiboot menu.
Any ideas?
Offline
Please don't crosspost:
https://bbs.archlinux.org/viewtopic.php … 0#p1473790
Offline
Please don't crosspost:
https://bbs.archlinux.org/viewtopic.php … 0#p1473790
Ok, as said in the crosspost linked above I will continue in this thread.
Offline
and this is my gummiboot tree structure in /boot:
/boot/
|--EFI
| |----Boot
| | |--BOOTx64.EFI
| |
| |-----gummiboot
| |--gummibootx64.efi
|
|----initramfs-linux-fallback.img
|----initramfs-linux.img
|----loader
| |--entries
| | |--arch.conf
| |
| |--loader.conf
|
|----vmlinuz-linux
Offline
As I said, I think you need to research how to boot an LVM-based system via gummiboot -- I'm pretty sure it can be done, I just don't know how...
This looks highly relevant:
https://gist.github.com/jasonwryan/4618490
http://jasonwryan.com/blog/2013/01/25/uefi/
Offline
As I said, I think you need to research how to boot an LVM-based system via gummiboot -- I'm pretty sure it can be done, I just don't know how...
This looks highly relevant:
https://gist.github.com/jasonwryan/4618490
http://jasonwryan.com/blog/2013/01/25/uefi/
It is more or less as I have done. The only difference is that I mount ESP partition in the default recommended place /boot rather than in a non-standard one.
Using default /boot location, initramfs-linux*.img are updated automatically when arch linux is updated. No need to do anything more.
I have checked a lot of wikis but without no luck ;(
Offline
As I said, I think you need to research how to boot an LVM-based system via gummiboot -- I'm pretty sure it can be done, I just don't know how...
This looks highly relevant:
https://gist.github.com/jasonwryan/4618490
http://jasonwryan.com/blog/2013/01/25/uefi/
I have found another link which talks about LVM and EFI:
http://www.rodsbooks.com/efi-bootloader … ation.html
It similar to my case. As commented I use default standard location for EFI, that is, /boot.
Still searching for a solution.........
Offline
What does efibootmgr report?
Offline
What does efibootmgr report?
First of all I have added an entry manually using efibootmgr by typing below command:
efibootmgr -c -d /dev/sdXY -p Y -l /EFI/gummiboot/gummibootx64.efi -L "Gummiboot"
Its output is:
BootCurrent: 0011
Timeout: 2 seconds
BootOrder: 0004,0011,0000,0001,0002,0003
Boot0000* Windows Boot Manager
Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller
Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller
Boot0003* Linux Boot Manager
Boot0011* UEFI: Generic Flash Disk 8.07
Boot0004* Gummiboot
efibootmgr reports below when typing: efibootmgr -v
BootCurrent: 0011
Timeout: 2 seconds
BootOrder: 0004,0011,0000,0001,0002,0003
Boot0000* Windows Boot Manager
Error in 'efibootmgr': free() : invalid pointer: 0x.............
===== Backtrace ==========
/usr/lib/libc.so.6 (......)
efibootmgr [.....]
/usr/lib/libc.so.6 (_libc_start_main+0xf0)[.....]
efibootmgr[......]
===== Memory map ========
.................... /usr/lib/efibootmgr
.................... /usr/lib/libgcc-5.so.1
.................... /usr/lib/libdl-2.20.so
.................... /usr/lib/libresolv.2.20.so
.................... /usr/lib/libc.2.20.so
.................... /usr/lib/libefivar.so.0
.................... /usr/lib/libpci.so.3.2.1
.................... /usr/lib/ld-2.20.so
I have tried to output the results of 'efibootmgr -v' to a file and the paste to it but I don't know how to do it (tee command not working and neither redirection 2>)
Offline
jasonwryan wrote:What does efibootmgr report?
First of all I have added an entry manually using efibootmgr by typing below command:
efibootmgr -c -d /dev/sdXY -p Y -l /EFI/gummiboot/gummibootx64.efi -L "Gummiboot"
Well, /dev/sdXY won't work...
Its output is:
BootCurrent: 0011 Timeout: 2 seconds BootOrder: 0004,0011,0000,0001,0002,0003 Boot0000* Windows Boot Manager Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller Boot0003* Linux Boot Manager Boot0011* UEFI: Generic Flash Disk 8.07 Boot0004* Gummiboot
Try setting next boot to 0003 and see if that helps.
efibootmgr reports below when typing: efibootmgr -v
BootCurrent: 0011 Timeout: 2 seconds BootOrder: 0004,0011,0000,0001,0002,0003 Boot0000* Windows Boot Manager Error in 'efibootmgr': free() : invalid pointer: 0x............. ===== Backtrace ========== /usr/lib/libc.so.6 (......) efibootmgr [.....] /usr/lib/libc.so.6 (_libc_start_main+0xf0)[.....] efibootmgr[......] ===== Memory map ======== .................... /usr/lib/efibootmgr .................... /usr/lib/libgcc-5.so.1 .................... /usr/lib/libdl-2.20.so .................... /usr/lib/libresolv.2.20.so .................... /usr/lib/libc.2.20.so .................... /usr/lib/libefivar.so.0 .................... /usr/lib/libpci.so.3.2.1 .................... /usr/lib/ld-2.20.so
That looks bad...
I have tried to output the results of 'efibootmgr -v' to a file and the paste to it but I don't know how to do it (tee command not working and neither redirection 2>)
efibootmgr -v > file
Offline
Well, /dev/sdXY won't work...
When I have specified sdXY, I mean, in my case is for example sdc4 (X is c and Y is 4)
Try setting next boot to 0003 and see if that helps.
I have changed boot order using:
efibootmgr -o 0004,0003,0000,0011,0001,0002
in order for Gummiboot to boot first.
Also I have set next boot to 0003 using:
efibootmgr -n 0003
but again when I restart my laptop..... it access to hdd trying to do something (I guess booting in the order specified maybe?) but finally Win8.1 boots up..... no gummiboot menu shown even if I press space bar during boot
efibootmgr -v > file
Redirection to a file does not work.
Also, Why BootCurrent cannot be changed? and how to solve the errors shown by efibootmgr -v?
Last edited by toni (2014-11-10 01:08:18)
Offline
I have installed below packages:
efibootmgr 0.11.0-1
efivar 0.15-1
Now "efibootmgr -v" outputs correct information without crashing and I can redirect it to a file (see below). It was a problem of an incompatibility version between efibootmgr 0.8 and efivar 0.15-1.
efibootmgr -v
BootCurrent: 0005
Timeout: 2 seconds
BootOrder: 0005,0000,0001,0002,0003,0004,0002,0000,0000
Boot0000* Windows Boot Manager HD(2,200800,32000,977cd65a-eba5-11e3-b3df-60029210ec8f)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,3)PCI(0,0)MAC(MAC(d897ba11434f,0)..BO
Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,3)PCI(0,0)MAC(MAC(d897ba11434f,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO
Boot0003* Linux Boot Manager HD(4,2522e800,200000,1af51a36-df2b-48ce-b0df-727d1dacdf30)File(\EFI\gummiboot\gummibootx64.efi)
Boot0004* Gummiboot HD(4,2522e800,200000,1af51a36-df2b-48ce-b0df-727d1dacdf30)File(\EFI\gummiboot\gummibootx64.efi)
Boot0005* UEFI: Generic Flash Disk 8.07 ACPI(a0341d0,0)PCI(14,0)USB(3,0)HD(1,800,1dfc00,0002ffa3)..BO
I have observed that in my EFI partition a new folder grub has been created after installing new efibootmgr 0.11.0-1. Now my boot partition (EFI System partition) looks like below:
/boot
|-- EFI
| |-- Boot
| | `-- BOOTX64.EFI
| `-- gummiboot
| `-- gummibootx64.efi
|-- grub
| `-- grub.cfg
|-- initramfs-linux-fallback.img
|-- initramfs-linux.img
|-- loader
| |-- entries
| | `-- arch.conf
| `-- loader.conf
`-- vmlinuz-linux
6 directories, 8 files
Also I posted here my blkid output:
/dev/sda1: LABEL="ARCH_201411" UUID="CE97-B268" TYPE="vfat" PARTUUID="0002ffa3-01"
/dev/sdb2: UUID="d95a78a9-f22c-4558-ac49-cec0cf2f980f" TYPE="ext4" PARTUUID="5cbfd28a-df68-4752-86d8-9863f2a0969f"
/dev/sdb3: UUID="Q5w0H1-Efb8-H03m-un9v-wsqG-vT8t-3yeSY3" TYPE="LVM2_member" PARTUUID="7f33830c-d668-4cfa-92f5-84835f4c9fbf"
/dev/sdb4: LABEL="UEFI" UUID="DED6-7DD2" TYPE="vfat" PARTUUID="1af51a36-df2b-48ce-b0df-727d1dacdf30"
/dev/sdc1: LABEL="System" UUID="7496938096934192" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="977cd652-eba5-11e3-b3df-60029210ec8f"
/dev/sdc2: UUID="4094-1C14" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="977cd65a-eba5-11e3-b3df-60029210ec8f"
/dev/sdc3: UUID="C0C09561C0955F0A" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="977cd65c-eba5-11e3-b3df-60029210ec8f"
/dev/sdc4: LABEL="TI31299800C" UUID="3ED09800D097BC99" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="977cd664-eba5-11e3-b3df-60029210ec8f"
/dev/sdc5: LABEL="Recovery" UUID="48801C7E801C74A2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="7ede7fc5-3852-11e4-9167-d897ba11434f"
/dev/loop0: TYPE="squashfs"
/dev/loop1: UUID="ece4aa52-a24f-4585-a448-f43320f58b05" TYPE="ext4"
/dev/loop2: UUID="ece4aa52-a24f-4585-a448-f43320f58b05" TYPE="ext4"
/dev/mapper/arch_airootfs: UUID="ece4aa52-a24f-4585-a448-f43320f58b05" TYPE="ext4"
/dev/mapper/VolGroup00-lvolswap: UUID="40b01f68-9104-4213-bd81-e76050b97492" TYPE="swap"
/dev/mapper/VolGroup00-lvolhome: UUID="9cdde0e7-2fb9-470c-8592-075d34a26999" TYPE="ext4"
/dev/mapper/VolGroup00-lvolroot: UUID="b43132f0-7cee-4d3a-a634-40f3ce4f133f" TYPE="ext4"
/dev/mapper/VolGroup00-lvolvar: UUID="a5ad70cb-25ef-462a-9962-ff321f266bca" TYPE="ext4"
/dev/sdb1: PARTUUID="6d28aac9-0ca1-4345-9257-a4d97508e98d"
Anyway, gummiboot menu does not appear so I cannot boot into arch linux. Why?
Offline
Please don't crosspost. I'll close the other thread as this has a more meaningful title...
Offline
Please don't crosspost. I'll close the other thread as this has a more meaningful title...
Ok, sorry. I forgot to mark that as solved. Thanks for closing it.
I cannot boot into arch linux using EFI partition and LVM.
Now efibootmgr outputs information correctly without any error.
Could you help me, please? I don't know why but gummiboot menu does not appear.
My firmware has Secure boot disabled and UEFI only enabled.
I highly appreciate if you can help me.
My EFI partition is mounted on /boot as recomended in gummiboot wiki.
Offline
See hbar's comment in your other thread...
Offline
See hbar's comment in your other thread...
Yes, I have seen that. He says that it is an incompatibility between efivar 0.15-1 and efibootmgr 0.8. He says that it will be solve in comming efibootmgr 0.11
efibootmgr 0.11.0-1 is already available so I have updated efibootmgr from 0.8 to 0.11.0-1 but it does not work, I mean, gummiboot menu does not appear.
Also before rebooting I have set the boot order to boot first gummiboot and then windows. Also I have set next boot to gummiboot. See below:
BootNext: 0004
BootCurrent: 0005
Timeout: 2 seconds
BootOrder: 0004,0003,0005,0000,0001,0002
Boot0000* Windows Boot Manager HD(2,200800,32000,977cd65a-eba5-11e3-b3df-60029210ec8f)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,3)PCI(0,0)MAC(MAC(d897ba11434f,0)..BO
Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,3)PCI(0,0)MAC(MAC(d897ba11434f,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO
Boot0003* Linux Boot Manager HD(4,2522e800,200000,1af51a36-df2b-48ce-b0df-727d1dacdf30)File(\EFI\gummiboot\gummibootx64.efi)
Boot0004* Gummiboot HD(4,2522e800,200000,1af51a36-df2b-48ce-b0df-727d1dacdf30)File(\EFI\gummiboot\gummibootx64.efi)
Boot0005* UEFI: Generic Flash Disk 8.07 ACPI(a0341d0,0)PCI(14,0)USB(3,0)HD(1,800,1dfc00,0002ffa3)..BO
So with the configuration above indicated, If I reboot my system, gummiboot menu does not appear. Entries in the above sample are pointing to the correct HDD. As hbar said, it seems like efibootmgr cannot found /boot.....
but I don't understand why. All my configuration indicated in this post seems ok. When computer reboots, blank screen is shown, my external USB HDD Leds begins to blink, no gummiboot menu is shown and after a few seconds, windows starts automatically....
hbar says that he doubts efibootmgr touches /boot so how can I check that? My EFI partition is mounted in /boot which is the recommended by gummiboot wiki, so what's the problem?
Last edited by toni (2014-11-14 02:23:23)
Offline
Please post the output of:
# parted -l
lsblk -f
Offline
Please post the output of:
# parted -l lsblk -f
Below the results. Note that:
/dev/sda : It is my laptop internal HDD
/dev/sdb : It is arch linux live in a USB stick
/dev/sdc : It is my arch linux installation in external HDD USB. /dev/sdc4 is the EFI System Partition (/boot partition where gummiboot is installed).
and my firmware boot order is: USB, HDD and then ODD (Optical Disk Drive, CD/DVD drive)
and secure boot is disabled in firmware and ONLY UEFI boot enabled.
so as my arch linux is in the external HDD USB it should be booted first.
parted -l
Model: ATA HGST HTS541010A9 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 1075MB 1074MB ntfs Basic data partition hidden, diag
2 1075MB 1180MB 105MB fat32 Basic data partition boot, esp
3 1180MB 1314MB 134MB ntfs Basic data partition msftres
4 1314MB 989GB 988GB ntfs Basic data partition msftdata
5 989GB 1000GB 11.3GB ntfs Basic data partition hidden, diag
Model: Generic Flash Disk (scsi)
Disk /dev/sdb: 1007MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 1007MB 1006MB primary fat32 boot, lba
Model: TOSHIBA MK3252GSX (scsi)
Disk /dev/sdc: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 3146kB 2097kB bios_grub
2 3146kB 1077MB 1074MB ext4 msftdata
3 1077MB 319GB 318GB lvm
4 319GB 320GB 1074MB fat32 boot, esp
lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
|-sda1
|-sda2
|-sda3
|-sda4
`-sda5
sdb
`-sdb1
sdc
|-sdc1
|-sdc2
|-sdc3
| |-VolGroup00-lvolswap
| |-VolGroup00-lvolhome /home
| |-VolGroup00-lvolroot /
| `-VolGroup00-lvolvar /var
`-sdc4 /boot
sr0
loop0
loop1
`-arch_airootfs /etc/resolv.conf
loop2
`-arch_airootfs /etc/resolv.conf
Offline
Also, after installing gummiboot in the new EFI partition recently created, the files vmlinuz-linux, initramfs-linux-fallback.img and initramfs-linux.img do not exist in /boot (ESP partition). Why?
Do I have to copy manually from the old /boot partiton? Why gummiboot installer does not copy or created them automatically?
Yes, you have to copy the contents over.
Your arch.conf should have "root=UUID=b43132f0-7cee-4d3a-a634-40f3ce4f133f rw"
I think...
Offline
toni wrote:Also, after installing gummiboot in the new EFI partition recently created, the files vmlinuz-linux, initramfs-linux-fallback.img and initramfs-linux.img do not exist in /boot (ESP partition). Why?
Do I have to copy manually from the old /boot partiton? Why gummiboot installer does not copy or created them automatically?Yes, you have to copy the contents over.
Your arch.conf should have "root=UUID=b43132f0-7cee-4d3a-a634-40f3ce4f133f rw"
I think...
I have just tried this, so arch.conf looks like:
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=UUID=b43132f0-7cee-4d3a-a634-40f3ce4f133f rw
#options root=/dev/mapper/VolGroup00-lvolroot rw
but still not working ;(
I am wondering if vmlinuz-linux is correct.... How can I force vmlinuz-linux to be re-generated again? If I do mkinitcpio -p linux it only re-generates initramfs-linux.img and initramfs-fallback-linux.img
I want to be sure that vmlinuz-linux is correct as I have copied it from my old /boot when BIOS-GPT was present in my arch linux installation.
Also, as gummiboot is a boot manager and not a bootloader, do I need to have a boot loader installed as well? or is it not necessary?
Last edited by toni (2014-11-14 21:33:43)
Offline
As I have already said, you have to copy the contents of your original /boot over.
vmlinuz can be re-created using:
# pacman -Syu linux
If you haven't copied /boot over, then there is no kernel for gummiboot to, er, boot...
Offline