Jump to content

AMD El Capitan (@Slice)

Shaneee

By Shaneee,
in Clover

 Share
21 posts in this topic

Recommended Posts

Shaneee
Shaneee
Posted
Posted

Hello @Slice. 

 

My self and other AMD users have been unable to boot El Capitan with Clover. We get black screen with static - in the corner. As you've stated in my previous posts the boot log is clean and clover had no issues. 

 

I've investigated this and found it to be an issue with boot.efi. I'm not sure if it's how Clover loads it as Enoch works ok but I replaced the boot.efi on my test partition with the one from Yosemite 10.10.5 and was able to boot El Capitan with Clover.

 

I hope this helps to resolve the issue without replacing boot.efi as I would like to use Clover. I can provide any information you need.

  • Like 1
Link to comment
Share on other sites
iWin32
iWin32
Posted
Posted

Chameleon, which is probably the only bootloader of the oldest origin, has always simply booted OS X without boot.efi.  Keep in mind, Chameleon is based off of Boot-132 modifications, which has been around since the days of OS X 10.5 Leopard.  In these days, emulating EFI was necessary, but true EFI emulation was a mere fantasy.  boot.efi is simply the stock Apple bootloader and is a regular UEFI application.  Chameleon is unable to load that because it isn't true EFI emulation.  Rather, it uses the same boot process as the Darwin bootloader, with Chameleon itself reading com.apple.Boot.plist (injecting the info provided in org.chameleon.Boot.plist) and then loading the kernel and extensions, but with the ability to "simulate" the small amount of EFI needed directly in the kernel.  Chameleon remains unaffected by boot.efi.  In fact, some earlier installations replaced that file with the "boot" file needed for Chameleon.

 

Clover, on the other hand, is a full-fledged UEFI bootloader and can emulate UEFI on BIOS-based computers.  As such, Clover can have no problems loading boot.efi.  In fact, Clover simply creates the conditions necessary for boot.efi to take over and load the kernel and extensions.  Chances are, Apple's stock bootloader is the problem.  If replacing the boot.efi file from Yosemite enables Clover to boot El Capitan on AMD systems (I wouldn't know... Left the Hackintosh scene a while ago because I'm typing this on my real Macbook Pro now), you've essentially downgraded the bootloader.  It would be like using NTLDR (the XP bootloader) to load Windows 7 instead of it's native bootloader (BCD).  It's possible, but for most scenarios unnecessary unless you're dual booting Windows XP and Windows 7.  Windows aside, I do believe that boot.efi is the culprit from what you demonstrated.  As to why, you'll need to figure that out on your own.  However, I hope this clears up as to why Chameleon can boot El Capitan without replacing boot.efi while Clover can't.  I wish you the best of luck!

  • Like 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

I have no AMD machine to check anything. So either you propose me some source code patches or provide as much information so I can decide anything.

Dumps, logs, datasheets AND other observations.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

I mean something like this

	<key>GUI</key>
	<dict>
		<key>Custom</key>
		<dict>
			<key>Tool</key>
			<array>
				<dict>
					<key>Arguments</key>
					<string>-b</string>
					<key>Disabled</key>
					<false/>
					<key>Hidden</key>
					<false/>
					<key>Hotkey</key>
					<string>S</string>
					<key>Path</key>
					<string>\EFI\CLOVER\TOOLS\Shell64-v1.efi</string>
					<key>Title</key>
					<string>MyCustomShell</string>
					<key>Volume</key>
					<string>D68F1885-571C-4441-8DD5-F14803EFEF54</string>
				</dict>
			</array>

But with your custom boot.efi and with a path where it is placed.

Link to comment
Share on other sites
Shaneee
Shaneee
Posted
  • Author
Posted

Ok didn't know that was possible. However I think installing the file will be easier rather than getting users who may not have a lot of knowledge to find their volumes UUID.

 

Thanks for the help Slice :)

Link to comment
Share on other sites
  • 3 weeks later...
polyzargone
polyzargone
Posted
Posted

I replaced boot.efi from /System/Library/CoreServices/ by the one from Yosemite 10.10.5 and indeed it allows me to use Clover to boot El Capitan.

 

BUT, SIP is enabled when I do so even if CsrActiveConfig is set to 0x3 in config.plist.

 

I guess it's because the boot.efi from 10.10.5 doesn't know the CsrActiveConfig variable :unsure: ? So i tried with depreciated rootless=0 but it's the same…

 

AMD kernel is in S/L/K and it's named kernel BTW.

 

Have you experienced that Shaneee ?

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted

I never actually checked that. Clover was unable to detect my 2TB drive so I'm back to using Enoch. You could try 0x67 as a test.

 

Just did… It's the same again :(.

 

I also tried what Slice suggested with this Custom tool entry but Clover stops at : "Reason : N68-S" (which is the name of the Mobo I use).

 

 

 

 

