Unable to boot in UEFI mode.

After looking around at the wiki for a few days and playing around with Arch in VirtualBox I went to see if it would boot on my native hardware, and all the turns up is a black screen. Legacy mode is not an option as I am dual booting Windows 8.1 64 bit. I suspect this is related to my issues with Fedora as the Fedora installation media will not boot either, though it once did. Fedora used to work on my machine until it got dropped one day. After the drop I started having some strange issues and tried reinstalling Fedora, only to find that once it hit the bootloader I would face a black screen that never goes away until I power the system down. I sent my laptop in to Lenovo to be serviced and they replaced the optical drive, hard drive and did a reinstall of Windows 8. Fedora still would not boot after I got the machine back. I tried Ubuntu after the drop before sending it off and it worked, and that is what I currently have installed. My knowledge of UEFI is limited. Any ideas? My laptop is a Thinkpad L440 by the way.

Head_on_a_Stick wrote:
Actually, Ubuntu will install and run with Secure Boot enabled (as will the Arch live ISO) -- the blog post is just about making your own Secure Boot keys.
From Ubuntu, post the output of:
# efibootmgr -v
Yeah I know that, but I left it off to save the extra hassle.
Here is the output for the command:
swilliams@speedy:~/Videos$ sudo efibootmgr -v
[sudo] password for swilliams:
BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0013,0000,0001,0002,0003,0007,0008,0009,000A,000B,000C,000D,0012
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Lenovo Diagnostics
Boot0004 Startup Interrupt Menu
Boot0005 Rescue and Recovery
Boot0006 MEBx Hot Key
Boot0007* USB CD 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
Boot0008* USB FDD 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
Boot0009* ATAPI CD0 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35400
Boot000A* ATA HDD0 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f604
Boot000B* ATA HDD1 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f605
Boot000C* USB HDD 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803
Boot000D* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot000E* IDER BOOT CDROM ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0)
Boot000F* IDER BOOT Floppy ACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0)
Boot0010* ATA HDD 030a2400d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f6
Boot0011* ATAPI CD 030a2400d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a354
Boot0012* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot0013* Windows Boot Manager HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)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.}....................
Boot0014* ubuntu HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\ubuntu\shimx64.efi)

Similar Messages

[SOLVED]Unable to boot in UEFI mode from CD

Hello gents!
Here's the problem:
According to the beginner's guide I followed the instruction to test if I am in UEFI mode:
In case you have a UEFI motherboard, the CD/USB will launch UEFI Shell and display a message that
startup.nsh
script will be launched. Allow the shell to launch it. Then, to check whether you have booted into UEFI mode, load the efivars kernel module (before chrooting) and then check whether there are files in
/sys/firmware/efi/vars/
# modprobe efivars # before chrooting
# ls -1 /sys/firmware/efi/vars/
Well, the thing is that when I boot the CD no UEFI Shell is launched as well as no
startup.nsh
When I try to load the efivars I don't receive any message, so, I assume, the module is loaded; but the, when I invoke ls the message I receive is:
#ls: cannot access /sys/firmware/efi/vars/: No such file or directory
To me it looks that for some reason I am unable to access the UEFI mode when starting the CD iso.
Thank you guys for your courteous attention.
Have a wonderful day!!!
P.S. I've searched already in the following posts:
https://bbs.archlinux.org/viewtopic.php … 84#p148184
https://bbs.archlinux.org/viewtopic.php … 55#p148155
P.S.2
My mobo is an ASUS Maximus V Gene with i3770K on it.
Edit:
Ok guys! Thanks to all of you, but everything was brought about by my scarce knowledge of the mobo. Logging into the BIOS, in the boot section, you have to choose between normal DVD and UEFI DVD. When selecting the last, everything, I mean, the startup phase at least, went well.
Enjoy everybody
Any idea how to close/"solved" this forum tread?
Last edited by guidone (2012-09-11 20:34:21)

guidone wrote:Any idea how to close/"solved" this forum tread?
README: Forum Rules
Simply edit the original post by clicking on the 'edit' button at the lower right corner of it and prepend [SOLVED] to the title.

Booting in UEFI mode

Hello,
I have a Z77A-G45 mainboard which supports UEFI. I am trying to install Windows 7 (64 bit) on a GPT hard drive which already has Linux Mint 13 (equivalent to Ubuntu 12.04 LTS) installed. The disk is 1TB big and I have reserved 250 GB of unallocated space for Windows at the beginning of the disk. The disk was partitioned using Gparted (or the Linux Mint partition editor which is also based in libparted I think).
The problem is that the Windows DVD only boots in BIOS mode, so it's not letting me install it on a GPT hard drive. As I have read I must boot the DVD in UEFI mode to be able to install Windows the way I want. The problem is that in the boot options I don't have one for booting in UEFI mode (the only option I get is tagged 'CD/DVD:ATAPI iHAS122 C'). I have read that I can boot into the UEFI shell, browse the DVD and start the installation program from a UEFI boot file (*.efi). When I try to do that most of the tutorials tell me to point my prompt to fs0: but I only see blk'n' (n is the number of the device) block devices. blk5 is the DVD. I mount it using the command 'mount' and the prompt tells me it boots successfully. Then I point the prompt to 'blk5:' and it works, but when I try 'cd' or 'ls' I get the error "ls/dir: Cannot open current directory - Not Found".
I am certain my motherboard supports UEFI and I am quite sure it's enabled because I get the graphical BIOS. I didn't have any problems formatting the disk as GPT, and the Windows installer (in BIOS mode) recognises all the partitions correctly but it won't let me install the OS complaining about the GPT hard drive.
What can I do? Is there a middle step I am skipping? As much as I read around everyone with this problem gets to browse the DVD in the UEFI shell but I am stuck there.
Thank you very much in advance.

