T540p firmware ignores Linux EFI boot

This post is for just a suggestion for anyone who is installing Linux on their Lenovo. The firmware in my new T540p (arrived from the factory 2014-12-19) does not recognize Linux EFI boot entries, at least not the way they are installed by Ubuntu 14.10 (which may be a bug in the Ubuntu installer). My bootloader would only look for one absolute path EFI/boot/bootx64.efi. If you install Linux, you will not necesarily get this file--it may instead be EFI/ubuntu/grubx64.efi, and the corresponding boot catalog entry may not be installed for you. In this case, your Lenovo will silently refuse to boot your Linux. If you have this problem. try this:
boot to Linux via LiveUSB or LiveCD
mount the boot partition
sudo mkdir /mnt/deadboot; sudo mount /dev/sda1 /mnt/deadboot
copy grubx64.cfg to bootx64.cfg into the magic directory:
sudo mkdir /mnt/deadboot/EFI/boot
sudo cp /mnt/deadboot/EFI/ubuntu/grubx64.efi /mnt/deadboot/EFI/boot/bootx64.efi
unmount and reboot
Also make sure your boot partition is an "EFI System" partition:
sudo fdisk /dev/sda
p
your boot partition should be listed as "EFI System" type
--if so, stop here
--else continue and fix it:
t
select the boot partition
select parition type 1
w
writes the change to disk and issues a warning that you can ignore
reboot
Notes: (1) your boot drive may not be /dev/sda1. Google for various ways to find it. (2) If your liveUSB or liveCD won't boot either, try switching the BIOS between legacy and UEFI boot. Recently downloaded 64-bit Ubuntu images will only boot UEFI.

These forums are not really your best choice to find an answer. Either the Mint tech support or forums can help you or you might try the Ubuntu forums. Macs are not the only computers that have and use EFI. Your issue may simply be one of configuring GRUB.

Similar Messages

HT1237 EFI Boot off USB.

Why isn't iMac 8,1 (Model identifier) in the list of firmware updates for EFI boot?

Sort of. Not sure if I'm missing something on my Mac or if there is an issue with the EFI boot USB memory stick.
When I power on and hold down the Options key, my MAC recognizes the USB EFI boot device and gives me the option to boot from USB or Hard Drive.
When I select EFI boot, it freezes and does nothing (or it is extremely slow booting).

Firmware 1.0.1 boot device order - efi password

Hi.
Having an "open firmware" (EFI) password set, firmware version 1.0.1 ignores the password and boots a boot cd like rEFIt boot helper. Boot CDs are always booted first without considering the so called "open firmware" password.
This is a security desaster!
What i want:
With an open firmware password set:
Always boot "Mac OS X" or "Windows" first. When holding down the "alt" key, let me choose the boot device, like a boot cd!
Please have some developer read this!
with kind regards
Thomas

Good Morning,
I'm going to type this out in English and try to translate it to Italian so pardon any mistakes on my part...
You can always verify your MacBook's BootCode version by going into Applications -> Utilities -> System Profiler and checking out...
Boot ROM Version: MB21.00A5.B07
SMC Version: 1.17f0
That should give you a good idea if you need any updates!
Hope this helps! 
David
(Thanks Google Translator)
Potete verificare sempre la versione di BootCode del vostro MacBook entrando in
Applicazioni - > programmi di utilità - > Profiler del sistema e verificare…
Versione della ROM del caricamento del sistema: MB21.00A5.B07
Versione di SMC: 1.17f0
Quello dovrebbe dargli una buona idea se avete bisogno di qualunque aggiornamenti!
Sperare che questo aiuti! 
David

Trouble setting up EFI boot on Macbook Pro

