[Solved] Arch boot problems

mlkewlj · 2016-04-02 17:26:41

I hope somebody among you can help me.
My system: Lenovo X1 Yoga, intel i7-6600U, SDD NVMe Samsung MZVKV512

I have installed Arch-Linux following the Installation Guide, the Beginner's Guide and the Dual Booting with Windows Guide. I encountered some difficulties installing the bootloader, as I initially installed grub2, then installed systemd-boot falsely, then installed rEFInd, decided that systemd-boot should be easier.
The installation is supposed to be finished now. When I boot, the bootloader offers the Windows Bootloader, the Arch Linux bootloader and the other things (EFI and Firmware). Booting into Windows works fine.

The Problem: When I choose to boot Arch Linux, nothing happens. I get a blank screen with background lighting, but nothing else. So the bootloader seems to correctly find the entry but then something fails. As I do not see any output, I can not tell, what happens. Can you help me finding out, what is going wrong?

Best
ML

P.s.: For future reference, my partitions are:
/dev/nvme0n1p1 EFI System
/dev/nvme0n1p2 Microsoft reserved
/dev/nvme0n1p3 Microsoft basic data
/dev/nvme0n1p4 Linux Filesystem (for /)
/dev/nvme0n1p5 Windows recovery environment
/dev/nvme0n1p6 Linux Filesystem (for /var)
/dev/nvme0n1p7 Linux Filesystem (for /home)
/dev/nvme0n1p8 Linux Filesystem (to bevome shared ntfs data folde)
/dev/nvme0n1p9 Swap

Last edited by mlkewlj (2016-04-03 15:06:03)

Amadren · 2016-04-02 17:35:10

I never could boot with rEFInd, try grub2 without EFI it should work.

Docbroke · 2016-04-02 18:15:46

which boot-loader you are having finally?? Can you post contents of /boot? (you can use arch live cd for that)

mlkewlj · 2016-04-02 21:20:28

I am (supposed to be) using systemd-boot in the end. Please find below the output:
Before mounting the EPS/EFI to /mnt/boot
root@archiso ~ # mount /dev/nvme0n1p4 /mnt
root@archiso ~ # ls -a /mnt/boot
. .. initramfs-linux-fallback.img initramfs-linux.img vmlinuz-linux.img
After mounting the EPS/EFI to /mnt/boot
root@archiso ~ # mount /dev/nvme0n1p1 /mnt/boot
root@archiso ~ # ls -a /mnt/boot
. .. BOOT EFI initramfs-linux-fallback.img initramfs-linux.img intel-ucode.img loader refind_linux.conf vmlinuz-linux.img

Last edited by mlkewlj (2016-04-02 21:21:32)

Docbroke · 2016-04-03 02:50:39

also post contents of folder /mnt/boot/{BOOT,EFI,loader}, recursively,, and if you have; please post contents of file /mnt/boot/loader/loader.conf, /mnt/boot/loader/entries, /mnt/boot/refind_linux.conf

Looks like you have refind installed, but contents of above folders shall clarify that.

If you want to install systemd-boot, please read wiki page on systemd-boot, you may be able troubleshoot yourself with that page in your arsenal.

mlkewlj · 2016-04-03 08:14:28

I have read the systemd-boot wiki, but I could not see that anything would deal with my situation. For the outputs, note that I wrote it to a USB stick. The USB stick has been mounted to /mnt/USB and the root folder has been mounted to /mnt/arch.

First the content of /boot in the root partition (i.e. BEFORE mounting /dev/nvme0n1p1 in /mnt/arch/boot)

/mnt/arch/boot:
initramfs-linux-fallback.img
initramfs-linux.img
vmlinuz-linux

Now the content after I mounted /dev/nvme0n1p1 in /mnt/arch/boot (which I guess is the one you want):

/mnt/arch/boot:
BOOT
EFI
initramfs-linux-fallback.img
initramfs-linux.img
intel-ucode.img
loader
refind_linux.conf
vmlinuz-linux
/mnt/arch/boot/BOOT:
BOOT.SDI
/mnt/arch/boot/EFI:
arch
Boot
grub
Microsoft
refind
systemd
tools
/mnt/arch/boot/EFI/arch:
grubx64.efi
/mnt/arch/boot/EFI/Boot:
BOOTX64.EFI
LenovoBT.EFI
License.txt
ReadMe.txt
/mnt/arch/boot/EFI/grub:
grubx64.efi
/mnt/arch/boot/EFI/Microsoft:
Boot
Recovery

I also had the impression/know that there were still refind files lingering around. I unistalled refind using the pacman -R command. Maybe this did not remove everything indeed.

