#218 rEFIt on MBP late 2011

open
nobody
9
2012-01-12
2012-01-11
Filippo
No

Hi! I've tried to install rEFIt on my MacBook Pro late 2011 but i've had no success, i think that there is something in the MBP firmware that block the installation...

Any suggestion or prove that i'm wrong is welcome..

Sorry for my poor english ;-)

Discussion

<< < 1 2 (Page 2 of 2)
  • Pork Chop
    Pork Chop
    2012-07-02

    has anyone with had anymore luck with a solution to this?

    heres what ive got:
    MacBookPro8,3, Intel Core i7, 2.3 GHz, 4 GB
    Boot ROM Version: MBP81.0047.B27
    SMC Version (system): 1.70f5

    report from rEFIt partition inspector:

    *** Report for internal hard disk ***

    Current GPT partition table:
    # Start LBA End LBA Type
    1 40 409639 EFI System (FAT)
    2 409640 1463879591 Mac OS X HFS+
    3 1463879592 1465149127 Mac OS X Boot

    Current MBR partition table:
    # A Start LBA End LBA Type
    1 1 1465149167 ee EFI Protective

    MBR contents:
    Boot Code: None

    Partition at LBA 40:
    Boot Code: None (Non-system disk message)
    File System: FAT32
    Listed in GPT as partition 1, type EFI System (FAT)

    Partition at LBA 409640:
    Boot Code: None
    File System: HFS Extended (HFS+)
    Listed in GPT as partition 2, type Mac OS X HFS+

    Partition at LBA 1463879592:
    Boot Code: None
    File System: HFS Extended (HFS+)
    Listed in GPT as partition 3, type Mac OS X Boot

    and i get the same thing. i install, reboot comes up to Apple login screen, reboot, hangs at loading screen, force power off, power on, Apple login screen. nvr a refit screen. ANYONE have any idea what in the world is going on? i desperately want to be able to run refit on this mac. =\

     
  • jEriko
    jEriko
    2012-08-03

    misterogwannabe, have you tried the various suggestions already listed on this page? Have you tried installing rEFIt on a separate partition? rEFIt is working just fine for me.

     
  • Dr Wahl
    Dr Wahl
    2012-08-22

    I was having this same issue but fixed it by running the "Repair Disk Permissions" function in the Disk Utility tool.

     
<< < 1 2 (Page 2 of 2)