I have not as i'm currently focused on moving in the opposite direction, however @vddrnnr has done this and had some success at least relinking syslogd using install_name_tool
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
I’ve moved it forward myself.... I have Safari 4.0.5 (Leopard version) running on 10A96!
I wonder why Finder is buttery smooth and everything else struggles with no GPU acceleration?
I’m not sure of your configuration at the moment, though I would go through all the graphics-related tweaks collected together on the WikiPost tips first before concluding that everything else is struggling. When you incorporate the fixes and tweaks into your installed build, you should notice some improvements. I’m working with a slower CPU situation (a single 1.67GHz G4) and with far less RAM (2GB) than you are, and I have managed to improve UI and graphics performance enough that it’s fairly responsive except in high-GPU-optimized tasks (like using VLC, where I am unable to get working video so far).
Also, is your G5 using an AGP graphics card, or is it PCIe? If it’s the former, you will not be getting GPU acceleration. Part of this was of Apple’s [lack of] doing (AGP support, as they were moving away from it with all Intel hardware), but part of this was, simultaneously, the industry’s move away from writing GPU drivers with BrookGPU, as was the case with vendors like ATI/AMD, and moving toward OpenCL instead (OpenCL driver support began with 10.6, with custom-written drivers for the integrated, 32-bit Intel GPUs, which served as a stop-gap in the Intel Mac line and were not OpenCL-compliant). I‘ve looked into this fairly complex issue, and I think that one was detailed in post #893).
Also something to consider is when and how OS X (not just SL-PPC) hands over graphics-related tasks to the GPU and not the CPU. If you’re running a PCIe G5 NVIDIA. NVIDIA did, as I understand it (and also seen in the kexts testing I did in Table 4), write a few OpenCL-compliant drivers for its PCIe cards shipped in PowerPC G5s). For those Macs, GPU acceleration should happen for things like QuickTime video playback or video games. I haven’t tested this because I lack the equipment (i.e., an A1177 Power Mac G5).
Yeah my G5 is AGP
.... and I tried loading said graphics related KEXTs marked as n/a (NVDA KEXTs, and the GeForcePPC.KEXT) both refused to load.
Going back to trying Leopard Finder on SL PPC, I made up a disposable 10A190 install on a spare partition and transferred my account from another system.
I then replaced Finder on my new 10A190 installation with the one from 10.5.8, repaired permissions to root, wheel using BatChmod and booted into it.
Alas, Finder from 10.5.8 kept crashing and restarting continuously again, so it wasn't a permissions issue.
However, back in my usual SL PPC system I've discovered that if I force a relaunch of Finder (the one that came with 10A190) using Force Quit, it suddenly shows external drives on the desktop and in the Sidebar. No idea why though
Cheers
Hugh
I then replaced Finder on my new 10A190 installation with the one from 10.5.8, repaired permissions to root, wheel using BatChmod and booted into it.
Alas, Finder from 10.5.8 kept crashing and restarting continuously again, so it wasn't a permissions issue.
However, back in my usual SL PPC system I've discovered that if I force a relaunch of Finder (the one that came with 10A190) using Force Quit, it suddenly shows external drives on the desktop and in the Sidebar. No idea why though
Cheers
Hugh
So, my clunky way around this (until someone comes up with something better) has been to write a script to relaunch Finder, and turn it into an application to run every time I plug in any external drives. It works, but I'm sure there could be a better method
The attached zip contains both the script and the app made from it, if anyone fancies trying it out...
Cheers
Hugh
The attached zip contains both the script and the app made from it, if anyone fancies trying it out...
Cheers
Hugh
Yeah my G5 is AGP.... and I tried loading said graphics related KEXTs marked as n/a (NVDA KEXTs, and the GeForcePPC.KEXT) both refused to load.
I’m guessing you have the GeForce FX 5200 Ultra which shipped standard with the mid-2004 DP 2.0 G5s. I own that configuration, though I have not tested Snow Leopard on it (originally, because I use it as a dedicated file/streaming server, and currently, because the logic board is dying).
From what I understand, based on some of the other folks who have tested it, they have managed to reach hardware acceleration of the GeForce FX 5200 Ultra with a PCI variant (aftermarket, of course).
As for kexts and bundles:
As found in the 10.5.8 build only, there are PPC-specific bundles and plugins associated with the GeForce.kext family. These are separate from the GeForcePPC.kext family which appears in 10.5.8 only. What might make this somewhat confusing is that both kexts have bundles and plugins which exist both as Intel-only (like “GeForceFXGLDriver.bundle” as found in SL-PPC, and “GeForceFXGLDriverPPC.bundle”, as found in 10.5.8 only).
In a paste of the table below, all the blue components (all of which are version “1.5.48”, bolded, in the first column) exist in the 10.5.8 GeForce.kext and GeForcePPC.kext families only.
What I would try is:
- Whilst logged into SL-PPC as root, open the /S/L/Extensions contents of both SL-PPC/10A96 and also a mounted 10.5.8 build.
- Then, from a working 10.5.8 build, copy over all the 1.5.48 bundles/plugins ending with “PPC” into their respective locations on your build of Snow Leopard.
- Once copied over, you should have a combination of bundle/plugin contents on your SL-PPC build which matches what this table above shows (that is: with a mix of 10.6-specific Intel bundles/plugins showing “1.6.0”, and 10.5.8 PPC bundles/plugins showing “1.5.48”).
- Once you’ve verified that, go back to your Extensions.mkext and trash it, then reboot. The “updating boot caches” dialogue box should show up whilst it re-generates a new Extensions.mkext.
- After reboot, open System Information and let us know if there’s been any change.
I’ve pasted two directory snapshots below from the 10.5.8 partition of my PowerBook G4 (the same Mac I’ve been using to test 10A96). That system is partitioned with both 10.5.8 and 10.6 10A96. What I’m calling “Figure 1” and “Figure 2” below are highlighted directory contents from 10.5.8 which you’ll want to bring over to 10A96, as root:
Figure 2.
Lastly, while you’re in there and moving over kexts, here are some others from 10.5.8 you might want to move over to 10A96, just for thoroughness’s sake:
Figure 3.
Figure 4.
Last edited:
I have the exact model. Upgraded to an SSD an 8 Gigabytes of RAM at some point as 4 GB was okay but I really liked having 8 GB as the family computer from the era was limited to 4 gigabytes of the same stuff. I’ll give your solution a try.
Do we have a date when this will be finalized and uploaded to the Garden ? Finalized, meaning everything or most everything works, including WIFI ? Tried the previous builds on my Titanium - its slow with no acceleration at all. I may try it on my DLSD.
This is going to take a long, long time, with no guarantee of complete success.
We should all be very grateful to those few who have taken on this mammoth task using their own time and resources, and for the great progress that has been made so far
Cheers
Hugh
My advice to you:
1) Stop asking this question. It’s a question you’ve asked multiple times on this thread (and which has patiently been answered multiple times… on this thread), because the answer is going to be the same, every time. This project will never be “finalized”, so stop asking, because the answer you want is the answer you will never get.
2) In addition, if you want to see progress on your Titanium PowerBook G4, then you’re going to have to get your hands dirty and do your own testing and experimenting. If you’re not patient enough to do that, then keep an ear peeled to this thread and don’t ask the above, because from this point forward you will be ignored.
3) If you want more stuff to work on your Mac, then maybe you ought to start with experimenting using Build 10A96 and not 10A190. The Titanium PowerBook is ancient when it comes to what Snow Leopard was initially set out to do, and Build 10A190 has a lot of PowerPC components stripped from it which were still present with 10A96.
Stop asking.
This a great temporary solution! Having to force relaunch Finder does indeed grow tiresome after an extended period of time.So, my clunky way around this (until someone comes up with something better) has been to write a script to relaunch Finder, and turn it into an application to run every time I plug in any external drives. It works, but I'm sure there could be a better method
The attached zip contains both the script and the app made from it, if anyone fancies trying it out...
Cheers
Hugh
With the greatest respect @Macbookprodude it does seem very much like you’re ‘trolling’ this thread - repeatedly asking the same questions. While i understand you’re eager for a more complete and functional build, constantly badgering those who are working on this for updates merely comes across as rude and entitled. It is analogous to a child in the back seat of a car asking ‘Are we there yet’ and equally as frustrating. Please refrain from doing this any further.
Thank you
I had the app in my startup list but I've removed it from there and kept it in the dock.
You only need to invoke it after plugging in external drives, and again after unmounting.
If there are any errors it might be worth adjusting the script from 'delay 2' to 'delay 3' and rebuilding the app.
Cheers
Hugh
Quick update:
I've managed to track down the Mac OS X Kernel Debug Kit for Snow Leopard seed build 10A222. The compressed file uploaded to this page contains the debug kernel for 10A222 and the tools necessary to generate debug symbols. I've also uploaded all other builds, debug kits and seed notes that i currently have access to.
Hopefully we can use this to find out what is preventing 10.0.0d3 from booting fully on PowerPC systems.
I've managed to track down the Mac OS X Kernel Debug Kit for Snow Leopard seed build 10A222. The compressed file uploaded to this page contains the debug kernel for 10A222 and the tools necessary to generate debug symbols. I've also uploaded all other builds, debug kits and seed notes that i currently have access to.
Hopefully we can use this to find out what is preventing 10.0.0d3 from booting fully on PowerPC systems.
Last edited:
Maybe we can backport this kernel to 10a190 or 10a96?
First of all, I had no idea there was ever a utility made for the builds, so this is fantastic news! It also raises hope that kernel debug kits for the earlier builds are out there somewhere.
Second of all, thank you for bringing this to our attention and uploading it! I can add a link to it in the WikiPost. Would you be okay with me mirroring it to the Snow Leopard for PowerPC main page on the Garden?
Alternately, maybe we’ll have a chance to find the kernel debug kits for 10A190 and even 10A96.
I haven’t been able to locate the debug kit for 10A096 but i have been running the 10A190 debug kernel for a number of weeks now. I thought i shared the link to the 10A190 debug kit earlier in the thread, but i may not have.
There should be a Kernel Debug kit for every build - i’ve uploaded the 10A190, 10A222 and 10A432 versions to the Macintoshrepository page along with all of the seed builds that I currently have. I’m also slowly uploading the same files to the main page on the garden but it’s just taking a bit longer for them to upload.
It’s entirely possible I may have missed it when I compiled all the thread’s tips into the WikiPost. If you can find it, I’ll set up a Table 6 with the debug kits.
It’s worth a shot, as it outputs a great deal more information in verbose mode we can pinpoint where any issues remain - we can also try and do the same with the Golden Master Kernel Debug Kit 10A432 which i’ve also uploaded. I still think we may need to compile our own version of the kernel but at the very least these kits should prove informative.
That’s hardly surprising given the sheer volume of posts on this thread! You’ve done an excellent job collating as much information as you have thus far. I think i did try and add a few bits to the WikiPost but it pushed us back over the limit and i was hesitant to start removing anything to make room. Are we able to add a second WikiPost underneath for a table of useful files and replacement binaries at all?
Unfortunately, no. The forum backend isn’t configured to host multiple WikiPosts under a single thread and has a cap on 70K characters for any post (including WikiPosts).
Shy of the admins bumping that up, what I have been doing, in revision round after round (there have been many rounds), is tightening text, formatting, and structure of the WikiPost to keep the headroom just below 70K. This is also why I offered to add links to the kernel debug kits to assure nothing is lost and we stay just under 70K.
[UPDATE: I have added a column on Table 1 with placeholders to the download links for the kernel debugging kits (which will link to the MacRep source, and backups on places like the garden and/or Archive).]
Last edited: