You are not logged in.
I had an existing dual-boot (arch/windows) system that was working great. I had to re-install Windows a few months ago, and left the existing Arch partition alone. I've been struggling for a couple of days to a) get a boot screen back, and b) get Arch to actually boot.
I finally got systemd-boot to giver me a boot screen. I have an entry for the standard Arch kernel, an entry for a custom Linux-cd-ivybridge kernel, and the Windows install.
Windows boots great. When I select either Arch entry, I just get a black screen with a horizontal blue line top and bottom.
http://i.imgur.com/7nnrjvt.jpg
What's interesting is that when I UEFI boot from the latest .iso (via a USB stick) I see those same blue lines for a second or two--but then followed by all the informational boot text (and those lovely green "OK"'s).
I have zero idea of what the issue could be.
It IS a UEFI system.
Here are my /boot/loader/entries/ entries:
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
#options root=/dev/sdb3 rw
options root=PARTUUID=e9df3aa3-0ba8-4f17-bee1-a7d045a7e0d7 rw title Arch Linux-CK-ivybridge
linux /vmlinuz-linux-ck-ivybridge
initrd /intel-ucode.img
initrd /initramfs-linux-ck-ivybridge.img
#options root=/dev/sdb3 rw
options root=PARTUUID=e9df3aa3-0ba8-4f17-bee1-a7d045a7e0d7 rwAny thoughts? Thanks in advance.
Here is the contents of the /dev/sda1 partition:
drwxr-xr-x 5 root root 1024 Aug 30 2016 EFI
-rwxr-xr-x 1 root root 23073294 May 29 19:30 initramfs-linux-ck-ivybridge-fallback.img
-rwxr-xr-x 1 root root 5980123 May 29 19:30 initramfs-linux-ck-ivybridge.img
-rwxr-xr-x 1 root root 23103473 May 29 19:30 initramfs-linux-fallback.img
-rwxr-xr-x 1 root root 5984633 May 29 19:30 initramfs-linux.img
-rwxr-xr-x 1 root root 987648 May 13 09:38 intel-ucode.img
drwxr-xr-x 3 root root 1024 May 29 18:20 loader
-rwxr-xr-x 1 root root 5044496 May 22 04:55 vmlinuz-linux
-rwxr-xr-x 1 root root 4954384 May 26 20:03 vmlinuz-linux-ck-ivybridge# blkid /dev/sdb3
/dev/sdb3: LABEL="arch64" UUID="aa179f13-7e2e-4d95-8845-f5d93f840c0e" TYPE="ext4" PARTUUID="e9df3aa3-0ba8-4f17-bee1-a7d045a7e0d7"
# cat /media/sdb3/etc/fstab
# /dev/sdb3 LABEL=arch64
UUID=aa179f13-7e2e-4d95-8845-f5d93f840c0e / ext4 rw,relatime,data=ordered0 1
# /dev/sda1
UUID=AA37-F581 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sda4 Win-D
/dev/sda4 /mnt/Win-D ntfs-3g defaults 0 0
# tmpfs
tmpfs /home/wilberfan/.cache tmpfs noatime,nodev,nosuid,size=400M 0 0Hey, be nice...I'm new at this!
Offline
Maybe my thread helps?
https://bbs.archlinux.org/viewtopic.php?id=226520
In any way, the kernel jus tgot updated to 4.11.3-1. So maybe, after chrooting into your system, the next update will take care of the problem? It might be worth checking out.
Offline