macOS boot.efi developer's thread

[PeterHolbrook]

Commit 7d3a9917ede0e89f0d49c16205deb89edb127e66.

Same warnings/error as before. Apparently, the compiler doesn't like subtracting a UINT8 from the constant 256.

Edit: The following would allow compilation:

newEPS->DMI.Checksum = (UINT8) (256 - (int) Checksum8(&newEPS->DMI, sizeof(newEPS->DMI)));

newEPS->Checksum = (UINT8) (256 - (int) Checksum8(newEPS, sizeof(* newEPS)));

Shall I post such a compilation?

 

[Pike R. Alpha]

Commit 7d3a9917ede0e89f0d49c16205deb89edb127e66.

Same warnings/error as before. Apparently, the compiler doesn't like subtracting a UINT8 from the constant 256.

Yeah MS compilers are weird.

Edit: New commit with new output. Let's see what this brings.

 

[PeterHolbrook]

Next SMBIOS test. Black boot.efi

To everyone interested in this project:

[P]eople must be aware that [this and other] interim future versions are NOT intended as a replacement for the official repository versions. Until further notice, those of you who want to use Pike's boot.efi ought to go to http://piker-alpha.github.io/macosxbootloader/ and download either the "black" version or the "grey" one, according to your particular preference (the change is purely cosmetic; otherwise, they are exactly the same; the choice is irrelevant as far as the operating system is concerned). Pike alone will decide when such repository versions will be updated with a newer version.

Please, notice that the [enclosed and other] upcoming experimental versions might contain bugs that could cripple your ability to boot your old Mac. So, unless you are absolutely certain of what you are doing and know how to reverse such undesirable situations, KEEP AWAY FROM THEM. In general terms, [these] versions ARE NOT FOR YOU!

 

[randyoo]

I want very badly to help, but still can't seem to get anywhere with creating a USB installer. Using the "createinstallmedia" method, I get a stick that works on a supported Mac. But after replacing the three boot.efi files, the stick just doesn't work on my Mac Pro 1,1. (gray screen, not even Apple logo, after selecting the USB stick after holding option at power on)

I'm not really looking for help, just venting. I'll keep trying.

GOT IT: On my 3rd brand of USB stick. Apparently it's very picky about brands?

Anyway, using the createinstallmedia method, and replacing the 3 boot.efi files, I can boot into the installer GUI, and I'm now attempting an install.

Update: no dice, says it's already installed on this Mac, even though there was only 1 formatted disk attached. I did notice a flash of diagnostic messages saying the SMBIOS table was found, and also replaced.

 

[PeterHolbrook]

@randyoo:

Up to now, merely replacing two or three boot.efi instances on the install media would take you nowhere on an old Mac Pro, because you ALSO had to incluye the old Mac Pro board id in three places. The latest builds are trying to bypass that limitation by causing the Mac Pro to masquerade as a Mac Pro 3,1. Is the latest build working for you?

 

[randyoo]

@randyoo:

Up to now, merely replacing two or three boot.efi instances on the install media would take you nowhere on an old Mac Pro, because you ALSO had to incluye the old Mac Pro board id in three places. The latest builds are trying to bypass that limitation by causing the Mac Pro to masquerade as a Mac Pro 3,1. Is the latest build working for you?

I saw the diagnostic messages indicating the SMBIOS table was found and replaced, but couldn't proceed with the install because it says El Capitan is already installed on this Mac. Trying with a different disk now...

 

[atvusr]

Tested 4d07b164050a1d5a757bf39c082c1fb4362db567 on MBP2,2:
patched Installer (Hennesie-Guide) - hangs still after "Waiting for DSMOS"
transferred OSX - boots into Desktop, but still Kernel Panic after 30 seconds.

 

[randyoo]

Okay, even with a different disk I encounter the same error: OS X El Capitan is already installed on this Mac.

A quick search for the error "is already installed on this Mac" gives the first result from insanely mac, where someone says they need to copy an "smbios.plist" file.

...so this error seems to have something to do with the SMBIOS.

 

[atvusr]

Okay, even with a different disk I encounter the same error: OS X El Capitan is already installed on this Mac.

