Yea, I guess my point more so was that if he installed LS 3.4.1 directly then it should have worked fine as it did.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Resolved 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
- Thread starter Mr. Zarniwoop
- Start date
- Sort by reaction score
Yea, I guess my point more so was that if he installed LS 3.4.1 directly then it should have worked fine as it did.
That's really good news. So, if you are right, the problem ought to be limited solely to the combination of LS 3.4.1 + Mavericks + any iteration of Pike's boot.efi (possibly due to some compiler quirk?).
How did you install LS 3.4.1 from an up-to-date full installer of 3.4.1? Or did you update to 3.4.1, say, from 3.4.0? Might the problem be in defective updates of LS itself that might affect Mavericks AND Yosemite?
I would imagine that anyone updating their previous Little Snitch version to v.3.4.1 and booting with any Pike Alpha compiled boot.efi would immediately experience not being able to boot their system after updating.
Can you, by any chance, UNINSTALL Little Snitch entirely in Mavericks (save your rules beforehand), reboot and reinstall it again using an up-to-date full installer of 3.4.1 (and restoring your rules)? Perhaps that will work correctly. Simply updating from earlier versions might leave some corrupt file.
I downloaded LS 3.4.1 and installed it onto a virgin-fresh Yosemite PB4 (on MacPro2,1 with latest boot.efi).
the new boot.efi was never intended to be used in combination with anything else than OS X 10.10 Yosemite! unexpected behavior of course is possible. Mavericks came with its own version of boot.efi from Apple HQ just as Yosemite has its new version issued by Apple.
Certainly that would be a definitive solution. I wonder how thoroughly Little Snitch's Uninstaller actually rids the entire system of all of its files or would something like AppDelete .app be more comprehensive ?
----------
I think it needs to be reiterated that others have reported this occurrence happening IN YOSEMITE while using the latest boot.efi "Yosemite" builds.
I know I tried the same in the Recovery boot and couldn't access it either. Even tried copying the Base System image from the installer that I manipulated accordingly and restoring it and disk utility would not allow it.
best tested graphics card for mac pro 1,1/2,1 and Yosemite
Hey just curious, what is the best mac pro 1,1 compatible video card that has been tested with yosemite? I suspect many have been using the 5770 or 5780 but I'm wondering if others have tested this with non-mac flashed nVidia or AMD graphics cards? I currently have a 5770 but am thinking of getting a flashed card but only if it works on Yosemite.
Many thanks and thanks again for all the hard work!
Cheers!
Hey just curious, what is the best mac pro 1,1 compatible video card that has been tested with yosemite? I suspect many have been using the 5770 or 5780 but I'm wondering if others have tested this with non-mac flashed nVidia or AMD graphics cards? I currently have a 5770 but am thinking of getting a flashed card but only if it works on Yosemite.
Many thanks and thanks again for all the hard work!
Cheers!
I have a flashed AMD Radeon 7950 in mine. I don't get the boot screen for some reason. I did get the boot screen in Mavericks/Tiamo.
Did my best to eradicate every trace of Little Snitch v3.4.1 on my OS X 10.9.5 system. Reinstalled it and placed the latest Build 6c697848ef boot.efi files in place and unfortunately got the continuous, looping boot that I reported earlier.
Returned Tiamo's boot.efi in place and the system immediately responded normally. I am afraid that the only way folks with a pre-existing Little Snitch install on their Yosemite drive will know if it will boot once updating to v3.4.1 is to do it and find out. I do not know of another way.
Did you try reinstalling Pike's boot.efi instead of Tiamo's? It is possible that it is corrupting the boot.efi regardless and replacing it with either boot.efi fixes it.
Remembering that since nether of the modified boot.efi versions are locked files, I replaced the working Tiamo's with the latest Pike while being booted in OS X 10.9.5 and thought repairing permissions before restarting might do the trick but alas no dice.
My last stab albeit unlikely to have any effect is I am booting my OS X 10.9.5 system (while keeping the Pike files in place) in Disk Warrior 4.4. Otherwise I think I have exhausted my known options.
App Store but I don't know which, if any of the updates replace the boot.efi. So you will have to be careful with that.
guys, just stop using Pike's boot.efi with OS X Mavericks. I'm pretty sure that even Apple's own boot.efi from Yosemite won't work properly under 10.9.x (if installed on a supported machine, that is...).
Last edited:
Before we explore the possibility of a quirk in the latest versions of VS and/or NASM, I think it would be a good idea for someone with LS 3.4.1 and Mavericks and Yosemite to test the following version of Pike's boot loader in both operating systems. It has been compiled in Debug/Win32 mode. If this works, then we've solved the hurdle. If it doesn't work, it seems to me the next step should be to compile Tiamo's original boot.efi with the current Visual Studio and see if it keeps working with LS 3.4.1 and Mavericks.
Please, report back with your findings.
Please, report back with your findings.
Last edited:
Obviously, you are mistaken. It has been reported by at least one person that Pike's boot.efi won't boot Yosemite if LS 3.4.1 is installed. So, it is NOT a non-issue.
Pike wrote the following in his blog:
However, I'm not very confident that will solve anything, since his boot loader seems to work perfectly without LS 3.4.1. In any case, maybe the users that have reported problems might want to try the above suggestions.
A lot has changed in Yosemite. For example. The kernel name and path to the kernel file have changed and thus boot.efi now expects to find:
/System/Library/Kernels/kernel
This instead of: /mach_kernel
Maybe that is the problem. Im not sure, but try one of these:
1.) Copy /mach_kernel to /System/Library/Kernels/kernel
2.) Add
<key>Kernel</key>
<string>/mach_kernel</string>
to com.apple.Boot.plist
Does that stops the reboot?
/System/Library/Kernels/kernel
This instead of: /mach_kernel
Maybe that is the problem. Im not sure, but try one of these:
1.) Copy /mach_kernel to /System/Library/Kernels/kernel
2.) Add
<key>Kernel</key>
<string>/mach_kernel</string>
to com.apple.Boot.plist
Does that stops the reboot?
However, I'm not very confident that will solve anything, since his boot loader seems to work perfectly without LS 3.4.1. In any case, maybe the users that have reported problems might want to try the above suggestions.
Let me rephrase then:
The fact that there is an issue with a particular version of Little Snitch, Yosemite and Pike's boot.efi is completely irrelevant to this thread.
For those who don't use Little Snitch, it IS a non-issue.