Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I overlooked this until a closer look-through the table, but you should try also bringing over these from 10.5.8, as well:

View attachment 1986094
No luck unfortunately. I won’t have time to try new kexts until Friday, but I’m starting to think that the issue isn’t kext related. There has to be some framework or device list to enable QE/CI on specific device ID.
I tried the second download, also needed on 10.5.8 to properly use the X800XT, no difference.
Could you please dump a list of loaded kexts with your X1900 on 10.6? Either with “kextstat” from Terminal or from System Profiler under the “Extensions” entry. Thanks!
 
  • Like
Reactions: ChrisCharman
No luck unfortunately. I won’t have time to try new kexts until Friday, but I’m starting to think that the issue isn’t kext related. There has to be some framework or device list to enable QE/CI on specific device ID.

No worries and take your time. I’ll look forward to your posts on what you figure out along the way!

My mental checklist is thinking through everything which could be a factor here — namely:

—> the back-ported GPU kexts _√
—> the back-ported IOGraphicsFamily kext _?
—> the back-ported ImageIO and CoreGraphics sub-frameworks inside the ApplicationServices framework _?

Beyond that, the cause could be something else entirely which no one else has reported yet.
 
  • Like
Reactions: ChrisCharman
I tried the second download, also needed on 10.5.8 to properly use the X800XT, no difference.
Could you please dump a list of loaded kexts with your X1900 on 10.6? Either with “kextstat” from Terminal or from System Profiler under the “Extensions” entry. Thanks!

I guess those two:
ati.png
 
  • Like
Reactions: ChrisCharman
ATY_Prionace is a sub-component of ATIRNDRV.kext.

Do you happen to know what this does? Curiously, the main kext itself isn’t specified with an architecture, while its internal sub-components are a combination of both Universal and Intel.

No idea :) I assumed they were installed with ATI driver based on the date, but I may be wrong, if the driver does not use kext.
 
  • Like
Reactions: ChrisCharman
As I have been trying to work on moving components from the 10A096 to 10A190 related to the AirPort, I have been having major trouble. Finder is so unstable and might quit on me any moment, prompting a relaunch or restart. It wouldn't cause any problems if I do this file moving booted into Tiger of Sorbet would it? I will still check permissions when I boot back into SL. Or is there a better way to work around this? Thanks.
 
As I have been trying to work on moving components from the 10A096 to 10A190 related to the AirPort, I have been having major trouble. Finder is so unstable and might quit on me any moment, prompting a relaunch or restart. It wouldn't cause any problems if I do this file moving booted into Tiger of Sorbet would it? I will still check permissions when I boot back into SL. Or is there a better way to work around this? Thanks.
Yes, it is preferable to copy the files across while booted into a different OS partition. 10A190 has issues with the filesystem and finder ‘out of box’ as well as stability. Just be sure to set ownership and permissions and remove the necessary .mkext and cache files each time before reboot.
 
Finder is so unstable and might quit on me any moment, prompting a relaunch or restart.

This might be a hardware issue – failing RAM. I thought 10A190 tends to freeze randomly on Finder operations until it became overly annoying – and ended with several KP and a death of one of RAM modules. Replaced it, forgot about such problems altogether.
 
I replaced most of the files except AirPort Base Station Agent and AirPort Utility which I couldn't find. However, I am not sure how to correctly set the permissions. I would have to use Terminal?
 
I replaced most of the files except AirPort Base Station Agent and AirPort Utility which I couldn't find. However, I am not sure how to correctly set the permissions. I would have to use Terminal?

Yes. Terminal — as super-user — is vital for much of this component replacement work.

If you move a component from 10A96 or 10.5.8 to 10A190, and you’re unsure whether the ownership/group for that moved component is correct, one useful command which can at least restore correct ownership/group is:

sudo chown -R 0:0 [path to component file/directory name]

The -R recursively applies changes to files and directories within, while 0:0 is a kind of “return to default ownership/group” setting, changing it to what it should be (kind of like an individual “correcting the permissions” command). Before running the command, the owner/group might be:

“tensixturtle admin”

But then you notice other components in that directory (an "ls -la" command) are all:

“root wheel”

After running that command on the component which had you as the “owner” and “admin” as the group, it will now show as “root wheel” like the rest.

But @ChrisCharman is right about the need to have two OSes on the same Mac, and to make these changes to Build 10A190 whilst, say, booted into 10.5.8 on another partition.
 
In between preparing the 10A96 monster patch .pkg from hell, I managed to get, with help from @wicknix and @Wowfunhappy , Dictionary.app in 10A96 to reach Wikipedia, via a Squid server I set up on another Mac on my LAN.

The formatting is a train wreck (I can’t begin to guess what the culprit is), but heck, it works!

1649331957222.png
 
This might be a hardware issue – failing RAM. I thought 10A190 tends to freeze randomly on Finder operations until it became overly annoying – and ended with several KP and a death of one of RAM modules. Replaced it, forgot about such problems altogether.
There are a number of things that can exasperate the instability of Finder on 10A190 - even colour space and font incompatibility due to the ‘in progress’ changes that were being made to the system, in addition to moving from a carbon to cocoa codebase.
 
What I would try to do is follow the steps in post #513 (also referenced in Appendix B of the WikiPost): retrieve the group of files in that post from one of the two disk images for Build 10A96, and copy those into their respective locations on your installation — accounting for file ownership/groupship and permissions being correct once you do so.