Add the Board-ID to the OSInstall.mpkg in '/Volumes/Install OS X El Capitan/Install OS X El Capitan.app/Contents/SharedSupport/' (see also Post #54).

Editing of the OSInstall.mpkg:

- make a copy of the /System/Installation/Packages/OSInstall.mpkg into a temporary folder for editing

- extract the OSInstall.mpkg via Terminal: xar -x -f OSInstall.mpkg

- get your Board-ID via Terminal: ioreg -lp IOService | grep board-id

- add the Board-ID to the 'Distribution' file in the line 'var platformSupportValues=[" ... "];' with a simple Plain-Text-Editor in the same manner as the already existing ID's

- delete the old OSInstall.mpkg in the temporary folder

- pack the files in the temporary folder into a new OSInstall.mpkg via Terminal: xar -c -f OSInstall.mpkg *

- replace the original OSInstall.mpkg in the Installer with the edited one.

 

[randyoo]

Add the Board-ID to the OSInstall.mpkg in '/Volumes/Install OS X El Capitan/Install OS X El Capitan.app/Contents/SharedSupport/' (see also Post #54).

Thanks, but I'm pretty sure we're supposed to not have to do that. (see post #155)

Pike, I searched "smbios.plist", and came up with a page where they indicate that you can't change just one of the SMBIOS values (eg boardID), they all have to match! So if we're pretending to be a MacPro3,1, then probably not only the SMboardproduct, but also the SMproductname (and maybe others?) need to be modified as well...

 

[Pike R. Alpha]

Thanks, but I'm pretty sure we're supposed to not have to do that. (see post #155)

Pike, I searched "smbios.plist", and came up with a page where they indicate that you can't change just one of the SMBIOS values (eg boardID), they all have to match! So if we're pretending to be a MacPro3,1, then probably not only the SMboardproduct, but also the SMproductname (and maybe others?) need to be modified as well...

Correct. We are currently working on an automated process, be it one step at a time to not break other stuff, so that you people won't have to add it anymore. And when the board-id is replaced successfully, so can anything else. Model name for example. But we first need a confirmation that it works. See post #138/#159 for how that can be done in a terminal window – you don't need to install OS X first.

 

[randyoo]

Correct. We are currently working on an automated process, be it one step at a time to not break other stuff, so that you people won't have to add it anymore. And when the board-id is replaced successfully, so can anything else. Model name for example. But we first need a confirmation that it works.

I ran ioreg per previous posts ("ioreg -lp IOService | grep board-id"), and it came back blank. Attached a screenshot of other ioreg output.

For comparison, the output of the same command on my MBP is as follows:

      "compatible" = <"MacBookPro9,1">
      "version" = <"1.0">
      "board-id" = <"Mac-4B7AC7E43945597E">
      "IOInterruptSpecifiers" = (<0900000005000000>)
      "IOPolledInterface" = "SMCPolledInterface is not serializable"
      "serial-number" = <redacted>
      "IOInterruptControllers" = ("io-apic-0")
      "IOPlatformUUID" = "<redacted>"
      "clock-frequency" = <00e1f505>
      "IOPlatformSystemSleepPolicy" = <534c505402000f00841e02000400000000140000000400000600000000000000cf25000000000000841e0200040000$
      "manufacturer" = <"Apple Inc.">
      "IOConsoleSecurityInterest" = "IOCommand is not serializable"
      "IOPlatformSerialNumber" = "<redacted>"
      "system-type" = <02>
      "product-name" = <"MacBookPro9,1">
      "model" = <"MacBookPro9,1">
      "name" = <"/">
      "IOBusyInterest" = "IOCommand is not serializable"

So shouldn't "board-id" be modified, rather than "product-name"?

 

[randyoo]

Correct. We are currently working on an automated process, be it one step at a time to not break other stuff, so that you people won't have to add it anymore. And when the board-id is replaced successfully, so can anything else. Model name for example. But we first need a confirmation that it works. See post #138/#159 for how that can be done in a terminal window – you don't need to install OS X first.

See my reply. Already tried, it comes back empty for "board-id"! Well, "grep" doesn't find it, so board-id isn't even listed. This is using the most recent commit, (4d07b164050a1d5a757bf39c082c1fb4362db567) running off an installation USB.

 

[mikeboss]

booted the installer with boot.efi 4d07b164050a1d5a757bf39c082c1fb4362db567

"ioreg -lp IOService | grep board-id" gives nothing back. nada.

 

[Pike R. Alpha]

booted the installer with boot.efi 4d07b164050a1d5a757bf39c082c1fb4362db567

"ioreg -lp IOService | grep board-id" gives nothing back. nada.

Thanks. And the debug output? Did that show the correct board-id?

 

[Pike R. Alpha]

I ran ioreg per previous posts ("ioreg -lp IOService | grep board-id"), and it came back blank. Attached a screenshot of other ioreg output...

So shouldn't "board-id" be modified, rather than "product-name"?

Thanks. And yes. That is exactly what we are doing, but I seem to have made a mistake somewhere. Will be fixed.

Edit: Peter, can you please compile the latest commit?

 

[mikeboss]

Thanks. And the debug output? Did that show the correct board-id?

 

[PeterHolbrook]

Next SMBIOS test. Black boot.efi

To everyone interested in this project:

[P]eople must be aware that [this and other] interim future versions are NOT intended as a replacement for the official repository versions. Until further notice, those of you who want to use Pike's boot.efi ought to go to http://piker-alpha.github.io/macosxbootloader/ and download either the "black" version or the "grey" one, according to your particular preference (the change is purely cosmetic; otherwise, they are exactly the same; the choice is irrelevant as far as the operating system is concerned). Pike alone will decide when such repository versions will be updated with a newer version.

Please, notice that the [enclosed and other] upcoming experimental versions might contain bugs that could cripple your ability to boot your old Mac. So, unless you are absolutely certain of what you are doing and know how to reverse such undesirable situations, KEEP AWAY FROM THEM. In general terms, [these] versions ARE NOT FOR YOU!

 

[Pike R. Alpha]

View attachment 590538

Ouch. Not the expected debug output. Definitely something wrong. Looking into it...

Edit: I am wondering if we enter the while loop so I added new debug output. That should help.

 

[splifingate]

Interesting. It failed for Mike. Did you try to download El Capitan from the App Store?

Edit: Sorry. Misinterpreted the board-id. But without the kernel cache and prelinkedkernel it boots. That is fine.

Did not have time this morning to try the download.

 

[Pike R. Alpha]

Did not have time this morning to try the download.

Can you compile and test the latest commit? I am waiting for the debug output.

Will go to bed now. Have an early appointment tomorrow.

 

[PeterHolbrook]

New debug output. Black boot.efi

Closing parentheses added to lines 232 and 244 of PlatformExpert.cpp.

To everyone interested in this project:

[P]eople must be aware that [this and other] interim future versions are NOT intended as a replacement for the official repository versions. Until further notice, those of you who want to use Pike's boot.efi ought to go to http://piker-alpha.github.io/macosxbootloader/ and download either the "black" version or the "grey" one, according to your particular preference (the change is purely cosmetic; otherwise, they are exactly the same; the choice is irrelevant as far as the operating system is concerned). Pike alone will decide when such repository versions will be updated with a newer version.

Please, notice that the [enclosed and other] upcoming experimental versions might contain bugs that could cripple your ability to boot your old Mac. So, unless you are absolutely certain of what you are doing and know how to reverse such undesirable situations, KEEP AWAY FROM THEM. In general terms, [these] versions ARE NOT FOR YOU!

 

[splifingate]

Can you compile and test the latest commit? I am waiting for the debug output.

Will go to bed now. Have an early appointment tomorrow.

compiled commit c099617 (VSE2015; modified PlatformExpert.cpp, as Peter so noted), and added teh boot.efi to the three respective places in the createinstallmedia partition (I use fixed-disks, as opposed to USB (though-I must admit--the thumb to which I installed the first createinstallmedia shows (and is bootable, if not sloooow) on Option-boot)).

grep of board-id results same as mike (nada; nothing).

I boot fully into the createinstallmedia Installer environment, but get the "El Capitan is already installed..." from the installer.app

Attached is (what I assume to be) debug output.

hth

 

[Pike R. Alpha]

compiled commit c099617 (VSE2015; modified PlatformExpert.cpp, as Peter so noted), and added teh boot.efi to the three respective places in the createinstallmedia partition (I use fixed-disks, as opposed to USB (though-I must admit--the thumb to which I installed the first createinstallmedia shows (and is bootable, if not sloooow) on Option-boot)).

grep of board-id results same as mike (nada; nothing).

I boot fully into the createinstallmedia Installer environment, but get the "El Capitan is already installed..." from the installer.app

Attached is (what I assume to be) debug output.

hth

Thanks. Yup. Never entered the while loop. Error located, but I need to run now. Back tonight.

Edit: Back home early. New commit available for compilation (board-id drama take III).

 

[PeterHolbrook]

board-id drama take III. Black boot.efi

To everyone interested in this project:

[P]eople must be aware that [this and other] interim future versions are NOT intended as a replacement for the official repository versions. Until further notice, those of you who want to use Pike's boot.efi ought to go to http://piker-alpha.github.io/macosxbootloader/ and download either the "black" version or the "grey" one, according to your particular preference (the change is purely cosmetic; otherwise, they are exactly the same; the choice is irrelevant as far as the operating system is concerned). Pike alone will decide when such repository versions will be updated with a newer version.

Please, notice that the [enclosed and other] upcoming experimental versions might contain bugs that could cripple your ability to boot your old Mac. So, unless you are absolutely certain of what you are doing and know how to reverse such undesirable situations, KEEP AWAY FROM THEM. In general terms, [these] versions ARE NOT FOR YOU!