Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Change start/end of search.

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 fe7d3941072d99d119421ddee4c13f3cdc3c80bc.zip
    205.4 KB · Views: 402
I have something odd to report. Last night, shortly before going to bed, and taking advantage of the fact that my Mac Pro 1,1 server wasn't being accessed and there was no likelihood that it would be for several hours, I decided to update to OS X 10.11.1. Everything went fine. When it finished its process, I didn't let it reboot normally, but chose my Installer partition instead. From Terminal, I copied Pike's boot.efi (version 3.0) on top of the two occurrences of Apple's new boot.efi in the usual folders. Then I rebooted the machine, which went fine.

And here's what's odd: Several days ago, taking advantage of the faked board identifier, I had tried to download El Capitan. Apparently, the App Store would let me, but no actual download occurred at any time. Last night, immediately after rebooting back to El Capitan 10.11.1, I was surprised to see a red 1 on the top right of my App Store icon on my Dock. I went to check what was being offered and, sure enough, it was OS X El Capitan Version 10.11.1 (not the update, mind you). I suppose this is being offered because, on the previous uptime of the computer, I had requested to download El Capitan. This is very surprising, at least for me.

Edit: Some more light into this curious issue. Now, when it tell it to go ahead and restore, the system identifies one of my sons' Apple ID and prompts me for his password, which I don't know. As I think I had mentioned, I had originally used his "Install OS X El Capitan.app", so that's why the system won't let me redownload using an account that isn't mine!
 
Last edited:

Attachments

  • FullSizeRender.jpg
    FullSizeRender.jpg
    85.9 KB · Views: 163
Show search range.

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 2c917b328bac162f77bbdd022e0f62e14f576d5e.zip
    205.4 KB · Views: 403
Interesting. Can you do the same with slide=0 (boot argument). New commit available for compilation/testing. Let's see of we're overshooting the target address.

I'd be happy to, but won't have access to the machine for at least a couple of hours. If nobody else has done it by then, I certainly will.
 
commit 2c917b32

First screenshot from createinstallmedia; second from legacy install
 

Attachments

  • image.jpeg
    image.jpeg
    48.9 KB · Views: 147
  • image.jpeg
    image.jpeg
    50.7 KB · Views: 157
commit 2c917b32

#nvram bootargs="slide=0"

First screencap from createinstallmedia; second from legacy install
 

Attachments

  • image.jpeg
    image.jpeg
    49.3 KB · Views: 137
  • image.jpeg
    image.jpeg
    50.2 KB · Views: 147
btw…with regards to "Stricter checks for MS compiler" (commit 6646899a):

with commit 2c917b32, I get two 'Warnings' (see attached).
 

Attachments

  • image.jpeg
    image.jpeg
    4.2 MB · Views: 137
  • image.jpeg
    image.jpeg
    3.7 MB · Views: 174
commit 3747e95e

#nvram boot-args=""

First screencap from createinstallmedia; second from legacy installer
 

Attachments

  • image.jpeg
    image.jpeg
    48.2 KB · Views: 143
  • image.jpeg
    image.jpeg
    51.6 KB · Views: 147
commit 3747e95e

#nvram boot-args="slide=0"

First screencap from createinstallmedia; second from legacy installer
 

Attachments

  • image.jpeg
    image.jpeg
    50.3 KB · Views: 141
  • image.jpeg
    image.jpeg
    48.7 KB · Views: 151
Can you make this change:

-startAddress = kldSegmentVirtualAddress;
+startAddress = loadedInfo->ImageBaseVirtualAddress;

Also. There is something I must be missing, because looking at the "Done @ 0x..." in your output. How got that less than the startAddress we give it?
 
Keep it up guys!!!

Just to send you greetings.
Checking you all the time to update my mac pro 1,1 as I use now Yosemite 10.10.5.

Waiting for a kind of installer and commits.

Cheers and thanks for your time!!!!!!
 
MachO.cpp

line 1334:

startAddress = kldSegmentVirtualAddress;

changed to:

startAddress = loadedInfo->ImageBaseVirtualAddress;

!/?...
 
Last edited:
commit 3747e95e

MachO.cpp

line 1334:

startAddress = kldSegmentVirtualAddress;

changed to:

startAddress = loadedInfo->ImageBaseVirtualAddress;

(compiled in Win10/VSE2015)

attached:

#nvram boot-args=""

First screencap from createinstallmedia; second from legacy installer
 

Attachments

  • image.jpeg
    image.jpeg
    46.8 KB · Views: 143
  • image.jpeg
    image.jpeg
    42 KB · Views: 151
commit 3747e95e

MachO.cpp

line 1334:

startAddress = kldSegmentVirtualAddress;

changed to:

startAddress = loadedInfo->ImageBaseVirtualAddress;

(compiled in Win10/VSE2015)

attached:

#nvram boot-args="slide=0"

First screencap is from createinstallmedia; second is from legacy installer...
 

Attachments

  • image.jpeg
    image.jpeg
    49.6 KB · Views: 138
  • image.jpeg
    image.jpeg
    47.4 KB · Views: 151
latest commit, with line 1334 of MachO.cpp modded, as specified
 

Attachments

  • boot_commit-3747e95e_psot-#567.zip
    205 KB · Views: 387
latest commit, with line 1334 of MachO.cpp modded, as specified
Thanks. Isn't that something. Still not there. I even checked the kernel here and that pattern is there, so we're not looking in the right place. Try this:
startAddress = loadedInfo->ImageBasePhysicalAddress;
endAddress = 0xffffffffffffffff;
 
---8<--------

Also. There is something I must be missing, because looking at the "Done @ 0x..." in your output. How got that less than the startAddress we give it?

I don't make the News, Pike; I just report it ;)

If I was more savy with all these things, I could probably make more headway.

The two times I have been in-doubt as to whether I have completed said tasks to-the-letter, I have repeated my steps, and re-screencap'ed the results.

I will go where you lead, and report what I can, when I can . . . just don't overly-use my enthusiasm para consolar a su Esposa <smile>
 
Thanks. Isn't that something. Still not there. I even checked the kernel here and that pattern is there, so we're not looking in the right place. Try this:
startAddress = loadedInfo->ImageBasePhysicalAddress;
endAddress = 0xffffffffffffffff;

#fsck!

o.k., I'm game (but, will only initially report from addition into createinstallmedia without changing boot-args (which takes something like one hour, etc., &c., et al.))
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.