Peter, there is one thing I have forgotten to mention: Yosemite disk was the only one installed in the machine while testing "option" Recovery boot (which worked). IDK if it's important but worth a shot. Later this evening I'll be able to do some more tests.
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
Peter, there is one thing I have forgotten to mention: Yosemite disk was the only one installed in the machine while testing "option" Recovery boot (which worked). IDK if it's important but worth a shot. Later this evening I'll be able to do some more tests.
Today my machine crashed again, but with another panic.
Look at this link for details.
Are there any possibilities to get more information? It seems to be that there are no panic logs on the hard disk which confuses me.
I believe it is some kind of software problem? (It seems that the mac does not crash at older OS X versions (I am testing this at the moment).
If the machine is up and does not hibernate it is very stable.
Look at this link for details.
Are there any possibilities to get more information? It seems to be that there are no panic logs on the hard disk which confuses me.
I believe it is some kind of software problem? (It seems that the mac does not crash at older OS X versions (I am testing this at the moment).
If the machine is up and does not hibernate it is very stable.
Indeed they are, thank you. Inserting one of those builds a few moments ago helped reveal the problem. A few years ago when my expensive Phonic firewire audio interface died, I sought an inexpensive replacement/solution. Since my toddlers are occupying much more of my time, finances limited, and I haven't been doing much multi track studio recording, I thought something USB would suffice for the time being. I remembered sometime ago, I purchased a USB audio driver for our PPC iMac that I had not used for a while. It turned out that the driver was/is still being developed and allowed older USB audio interfaces to work on current Mac OS systems. Since I already had the driver and noticed that it supported the old MBox USB audio interface in Mavericks, I picked up an MBox up for like $10-15 bucks. Anyway, for some reason any build complied since the initial one that "mikeboss" first compiled cannot effectively load the driver.
So it would appear that I will have to remain status quo until the developer of the usb audio driver releases a version compatible with Yosemite in order to update to a newer Pike Alpha boot.efi build.
----------
Yes exactly. Your build ink here is the only boot.efi that will currently boot the usb audio driver.
So I've been using Commit 2ed42fe, with the gray boot screen, and although I can't check whether it can be selected by option-booting (non-EFI card), I can boot from it using Command-R.
Everything seems to be working well.
So... is it looking like 2ed42fe may be considered the "final" release ?
Just curious.
- Jay
Everything seems to be working well.
So... is it looking like 2ed42fe may be considered the "final" release ?
Just curious.
- Jay
Yes it appears that way. There is one other commit but it was just to update the txt to do list.
Successful install
After trying SFOTT, which was unsuccessful, I have finally managed to follow Hennesie2000 guide and I am now running Yose on my Mac Pro 2,1
I was on Mavericks on Chimera bootloader, on a separate disk so now I have more room for storage
Can anyone advise, if apple software upgrade overwrites boot.efi what are the steps to copy Piker's one over?
Many thanks to Piker and Hennesie2000
After trying SFOTT, which was unsuccessful, I have finally managed to follow Hennesie2000 guide and I am now running Yose on my Mac Pro 2,1
I was on Mavericks on Chimera bootloader, on a separate disk so now I have more room for storage
Can anyone advise, if apple software upgrade overwrites boot.efi what are the steps to copy Piker's one over?
Many thanks to Piker and Hennesie2000
After trying SFOTT, which was unsuccessful, I have finally managed to follow Hennesie2000 guide and I am now running Yose on my Mac Pro 2,1
I was on Mavericks on Chimera bootloader, on a separate disk so now I have more room for storage
Can anyone advise, if apple software upgrade overwrites boot.efi what are the steps to copy Piker's one over?
Many thanks to Piker and Hennesie2000
There haven't been any updates for 10.10 yet but you can expect one of them in the future might. If you use Tobyg's script for Mavericks you can replace the boot.efi.tiamo that it puts in the /usr/standalone/i386 folder with this new one and change the name to boot.efi.tiamo and it will function just like the script did with Mavericks.
The steps would be to:
1. Install the script but DO NOT restart.
2. Delete the installed boot.efi.tiamo in the /usr/standalone/i386 folder
3. Duplicate the boot.efi file that is in that folder (command + D)
4. Change the name from "boot.efi copy" to boot.efi.Tiamo
5. Restart
There are new news from my hardware:
I switched the riser boards an tested them solitary. Well the machine crashed once. After installing both riser cards again a red led at DIMM 4 was lightening (here a picture).
This is my 2x2GB RAM pair (i think that these are the Nanya-Rams from this picture: link. Well they have different timings than the other sticks).
I switched the positions of the sticks. No red light anymore, but still hang ups. At the last hang up (the machine was in standby, but sometimes it randomly power ups and freeze) two leds on the logic board was lightening (this picture). Could this really by an issue caused by software? Seems to be faulty hardware to me. At the second hang up the sticks were VERY HOT (all sticks). I could not touch them for more than 2 seconds!
I will remove the 2x2GB pair and will wait what happens.
I never installed a lot of software to my testing OS (like Lion). But I am using Mavericks/Yosemite for daily use.
So whats the point if the machine keeps failing without the suspect sticks?
Could it be a implementation issue in the boot.efi? But I never heard of other MacPros failing with this behavior?
I have to say that the dealer checked the machine, but he could not find any defects. Well, he only had installed a blank OS and he had done apple hardware test. But maybe the issue did just not happened at testing by him...
This machine really drives me crazy -.-
Last but not least two pictures of the riser cards: link1 and link2
ps. Could it be a faulty logic board or CPU (which can not go into the power saving states)?
I switched the riser boards an tested them solitary. Well the machine crashed once. After installing both riser cards again a red led at DIMM 4 was lightening (here a picture).
This is my 2x2GB RAM pair (i think that these are the Nanya-Rams from this picture: link. Well they have different timings than the other sticks).
I switched the positions of the sticks. No red light anymore, but still hang ups. At the last hang up (the machine was in standby, but sometimes it randomly power ups and freeze) two leds on the logic board was lightening (this picture). Could this really by an issue caused by software? Seems to be faulty hardware to me. At the second hang up the sticks were VERY HOT (all sticks). I could not touch them for more than 2 seconds!
I will remove the 2x2GB pair and will wait what happens.
I never installed a lot of software to my testing OS (like Lion). But I am using Mavericks/Yosemite for daily use.
So whats the point if the machine keeps failing without the suspect sticks?
Could it be a implementation issue in the boot.efi? But I never heard of other MacPros failing with this behavior?
I have to say that the dealer checked the machine, but he could not find any defects. Well, he only had installed a blank OS and he had done apple hardware test. But maybe the issue did just not happened at testing by him...
This machine really drives me crazy -.-
Last but not least two pictures of the riser cards: link1 and link2
ps. Could it be a faulty logic board or CPU (which can not go into the power saving states)?
Okay.
All in all this seems to be a hardware related question (I can not believe that software can cause such crashes)...
Maybe it is related to the RAM sticks. I will test the machine tomorrow (at my time zone it is 3:30 am ). I could imagine that the different sticks with different timings (and clocks) will not work together (or the 2x2GB sticks are just faulty).
Kind regards
Chris
All in all this seems to be a hardware related question (I can not believe that software can cause such crashes)...
Maybe it is related to the RAM sticks. I will test the machine tomorrow (at my time zone it is 3:30 am
). I could imagine that the different sticks with different timings (and clocks) will not work together (or the 2x2GB sticks are just faulty). Kind regards
Chris
I can remember that after one particular OS X release (was it Snow Leopard?), a lot of my customers started having crashes with their Mac Pros. the cause was Apple shifting lots of GUI related tasks to the GPU at the time and the passive cooling of the 7300 was not up to the task... so yes, software can cause hardware to fail.
FB-DIMMs are getting very hot, this is normal. although later models had a newer and cooler running AMB (advanced memory buffer) chip on them.
I suspect the capacitors on the riser-boards are getting old/tired. often they work stable again after reducing the number of DIMMs used to a total of only four.
FB-DIMMs are getting very hot, this is normal. although later models had a newer and cooler running AMB (advanced memory buffer) chip on them.
I suspect the capacitors on the riser-boards are getting old/tired. often they work stable again after reducing the number of DIMMs used to a total of only four.
Guy, let's back to the topic, unless you want this thread to become totally unreadable
Peter, I did some more tests with latest commit (one I posted recently) and it does perfectly boot Recovery partition with option.
No fancy BaseSystem.dmg tricks, only replaced boot.efi in com.apple.recovery folder. Presence of other bootable drives does not matter at all.
There must be another variable which we don't see at this moment. And it isn't VS or NASM version difference - you tested both compilations: mine and your own.
Peter, I did some more tests with latest commit (one I posted recently) and it does perfectly boot Recovery partition with option.
No fancy BaseSystem.dmg tricks, only replaced boot.efi in com.apple.recovery folder. Presence of other bootable drives does not matter at all.
There must be another variable which we don't see at this moment. And it isn't VS or NASM version difference - you tested both compilations: mine and your own.
Guy, let's back to the topic, unless you want this thread to become totally unreadable
Peter, I did some more tests with latest commit (one I posted recently) and it does perfectly boot Recovery partition with option.
No fancy BaseSystem.dmg tricks, only replaced boot.efi in com.apple.recovery folder. Presence of other bootable drives does not matter at all.
There must be another variable which we don't see at this moment. And it isn't VS or NASM version difference - you tested both compilations: mine and your own.
I read your message in Pike's blog and the answer he gave you. Partition differences might account why Option booting the Recovery HD works for you but not for me. Although I'm presently using my own build of boot.efi, I tested yours, as you know, and neither work with Option booting on my Mac Pro, although both work equally well with Cmd-R. That's all very strange. My disk setup is a follows:
Bay 1: GUID, Macintosh HD, with Yosemite (HFS+ Journaled) and the Recovery 10.10 partition (plus EFI, I suppose).
Bay 2: GUID, Windows, with Windows 7 (NTFS with write privileges from the Mac end via Paragon NTFS for OS X ).
Bay 3: GUID, Snow Leopard (HFS+ Journaled) (plus EFI, I suppose).
Bay 4: MBR, with three partitions:
1. BOOT (HFS Journaled): Chameleon (no longer used).
2. Install (HFS+): It presently contains the Mac Pro-custom made Yosemite installer (I don't like using pen drives for that purpose). I've had this since Mountain Lion.
3. Backup (HFS+): Used for SuperDuper! (OS X) backups and Paragon (Windows) Drive Backup backups.
2. Install (HFS+): It presently contains the Mac Pro-custom made Yosemite installer (I don't like using pen drives for that purpose). I've had this since Mountain Lion.
3. Backup (HFS+): Used for SuperDuper! (OS X) backups and Paragon (Windows) Drive Backup backups.
As I said elsewhere, Option booting works for regular Yosemite, Windows 7, Snow Leopard and Chameleon. It definitely does NOT work for Recovery 10.10. Would it work if I started moving the disks round the bays? It might, but I wouldn't like experimenting with 24 permutations.
Guy, let's back to the topic, unless you want this thread to become totally unreadable
No fancy BaseSystem.dmg tricks, only replaced boot.efi in com.apple.recovery folder.
Where is that folder? Unable to find it!
Where is that folder? Unable to find it!
The whole thing is hidden. If you want to see such things, first you need to mount the Recovery HD. Since, apparently, you don't know how to do that, you might want to consider whether you want to learn. Fiddling with these things could harm your computer if you don't know what you are doing.
Done. Found the answer on the web: mount the Recovery HD (debug menu Disk Utility).
Done. Found the answer on the web: mount the Recovery HD (debug menu Disk Utility).
Good for you.
He meant more than three partitions on Yosemite drive.
My disk setup is:
– 3x HDD in RAID 0
– Mavericks SSD
– Yosemite HDD
– TM HDD
All GUID, no MBR/FAT/NTFS etc.
Option boots Recovery without a problem.
Perhaps Windows partitions/drives cause the issue?
The "issue" didn't exist with the Mavericks Recovery HD, and the "issue" is not there when I Option-boot Yosemite, Windows 7, Snow Leopard or Chameleon. It's there exclusively if I try to Option-boot the Yosemite Recovery HD. Very odd. Hennesie reported having exactly the same problem.
Last edited:
I have three partitions on my HDD. Yosemite/Clover/Windows 7. There is also the two hidden partitions EFI and Recovery HD.
Darwin/XNU Kernel Sources 10.10
Apple has now released the sources of the Darwin/XNU Kernel 2782.1.97: www.opensource.apple.com.
Here the sources as Tarballs.
Apple has now released the sources of the Darwin/XNU Kernel 2782.1.97: www.opensource.apple.com.
Here the sources as Tarballs.