For the files (I only have one entry arch.conf):

loader.conf wrote:

timeout 4
# default 1751cd16fd91476f9744b3ec6117b8c7-*
default arch

arch.conf wrote:

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=/dev/nvme0n1p4 rw (This was originally the PARTUUID. Did not work either.)

refind_linux.conf wrote:

"Boot with standard options" "ro root=/dev/nvme0n1p4 quiet "
"Boot to single-user mode" "ro root=/dev/nvme0n1p4 quiet single"
"Boot with minimal options" "ro root=/dev/nvme0n1p4"

Thank you very much.
ML

Last edited by mlkewlj (2016-04-03 08:21:52)

Docbroke · 2016-04-03 10:32:13

your loader.conf & arch.conf are files of systemd-boot. You have only arch.conf in you entries, but no file for windows, but you are getting windows as a boot option, that means you are not booting from systemd-boot. The booloader for systemd-boot is bootx64.efi, try to choose that in your next boot from bios, to see if you can boot arch. I think currently you are booting from grub.

Head_on_a_Stick · 2016-04-03 11:17:43

Please post the full output of:

# efibootmgr -v
# parted -l

These commands can be run from any live environment.

mlkewl wrote:

First the content of /boot in the root partition (i.e. BEFORE mounting /dev/nvme0n1p1 in /mnt/arch/boot)
[...]
Now the content after I mounted /dev/nvme0n1p1 in /mnt/arch/boot

You have managed to install your kernel image & initramfs to the non-ESP /boot folder, you should probably delete this to prevent further confusion.

You also appear to be missing the Windows bootmanager, this should be at $ESP/EFI/Microsoft/Boot/bootmgfw.efi

Docbroke wrote:

You have only arch.conf in you entries, but no file for windows, but you are getting windows as a boot option, that means you are not booting from systemd-boot.

systemd-boot will generate a menu entry for Windows automagically as long as the Windows-generated EFI system partition is shared and mounted to /boot

mlkewlj · 2016-04-03 14:13:37

efibootmgr -v wrote:

BootCurrent: 0017
Timeout: 2 seconds
BootOrder: 0001,0017,0000,0018,0019,001A,001B,001C,0021
Boot0000* Windows Boot Manager HD(1,GPT,a716729b-6934-4357-ae03-c00973f8bfd3,0x800,0x82000)/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* Linux Boot Manager HD(1,GPT,a716729b-6934-4357-ae03-c00973f8bfd3,0x800,0x82000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0015 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0016 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0017* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001A* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001B* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001C* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001D* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot001E* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot001F* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0020* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0021* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)

parted -l wrote:

Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.
Ignore/Cancel?

Is this a problem?

Last edited by mlkewlj (2016-04-03 14:17:46)

Head_on_a_Stick · 2016-04-03 14:38:26

mlkewlj wrote:

Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.
Ignore/Cancel?

Is this a problem?

No, just "Ignore" it and post the output.

Also, please use code tags rather than quote tags when posting terminal output.

We need to see everything that's on the ESP, from the live ISO run:

mount /dev/nvme0n1p1 /mnt
ls -R /mnt

& post the full output of the second command.

Last edited by Head_on_a_Stick (2016-04-03 14:39:05)

mlkewlj · 2016-04-03 15:04:54

Dear all. The problem has been solved. There is an issue with the intel pstate driver on Gen4 X1's (c.f. https://bbs.archlinux.org/viewtopic.php?id=210007 and https://bugzilla.kernel.org/show_bug.cgi?id=110941). I used the flag "intel_pstate=disable" when booting the .iso but did not think of using it when booting arch from the harddrive. But that was what I had to do...

Thank you.
ML

Arch Linux

#1 2016-04-02 17:26:41

[Solved] Arch boot problems

#2 2016-04-02 17:35:10

Re: [Solved] Arch boot problems

#3 2016-04-02 18:15:46

Re: [Solved] Arch boot problems

#4 2016-04-02 21:20:28

Re: [Solved] Arch boot problems

#5 2016-04-03 02:50:39

Re: [Solved] Arch boot problems

#6 2016-04-03 08:14:28

Re: [Solved] Arch boot problems

#7 2016-04-03 10:32:13

Re: [Solved] Arch boot problems

#8 2016-04-03 11:17:43

Re: [Solved] Arch boot problems

#9 2016-04-03 14:13:37

Re: [Solved] Arch boot problems

#10 2016-04-03 14:38:26

Re: [Solved] Arch boot problems

#11 2016-04-03 15:04:54

Re: [Solved] Arch boot problems

Board footer