[SOLVED] E7450 Can't boot into installer

[visio]

Hello,

 

I've been attempting to get El Capitan installed on my Latitude E7450, and am moments away from just setting it on fire and moving on with life. I have (repeatedly) followed the steps as posted in these two threads:

1. https://osxlatitude.com/index.php?/topic/8514-dell-latitude-e7450-el-capitan-clover-uefi-only/ 
2. https://osxlatitude.com/index.php?/topic/8506-dell-latitude-inspiron-el-capitan-clover-guide/

The main differences from my machine and the one in the guide linked above, are:

• Processor:  Intel® Core i5-5300U CPU @ 2.30GHz
• Memory:  1x 8GB DDR3L 1600 MHz DIMM

 

Following the guide as-is, I end up suffering with the error:

 

OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi

Using reloc block: yes, hibernate wake: no

+++++++++++++++++++++++++++++++++++++++++++++++

 

This occurs every time. I've tried different USB ports, doesn't matter. Replacing 'OsxAptioFixDrv-64.efi' with 'OsxAptioFix2Drv-64.efi' , with 10 (re)boots (multiple usb ports), I get a mix of:

• OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi
  Using reloc block: yes, hibernate wake: no
  +++++++++++++++++++++++++++++++++++++++++++++++
   
• OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi
  Using reloc block: yes, hibernate wake: no
  Error allocating 0x#### pages at 0x####... alloc type 2
  Error loading kernel cache (0x9)
  Boot failed, sleeping for 10 seconds before exiting...
   
• OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi
  Using reloc block: yes, hibernate wake: no
  Error allocating 0x#### pages at 0x####... alloc type 2
  Could not allocate runtime area
  Boot failed, sleeping for 10 seconds before exiting...

Finally, replacing 'OsxAptioFixDrv-64.efi' with 'OsxLowMemFixDrv-64.efi', I simply get:

• +++++++++++++++++++++++++++++++++++++++++++++++

 

One thing I see as soon as Clover loads is a circle/icon on the left that says 'Not detected', yet I'm not sure exactly what is not being detected.

 

In an attempt to provide as much information as possible, I've attached the cpuinfo, lspci, and dmesg output of my laptop (undocked, Fedora 23) to give an accurate reading of the hardware. 

 

Please send help...

 

Thank you.

 

 

Edit:

I'm using Clover v2.3k_r3354

I've attached my EFI folder as well. The only modification made to 'config.plist' was adding in '-v' to the boot args

Clover v2.3k_r3354

cpuinfo.txt

dmesg.txt

lspci_vv.txt

EFI.zip

[Bronxteck]

try a newer version of clover they made some corrections after rev 3348 to optiofix you can also try optiofix2

[Jake Lo]

@visio
See post #1 to 3 here. User was able to proceed after resetting the BIOS in post #3.

[visio]

Thank you for the suggestions.

 

@Bronxteck: Do you mean 'OsxAptioFix2Drv-64.efi'? If so, I've given that a go as well. I get different (better?) results as posted above, but still not able to get to the installer. I edited my post to include my Clover version as well as EFI folder.

 

@Jake Lo: Your post/guide is the only one I've come across for this machine and I tried for awhile before giving up. That post by seeker_pl that you linked to is what made me even try again, seeing that someone else got it working.

 

I'm hoping its not something simple/stupid that I'm missing. I've done successful hackintoshes in the past (D630, Optiplex 755. Thinkpad T410, T510, HP EliteBook 840 G1) but I'm just at a loss and wondering if some config in this CTO laptop is the issue.

[Jake Lo]

Try new bootpack.

[visio]

I've tried the new boot pack, but unfortunately I'm still unable to get any further. I've enabled the debug in clover to try to get a little more detail if it helps. I've tried with both versions of OsxAptioFix.

 

 

debug_FixDrv.txt

debug_Fix2Drv.txt

[Bronxteck]

have you tried booting in safemode or and or without caches. also it looks like your debug is showing 2 EFI volumes i think clover defaults to EFI on disk 0 partition 1 it also shows both optiofix's are successfully loaded

[Jake Lo]

@visio

 

This is a bit of a stretch, but after looking through your log, I noticed you have 1 stick of RAM in slot B and empty on A.

I experimented by removing one of my RAM from slot A since I have 2 sticks and encountered the same issue you mentioned. It auto reboot after loading ++++++++++++++++

 

Moving the RAM to slot A and leaving slot B empty gets me to a successful boot. So please try that and see if you have the same success.

I think a few has reported this issue somewhere but I can't recall where I've seen it.

[Bronxteck]

yeah i think thats the issue as well jake. it is a reported issue. if using one dim it has to be in slot a.

[visio]

Thank you! 

 

Moving the memory from Slot B to Slot A got me past all those errors. The '++++' still showed up, and after half a second continued on (I was in verbose mode) until it crashed with some graphics error (AppleIntelBDWGraphicsFramebuffer). Changed the DVMT again and booted into the installer.

 

I appreciate you guys looking over the logs to find this, even though it ended up so simple.