Any idea what's going on? Getting this bunch of errors and running Fix permissions results in Onyx freezing.
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.
Snow Leopard on Unsupported PowerPC Macs
- Thread starter Larsvonhier
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
// In /var/log/system.log
endless restart cupsd (no ppc, copy from 10.5 fixed)
endless restart ntpd (no ppc, copy from 10.5 fixed)
// Some hangs
Sharing, Safari - update_dyld_cache for ppc does not help significantly, but Apple.com load with problems but load
Could anyone please upload these two from 10.5.8? cupsd and ntpd
I also got this endless loop and update_dyld_cache failure.
It’s that the version of Disk Utility/diskutil/fsck in Builds 10A96 and 10A190, which I think — like Finder — might be early Cocoa re-writes of previously Carbonized code, are functionally incomplete and won’t fix permissions or check the disk properly. Onyx relies on the same system components to run the permissions verification/fix as Disk Utility does. On that front, Onyx won’t be of much help. I’ved used Onyx on SL-PPC mostly for UI/UX tweaks.
The verify/fix permissions and disk verification workaround I use (which may or may not be up your alley) is the PowerBook I use for testing Snow Leopard has the internal IDE-to-SATA SSD split into two equal APM partitions. One partition has Build 10A96 of SL-PPC, and the other has Leopard 10.5.8. [When I refer to “testing” here, with some notable exceptions, I treat everything I do on the Clouded Leopard setup to be “testing”, even though I’ve been daily-driving it for selected tasks for several months (namely, browsing with InterwebPPC, a bit of Adobe CS4 work, a tiny bit of audio editing, some writing, and as a Terminal console for other computers on my local network.]
I have Leopard on that PowerBook for two reasons: to boot into it to use Disk Utility (or, theoretically, Onyx’s verify/fix permissions feature) on the Build 10A96 partition; and to log in to Leopard as root to move and test frameworks and kexts in Build 10A96/SL-PPC to then reboot into SL to test the changes. For the latter, I prefer to do it this way because running the framework/kext moves as root in Leopard obviates a need to deal with chown/chmod on those moved SL-PPC frameworks/kexts being tested. For the former, it works as expected when fixing the occasional invalid node count or when fixing permissions. Unfortunately, I have tested the 10.5.8 version of Disk Utility on SL-PPC, and it’s one of several Leopard applications from Apple which does not work (as noted at the tail end of Table 4 in the WikiPost).
I’m not sure how helpful this is, but it might help out with what you’re seeing in your console.
Last edited:
This one is a bit tricky given the particular permissions of components inside /usr/libexec/cups/backend/ (such as ipp): they’re set to 500, limiting the ability to move from a Leopard source unless you’re logged in as root (I remember I had to boot into Leopard as root in order to move aside the SL-PPC components as “[component].old” and move in the Leopard components). This is where having Leopard on a secondary partition on the same machine comes in especially helpful.
I’ve tar-zipped the files you’ll need. Let me know if I missed any. You’ll see the “.old”; those are the set-aside versions from 10A96. You’ll need to expand the archive as root and move everything into place logged in as root.
cups and ntpd problem gone, but com.apple.launchd and com.apple.dyld error loops are ongoing.
Quick question:
were you able to boot from a PowerPC Mac running Leopard or an Intel Mac (running at least Leopard, Snow Leopard, or maybe Lion) and mounted your SL-PPC partition on that Mac to run a thorough Repair Permissions and Repair Disk via Disk Utility on it from there? That could help with the dyld issues you’re seeing.
Also, just to be clear: are you running Build 10A96 or Build 10A190?
I got one PowerMac with two partitions now (10.6 10A190 and 10.5.8). Re-installed 10.5.8 after you suggestion. I ran Disk Utility when booted into 10.5.8 to repair permissions on 10.6, but it just said all appears okay after a couple of seconds (which obviously is not enough even to verify permissions).
I could try making a bootable USB with 10A190 and run Disk Utility from there probably.
Huh. That’s not what I would have expected. It usually takes 5-10min with Disk Util in 10.5.8 to check and repair permissions on my 10A96 disk.
I’ve not been using 10A190, so I’m unable to share what I’ve experienced with that.
Wait, do you mean a bootable USB with Leopard on it, or do you mean something else entirely?
I made it to boot from USB into 10A190 and run Disk Utility from it. Same thing: permissions get “repaired” in a second without any errors in output. Verifying disk does take a couple of minutes and results in the volume appears to be okay.
So it does nothing.
Has anyone successfully installed iWorks on 10A190?
I tried to install a trial, it did not start. Installed updates 2 and 3 upon it, no errors with installation, but it still fails to start.
I tried to install a trial, it did not start. Installed updates 2 and 3 upon it, no errors with installation, but it still fails to start.
As I glance at Appendix A in the wikipost, I don’t see that iWorks or any of iLife has been tested yet.
Yeah, that's why I asked.
BTW I ran software update and it found something to download. I will give it a try:
You probably shouldn’t expect anything from Software Update to work in the PowerPC environment. In fact, if may even break some of the components with Intel-only counterparts and, consequently, break your installation of the system. From the vantage of Apple’s servers, it only sees your system as a Snow Leopard system, which implicitly is an Intel system.
Yes, I am aware of such possibility, but in the worst case I will lose some time to reinstall the OS afresh.
Anyway, it did update something for iLife and Front Row, as well as Airport Utility, while iTunes update does not do anything. iTunes started, but an old v. 8.
Airport Utility seems to work fine after update (i.e. at least nothing is broken apparently), cannot test iLife, don’t have it installed. Sadly, iWorks did not get fixed.
Some updates about software:
Stuffit Deluxe 15 – works
Pathfinder 5.2.2 – mostly works, some weird behavior is there (maybe I didn't make all settings correct)
PopChar 5.3 – works
Xbench 1.3 – works
Pibull Pro 2.4.4 (Hotline client) – works
KDX – works (trackers, servers, chats, downloads, all good)
Socialite – apparently fails to work (did not test comprehensively), tries to update (to Intel-only version), fails to start after update
Speed Download 5 – installs normally, takes license, however does not download
iWork 09 – installs but fails to start
Stuffit Deluxe 15 – works
Pathfinder 5.2.2 – mostly works, some weird behavior is there (maybe I didn't make all settings correct)
PopChar 5.3 – works
Xbench 1.3 – works
Pibull Pro 2.4.4 (Hotline client) – works
KDX – works (trackers, servers, chats, downloads, all good)
Socialite – apparently fails to work (did not test comprehensively), tries to update (to Intel-only version), fails to start after update
Speed Download 5 – installs normally, takes license, however does not download
iWork 09 – installs but fails to start
folks, I need to recycle the drive I used for this project, and so as I won't be working on this again, I will be deleting the overlay repo I made shortly as well.
Can I ask that someone interested in MP on 10.6 PPC fork it in the next day or two and take it from there please?
Thanks, it's been interesting!
Can I ask that someone interested in MP on 10.6 PPC fork it in the next day or two and take it from there please?
Thanks, it's been interesting!
Why not just open a new repo on a different account and just leave it there for someone else?
(Oh, wait. I think you have me on ignore because I pressed you to show your work, never mind.)
Can you provide a link to the repo to enable a fork please, as I can’t seem to find it. Having been very busy of late i’ve missed the last few pages of this thread however it seems non-sensical to erase anything that has proven useful whether you wish to continue to maintain or not.
Yes ethernet should work without any modifications. If you wish to use wifi for any reason you will need to copy over files from 10A096.
This issue only seems to appear using ‘supported’ cards so i assume it’s a framework issue. Using an unsupported card causes the OS to use the fallback graphics system which i suppose could also be prioritised by changing the graphics preferences via terminal until the issue is resolved.
Or update the system python if like me your goal is to bring the system closer to vanilla Snow Leopardit is failing running some python code, trying to use the system python. If you look at the original Portfile, we see that systems < darwin 10 (snowleopard) are forced to use a newer MacPorts-provided python.
macports-ports/devel/ninja/Portfile at master · macports/macports-ports
The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.github.com
So here our current system has a system python that is older that the one in the final SnowLeopard 10.6.8, and is behaving like a system < darwin 10.
So you need to change the test in the Portfile to < 11 instead of < 10, so as to force the MacPorts python for this build. These are the types of fixes I put in that repo referenced.
to do a one-off fix for ninja, you edit your Portfile with:
bbedit (backtick) port file ninja (backtick)
make your edit, save the file, and then clean and retry your build.
Last edited:
By any chance are you able to list any of the features that you know are missing so that others can investigate updating them please? Clearly you have a good understanding of what is included in the official release of Snow Leopard versus the developer seedsSimilar issue. Assumptions made for system features that are available on 10.6 are NOT available on this version of 10.6 because it is not the same as 10.6.8. So in places, you again have to force the build to features that are usually used only on 10.5 in some way.
In this case, I did a lot of work a few months ago to make glib2 build on older systems. Some of the tweaks are not working right on this 10.6 version. Specifically, some of the tests in this patch I wrote up will have to be adjusted to force some of the tweaks to be applied on this 10.6-for-PowerPC system:
macports-ports/devel/glib2/files/patch-glib2-findfolders-before-SL.diff at master · macports/macports-ports
The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.
My two cents would be to recommend that you disable dependency tracking if you attempt to cross compile from another version of Mac OS, and i’m sure there will be a number of other flags needed. Otherwise give it a bash and see what happens - reported findings will be much appreciated.
This issue remains unresolved under 10A190 currently