Because your iMac uses an AGP bus graphics card, you will not be able to tap into hardware support for Core Image and Quartz Extreme. What moving the video drivers over from 10.5.8 do is bring some support for your video card in 10.6, including software support for CI/QE. In addition, I would spend some time looking at the posts mentioned in Appendix B on how to further improve graphics performance, as there are a number of tweaks along the way which can improve performance even in the absence of hardware support.




In general: with this project, any files we’ve been pulling from Leopard 10.5.8 have been from just that: the final build produced by Apple. It would probably not be a good idea to pull anything from Sorbet Leopard.

If my memory serves… someone in my Mythical OSX on PowerPC Macs Discord server…. Someone is working on a graphics acceleration solution for AGP PowerPC Macs.
 
If my memory serves… someone in my Mythical OSX on PowerPC Macs Discord server…. Someone is working on a graphics acceleration solution for AGP PowerPC Macs.

Are you able to share more information here about that — such as how long ago this effort came up, how much work they’ve been able to do, whether they’re active on the MR forums, and so on?

I would really be eager to learn from them what they’re actively looking into and whether they could benefit from community participation. This MR forum thread would be the place to do that collaborating, as the most eyes are going to see it.
 
Are you able to share more information here about that — such as how long ago this effort came up, how much work they’ve been able to do, whether they’re active on the MR forums, and so on?

I would really be eager to learn from them what they’re actively looking into and whether they could benefit from community participation. This MR forum thread would be the place to do that collaborating, as the most eyes are going to see it.

I haven’t heard anything in quite a while… I assume they’re still working at it, but how often I don’t know.
 
Thanks for the guidance. It recognizes networks with the AirPort now so I must have done something right! However, it fails to connect to my network and I wonder if that is because I didn't transfer the AirPort base Station Agent and AirPort Utility? Those files were simply not there in the 10A096 Server image (1st one on Macintosh Garden). Is there another image that would work better? Thanks.
 
Thanks for the guidance. It recognizes networks with the AirPort now so I must have done something right! However, it fails to connect to my network and I wonder if that is because I didn't transfer the AirPort base Station Agent and AirPort Utility? Those files were simply not there in the 10A096 Server image (1st one on Macintosh Garden). Is there another image that would work better? Thanks.
I checked the 10A096 Client as well; no luck. 10A096 Clean doesn't mount at all.
 

Attachments

  • Screen Shot 2022-04-07 at 9.18.16 PM.png
    Screen Shot 2022-04-07 at 9.18.16 PM.png
    140.1 KB · Views: 71
  • Screen Shot 2022-04-07 at 9.17.43 PM.png
    Screen Shot 2022-04-07 at 9.17.43 PM.png
    241.5 KB · Views: 63
Snow Leopard was Apple’s project of heavily refining OS X under the bonnet and cutting down on kernel-level kludges which arose when Apple began to support both PowerPC and Intel architectures from Tiger 10.4.3 forward. Initially, Apple team developers began work on Darwin kernel 10.0.0 (Snow Leopard) with Universal support for both PowerPC and Intel architecture. Mid-stream in that development en route to the retail release, Apple announced officially they would drop support for PowerPC architecture.

(Separately, a small team at Apple, from several available sources at the time, may have maintained a Universal binary fork for development internally as a fallback contingency, with internal nightly builds beyond what was made available to Apple Developer Connection members).

Those of us who’ve been working with the Snow Leopard builds which run on PowerPC architecture have observed some of these refinements even in the alpha builds to which we have access.

As to why I choose to work on this project? Snow Leopard was, far and away, the most stable major version of OS X/macOS I’ve ever worked with (and others have said similarly, sometimes noting how OS X Mavericks came pretty close). It was the last major version of OS X before a move to monetize services within the OS, to side-port iOS UI-related functions back into OS X, to move services toward a cloud-based model (with related phoning-home routines hard-baked into the OS), and the last major version before the cumbersome partition system which came to the fore with OS X Lion and Apple’s abandonment of distributing the OS with optical media.

As to why I don’t just use 10.5.8 Leopard and be done with it?

Two of my PowerPC Macs actually do run 10.5.8 because that’s how I set them up to run before this community project started. Out of box, 10.5.8 consumes significantly more drive space (some of which can be alleviated via user-discovered routines like removing the significant disk waste of the Designable.nib files).

Separately, the UI for Finder in 10.5.8 is both “looser” and of lower contrast than even the version being worked on with the earliest ADP build of Snow Leopard, Build 10A96 (notable, in that 10A96 still featured a Carbon code base, which wouldn’t get replaced with a Cocoa code base until a bit later in Snow Leopard’s development).

Finally, after using Build 10A96 with one PowerBook alongside 10.5.8 on another complementary PowerBook of the same specs, I can’t say 10.5.8 is any more stable than what’s found with Build 10A96 — which is sort of a testament of that refinement which underwrote Apple’s purpose of developing Snow Leopard in the first place. Some of those refinements for the retail release of Snow Leopard actually do appear quietly in Leopard, post-10.5.6, and this project has back-ported several of those refinements into Builds 10A96 and 10A190 and yielding positive results.

I hope this helps to answer your question.
Thank you for taking the time to answer my question, and I was very sad at the time SL was deemed unusable in modern context, and I do understand the issue of how enormous Leopard was.

What specifically are the refinements that appeared in Leopard after 10.5.6? You are reminding me that one of the reasons I kept a 2011 machine is because of its native ability to boot into 10.6.7
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.