I've been running Arch as a single OS on my Macbook Pro 7.1 for a few months using the bios compatibility mode. I would like to try a pure EFI boot. The reason is that I have an OCZ Vertex II SSD that the MBP fails to boot from, while booting works fine on an 4 y/o Dell Inspiron 6400. I suspect the SATA running in IDE mode on the MBP is the cause, and this wiki entry suggests that under grub2 AHCI can be forced. Also the same page states that the TRIM feature in the kernel is not available in IDE mode.
I read the wiki pages on EFI, grub2 and this how-to http://grub.enbug.org/TestingOnMacbook, but some things are not clear to me:
- Do i need a separate 'EFI System' partition? If so what folder structure should it have and on which mount point should it be mounted? Does it need to be fat32?
- Do I need a BIOS Boot Partition?
- The how to explains using the 'Apple bootloader'. But isn't that what grub2 is?
- Do I need GPT for using EFI on a MBP?
- Do I need grub2-efi or does grub2 from core/community work well enough?
Last edited by rwd (2010-11-25 08:10:23)

Thanks for the tips skodabenz. I am getting some progress, in the sense that the Grub menu shows up. But selecting any item results in black screen with a prompt in the top-left. These are the things that I've been trying, each time swapping harddisk with the SSD:
- following the tips on http://grub.enbug.org/TestingOnMacbook I verified that the firmware is 64 bit using the mac OSX cd.
- Also I changed the path of the the contents of /efi/efi/grub2_efi_x86_64_bzr to /efi/EFI/BOOT/
and renamed grub.efi to BOOTX64.EFI as that is where the firmware seems to expect it
- Furthermore since efi is on a separate partition I added '/boot/' to the initrd and kernel lines (see grub.cfg. below).
One or more of these changes made that I when booting with the alt key pressed I can get into the grub menu. Just before the grub menu appears though I see an error message that is too quick to read. Something like "error 'prefix' ...". Selecting any item in the grub menu results in a prompt.
- To be sure that it wasn't a typo in grub.cfg I tried this within the chroot, and it doesn't show any errors:
cat /efi/EFI/BOOT/grub.cfg | /bin/grub2_efi_x86_64_bzr-script-check --verbose
- I then decided to compile more modules so I did:
grub2_efi_x86_64_bzr-mkimage -d /usr/lib/grub2_efi_x86_64_bzr/x86_64-efi -O x86_64-efi -p "" -o /efi/EFI/BOOT/BOOTX64.EFI minicmd part_msdos part_gpt fat ext2 hfsplus ntfs reiserfs xfs iso9660 ls search loopback linux chain reboot halt appleldr help configfile hexdump loadbios fixvideo sh
- Still no boot, so I installed the 2.6.36-ck kernel from aur.
- Then I tried the ahci force tip mentioned in https://wiki.archlinux.org/index.php/Solid_State_Drives
and added to menu items in the grub.cfg 'insmod setpci' and added to the menu items 'setpci -d 10de:0d85 90.b=40' with the pci id determined from 'lspci -nn'
A strange thing I noticed was that even though when booting from the SSD there is only one drive, when I press 'c' in the grub menu and then 'ls' I get this output, so now there is both a hd0 and hd1:
(hd0) (hd1) (hd1,gpt3) (hd1,gpt2) (hd1,gpt1) (cd0)
a 'ls (hd1,gpt2)' shows the contents of the partition that contains /boot. When I change the items in grub cfg to set 'root=(hd0,gpt2)' I get 'no such partition' error. When I change it to 'set root=(hd1,gpt2)' I get the black screen with a prompt.
A little research showed the cause for this:
[root@arch-macbookpro boot]# cat /boot/grub2_efi_x86_64_bzr/device.map
(hd0) /dev/disk/by-id/ata-Hitachi_HTS545025B9SA02_100610PBL2003SKV6ZPV
(hd1) /dev/disk/by-id/usb-OCZ-VERT_EX2_FCF0FEFFEFFCF0F33F5231144FF5FD-0:0
I guess I have to change this file and reinstall grub2. Will post the results in a next post.
This is the grub.cfg so far. None of these menu items work:
# Example Config file for GRUB2 - The GNU GRand Unified Bootloader
# /boot/grub2_efi/grub.cfg.example
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,2)
# /dev/sda3 (hd0,3)
# Load Graphical modules
set debug=video
insmod efi_gop
#insmod efi_uga
# Load Font module
insmod font
# Setup GFXTERM along with loading unifont.pf2 font file
if loadfont ${prefix}/unifont.pf2
then
insmod gfxterm
set gfxmode="auto"
set gfxpayload=keep
terminal_output gfxterm
set color_normal=light-blue/black
set color_highlight=light-cyan/blue
insmod png
insmod jpeg
# background_image ${prefix}/archlinux.png
fi
insmod part_gpt
insmod part_msdos
insmod fat
insmod ext2
insmod setpci
# Timeout for menu
set timeout=3
# Set default boot entry as Entry 0
set default=0
menuentry "Arch Linux - with bios dump" {
#search --set -f /boot/vmlinuz26
#setpci -d 10de:0d85 90.b=40
set root=(hd1,gpt2)
loadbios /boot/vbios.bin /boot/int10.bin
linux /boot/vmlinuz26-ck root=/dev/sda2 rootfstype=ext4 video=efifb agp=off
initrd /boot/kernel26-ck.img
menuentry "Arch Linux - Linux (with bios dump and fix video)" {
#search --set -f /boot/vmlinuz26
#setpci -d 10de:0d85 90.b=40
set root=(hd1,gpt2)
fix_video
loadbios /boot/vbios.bin /boot/int10.bin
linux /boot/vmlinuz26-ck root=/dev/sda2 rootfstype=ext4 video=efifb agp=off
initrd /boot/kernel26-ck.img
menuentry "Arch Linux" {
#search --set -f /boot/vmlinuz26
#setpci -d 10de:0d85 90.b=40
set root=(hd1,gpt2)
fakebios
linux /boot/vmlinuz26-ck root=/dev/sda2 rootfstype=ext4 video=efifb agp=off
initrd /boot/kernel26-ck.img
menuentry "Arch Linux test" {
#setpci -d 10de:0d85 90.b=40
set root=(hd1,gpt2)
linux /boot/vmlinuz26-ck root=/dev/sda2 rootfstype=ext4 video=efifb agp=off
initrd /boot/kernel26-ck.img
menuentry "Arch Linux test2" {
#setpci -d 10de:0d85 90.b=40
set root=(hd1,2)
linux /boot/vmlinuz26-ck root=/dev/sda2 rootfstype=ext4 video=efifb
initrd /boot/kernel26-ck.img
menuentry "Arch Linux test uuid" {
#setpci -d 10de:0d85 90.b=40
search --no-floppy --fs-uuid d76f36b4-109a-48cd-81de-941f169b2213 --set root
linux /boot/vmlinuz26-ck root=/dev/disk/by-uuid/d76f36b4-109a-48cd-81de-941f169b2213 ro rootfstype=ext4 video=efifb
initrd /boot/kernel26-ck.img
Last edited by rwd (2010-11-27 20:35:01)

[SOLVED] Two Grub boot menus on Macbook pro 7.1 efi boot

Hello
This is my first Arch post and I feel a bit of a fool for making the error I'm going to describe but here we go....
A couple of weeks ago I installed Arch as dual boot on my Macbook pro 7.1 and I'm generally quite happy with the result. I boot as EFI using Grub2 having followed instructions to make a standalone boot.efi and boot from the mac's bootloader. The boot.efi file is placed on a small macosx journaled partition that has been made bootable with "bless". I've been able to boot between the two systems using 'alt' at startup or, more generally, just leave the pc to boot into Arch.
When I generated the boot.cfg file I didn't specify ro or rw but grub added ro. So I've had the "root mounted as ro" warning since upgrading to 3.10.3-1 (I don't subscribe to the testing repository) although it was obviously an issue from the start and I was aware of it. After reading some of the forum posts today I thought I'd have a go at changing the boot parameters at startup and edit the boot menu to include rw. This worked and I didn't get the read only warning. I decided to try to generate a new grub.fcg and specify rw before generating a new boot.efi. On inspecting the new boot.cfg I noticed it had both ro and rw entries. I decided to think about what to do (thinking of removing the ro) before making the standalone file.
Anyway, I had to boot into osx for something else but when doing so noticed that I now have 3 efi boot options in the mac bootmanager. Two are grub and one boots osx. I've had a look in the forums and on the internet in general but can't find out how to remove the second entry. My guess is I've installed grub on my Arch /boot partition but can't figure out how to remove it.
Although I can boot into Arch as normal as the pc defaults to the original grub menu, I'd like to remove the additional entry if possible and would be grateful for any help.
Dylan
Last edited by youngdm (2013-08-06 21:00:37)

These are the instructions I followed
grub-mkconfig -o boot/grub/grub.cfg grub-mkstandalone -o boot.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg
Then in osx:
sudo bless --device /dev/disk0s4 --setBoot
I think that on initial installation I ran the command above as one and then last night ran it as two. Like this:
grub-mkconfig -o boot/grub/grub.cfg
grub-mkstandalone -o boot.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg
The instructions were from:
http://codylittlewood.com/arch-linux-on … tallation/
From the apple discussion forums..
This one is a bit more tricky, surely there is another way but this one is simple and not so risky
1- burn a GParted Live CD iso
2- boot on the GParted live CD (press alt on boot and wait for the CD boot option to appear) and choose the first boot entry
3- during the boot process accept every option with its default value
4- in GParted select the EFI partition and somewhere in the menus select the "flags" entry and uncheck "boot"
5- exit GParted Live CD and boot in Mac OS
6- a new volume has appeared "/volumes/efi"
in the finder go to "/volumes/efi/EFI" and delete the "ubuntu" folder
7- repeat steps 2/3 and step 4 but check "boot" instead of unchecking it
8- exit GParted live CD and reboot
I have found the instructions above on the apple discussion forums but as noted above I'm a little wary about following them. I guess though that I need to remove the entry in the mac EFI partition which is hidden in osx but shows as sda1 in Arch.
Do you think I could mount sda1 in Arch and have a look at what's on there? From the instructions above it looks like there should be a directory for Arch that could be deleted. I presume that Arch is booting from the blessed partition on sda4. Is this correct?
Last edited by youngdm (2013-08-06 11:46:09)

Upgrade kernel26-firmware to linux-firmware report with some problem

Just now I upgrade my system from kernel26-firmware to linux-firmware, in X (Awesome WM).
After press Y and pacman start downloading, I'm afk for a while (take a bath), when I'm come back
My system freeze and proses show that system still make mkinitcpio for fallback.
I hard reset, and boot. Boot failed in 10 seconds message because it can't detect my filesystem.
Follow suggestion that I need add some parameters I can boot.
Then I check with pacman -Syu, and you can guess there's still db.lck. Then I remove it, and invoke pacman -Syu again, pacman failed because there's already file from linux-firmware on disk.
I try to downgrade, but failed with the same reason. Then I remove all folder and file that conflict, and install kernel26-firmware then upgrade to linux-firmware, now I have linux-firmware on my system.
Learn a lot from that problem, any thought guys ?! Maybe some of you have a better way to solve something like that ?!
regards,
igndenok
Edit:
After I read pacman man, there's a force option (-f). Can I used that just in case (maybe) I have the same problem again ?
Last edited by igndenok (2010-06-21 15:11:27)

All I can say is that when the linux-firmware package got into [testing], I switched without problems on my laptop. I 'migrated' to the linux-firmware package on my server a few hours ago and it went smoothly too. I don't really think your problem has anything to do with the firmware package, since that doesn't trigger an initcpio rebuild, nor are there any file conflicts between both firmware packages.

Macbook Pro 6,2 EFI Boot rEFind

I have been using Linux for a while, but I am not very familiar with the booting process of Linux.
First, I have managed to get Arch booting using grub2-efi, however I would like to use the Linux Kernel EFISTUB.
I have placed the initramfs-linux.img and vmlinuz-linux.efi in the /EFI/Arch/ (which happens to be mounted on /boot) and a linux.conf in the same place containing
initrd=\EFI\Arch\initramfs-linux.img root=/dev/sda5 ro quiet
When I try to boot Arch using rEFInd (not rEFInd to Grub2 to Arch) I see that rEFInd attempts to use the settings found in the linux.conf then I get the following:
[ 0.592308] i8042: No controller found
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents....
[ 0.673673] uhci_hcd 0000:00:1a.0: Found HC with no IRQ. Check PIOS/PCI 0000:00:1a.0 setup!
[ 0.673739] uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -19
[ 0.673793] uhci_hcd 0000:00:1d.0: Found HC with no IRQ. Check PIOS/PCI 0000:00:1a.0 setup!
[ 0.673849] uhci_hcd 0000:00:1d.0: init 0000:00:1a.0 fail, -19
ERROR: device '' not found. Skipping fsck.
ERROR: Unable to find root device ''.
You are being dropped to a recovery shell
Type /exit/ to try and continue booting
sh: can't access tty; job control turned off
I am not sure what most of it means, however my research tells me that the uhci_hcd is some device that the kernel cannot use correctly and the two that start with ERROR: are related to the EFI booting. Since I specified the device in the linux.conf should it be looking there and not in ''?
Can someone guide me along the correct path?
Comment reguarding the "uhci_hcd" and "No controller found" messages are welcome as well.
Last edited by raisdead (2012-09-15 19:32:29)

Hello raisdead.
I'm using an iMac (mid 2010, with i3 processor and AMD 4670 graphics).
I also have been trying to get EFISTUB boot to work and I've got it running now. I prefer it to grub.
Your log reports are OK (like mine) until the ERROR comes up.
I think you may not have got the correct UUID for your disk in the refind_linux.conf file.
If you can boot with another linux, maybe a live install disk, and run
sudo blkid /dev/sda7 (or whatever the number is for your arch disk partition)
you will get the UUID to put in your refind_linux.conf file.
In the refind_linux.conf file, the menu line I use to boot with is
"Boot default" "root=UUID=e5ead341-2bea-4933-969c-09ba528e9729 ro nosplash nomodeset init=/bin/systemd"
You might use the same but with your own UUID value, and maybe no init= value, if you are not using systemd yet (despite initial problems I recommend it).
The nomodeset is to avoid a black screen problem with the radeon video module.
My boot files are under EFI/arch353/ on the first partition on my mac. The files there are
refind_linux.conf
vmlinuz-linux
initramfs-linux.img
initramfs-linux-fallback.img
To keep this up to date when the kernel changes I mount the EFI partition (do this before the new kernel is installed, otherwise you might lose the ability to mount)
mount /dev/sda1 /mnt/uefi
make a new folder arch354 (say)
and copy over the new vmlinuz, initramfs files, together with a copy of the original refind_linux.conf
When one version isn't needed just delete its folder.
refind seems to find anything that might be bootable.
Good luck.

Mac partition now called efi boot?

I upgraded my HD and restored my data using a cloned image file. I am also running a second partiton with windows 7 installed. before i upgraded, when i hit 'option' to choose my boot volume, i believe my choices were "macintosh hd" and "windows(or something similar)". now my "macintosh hd" is called "efi boot" and it does not boot into mac by default but rather windows. how do i rename that partition/fix this problem?
thanks in advance
tom

Hi,
I have this same issue. I tried to change the partitions to say the names I want, and when I Option Boot, it still shows the incorrect name, ignoring my changes.
ideas?
Thanks.

Sleekbook 6 efi boot

Hardware: HP ENVY Sleekbook 6 (6-1110us)
Firmware Ver: F.12
O/S: Ubuntu 12.10
I am encountering problems attempting to change the (U)EFI Boot Options on my Sleekbook. I can view the boot parameters, but changes do not appear to get saved in NVRAM. I believe this might be caused by one of the current boot options being broken.
The Boot Order shows the following: 2001,3004,3002,3003,3005,2002
However, in the list of Boot Options, 2002 (or Boot2002) does not exist. All of the boot options I have created are in the 000x range, so I assume the 300x and 200x boot options are either from the factory or auto-generated by the firmware. I cannot recreate Boot2002, nor can I remove it from the Boot Order. I have tried this both from Ubuntu (via efibootmgr) and via an EFI Shell. When running the command "bcfg boot dump -v" in the EFI Shell, it shows the first 5 boot options, then gives an error "variable Boot2002 not found".
I have also reset the firmware to defaults via the setup utility. No change.
Is there a way to restore the Boot2002 boot option?
Alternatively, reseting all the boot options to defaults would also work for me. If I have to recreate the boot options for Ubuntu, that is not a problem.
Booting Ubuntu and running the EFI Shell both work fine.
A little history (if it helps) ...
It originally came with Windows 8, which I replaced with Ubuntu 12.10, completely restructuring the disk in the process. (I do have a full image of the factory-installed disk.) I tried out a few different installs before settling on what I wanted. Now I have extraneous boot options I would like to get rid of, both to clean things up and to reduce confusion.
To say thanks, click the "Kudos" button!

Good Morning @CCStefanini ,
Welcome to the HP Forums!
It is a terrific place to find answers and ideas!
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I grasp that you tried to do the recovery from the recovery disks HP sent but received this error " P2PP BurnBoot Check Failed" .
You have tried changing the date in the bios but there was no change.
Here is a link to Troubleshooting HP System Recovery Problems (Windows 7) that will guide you through some steps.
Here is a link to a search I did in the forum for your error that were resolved. You may wish to peruse these as they may have a suggestion that may help. P2PP BurnBoot Check Failed forum search
As HP did just send you the recovery kit, you may also contact them for assistance.
Please call our technical support at 800 474 6836. If you live outside the US/Canada Region, please click the link below to get a support number for your region.
World Wide Phone Support
Good Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

MacbookPro EFI Boot password issues

I have Windows installed via bootcamp on the same hard drive as my Mac partition. I do have the EFI boot password set up, which has never been an issue before. I normally just hit option, type in my password and boot whatever I need to boot.
I recently installed an update to Windows 7 SP 1 (64 bit) as well as a few other Windows security updates. After that Windows update, for some reason, my 'b' key will not work at the EFI boot password screen. The 'b' key is part of my EFI boot password. When I boot in to Mac regurarly, my keyboard works just fine, 'b' key included. It is just at the boot password screen and only my 'b' key that will not work.
I have used the nvram utility (in my booted mac) to reset the nvram, I have reset the SMC. Nothing has worked to get my 'b' key back at the boot password screen. As you know, I cant use any of the boot keys to help fix this problem either.
Any ideas on what is causing this?

Bump because this is a weird problem. Did SP1 screw up my firmware somehow?

Macbook freezes when choosing efi boot in Mavericks?

Hi. I'm not sure how many have already upgraded to Mavericks, but I'm experiencing the following:
I was trying to install Windows 7 with BootCamp but got errors about "not being able to boot from this disk" even though I did everything the way I should.
I started looking around and found a huge community that was trying to get Windows 7 installed in EFI mode (without bootcamp bios emulation) on older macs (and more succesfully on newer macs).
Now the thing is that all these people say that they can boot fine from normal "windows" installation and boot just fine from "efi boot" installation, but that they got errors during install.
My problem: Is that as soon as I choose EFI boot on my windows 7 DVD or windows 7 USB installer, my macbookpro9,2 will freeze. First the screen will hang a short while (the press-alt-during-boot-screen) then this screen will get grainy, and then the top few centimeters will go black with colored bars in them.
After this happens I can do nothing else than force the macbook to power down.
The windows installer boots fine from the normal "windows" boot mode but then I get these "windows may not be able to boot from this disk" errors.
So I have two questions:
1. Does anyone have experience with the "Windows can't be installed on this disk, Windows may not be able to boot properly from it" errors?
2. Does anyone have experience with installing Windows 7 when choosing EFI boot in the boot manager?
I would appreciate it if some of you that have a window 7 USB or DVD installer, please insert it into your mac, press alt during boot, choose EFI, and check if it freezes, boots windows install, or boots OSX.
Kind regards,
Jasper de Werk

Hello raisdead.
I'm using an iMac (mid 2010, with i3 processor and AMD 4670 graphics).
I also have been trying to get EFISTUB boot to work and I've got it running now. I prefer it to grub.
Your log reports are OK (like mine) until the ERROR comes up.
I think you may not have got the correct UUID for your disk in the refind_linux.conf file.
If you can boot with another linux, maybe a live install disk, and run
sudo blkid /dev/sda7 (or whatever the number is for your arch disk partition)
you will get the UUID to put in your refind_linux.conf file.
In the refind_linux.conf file, the menu line I use to boot with is
"Boot default" "root=UUID=e5ead341-2bea-4933-969c-09ba528e9729 ro nosplash nomodeset init=/bin/systemd"
You might use the same but with your own UUID value, and maybe no init= value, if you are not using systemd yet (despite initial problems I recommend it).
The nomodeset is to avoid a black screen problem with the radeon video module.
My boot files are under EFI/arch353/ on the first partition on my mac. The files there are
refind_linux.conf
vmlinuz-linux
initramfs-linux.img
initramfs-linux-fallback.img
To keep this up to date when the kernel changes I mount the EFI partition (do this before the new kernel is installed, otherwise you might lose the ability to mount)
mount /dev/sda1 /mnt/uefi
make a new folder arch354 (say)
and copy over the new vmlinuz, initramfs files, together with a copy of the original refind_linux.conf
When one version isn't needed just delete its folder.
refind seems to find anything that might be bootable.
Good luck.

What is the EFI boot option for mac, and why is my Mac having problems with it?

I just updated my 2012 Macbook Pro to 10.9, and I am having some problems with it. I have a bootcamp partition on it and regularly awitch between mac and windows, and 2when I went to switch nack to my Mac side, It said EFI boot nstead of the regular Macintosh HD. When I choose that option, the aple logo comes up and progress bar appears. Once the progress bar finishes, the computer shuts off and doesnt do anything. When I turn it on again, it just starts the efi boot again and shuts off when it finishes. Why is this happening and what can I do to fix this. All help is extremely appreciated.

That usually happen because the OS X partition got corrupted. Abiotu the only fix for that is to reinstall OS X and to do that you might have to completely erase the drive or repartition it as one partition. Which will wipe out the Windows side. So backup everthing you can before you start.
nisuteng wrote:
Hi, did you fix the problem?
I have the same problem... and my warranty has expired...
please help~~
thanks!!

How can i remove a hybrid mbr from my system drive so that Efi booted windows will install.

Hi,
i have just clean installed OSX lion on a freshly wiped drive in my macbook pro, using a bootable lion installer usb i used disk utility to partition my drive into a mac and a windows partition under the GPT/GUID partition scheme, i then proceeded to install lion onto the mac partition, and completed the set up, All Good...
so i plug in my Windows 8 EFI Boot USB stick (Notice, EFI boot here, NOT BIOS EMULATION BOOT), shutdown and power on the mac and proceed to the boot picker by holding option, So far so good, the usb key is recognised and the system boots into the Windows Setup in EFI mode, Enter product key, accept terms and so on, Now i select my Windows partition and windows Says That it cant install to Partition 4 (EFI Partiton, OSX Lion, Lion recovery, Windows), It says that it can only install to a GPT / GUID based disk as expected...
Why is there a protective MBR on my drive when i didnt add one, and i have not even touched bootcamp assistant...
How can i remove this Protective MBR from my drive so that my disk is PURE GPT so windows can install?
hours of googling has turned up nothing...
System:
Macbook Pro 13 inch Mid 2009
Mac os: OSX Lion
Version of windows trying to install: Windows 8 Release Preview 64 bit in EFI Mode

Alexander, I would like to apologize for the TERRIBLE answers you have been given so far. I too had this question, and so here is what my thoughts are, as maybe they might provide insight in leading you towards the answer.
I am a *nix user in general, and thus own a mac and a thinkpad. In fact I just got my thinkpad not too long ago. As such, I transfered my faster hard drive to my faster computer, which made logcal sense to me. Ergo, I moved my Mac drive to my lenovo. On this drive I have a hybrid mbr which is no longer needed. So my thoughts are this:
From what I gather, the UEFI standard indicates that there is to be a protective MBR on all GPT systems. This is so that when you use programs that are not GPT aware, they will see a presumably "full" drive and not think that they have the right to destroy your existing data in what it thinks is free space. For instance, fdisk or other MBR only partitioning systems. Thus, if your system has only a MBR with a single EE partition, it would be my guess that it was in fact not put there by installing Windows, but rather for the protection of your system.
If you are in my situation, where you do indeed have a hybrid MBR with written out partitions, it would be my guess that the only way to rid yourself of it is to do it manually. The way I would recommend, is using gdisk (gpt fdisk). It is command line only, but the syntax is pretty easy:
$ sudo gdisk /dev/disk0
Assuming you are using your mac partition and your primary hdd is disk0. That will put you into an interactive session of gdisk. Enter "?" for command options. What you need is the "recovery and transformation" section which is the "r" I think. From there I would say you probably want to create a new hybrid mbr (you will be using this to delete it). When it asks you for the partitions you would like to include, just hit enter. It should then ask you if you would like to create a protective entry for the remainder of the empty space. This is what you want so tell it to do that. After you are done, "w" will write and exit. You may want to first use the "p" to print and ensure that you have what you want. You can proabably check your work by using fdisk as so:
$ sudo fdisk -l /dev/disk0
I hope this helps you, and if you find that there is a better way, I hope you might enlighten this thread.
Cheers!
PS The command examples, the $ is to indicate it is a bash/shell command as a non-root user, do not include it in the command.

Linux Wont Boot Up- Blue Screen Of Death.

I have been trying to boot up linux on my pc with a bottable usb and also from a hard disk it does not matter what linux i try to install whether its Puppy Linux or ubuntu When i boot up in any mode, the screen goes dim for 1 secound then black like the laptop is turned off???
I didnt pay for a locked up frozen hunk of junk! I want it to support other operating systems (OS)
Ive done some google research and what i can find is toshiba basically doesent support linux but could the black screen be releated to something else,others have successfully booted linux with toshiba I got the laptop a few months ago.
And when i tried to boot into windows after trying to get linux to boot after a few hours doing this, I get a blue screen of death for a split secound then the pc turned of, I have now formated the partion to reinstall windows
again, But it seems like the disk has crashed Getting a error message saying "Error TRY: Null or Invaild" Might try to reinstall windows and see what happends (theres not ticking sound and the disk sounds like its processing normally)
Whats the probablem??
Thanks,
Spudster
Laptop Model: L750D Laptop Satelite Series.
PS: Everything was going perfectly fine before i tried ran my bootable linux..
But linux is a handy little system and i do need it as toshiba shouldnt be so locked up hoping to solve these issues anyhow.

Going to bump!

Only "EFI boot" appears for my external drive

I bought a 4TB Seagate USB 3 drive, designed for Macs.
I changed the partitioning so it is as follows:
1st (with the Seagate files) 2.5TB
2nd 500GB called "Backup"
3rd 1.5TB called "Data"
I used Carbon Copy cloner to backup my internal drive to the 500GB partition--CCC said the drive would be bootable. When I open Preferences/Startup Disk the "Backup" parition shows up as an option.
But when I Option boot my mac, I only see these choices:
Macintosh HD
OS X 10.9 Recovery
and then indicating a USB drive:
"EFI Boot"
My "Backup" partition is not listed.
When I tried clicking "EFI Boot" my Mac just freezes.
Is my "Backup" partition too far into the drive (starting at 2.5TB) to actually be listed properly in startup?
Thanks!

Followup: I made a bootable copy into the 1st partition, and that one showed up first with its full name, followed by "EFI Boot". I discovered on trying to boot from #1 that it seems as if the Mac has frozen but it takes quite awhile to actually boot, but it did. So then I tried booting from the second one, and that eventually worked. So I guess the only issue is the weird name.

T540p firmware ignores Linux EFI boot

Similar Messages

Maybe you are looking for