I copied all of the files from the dvd to a usb 3.0 stick and installed from the in UEFI mode. (Just select the UEFI: HP usb stick or whatever)
Are you sure you don't see UEFI: DVD Burner in the boot list?

[SOLVED] Unable to boot in UEFI System

For several days I have been trying to get Arch to boot on my desktop by following the Beginners' guide and refering to other Arch wiki articles as well as Arch Forum posts for any problems that I had. I have tried a few bootloaders such as GRUB, gummiboot, and rEFInd and they all give the same result when I attempt to boot - a blinking cursor with no menu and then it returns me to the BIOS;. My UEFI motherboard is the ASUS VI Hero. I have disabled secure boot and both fast boots. I use a live USB with UEFI that is able to boot on my system and was created with dd.
Below are the outputs of some commands that might be useful.
root@archiso ~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 512M 0 part
├─sda2 8:2 0 4G 0 part
└─sda3 8:3 0 219.1G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 487.3M 0 part
└─sdb2 8:18 0 931G 0 part
sdc 8:32 0 232.9G 0 disk
├─sdc1 8:33 0 100M 0 part
└─sdc2 8:34 0 232.8G 0 part
sdd 8:48 1 3.8G 0 disk
├─sdd1 8:49 1 595M 0 part /run/archiso/bootmnt
└─sdd2 8:50 1 31M 0 part
loop0 7:0 0 256.8M 1 loop /run/archiso/sfs/airootfs
loop1 7:1 0 32G 1 loop
└─arch_airootfs 254:0 0 32G 0 dm /
loop2 7:2 0 256M 0 loop
└─arch_airootfs 254:0 0 32G 0 dm /
Windows 7 is on sdc and Arch is on sda (sdb is an extra storage device for Windows). Both sdc and sda are SDDs.
root@archiso ~ # parted /dev/sda print
Model: ATA SanDisk SDSSDHII (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot, esp
2 538MB 4833MB 4295MB linux-swap(v1)
3 4833MB 240GB 235GB ext4
root@archiso ~ # cat /mnt/etc/fstab
# UUID=0dff590b-24f1-47a2-870e-3f4d2c5bcb6a
/dev/sda3 / ext4 rw,relatime,data=ordered,discard 0 1
# UUID=FA3A-728C
/dev/sda1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# UUID=524e2980-d1e6-4948-88f9-c193682d5a9e
/dev/sda2 none swap defaults 0 0
# efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* grub
Boot0001* Hard Drive
Boot0002* ubuntu
Boot0003* UEFI: General USB Flash Disk
Boot0008 Hard Drive
Ignore ubuntu, that was on my HDD from before but has been removed. The grub option usually disappears after reboot unless I run efibootmgr -O after I install the bootloader. Using efibootmgr -v option, the output is a bit hard to read.
# efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* grub HD(1,800,100000,f9c04628-178b-4c94-9b92-62c04f2a5151)File(\EFI\grub\grubx64.efi)
Boot0001* Hard Drive BIOS(2,0,00)..GO..NO........u.W.D.C. .W.D.1.0.E.Z.E.X.-.0.8.M.2.N.A.0....................A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.3.C.1.F.6.4.5.0.4.6........BO..NO........u.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .2.5.0.G.B....................A.................................>..Gd-.;.A..MQ..L.1.S.B.D.S.N.F.A.7.1.3.0.7.5. .L. . . . ........BO..NO........o.S.a.n.D.i.s.k. .S.D.S.S.D.H.I.I.2.4.0.G....................A...........................>..Gd-.;.A..MQ..L.4.1.3.4.3.7.0.4.7.0.2.0. . . . . . . . ........BO..NO........u.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k....................A.............................B..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k........BO
Boot0002* ubuntu HD(1,800,f3a9e,3eaa3162-6352-4ad8-a725-89c738f2b3ad)File(\EFI\Ubuntu\grubx64.efi)
Boot0003* UEFI: General USB Flash Disk ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(1,fc,f800,612a5c68)..BO
Boot0008 Hard Drive BIOS(2,0,00)..GO..NO........o.S.a.n.D.i.s.k. .S.D.S.S.D.H.I.I.2.4.0.G....................A...........................>..Gd-.;.A..MQ..L.4.1.3.4.3.7.0.4.7.0.2.0. . . . . . . . ........BO..NO........u.W.D.C. .W.D.1.0.E.Z.E.X.-.0.8.M.2.N.A.0....................A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.3.C.1.F.6.4.5.0.4.6........BO..NO........u.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .2.5.0.G.B....................A.................................>..Gd-.;.A..MQ..L.1.S.B.D.S.N.F.A.7.1.3.0.7.5. .L. . . . ........BO..NO........o.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k....................A.......................B..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k........BO
I mount /dev/sda3 to /mnt and /dev/sda1 to /mnt/boot before I arch-chroot and when I tried grub, I installed with:
# grub-install --target=x86_64-efi --efi-directory=/boot--bootloader-id=grub --recheck
No errors are reported. I then make a config file for grub with:
# grub-mkconfig -o /boot/grub/grub.cfg
Last edited by DetotatedWam (2015-04-01 22:12:06)

Boot\ Secure Boot menu >
Secure Boot state: Disabled
Platform Key (PK) state: Unloaded
OS Type: Windows UEFI mode
I have tried setting "OS Type" to "Other OS" before but that doesn't change anything. I just tried it again and the BIOS freezes upon "Save Changes & Reset".
Boot\ Secure Boot menu\ Key Management >
PK Management: Unloaded
KEK Management: Unloaded
DB Management: Unloaded
DBX Management: Unloaded
The other day, I deleted all of them and backed them up on a USB in order to disable secure boot.
Note: After looking at this menu again I am noticing options to append from file for KEK, DB, and DBX that might help.
Append KEK from File
Allows you to load the additional
KEK from a storage device for an
additional db and dbx loaded
management.
[Yes]
Load the default KEK
[No]
Load from a USB storage device
Append db from File
Allows you to load the additional db
variable from a storage device so
that more custom signed UEFI
executble files can be loaded.
*UEFI executabled files include UEFI
boot loaders, drivers and
applications.
[Yes]
Load the default db
[No]
Load from a USB storage device
Append dbx from File
Allows you to load the additional
dbx variable from a storage device
so that more custom signed UEFI
executble files cannot be loaded.
*UEFI executabled files include UEFI
boot loaders, drivers and
applications.
[Yes]
Load the default dbx
[No]
Load from a USB storage device
Boot\ CSM (Compatibility Support Module)
Launch CSM: Enabled
Boot Device Control: UEFI and Legacy OPROM
Boot from Network Devices: Legacy OPROM first
Boot from Storage Devices: Both, UEFI first
Boot from PCI-E/PCI Expansion Devices: Legacy OPROM first
As a side note: After a reboot, I noticed the Arch boot option disappeared again.
Head_on_a_Stick wrote:Have you managed to boot any other distributions that are not compatible with Secure Boot?
I have been able to boot Windows 7 and ubuntu but I beleive both are compatible with Secure Boot so, no.
Head_on_a_Stick wrote:The Arch live ISO has the EFI applications PreLoader.efi & HashTool.efi included so that will boot up with Secure Boot enabled.
I will try this and post the results.
Edit: Now my BIOS Freezes everytime I try to save & exit.
Last edited by DetotatedWam (2015-04-01 19:59:18)

Unable to boot into safe mode with FileVault 2 enabled

I was trying to boot into safe mode earlier to try and fix a few things. It looks like I can't and I suspect it is because of FV2.
When the system starts I press shift after the tone, but then I have to release shift and enter the password and then Lion will only boot into normal mode.
I've also tried with sudo nvram boot-args="-x" from the terminal, but while it seesm that this way Lion starts to boot into safe mode, after a while it just restarts as if something crashed etc and then again, I have to enter the password for FV and all again as in a loop, i.e. Lion won't even start this way.
So I went into the recovery mode and I could make Lion start again at least in normale mode with sudo nvram boot-args="".
Any idea of what could be preventing Lion from entering safe mode?
Thanks in advance

The symptom may be unrelated to FileVault 2. I encountered the symptom with FileVault 2 disabled and with backward conversion (decryption) complete.
Apple reference for my bug report: 152162960. If the symptoms on your Mac compare to those on mine: progress may seem to cease during safe fsck.
Vito, as you are comfortable with the nvram command, please try the following:
sudo nvram boot-args="-v -x"
Restart the computer and note the last verbose lines that appear before you sense that progress has ceased. Then please add a note of those lines to this topic.
Additional questions
What model is your Mac?
What type of disk for the startup volume?
How many files on that volume?
Approximately how large are the attributes file and catalog file? (You might gain this information with a demo version of iDefrag.)
My current envronment
MacBookPro5,2
8 GB memory
startup from internal 320 GB rotational disk, Serial-ATA, Hitachi HTS723232L9SA62 (probably Travelstar 7K320)
3,961,791 files
495,744 folders /* not including the root folder */
catalog file 3.0 GB, not fragmented
attributes file 2.2 GB, not fragmented.
At http://www.wuala.com/grahamperrin/public/2012/01/09/a/?mode=gallery file speedy.txt includes details of the volume.

Unable to boot with UEFI by bootable windows 8.1 DVD

Hi guysUnfortunately when I want to install windows with UEFI from bios, there is no choice for choosing boot from DVD, while my DVD is bootable and it is in my DVD Rom. On the other, by changing UEFI to Legacy support, it can recognize my bootable DVD of windows 8.1. I really cant understand what is the problem. Please help to install new windows through UEFI (((((((((Thanks

I think this is a problem with new laptops (as far as I know), you cannot boot into UEFI using DVD.
(Try disabling / enabling SecureBoot but I dont think that will help either)
You can however create a bootable USB and boot into UEFI.

Unable to boot in safe mode or leopard disk after a failed update

I was doing an update to 10.6 last night and got an error. Now when computer starts up, I get a Finder error after I log in and will not start up. Just continue to shows the Finder error when clicking on ok. I can't copy and paste to show you the error as computer will not do anything. I tried starting up in safe mode, samething happened. I then booted from DVD and it just sits there with gray apple on screen. Ideas? No exteral anything is plugged into it either. Please help!

I then booted from DVD and it just sits there with gray apple on screen.
Is that the same DVD you used to install 10.6, or the one that came with your Mac? If so, is it scratched or dirty? Did you try to boot from it by holding down the C key at startup? Can you run the Apple Hardware Test from the Applications disc that came with your Mac?
Intel-based Macs: Using Apple Hardware Test

Prepare an usb thumb drive, to boot windows 7 or 8 in UEFI mode

Purpose of this post:
Prepare an usb thumb drive, to boot windows 7 in UEFI mode and install the system in pure UEFI mode.
Why am I writing this:
I had a hard time finding out how to make a custom installation of windows 7 in pure UEFI mode, and avoid using the factory restore disks. After hours of research, experiments etc I finally got the point and found a solution. And I'm happy to share my research with you. I hope this will be of help. If something is not clear, or more information is needed, I will be glad to explain things further.
History:
As most of you already know, BIOS was developed for PC in early eighties and has remained unchanged in recent years. But, since 2000, Intel started working on a new firmware interface, called Extensible Firmware Interface, abbreviated EFI. And since 2005 United EFI Forum has been handling the responsibility for development, management and promotion of UEFI specifications. Bigger companies like Intel, AMD, Microsoft and Dell have already started to bring out their products in accordance to UEFI standards which has more stable, secure and easier to use interface.
How does UEFI works (in a nutshell):
Once you power on the UEFI based PC, the Pre-EFI is executed which initializes only the CPU, memory and the chipset. This followed by Driver Execution Environment (DEX) where other hardware is initialized.
Advantages of UEFI:
    It can integrate various drivers this will not require to load during booting so saves time.
   PC can connect to network without OS.
   Also integrated drivers allow rendering GUI based control panel which out dates the old school bluish BIOS screen.
   Not all the installed hard drives are scanned as boot drive is set during the installation of OS in UFFI.
   Applications like anti-virus and diagnostic tools can be stored on virtually any non-volatile storage devices attached to a PC.
For a system to boot and install in UEFI the partition table of the HDD should be GPT (GUID Partition Table), not the old school MBR (master boot record). GPT has many advantages, can have virtually an unlimited number of partitions (windows will allow only 128) and impressively big partitions.
Since UEFI has a lot of advantages why not having a system install and boot in UEFI mode? AFAIK new Lenovo notebooks/netbooks are UEFI capable and OS’s are already installed in pure UEFI mode.
So, let’s go now to the point. Do you want to have more control over your HDD? Let say, you have a 320GB HDD and you have divided it in two partitions, one of 50GB, for your Windows 7, and the remaining for your data. If something goes wrong and you need to restore your system to factory default, with the recovery disks, it will wipe your partition scheme, set the system to default and this way your data will be lost.
You may want to make a “vanilla” installation of windows from a USB thumb drive and avoid using factory recovery disks. Now here things get complicated. A standard preparation of the USB with Microsoft’s software (Windows 7 USB/DVD Download Tool), or other tools, will give you a bios installation, not a UEFI one. So for the system to boot, you will need to change some settings in bios, and changing it from UEFI to legacy bios. The installation will prepare the HDD in MBR partition table, and you will lose all the advantages of UEFI, described above.
Now this can be avoided, by properly preparing an USB to boot and install in UEFI mode. Here are the steps:
Step by step tutorial:
1.   In a windows computer, download a legal copy (although trial) of the windows 7 os. You can do this from here: http://www.mydigitallife.info/official-windows-7-sp1-iso-from-digital-river/
Be sure to download the same version that came preinstalled in your computer. For example, if you have a Lenovo x120e, with a Windows 7 professional, 64bit, download an iso image of the Windows 7 professional 64bit.
2.   Once downloaded burn the iso to a USB thumb (at least 4GB) using Windows 7 USB/DVD Download Tool.
3.   After preparing this, create a folder on your computer, name it whatever (i.e. W7pro64bit). Go to the root of your USB
and select all the files and folders there (9 in total) copy, and paste to your folder you created, W7pro64bit.
4.   Using windows format the usb again in FAT32. Windows 7 USB/DVD Download tool, formats it in NTFS. We need a FAT32 formatted disk to achieve our goal. Formating again the USB in FAT32 will not touch the MBR of the USB thumbdrive. And after copying back the files (see step 6) the USB will still be bootable. (nice, and simple, isn't it?)
5.   Now go to the folder W7pro64bit and do the following:
a.   Browse to W7pro64bit\sources\ and open install.wim file. It’s a big file, and can be opened as an archive with 7zip (free software). Do not extract it, do not modify it, just browse the file with 7zip. Just to be sure you do not mess with that file, you can copy it somewhere else in your computer, and than procede.
b.   Browse this file (install.wim) to \1\Windows\Boot\EFI\ and locate the file bootmgfw.efi. Do not move, delete it, but just drag that file to the desktop. (if you have copied the file install.wim to another place in your computer, than you are safely do whatever you want with that file ) Close the 7zip program to release the install.wim file.
c.   Rename the file you just copied to the desktop from bootmgfw.efi to bootx64.efi.
d.   Now go back to w7pro64bit folder and browse \efi\Microsoft. Form there copy the folder boot and paste it one level up, on the folder: \efi. It will look like this: \efi\boot.
e.   Now copy the file you saved on your desktop and renamed (bootx64.efi) to \efi\boot (inside the boot folder you copied on step 5d
6.   Now go to the root of the folder W7pro64bit and select all folders and files (9 in total) copy, and paste all those files back to your USB thumb drive. (see step 4 for more info)
7.   Go to the computer that you are going to reinstall, and before restarting it, use the program ABR (activation backup and restore) to backup the license of your windows os. (use google to find ABR). Advanced Tokens Manager (ATM ) is great too. This link may be of help: Backup and restore W7 activation. After the program finishes its magic, it will create a few files inside the folder where the program itself reside. Copy these files to a new folder in your usb. Rename it to ABR so you will quickly find it later. (if you decide to use ATM, the procedure may be a little different. But you are smart enough to figure out how to use it)
8.   Backup to an external storage all your data before continuing.(reminder: are you sure you saved the license as explained in step 7, to a safe place? To a external drive, to another computer? If you are sure, than go on with step 9)
9.   Now restart your laptop, and enter your bios settings. Go to the boot settings, and set the computer to boot in UEFI only. Not both, not UEFI first, or legacy, BUT UEFI only. Save and restart.
10.   Press f12 (or the corresponding key for your machine) to choose the boot device and chose to start from the USB thumb drive with your windows 7 pro 64 bit.
11.   If everything is done correctly, your computer will boot from the USB.
12.   Follow the wizard and choose a custom install, not upgrade. At the disk partition window delete all the partition you see there until you have only one unallocated space.
13.   Select it, and click next to install windows, without making partition in this point. The installer will create a GPT partition table not a MBR since the USB booted in UEFI mode.
14.   Immediately after the first restart remove your USB thumb, and the installation will continue from the HDD. Wait until installation finishes.
15.   When you will be finally on your desktop, on the installed OS plug your USB go to the ABR folder and click on restore.exe. It will restore your license and your copy of windows will be activated.
16.   Now you can go in computer management/disk management and shrink the HDD to create your partitioning scheme. Make sure to leave enough space to your windows os. (30gb or more for extra programs you will install at your choice)
17.      Download from lenovo.com thinkvantage system update and update your system. Windows update too can install all the necessary drivers, if you need only basic drivers support.
Note: if tvsu will fail to work, see this:
http://forums.lenovo.com/t5/ThinkVantage-Technologies/ThinkVantage-System-Update-Servers-down-the-wh...
It may look a looong tutorial, but once you do this for the first time, it will look a piece of cake.
Final words:
From now on, you can install windows 7 in UEFI mode with your special USB without changing your partition scheme anymore. If you have a data partition beside your os partition (see the example above), when you reinstall the system using your USB thumb drive, at the disk partition window chose the partition where windows is installed, delete it, and reinstall windows to the unformatted area. Your partition with your data will be intact and the installation will automatically mount your data partition to the system. And, all the scope of this procedure, you will always have a pure UEFI installation of the system, with all its benefits.
Have fun!
abvasili
Moderator note: changed subject to match new content. Was: Prepare an usb thumb drive, to boot windows 7 in UEFI mode
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.

seanare wrote:
Thank you, as I noted here, your post was the key to my getting a Windows 8 SecureBooting setup on a W530.
In the case of Windows 8, I needed to copy the files away, reformat my USB key as FAT32 and copy the files back, and viola I was able to boot from my USB install media with the BIOS set to only boot UEFI. From there, there rest was easy (for Windows 8, the copying and renaming is not necessary, the key is having a FAT32 partition on the USB media, rather than an NTFS one; the EFI files are already in the right location).
Thank you again good sir.
You are welcome... and I'm happy that the change of the file system helps with windows 8 too. Thanks for confirming that.
abvasili
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.

[SOLVED] Attempting to boot from USB key in UEFI mode

I am attempting to boot from a USB Key in UEFI mode to dual boot windows 8 and arch linux. I'm unsuccessful in getting the USB key to boot in UEFI mode.
I am following the guide on page: https://wiki.archlinux.org/index.php/Un … _Interface due to the fact that I am receiving error " No loader found. Configuration files in /loader/entries/*.conf are needed."
I am attempting to use the archiso media and have created refind.conf according to https://bugs.archlinux.org/task/31894#comment102233 in (USB)/EFI/boot/refind.conf
However, I'm stuck on the initial step from the wiki: Install refind-efi pkg. In the usb's filesystem, overwrite the file EFI/boot/bootx64.efi with /usr/lib/refind/refind_x64.efi.
My question is: How do I install the refind-efi package onto the USB key using an arch linux host machine and the USB plugged into the machine.
Last edited by tonysoprano (2013-02-13 04:09:56)

swordfish wrote:1. Might be possible, that the uefi integration is pretty bad. Have you already looked for an update of the uefi bios?
This is my thought, too. The "memory map has changed" message sounds like the firmware is messing with the way memory is laid out in the middle of the boot process. A firmware update, if available, is likely to be the best way to deal with this problem. If not, trying Fedora's patched GRUB Legacy and GRUB 2 are also worth doing; it's conceivable that one of them includes a workaround for the problem.
2. In your first posting you mention Windows 8 on this machine. Is W8 starting in uefi mode?
This is important, but if the disk uses GPT partitioning, then Windows is starting in EFI mode.
3. If W8 is starting in uefi mode, are you sure that secure boot is disabled?
It is; if it weren't, neither rEFInd nor ELILO could start -- or even if they were configured to start in Secure Boot mode, ELILO doesn't launch its kernels in a way that respects Secure Boot, so the ELILO failure can't be caused by Secure Boot. Also, when launched with Secure Boot active, rEFInd returns a clear error message about a security violation and then returns to its main menu; it doesn't hang the computer.
One possible workaround occurs to me if all else fails: Have rEFInd launch a BIOS version of GRUB. The setup procedure, in outline, is as follows:
Create a BIOS Boot Partition on the disk.
Install the BIOS version of GRUB 2.
Configure rEFInd to include a scan for BIOS-mode boot loaders by uncommenting the "scanfor" line in refind.conf and adding "hdbios" to it.
Thereafter, you'll see a new "generic" icon, which should launch GRUB, which should launch Linux in BIOS mode, even though Windows launches in EFI mode. This will work on most modern UEFI-based computers with a single hard disk, but things get trickier with multiple disks and with some UEFI implementations that lack the necessary firmware features. If a future firmware update fixes the problem, or if a future kernel's EFI stub loader includes a workaround, the EFI-mode booting will become an option once again.

Cannot boot Arch (USB or HDD) in UEFI Mode

I have a new MSi GT70-0ND, 1x 128GB SSD (no RAID) and 1x 750GB HDD. The SSD was preloaded with an MSi OEM copy of Windows 8. I did not receive an OEM disc, so I've tried to avoid touching the SSD and the hidden recovery partition on the HDD.
Using Universal USB Installer, installed archiso onto USB flashdrive.
Windows boot device selection menu did not detect the flashdrive.
Checked UEFI BIOS settings - USB set to "Full Initial".
Moved flashdrive from port to port, eventually was detected.
Reboot, received an error relating to bootloader signing.
Rebooted again into UEFI BIOS settings, disabled secure boot.
Rebooted, received infamous "No loader found. Configuration files in \loader\entries\*.conf are needed."
Googled, checked forums, saw gummiboot issues, recommendations to use rEFInd, and dd/UEFI issue.
Transferred archiso to working Arch machine, followed instructions here https://wiki.archlinux.org/index.php/UE … B_from_ISO.
Installed rEFInd using instructions here https://bugs.archlinux.org/task/31894#comment102233. I have since tried various changes to refind.conf and can not discern any difference.
Attempted to boot laptop from flashdrive in UEFI mode after Windows' boot device menu again failed to detect flashdrive multiple times.
Got rEFInd menu, found nothing functional (except Windows bootloader, of course): Arch entry froze the system requiring hard reboot, UEFI Shell v2 gave an assertion error (from memory, it was "String.c(166) String != ((void *)0)"); Googled, seeing some related but no identical errors, UEFI Shell v1 failed to start reporting something like "using load options '<null string>'".
Rebooted in BIOS/Legacy mode, but flashdrive was unbootable (duh)
Again using Universal USB Installer, installed archiso onto flashdrive.
Rebooted in BIOS/Legacy mode, archiso menu appeared, but during udev events, received a drm/nouveau init table error; Hard reboot. Appended
nouveau.modeset=0
to kernel line, everything worked
Installed vanilla Arch system to the HDD including UEFISYS partition.
When it came time to set up and install rEFInd/efibootmgr, of course
modprobe efivars
failed.
Redid flashdrive the UEFI-safe way on Arch machine, attempted to boot in UEFI mode, it appears that menu entries from my /boot/efi (UEFISYS) partition are present, but this is irrelevant as only the Windows bootloader and \refindx64.efi work (loads rEFInd graphical mode, in which nothing works except BOOTX64.efi which quickly flashes a message with a file path (too quickly to read) then loads Windows. UEFI Shell v2 now has same error as v1:
Using load options '<null string'> Error: Not Found while loading shellx64_v2.efi
rEFInd (version 0.5.0) "About" dialog reports EFI Revision 2.31, Firmware: American Megatrends 4.653, Screen Output: Graphics Output (UEFI)
I have tried adding various things to the refind.conf "options" directive, e.g. gpt, loglevel=7, pci=nocrs, add_efi_memmap, archisobasedir=arch, archisolabel=ARCH_201212, acpi=off, etc. in different combinations.
I am at wits' end. Bottom line: nothing but rEFInd (via flashdrive) and Windows works in UEFI boot mode - nothing. Any help will be greatly appreciated. Thank you.

I doubt if this will help you with your main goal, but I've fixed a few memory bugs in rEFInd recently, so the "String.c(166) String != ((void *)0)" error you mentioned might go away if you upgraded to the latest version of rEFInd (0.6.0).
Beyond that, here's a suggestion:
Prepare a USB flash drive or CD-R with rEFInd 0.6.0. Be sure to include an EFI driver for whatever filesystem you used in Arch's /boot (or root, if there's no separate /boot partition) in the flash drive's or CD's EFI/BOOT/drivers_x64 directory. (Note that rEFInd 0.6.0 includes an ext4fs driver.)
Using an emergency disc, create a refind_linux.conf file in Arch's /boot directory. Include, at a minimum, two lines, each of which should include the options "ro root=/dev/{whatever} initrd={\path\to\initrd}", changing the device filename to point to your root and the initrd= specification to point to your two Arch initrd files (one for each line). The path should be relative to the root of whatever filesystem holds those files, so if you've got a separate /boot partition, there would be no directories, just the filename preceded by a backslash; and if you have no separate /boot partition, you'd lead with "\boot\". Note the need for BACKslashes, not forward slashes, in the initrd= specification (but forward slashes in the root= specification).
Reboot using the rEFInd flash drive or CD-R you've prepared. With any luck, rEFInd should come up and show you an Arch option. Try using it. If it fails, try again, but hit Insert and select the second option from the list.
With any luck this will get your system booted in EFI mode, but I can't make any promises about that.

Blue screen when booting from USB drive in UEFI mode (2013.07)

SOLUTION for me was to update the firmware on my ASRock mb as thatu pdate changed the EFI software (by American Megatrends) version from 2.00 to 2.31. However, other users are still experiencing the blue screen.
SHORT VERSION
When I try to boot Arch Linux 2013.07 with an USB drive in UEFI mode (for installation), I get a blue screen (which is rather a literal description and not a hint towards the old Windows' one) with the message
Failed to install override security policy (14): Not found
LONG VERSION
I made an USB installation media (product: Intenso Rainbow) by following this advice on the wiki.
I used the july release of Arch for that. First of, after installing the image to the USB stick I found that I needed to correct the label in the archiso-x86_64.conf file to ARCH_201307 (or was it the label of the usb stick, can't remember right now). (Pretty sure it was the same problem with "Linux Live USB Creator" which I used 3-4 months ago...)
After doing that, I rebooted and selected the entry
UEFI Intenso Rainbow
from this list of entries:
SATA HDJ ... something (the hard drive where Win 7 64 bit is installed with all programs)
SATA something (hard drive which only contains data)
Windows Boot Manager
USB: Intenso Rainbow
UEFI: Intenso Rainbow
It went to a blue screen with a message in white text saying
Failed to install override security policy (14): Not found
Below that was an OK button which had a black rectangle over it.
After I experienced the bluescreen, I tried booting the
USB Intenso Rainbow
entry and the boot process then worked fine, I got to that Arch menu where I could choose
Boot Arch Linux (x86_64)
Boot Arch Linux (i686)
Boot existing OS
Run Memtest...
and so on...
But just to make sure, I then did the check for UEFI mode according to this and only saw a folder acpi and ... something else I can't really remember, but it definitely was not efi. Thing is, I needwant to boot into UEFI mode as I have Win 7 already installed in UEFI mode.
Some info about my motherboard: it's from ASRock and is called H67M. The BIOS is dated to 2011-10-26 and is version 1.7.
So far, I only found a mention of the problem here at superuser.com.
Last edited by jones (2013-07-15 07:15:18)

Ok then, so this thread has also become about the blank screen problem when booting (in this particular case, Arch 2013.06 since 2013.07 seems to be worse).
srs5694 wrote:Typically, you adjust kernel boot options using your boot manager or boot loader. In GRUB, you hit the "e" key to open an editor. In rEFInd, you hit F2 or Insert twice. I don't recall offhand what key does the job for gummiboot (which I'm pretty sure the Arch installer uses), but I'm certain it's got the feature.
You are right. Thanks. I realized I had the gummiboot config right in front of me all the time. It's the file 'archiso-x86_64.conf' in \loader\entries (on Windows).
An addendum: I think the USB: Intenso Rainbow boot option takes me into a GRUB menu. Hitting 'e' in this "big" and fully designed menu didn't do anything IIRC. Hitting 'Tab' did the trick to get into editing the boot command line.
Hitting 'e' worked in the gummiboot menu though.
So I tried booting with the following options (also by combining some of them)
nomodeset
acpi_backlight=vendor
radeon.modeset=0 (I have a Gigabyte 7870 card in this desktop machien)
i915.modeset=0
but it did not help.
To be rather safe than sorry: I should mention that there are two grey-ish bars visible on the top and bottom of the screen after I try to boot the first entry, Arch Linux archiso x86_64 UEFI USB. Always has been with those two older Arch version (2013.05+2013.06). I also found another thread where one user talks about using the VGA port of the monitor, which I am currently not, I am using the DVI one, so that's worth a try too. EDIT It did not help either. What I did was setting the primary graphics adapter in the UEFI north bridge configuration menu to 'onboard' which worked immediately when rebooting (I hit the button labeled "Source" on my monitor and it showed it is using the "Analog" mode), but the problem just stayed the same. Adding aforementioned boot options or a combination thereof did not change anything.
Thanks for the e-mail addresses, I sent one to James Bottomley.
Last edited by jones (2013-07-07 11:12:05)

How do I boot into recovery mode with wireless keyboard

I am unable to boot into recovery mode using either cmd-R or holding down the alt key. How is it supposed to work?
Message was edited by: Niklas Brunberg (better title)

I understand your concerns - I'm glad both of my machines are dual bootable (just in case) and I have my Snow Leopard install disks..... However, this is what Apple has decided, so we need to find the best way to deal with it. Personally, I've tested the recovery mode several times and, at least on my machine, it was not reliable (i.e. it wouldn't work - I tried it again and it did, but it spent more than an hour downloading the entire 4 GB installer again and then another 30 minutes installing it), and on a third try, I found that it had vanished because I had cloned by drive. When you clone, only your system is cloned, not the extra partition.
So, I've decided to rely on a) my bootable clones and b) a copy of the installer (.dmg) in case my clones fail. I don't feel comfortable relying on something that requires an internet connection and a full download to work. But, that works for me; you may want to take a different approach.

Impossible to install arch in UEFI mode on my Acer Aspire S3-391

Hi there,
I am trying to install arch-linux on my Acer Aspire S3-391, which came with a pre-shipped Windows 8. I am trying to make a dual boot, so I would like to keep the UEFI mode at startup. However, my computer won't boot on the Arch Linux USB Flash drive when in UEFI mode : when plugged in, the key prevents the computer from loading anything. The "Acer" page keeps on reloading itself, without even letting me access the BIOS menu (In other words, the computer is blocked at "POST" phase when the installation media of arch is plugged in).
Here's what I did to try and solve the problem :
1) of course, I disabled Secure Boot and hibernation in Windows 8.
2) tried to boot in legacy bios. It works, and i could install arch this way : but as told before, i would like to install it in UEFI mode.
3) Checked, re-checked and re-rechecked the installation media.
4) tried to install Ubuntu in UEFI mode. It worked : the bootable key of Ubuntu was loaded, when the bootable key of arch is blocked. Why ? No idea...
5) Installed Ubuntu, and tried to install Arch in UEFI mode from Ubuntu, following the tutorial "Install_from_Existing_Linux". No luck here : i was blocked at step "Testing if you are booted into UEFI mode" on the beginner's guide : I was not, and I couldn't find any solution in the tutorial.
Any suggestions on what I should try next ?

If you've already installed in BIOS/CSM/legacy mode, my recommendation is to install your EFI-mode boot loader and try it out. You'll need to use something else that does boot (such as Ubuntu), install the boot loader using the Windows bcdedit command (assuming you're dual-booting), or install the boot loader as EFI/BOOT/bootx64.efi (if you're setting up for Linux alone) to get it to work, though.

Win2003 SP2 VM won't boot to safe mode

I have a Windows Server 2003 SP2 VM set up in Hyper-V on my Windows Server 2008 R2 server. The VM was created as an export from AppAssure 5 export to Hyper-V Virtual Standby. This particular server won't complete the boot but "sits"
at the Windows splash screen indefinitely (I've let it run for two hours with no change). I specifically use the work "sits" vs. "hangs" because the progress bar continues to move and the CPU usage fluctuates between 20 and 30%.
AppAssure T3 support want me to try to boot into safe mode but I'm unable to do so. I'm connecting to the VM through Hyper-V manager on my local Windows 7 PC. I have inserted the integration services disk in the vmguest and it shows that keyboard
input is being captured but it doesn't seem to recognize the F8 keystroke.
Before I try to run startup recovery from install I was hoping someone here might be able to offer insight into why I'm unable to boot to safe mode. I do have one other VM server created through the AppAssure export and I can boot normally or into
safe mode with that one.
Thanks in advance for any insight provided.

Thanks for the reply. I'm currently into the 5th hour of the boot process and no joy yet. I'll let it go for a little bit longer before stopping to so I can re-enable my protection of the server.
Yesterday, I tried mounting the drive to see if any errors were being registered in the event log that might not be causing a bsod or other start up error but kept getting an error when trying to read the event logs through my win 7 pc. It said
it wanted to convert them to .evtx and I said ok then would get an error that the log was corrupt or unreadable.

I cannot boot into safe mode

I cannot boot into safe mode
I ran onxy, all appeared ok,
I booted from installer DVD,- repaired the drive, - nothing wrong with the drive,
and repaired disk permissions, twice, as a few permissions were incorrect
The only app which automatically logs in user account is KeyCue, and has done so always, and I don't know what what it belongs to. Nothing logs in automatically in the admin account.
I intermittently have a problem with DVDs not mounting, and a safe boot fixes the problem.

further to being unable to boot in safe mode-
normally when i boot in safe mode, when its starts up and reaches the login screen, above this are the words in red safe boot. As the words were missing from the login screen I had assumed that I was not in safe boot. I currently have about 94 GB of HD space. Other than this booting process appears to be normal. What prompted the safe boot was a DVD which mounted ok on insert, had unmounted when I went to eject, a restart and holding down the shift key ejected the disk, and I then tried to do the safe boot. Since I ran disk utility from the installer disk the same DVD has mounted and ejected just fine. The vanishing disk problem started 4-5 months ago, and has always been fixed by a safe boot

Unable to boot in UEFI mode.

Similar Messages

Maybe you are looking for