<key>GUI</key>
<dict>
  <key>Custom</key>
  <dict>
   <key>Entries</key>
   <array>
    <dict>
     <key>Disabled</key>
     <false/>
     <key>FullTitle</key>
     <string>El Capitan</string>
     <key>Ignore</key>
     <false/>
     <key>Image</key>
     <string>\EFI\CLOVER\themes\yosemitelogin\icons\os_cap.icns</string>
     <key>NoCaches</key>
     <false/>
     <key>Type</key>
     <string>OSX</string>
     <key>Volume</key>
     <string>4226B7CB-FA82-42DE-85AF-1C7CB1CD17C2</string>
     <key>VolumeType</key>
     <string>Internal</string>
    </dict>
    <dict>
     <key>Disabled</key>
     <false/>
     <key>FullTitle</key>
     <string>Yosemite</string>
     <key>Ignore</key>
     <false/>
     <key>Image</key>
     <string>\EFI\CLOVER\themes\yosemitelogin\icons\os_yos.icns</string>
     <key>NoCaches</key>
     <false/>
     <key>Type</key>
     <string>OSX</string>
     <key>Volume</key>
     <string>8507C002-9C28-4395-81E9-81630653D054</string>
     <key>VolumeType</key>
     <string>Internal</string>
    </dict>
   </array>
   <key>Tool</key>
   <array>
    <dict>
     <key>Disabled</key>
     <false/>
     <key>FullTitle</key>
     <string>Yosemite boot.efi for El Cap`</string>
     <key>Hidden</key>
     <false/>
     <key>Ignore</key>
     <false/>
     <key>Path</key>
     <string>\System\Library\CoreServices\boot2.efi</string>
     <key>Volume</key>
     <string>8507C002-9C28-4395-81E9-81630653D054</string>
    </dict>
   </array>
  </dict>

 

 

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Just did… It's the same again :(.

 

I also tried what Slice suggested with this Custom tool entry but Clover stops at : "Reason : N68-S" (which is the name of the Mobo I use).

 

 

 

<key>GUI</key>
<dict>
  <key>Custom</key>
  <dict>
   <key>Entries</key>
   <array>
    <dict>
     <key>Disabled</key>
     <false/>
     <key>FullTitle</key>
     <string>El Capitan</string>
     <key>Ignore</key>
     <false/>
     <key>Image</key>
     <string>\EFI\CLOVER\themes\yosemitelogin\icons\os_cap.icns</string>
     <key>NoCaches</key>
     <false/>
     <key>Type</key>
     <string>OSX</string>
     <key>Volume</key>
     <string>4226B7CB-FA82-42DE-85AF-1C7CB1CD17C2</string>
     <key>VolumeType</key>
     <string>Internal</string>
    </dict>
    <dict>
     <key>Disabled</key>
     <false/>
     <key>FullTitle</key>
     <string>Yosemite</string>
     <key>Ignore</key>
     <false/>
     <key>Image</key>
     <string>\EFI\CLOVER\themes\yosemitelogin\icons\os_yos.icns</string>
     <key>NoCaches</key>
     <false/>
     <key>Type</key>
     <string>OSX</string>
     <key>Volume</key>
     <string>8507C002-9C28-4395-81E9-81630653D054</string>
     <key>VolumeType</key>
     <string>Internal</string>
    </dict>
   </array>
   <key>Tool</key>
   <array>
    <dict>
     <key>Disabled</key>
     <false/>
     <key>FullTitle</key>
     <string>Yosemite boot.efi for El Cap`</string>
     <key>Hidden</key>
     <false/>
     <key>Ignore</key>
     <false/>
     <key>Path</key>
     <string>\System\Library\CoreServices\boot2.efi</string>
     <key>Volume</key>
     <string>8507C002-9C28-4395-81E9-81630653D054</string>
    </dict>
   </array>
  </dict>

 

 

AFAIK  "Reason : ..." means you set wrong SMBIOS values, namely BoardId that must be real Mac boardID compatible with ElCapitan.

Attempt to install ElCapitan on MacBook1,1 will fail with the same reason.

Link to comment
Share on other sites
polyzargone
polyzargone
Posted
Posted

This is the SMBios I use in config.plist (SN, SmUUID and Serial Board Number replaced by x) :

 

 

 

 

<key>SMBIOS</key>
<dict>
  <key>BiosReleaseDate</key>
  <string>09/03/09</string>
  <key>BiosVendor</key>
  <string>Apple Inc.</string>
  <key>BiosVersion</key>
  <string>IM101.88Z.00CC.B00.0909031926</string>
  <key>Board-ID</key>
  <string>Mac-F2268CC8</string>
  <key>BoardManufacturer</key>
  <string>Apple Inc.</string>
  <key>BoardSerialNumber</key>
  <string>xxxxxxxxxxxxxxxxx</string>
  <key>BoardType</key>
  <integer>10</integer>
  <key>ChassisAssetTag</key>
  <string>iMac-Aluminum</string>
  <key>ChassisManufacturer</key>
  <string>Apple Inc.</string>
  <key>ChassisType</key>
  <string>13</string>
  <key>Family</key>
  <string>iMac</string>
  <key>Manufacturer</key>
  <string>Apple Inc.</string>
  <key>ProductName</key>
  <string>iMac10,1</string>
  <key>SerialNumber</key>
  <string>xxxxxxxxxxx</string>
  <key>SmUUID</key>
  <string>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</string>
  <key>Trust</key>
  <false/>
  <key>Version</key>
  <string>1.0</string>
</dict>

 

 

 

I'm sure iMac10,1 works with El Capitan. I use it on several Intel Hacks.

 

If I delete the Custom Tool entry, it boots fine.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...