You are not logged in.
Pages: 1
Topic closed
On my Lenovo ThinkPad T430, I have the following partition scheme:
/dev/sda1 - 1.5G - WINDOWS SYSTEM_DRV
/dev/sda2 - 255G - Windows7_OS
/dev/sda3 - 13.7G - Lenovo_Recovery
/dev/sda4 - 512M - /boot
/dev/sda5 - 30G - /
/dev/sda6 - 15G - /var
/dev/sda7 - 150G - /home
In my boot-Partition are the following files:
initramfs-linux-fallback.img
initramfs-linux.img
vmlinuz-linux (3.7 Kernel)
EFI/
BOOT/
BOOTX64.EFI
gummiboot/
gummibootx64.efi
loader/
loader.conf
entries/
arch.conf
This is my loader.conf:
timeout 3
default arch
And this is my arch.conf:
title Arch
efi /vmlinuz-linux
options root=LABEL=root initrd=/initramfs-linux.img ro
I added gummiboot via efibootmgr.
If I start the computer I get into the gummiboot start menu with two entries: "Arch" and "EFI Default Loader".
If I select "Arch" the screen becomes black.
If I select "EFI Default Loader" I get a new gummiboot screen with just one entry "Arch".
If I select this, the screen remains also black.
I am able though to boot into the UEFI shell (V1 or V2) via an Arch CD.
If I then type "fs0:" and "\EFI\gummiboot\gummibootx64.efi", I get my gummiboot boot-screen and from there I am able to start "Arch".
Does anybody has any clue what I could try to make it work directly?
Thank you,
Martin
Offline
Same problem.
Since a couple of months ago I was able to boot by adding the Arch entry directly in UEFI firmware. Great, fast!
Starting with 3.8 kernel and the systemd push to gummiboot, I thought it is time to install and boot through gummiboot.
From here: https://wiki.archlinux.org/index.php/UEFI_Bootloaders
Using efibootmgr entry:
Booting Arch directly from UEFI works. No Gummiboot involved.
Using UEFI Shell
Selecting UEFI Shell from Gummiboot and launching my archlinux.nsh script launches Arch.
But using Gummiboot, I select the Arch Linux entry and the screen goes blank.
Please tell me if you need more info. I cannot understand what's wrong. The syntax to boot arch is ok (proved by booting directly through UEFI or with UEFI shell and archlinux script).
Same syntax is used in arch.conf entry of Gummiboot. I am confortable with UEFI but I don't know how to debug gummiboot. The screen goes blank and that is game over
Offline
Many people are reporting problems booting some kernels in the 3.7 and 3.8 series via the EFI stub loader, and recent reports suggest that these problems can come and go depending on interactions with the boot manager (gummiboot, rEFInd, or EFI shell). AFAIK, the true cause has yet to be determined. My first guess is that you're running into this problem, but it's possible there's an error in your options that's causing the kernel to hang. The main thread on this problem is here:
https://bbs.archlinux.org/viewtopic.php?id=156670&p=1
Edit: There's also a bug report here:
https://bugs.archlinux.org/task/34358
Last edited by srs5694 (2013-03-25 16:32:47)
Offline
since the last update it suddenly works for me. Kernel 3.8 and new gummiboot. I'd like to mark this thread as solved - sort of.
Offline
I got this exact same problem after upgrading to linux-3.12.7-2-x86_64 from linux-3.12.6-1-x86_64 on Lenovo ThinkPad T430s.
Offline
I am having exactly the same issue.
$ uname -a
Linux mohammad-tp 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64 GNU/Linux
$ pacman -Q gummiboot
gummiboot 43-2
Offline
There are a number of threads about this issue, going back as far as 3.7 (as srs5694 notes). Bottom line is that sometimes gummiboot just won't play with the vanilla kernels.
Please don't necrobump old threads: https://wiki.archlinux.org/index.php/Fo … Bumping.27
Closing
Offline
Pages: 1
Topic closed