Some posts in thread [2] indicated that booting in legacy bios mode worked. I created a new disk image (again following the wiki instructions: https://wiki.archlinux.org/index.php/US … ion_Media) and was able to confirm that I could successfully boot from this other image after switching into legacy mode.

In thread [1], there was the suggestion to go into a UEFI shell and try a command like

which I did. After pressing enter nothing happened (the screen did not go blank, all the text remained, no messages appeared).

Eventually in that same thread, a workaround was suggested in this post. I have not tried this because I was unable to understand what exactly was being done, both because of the terse nature of the post and the fact that the referenced article is not in a language which I read (and google translate did not make it clear enough). I was unable to evaluate whether that was a sensible thing to do.

Now, finally, the questions

Firstly, does anyone have any suggestions about how to solve or troubleshoot my blank screen issue?

If not, does anyone have an opinion about which of the workarounds (switching into legacy mode or the one that I don't quite understand yet) would be better? I am not planning to dual boot the system, so I do not need to use UEFI to be win8 friendly, etc.

My experience were about a problem with nvidia card, which need to modify the kernel line by adding nomodestUnfortunately your situation doesn't leave Xorg logs. Maybe there is the main cause.Try to modify grub to load a vesa driver or you should try to start in "level 3", something like systemd.unit=multi-user.target at the kernel lineBut I think it's hardly achievable because it isn't a normal installation. Therefore you may need to unpack the iso and modify there.

Same was mine, but I could go back to use UEFI boot.My fix was to change a line in the xorg.conf.If you can see the grub display, then the problem is on the way X try to start up.You may try to run UEFI boot, and see what X had to say, later.

Having exactly the same issue with 201307 iso on my Lenovo z580. System boots from USB flash, boot options are displayed but screen goes black after one of the options is selected. Strange thing is that when I press -but not hold- power off button, system shuts itself down. It seems like a regular OS shutdown.

My problem seems to be fixed in archiso 201307My Laptop is dell vostro 5460 / Intel HD Graphics 4000+NVIDIA GEFORCE. When I turn on UEFI mode with secure boot off and legacy options on, I can boot usb device in legacy boot. And for archiso 201306, the situation is exactly the same: blank screen after choosing "Arch Linux archiso x86_64 UEFI USB", can be turned off by pressing the power button; even turning KMS off doesn't help... I haven't tried turning UEFI off. but neither the dd command nor the copying method in the wiki works for 201306.However, after swithed to ISO201307, no workarouds are needed any more, even dd works (maybe that's because my laptop doesn't support usb uefi boot). Maybe, it's due to kernel upgrade?

Notes: sometimes, usb stick quality counts. 201307 doesn't work at first when I was using my old 2GB flash disk...

I'm having the same issue on a Lenovo Thinkpad Yoga. All known remedies failed (nomodeset, etc) I was however able to use a USB stick which I accidentally had flying around with a 2012_12 and nomodeset which allowed me to boot in UEFI mode. I had to modprobe efivars manually. Also, Fedora worked as well.

I will attempt the actual (arch) installation tomorrow night and report back. I do consider the current ISO somewhat broken in this regard but can't pin down where exactly it fails. If developers wanna contact me to gather (debug) info please go ahead.

Neri, did you get any further with this? I just got my own Thinkpad Yoga and am facing the same problems. Everything works fine in legacy Boot but the screen stays black on UEFI boot regardless of the known workarounds.

might it help to first install using legacy boot and later on convert to UEFI?

If UEFI isn't the most priority, just go for legacy and use grub to boot in MBR mode.The only obstacle it could be to have the hard disk partitioned in GPT, then MBR booting might become a problem. I think that's better to setup in legacy mode and use gummiboot or refind as boot manager.

Neri, did you get any further with this? I just got my own Thinkpad Yoga and am facing the same problems. Everything works fine in legacy Boot but the screen stays black on UEFI boot regardless of the known workarounds.

might it help to first install using legacy boot and later on convert to UEFI?

Not really with Arch directly anyways. What you can do is:

1. Use Fedora 20 USB to boot the sucker up2. Use Archlinux-bootstrap install (download expand etc)3. Use refind as the bootmanager seems to solve the dual boot issues

ATM i'm fighting a mkinitcpio segfault. But that is after the installation was basically successful. It would be nice if we can find a way to fix the install medium ...

EDIT:----------------------------------------All sorted out. Unfortunately you'll have to bypass the Archlinux Install medium and resort to the fedora 20 installer. I used the XFCE4version for a smaller download.Here are the basic steps for a Dual-Boot setup:In windows (Disk Management) truncate your C: Drive. I ended up making basically what will became /dev/sda4 smaller and didn't nottouch any partition or free space before that. Here's the final Layout:/dev/sda: empty space1. recovery partition 2. ESP3. reserved4. windows5. Linux Root6. Linux home7. Swap

The installation happened from within Fedora Live using an Archlinux Boot strap image according to the Wiki for installing from anexisting Linux and the Wiki Installation Guide. I mounted /dev/sda2 (aka. the existing ESP partition) as /boot and installed refindaccording to the wiki. Please note, when you install Arch through the archlinux bootstrap method make sure you pacman -S archlinux-keyring in the bootstrap chroot first before you run the pacstrap command - it will accelerate the process tremendously!