Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Commit 53e40265 compiled, replaced x3, successful boot into createinstallmedia, and Install OSX --> "…already installed…."
 

Attachments

  • image.jpeg
    image.jpeg
    1 MB · Views: 238
Commit 53e40265 compiled in VSE2015 on Win10; tested, and verified
 

Attachments

  • boot_commit-53e40265.zip
    204.4 KB · Views: 422
And the properties? Are they ok now?

I use the original 2006 MacPro ordered November, 2006, and updated with two x5365's and SMC'd to a 2,1

[brief subset of ioreg output]:

|
+-o MacOro2,1 <class IOPlatformExpertDevice, id 0x100000112, registered, matched, active, busy 0 (79353 ms), retain 29>
| {
| "compatible" = <"Mac-F4208DC8">
| version = 1.0
| board-id = Mac-F4208DC8
| system type = 03
| product-name = MacPro2,1
| model = MacPro2,1

edit: looks o.k., to me
 
Ok . Thanks guys. Now we know that the data is correct and not corrupted. Great.

Made a small change in the source code. Now also shows the address of the table. Need to know the memory layout so please report the value in the changed line:

"factoryEPS[the address that I am looking for]->"

What do you get?
 
Last edited:
I use the original 2006 MacPro ordered November, 2006, and updated with two x5365's and SMC'd to a 2,1

[brief subset of ioreg output]:

|
+-o MacOro2,1 <class IOPlatformExpertDevice, id 0x100000112, registered, matched, active, busy 0 (79353 ms), retain 29>
| {
| "compatible" = <"Mac-F4208DC8">
| version = 1.0
| board-id = Mac-F4208DC8
| system type = 03
| product-name = MacPro2,1
| model = MacPro2,1

edit: looks o.k., to me
I understand that your Mac Pro was converted from a 1,1 to a later model (2,1) but what was required to make this change?

Edit: I think to have located it. Apple used to provide a firmware update for it, but pulled it some time later.
 
Ok . Thanks guys. Now we know that the data is correct and not corrupted. Great.

Made a small change in the source code. Now also shows the address of the table. Need to know the memory layout so please report the value in the changed line:

"factoryEPS[the address that I am looking for]->"

What do you get?

Looks like '[p]'->
 

Attachments

  • image.jpeg
    image.jpeg
    1.2 MB · Views: 211
Commit 0a75b301; tested, and verified.
 

Attachments

  • boot_commit-0a75b301.zip
    204.4 KB · Views: 403
Last edited:
Commit 0a75b301; tested, and verified.

Commit 0a75b..

appears to be: factoryEPS[0x7cfc167c7faa2000]

sorry for the barely legible photo. It's a screen capture from a video! :)

EDIT: Also, ioreg output seems to be correct again:
Code:
bash-3.2# ioreg -p IODeviceTree -d 2 -k board-id
+-o Root  <class IORegistryEntry, id 0x100000100, retain 13>
  +-o /  <class IOPlatformExpertDevice, id 0x100000111, registered, matched, ac$
      {
        "compatible" = <"MacPro2,1">
        "version" = <"1.0">
        "board-id" = <"Mac-F4208DC8">
        "IOInterruptSpecifiers" = (<0900000005000000>)
        "IOPolledInterface" = "SMCPolledInterface is not serializable"
        "serial-number" = <55513200000000000000000000473837XXXXXXXXXXXXXXXXX>
        "IOInterruptControllers" = ("io-apic-0")
        "IOPlatformUUID" = "2B12FE1B-1090-593B-B740-XXXXXXXXXXXX"
        "clock-frequency" = <00b5644f>
        "manufacturer" = <"Apple Computer, Inc.">
        "IOConsoleSecurityInterest" = "IOCommand is not serializable"
        "IOPlatformSerialNumber" = "G87XXXXXXXXX"
        "system-type" = <03>
        "product-name" = <"MacPro2,1">
        "model" = <"MacPro2,1">
        "name" = <"/">
        "IOBusyInterest" = "IOCommand is not serializable"
      }
 

Attachments

  • FullSizeRender.jpg
    FullSizeRender.jpg
    29.6 KB · Views: 182
Last edited:
Another test

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!
 

Attachments

  • boot cfdeb3e757091e9102ad109e43bdbd075f0bf283.zip
    205.5 KB · Views: 371
attached output from commit cfdeb3e7...

neither of the previous ioreg commands produce any output.

# ioreg -p IODeviceTree -r -n / -d 1 -->

+-o /IOPlatformExpertDevice, id 0x100000112

"compatible" = "Apple002,1"
"model" = "Apple002,1"
 
attached output from commit cfdeb3e7...

neither of the previous ioreg commands produce any output.

# ioreg -p IODeviceTree -r -n / -d 1 -->

+-o /IOPlatformExpertDevice, id 0x100000112

"compatible" = "Apple002,1"
"model" = "Apple002,1"
Thanks. Can you make this change:
memcpy(startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);
memcpy((CHAR8 *)startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);

Note: memcpy is using VOID * by default. We're using a CHAR * instead.
 
@pike & @splifingate

Since splifingate is perfectly capable of compiling the source code, I won't be compiling the particular builds with instructions that appear posted here for him to test, unless you want me to. If so, let me know.
 
Thanks. Can you make this change:
memcpy(startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);
memcpy((CHAR8 *)startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);

Note: memcpy is using VOID * by default. We're using a CHAR * instead.

PlatformExpert.cpp

288: memcpy(startOfStringTable, (UINT8 *)"Mac-F42C88C8", 12);

found . . .

replace 288 with

288: memcpy((CHAR8 *)startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);

or,

288: memcpy(startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);
289: memcpy((CHAR8 *)startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);

?
 
@pike & @splifingate

Since splifingate is perfectly capable of compiling the source code, I won't be compiling the particular builds with instructions that appear posted here for him to test, unless you want me to. If so, let me know.

Multiples are good for verification . . . I'll try for as long as I'm able (other requisites will impede, later) -smile-
 
PlatformExpert.cpp

288: memcpy(startOfStringTable, (UINT8 *)"Mac-F42C88C8", 12);

found . . .

replace 288 with

288: memcpy((CHAR8 *)startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);

or,

288: memcpy(startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);
289: memcpy((CHAR8 *)startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);

?
Please replace 288 with the new line.
 
PlatformExpert.cpp:

288: // memcpy(startOfStringTable, (UINT8 *)"Mac-F42C88C8", 12);
289: memcpy((CHAR8 *)startOfStringTable, (CHAR8 *)"Mac-F42C88C8", 12);
 

Attachments

  • image.jpeg
    image.jpeg
    1.1 MB · Views: 194
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.