Snow Leopard on Unsupported PowerPC Macs

[vddrnnr]

Hi @Macbookprodude,

No we are still without QE/CI but following the processes of replacing
the frameworks inside the ApplicationServices framework we get a very "smooth"
UI ( Not perfect but much better than without).
@Larsvonhier as also tested it with other graphics based on radeon and rage and
it seems to help also. Unfortunately no word on Geforces without QE/CI.

Best regards,
voidRunner

 

[Macbookprodude]

Ok, but at least I can still try it (downloading from Macintosh Garden now) the beta thats there and get an idea of what to expect ? I wish I could help, however I am not a developer, nor programmer sadly.. I can offer suggestions and stuff, but thats all. Once all the bugs have been worked out and SL PPC runs like Leopard but better, will you upload another build with the improvements ? I am really excited about this.

 

[vddrnnr]

Hi @Macbookprodude,

I think we are hoping that we may create a full installer but there is a lot to
Iron out first.
But one off the things we already talked about is to create and image of the HD of a
fully running system to help those who may find it difficult to
do the whole install and replace process to get the system up and running
( I think @Larsvonhier already made one available for download ).

PS. We are excited too ;-)

Best regards,
voidRunner

 

[Macbookprodude]

Yeah, I am doing that as we speak.. I downloaded the image and going to try it. Its almost done copying to my paritition. I only hope that when this is all done.. Snow Leopard will be our new home for PPC - and hopefully all the apps in there work with out machines.

 

[Macbookprodude]

Hello everyone ! First I'd like to say as a die-hard PowerPC mac user since 1999 I can really say - IT WORKS ! I was able to use the snow leopard image and made a partition on my PowerBook G4 1.67 and while airport, CI/QE did not work - never the less, Snow booted up and it said 10.6 This is dynamite we have.. if and when the final product will be patched to allow airport, QE/CI - like normal snow leopard/Leopard - I think this will turn the tables with PowerPC - we will have the ability to make better use of PPC, grand central dispatch hopefully will work on dual/dual core G5 and Quad. Apple ended PPC too early as Snow Leopard should have been the final OS, maybe Lion too might have some PPC code.

Its too bad i am not a developer or programmer(took c++ in college and sucked at it), however I am willing to help with suggestions on how to make Snow work for us. Finally, i CHECKED all the apps and they all appear to be working with out any issues, even Safari worked, though broken due to TLS. Software update did not work as I assume this will work eventually. I am all for this as this will DEFINATELY breath new life into our PPC machines.

Sadly, my Pismo will NOT be getting this update because it can hardly run Leopard and nothing really works well with it, so Tiger my Pismo will remain, though I am also working with some folks who are sympathetic to my OS 9 concerns, as a few developers there may be updating OS 9 soon to fix the TLS in classila.

All in all, snow leopard is cool to see running on our PPC macs. This should give us several more years of time with our beloved machines. I look forward to the updated/final product, as I will migrate from Leopard to Snow on my PB G4 1.67 and G5 Quad. Kudos to you all ! I just wish i KNEW how to program and develop, sadly, I don't.

 

[cc333]

Hey, this is neat!

I've been following along, and noticed that a fair number of builds are available to experiment with.

On a whim, I checked around to see if i could find any, and found a torrent of build 10a286. Would that be useful to anyone? It seems that most PPC-ness was stripped out sometime shortly after a190, but there might be some things within a286 that later builds don't have? It was mentioned that some components of a222 were still PPC compatible and improved over their a190 counterparts, so maybe?

I also have a PowerBook G4 A1106 to test with, if that would help. I haven't noticed that anyone else has mentioned that particular model so far.

c

 

[vddrnnr]

Hi all,

Some information about syslogd.
As I mentioned previously I'm using syslogd and syslog from Leopard because the
version in OSX Server 096 crashes and makes the CPU go full throtle all the time.
While testing my apps and looking at /vat/log/system.log I kept seeing
a lot of errors regarding the syslogd process itself.
Looking closer I found it was complaining about a missing synbol in
/usr/lib/libSystem.B.dylib
I copied the dylib from Leopard and renamed it libSystem.B.1058.dylib and
then used the install_name_tool to "relink it" with the version from Leopard
a bit like Webkit does when rel-inking other apps.
So I'm happy to report that syslogd is now working properly without any errors.

Best regards,
voidRunner

 

[Hughmac]

Hi all,

Some information about syslogd.
As I mentioned previously I'm using syslogd and syslog from Leopard because the
version in OSX Server 096 crashes and makes the CPU go full throtle all the time.
While testing my apps and looking at /vat/log/system.log I kept seeing
a lot of errors regarding the syslogd process itself.
Looking closer I found it was complaining about a missing synbol in
/usr/lib/libSystem.B.dylib
I copied the dylib from Leopard and renamed it libSystem.B.1058.dylib and
then used the install_name_tool to "relink it" with the version from Leopard
a bit like Webkit does when rel-inking other apps.
So I'm happy to report that syslogd is now working properly without any errors.

Best regards,
voidRunner

Aah, could that be why my CPU is always at 100% in 10A190?

I would appreciate more detailed instructions for the whole process to fix this please?

Cheers

Hugh

 

[ChrisCharman]

Hi all,

Some information about syslogd.
As I mentioned previously I'm using syslogd and syslog from Leopard because the
version in OSX Server 096 crashes and makes the CPU go full throtle all the time.
While testing my apps and looking at /vat/log/system.log I kept seeing
a lot of errors regarding the syslogd process itself.
Looking closer I found it was complaining about a missing synbol in
/usr/lib/libSystem.B.dylib
I copied the dylib from Leopard and renamed it libSystem.B.1058.dylib and
then used the install_name_tool to "relink it" with the version from Leopard
a bit like Webkit does when rel-inking other apps.
So I'm happy to report that syslogd is now working properly without any errors.

Best regards,
voidRunner

@vddrnnr that’s great news! I was having issues trying to compile Syslogd because of issues with/usr/lib/libSystem.B.dylib! That explains it

 

[vddrnnr]

Hi @ChrisCharman,

I was doing some more tests with syslogd and I've found
something strange.
If I replace syslogd with the replink process done and reboot it does not
start.
But if I restart with the untouched Leopard version and then do a

sudo killall syslogd;sudo cp syslogd.relinked syslogd

Than it works. It's strange

Best regards,
voidRunner

 

[Larsvonhier]

Hey, this is neat!

I've been following along, and noticed that a fair number of builds are available to experiment with.

On a whim, I checked around to see if i could find any, and found a torrent of build 10a286. Would that be useful to anyone? It seems that most PPC-ness was stripped out sometime shortly after a190, but there might be some things within a286 that later builds don't have? It was mentioned that some components of a222 were still PPC compatible and improved over their a190 counterparts, so maybe?

I also have a PowerBook G4 A1106 to test with, if that would help. I haven't noticed that anyone else has mentioned that particular model so far.

c

Sure, more test machines always welcome!
A286 is already „available“, found it on a torrent also and got it dl‘d after a couple of days. If you can manage to upload it somewhere accessible faster, pls. do so and add the link to table on page#1. Thanks!!

PS: Currently I‘m leeching A222 server, A335 user, and 9A343 (Leo, for the latest Nvidia PPC support ever).

 

[armdn]

Hi @Macbookprodude,

No we are still without QE/CI but following the processes of replacing
the frameworks inside the ApplicationServices framework we get a very "smooth"
UI ( Not perfect but much better than without).
@Larsvonhier as also tested it with other graphics based on radeon and rage and
it seems to help also. Unfortunately no word on Geforces without QE/CI.

Best regards,
voidRunner

I tried to do that, in 10A190, after reboot loginwindow died at all.

 

[armdn]

FIXED! Airport Extreme is now working!

And somewhat fixed AirPort section of System Profiler. But it is incorrect detect status of AirPort Extreme. Actually it is active...

What to do with that little bugs is still a question. And in logs many errors about CarbonLib or something...

To make AirPort Extreme working, we need to import these components from 10A96 above the same in 10A190:
/System/Library/CoreServices/Menu Extras/AirPort.menu
/System/Library/CoreServices/Apple80211Agent.app
/System/Library/Frameworks/AirPort.framework
/System/Library/PrivateFrameworks/Apple80211.framework
/System/Library/Extensions/IO80211Family.kext
/usr/libexec/airportd

 

[armdn]

I'm also tried to mess up with IOPCIFamily.kext from 10.5.8 to 10A190...and get killed OS completely. But now i'm fully understand HOW kernel is going detect Macintosh model.

AppleMacRisc2PE - is the extensions for PowerPC Macs. As this extension related to Platform Expert. ("PE" - Platform Expert).

And now, i think, we have only few ways: Rebuild IOPCIFamily.kext with AGP support inside, or call Netkas to share it's own code of ATY_Init.kext to rebuild it to PowerPC platform...

 

[armdn]

Looked into 10A380. It is almost unusable.
The kernel itself builded for PowerPC

But Finder is intel-only now...

Some extensions still builded for PowerPC, but most of them useless...

Spoiler: Extensions

ACard6280ATA.kext/Contents/MacOS/ACard6280ATA:                                                 Mach-O universal binary with 2 architectures: [ppc:Mach-O object ppc] [i386:Mach-O object i386]
ACard6280ATA.kext/Contents/MacOS/ACard6280ATA (for architecture ppc):    Mach-O object ppc
ACard62xxM.kext/Contents/MacOS/ACard62xxM:                                                     Mach-O universal binary with 2 architectures: [ppc:Mach-O object ppc] [i386:Mach-O object i386]
ACard62xxM.kext/Contents/MacOS/ACard62xxM (for architecture ppc):    Mach-O object ppc
ACard67162.kext/Contents/MacOS/ACard67162:                                                     Mach-O universal binary with 2 architectures: [ppc:Mach-O object ppc] [i386:Mach-O object i386]
ACard67162.kext/Contents/MacOS/ACard67162 (for architecture ppc):    Mach-O object ppc
ACard671xSCSI.kext/Contents/MacOS/ACard671xSCSI:                                               Mach-O universal binary with 2 architectures: [ppc:Mach-O object ppc] [i386:Mach-O object i386]
ACard671xSCSI.kext/Contents/MacOS/ACard671xSCSI (for architecture ppc):    Mach-O object ppc
ACard6885M.kext/Contents/MacOS/ACard6885M:                                                     Mach-O universal binary with 2 architectures: [ppc:Mach-O object ppc] [i386:Mach-O object i386]
ACard6885M.kext/Contents/MacOS/ACard6885M (for architecture ppc):    Mach-O object ppc
ACard68xxM.kext/Contents/MacOS/ACard68xxM:                                                     Mach-O universal binary with 2 architectures: [ppc:Mach-O object ppc] [i386:Mach-O object i386]
ACard68xxM.kext/Contents/MacOS/ACard68xxM (for architecture ppc):    Mach-O object ppc
ALF.kext/Contents/MacOS/ALF:                                                                   Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
ALF.kext/Contents/MacOS/ALF (for architecture ppc):    Mach-O object ppc
ATTOCelerityFC.kext/Contents/MacOS/ATTOCelerityFC:                                             Mach-O universal binary with 3 architectures: [ppc:Mach-O object ppc] [x86_64:Mach-O 64-bit kext bundle x86_64]
ATTOCelerityFC.kext/Contents/MacOS/ATTOCelerityFC (for architecture ppc):    Mach-O object ppc
ATTOCelerityFC8.kext/Contents/MacOS/ATTOCelerityFC8:                                           Mach-O universal binary with 3 architectures: [ppc:Mach-O object ppc] [x86_64:Mach-O 64-bit kext bundle x86_64]
ATTOCelerityFC8.kext/Contents/MacOS/ATTOCelerityFC8 (for architecture ppc):    Mach-O object ppc
ATTOExpressPCI4.kext/Contents/MacOS/ATTOExpressPCI4:                                           Mach-O universal binary with 3 architectures: [ppc:Mach-O object ppc] [x86_64:Mach-O 64-bit kext bundle x86_64]
ATTOExpressPCI4.kext/Contents/MacOS/ATTOExpressPCI4 (for architecture ppc):    Mach-O object ppc
ATTOExpressSASHBA.kext/Contents/MacOS/ATTOExpressSASHBA:                                       Mach-O universal binary with 3 architectures: [ppc:Mach-O object ppc] [x86_64:Mach-O 64-bit kext bundle x86_64]
ATTOExpressSASHBA.kext/Contents/MacOS/ATTOExpressSASHBA (for architecture ppc):    Mach-O object ppc
ATTOExpressSASHBA2.kext/Contents/MacOS/ATTOExpressSASHBA2:                                     Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc]
ATTOExpressSASHBA2.kext/Contents/MacOS/ATTOExpressSASHBA2 (for architecture ppc):    Mach-O object ppc
ATTOExpressSASRAID.kext/Contents/MacOS/ATTOExpressSASRAID:                                     Mach-O universal binary with 3 architectures: [ppc:Mach-O object ppc] [x86_64:Mach-O 64-bit kext bundle x86_64]
ATTOExpressSASRAID.kext/Contents/MacOS/ATTOExpressSASRAID (for architecture ppc):    Mach-O object ppc
Accusys6xxxx.kext/Contents/MacOS/Accusys6xxxx:                                                 Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
Accusys6xxxx.kext/Contents/MacOS/Accusys6xxxx (for architecture ppc):    Mach-O object ppc
AppleFSCompressionTypeZlib.kext/Contents/MacOS/AppleFSCompressionTypeZlib:                     Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
AppleFSCompressionTypeZlib.kext/Contents/MacOS/AppleFSCompressionTypeZlib (for architecture ppc):    Mach-O object ppc
AppleFWAudio.kext/Contents/MacOS/AppleFWAudio:                                                 Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc]
AppleFWAudio.kext/Contents/MacOS/AppleFWAudio (for architecture ppc):    Mach-O object ppc
AppleLSIFusionMPT.kext/Contents/MacOS/AppleLSIFusionMPT:                                       Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
AppleLSIFusionMPT.kext/Contents/MacOS/AppleLSIFusionMPT (for architecture ppc):    Mach-O object ppc
AppleMatch.kext/Contents/MacOS/AppleMatch:                                                     Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
AppleMatch.kext/Contents/MacOS/AppleMatch (for architecture ppc):    Mach-O object ppc
AppleMikeyHIDDriver.kext/Contents/MacOS/AppleMikeyHIDDriver:                                   Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
AppleMikeyHIDDriver.kext/Contents/MacOS/AppleMikeyHIDDriver (for architecture ppc):    Mach-O object ppc
AppleSmartBatteryManager.kext/Contents/MacOS/AppleSmartBatteryManager:                         Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
AppleSmartBatteryManager.kext/Contents/MacOS/AppleSmartBatteryManager (for architecture ppc):    Mach-O object ppc
AppleUSBDisplays.kext/Contents/MacOS/AppleUSBDisplays:                                         Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
AppleUSBDisplays.kext/Contents/MacOS/AppleUSBDisplays (for architecture ppc):    Mach-O object ppc
ArcMSR.kext/Contents/MacOS/ArcMSR:                                                             Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
ArcMSR.kext/Contents/MacOS/ArcMSR (for architecture ppc):    Mach-O object ppc
CalDigitHDProDrv.kext/Contents/MacOS/CalDigitHDProDrv:                                         Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
CalDigitHDProDrv.kext/Contents/MacOS/CalDigitHDProDrv (for architecture ppc):    Mach-O object ppc
HighPointIOP.kext/Contents/MacOS/HighPointIOP:                                                 Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
HighPointIOP.kext/Contents/MacOS/HighPointIOP (for architecture ppc):    Mach-O object ppc
HighPointRR.kext/Contents/MacOS/HighPointRR:                                                   Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc]
HighPointRR.kext/Contents/MacOS/HighPointRR (for architecture ppc):    Mach-O object ppc
IOBluetoothFamily.kext/Contents/MacOS/IOBluetoothFamily:                                       Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
IOBluetoothFamily.kext/Contents/MacOS/IOBluetoothFamily (for architecture ppc):    Mach-O object ppc
IOBluetoothHIDDriver.kext/Contents/MacOS/IOBluetoothHIDDriver:                                 Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
IOBluetoothHIDDriver.kext/Contents/MacOS/IOBluetoothHIDDriver (for architecture ppc):    Mach-O object ppc
IOFireWireAVC.kext/Contents/MacOS/IOFireWireAVC:                                               Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
IOFireWireAVC.kext/Contents/MacOS/IOFireWireAVC (for architecture ppc):    Mach-O object ppc
IOFireWireFamily.kext/Contents/MacOS/IOFireWireFamily:                                         Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc]
IOFireWireFamily.kext/Contents/MacOS/IOFireWireFamily (for architecture ppc):    Mach-O object ppc
IOFireWireSBP2.kext/Contents/MacOS/IOFireWireSBP2:                                             Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
IOFireWireSBP2.kext/Contents/MacOS/IOFireWireSBP2 (for architecture ppc):    Mach-O object ppc
IOFireWireSerialBusProtocolTransport.kext/Contents/MacOS/IOFireWireSerialBusProtocolTransport: Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
IOFireWireSerialBusProtocolTransport.kext/Contents/MacOS/IOFireWireSerialBusProtocolTransport (for architecture ppc):    Mach-O object ppc
IOSCSIArchitectureModelFamily.kext/Contents/MacOS/IOSCSIArchitectureModelFamily:               Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
IOSCSIArchitectureModelFamily.kext/Contents/MacOS/IOSCSIArchitectureModelFamily (for architecture ppc):    Mach-O object ppc
IOVideoFamily.kext/Contents/MacOS/IOVideoFamily:                                               Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
IOVideoFamily.kext/Contents/MacOS/IOVideoFamily (for architecture ppc):    Mach-O object ppc
JMicronATA.kext/Contents/MacOS/JMicronATA:                                                     Mach-O universal binary with 2 architectures: [ppc:Mach-O object ppc] [i386:Mach-O object i386]
JMicronATA.kext/Contents/MacOS/JMicronATA (for architecture ppc):    Mach-O object ppc
PPP.kext/Contents/MacOS/PPP:                                                                   Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
PPP.kext/Contents/MacOS/PPP (for architecture ppc):    Mach-O object ppc
SoftRAID.kext/Contents/MacOS/SoftRAID:                                                         Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
SoftRAID.kext/Contents/MacOS/SoftRAID (for architecture ppc):    Mach-O object ppc
mcxalr.kext/Contents/MacOS/mcxalr:                                                             Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [ppc:Mach-O object ppc]
mcxalr.kext/Contents/MacOS/mcxalr (for architecture ppc):    Mach-O object ppc

We can try to load newer Kernel on older build of system... But i think the only way is to build our own kernel.

 

[Larsvonhier]

I'm also tried to mess up with IOPCIFamily.kext from 10.5.8 to 10A190...and get killed OS completely. But now i'm fully understand HOW kernel is going detect Macintosh model.
View attachment 919076

AppleMacRisc2PE - is the extensions for PowerPC Macs. As this extension related to Platform Expert. ("PE" - Platform Expert).

And now, i think, we have only few ways: Rebuild IOPCIFamily.kext with AGP support inside, or call Netkas to share it's own code of ATY_Init.kext to rebuild it to PowerPC platform...

Good idea, I think Netkas might help either by supplying source code (it´s very old by now, so perhaps no real big deal for him) or he might be willing to compile it for PPC for us. How about these options, @netkas ? Interested in helping out here... we´d be delighted to hear from you!

About the AppleMacRisc_PE: On G5 it´s AppleMacRisc4PE, so at least this selection is made by... ...kernel? ...Boot.X?
[automerge]1590564152[/automerge]
About the yet "unsupported" Nvidia´s running on software CI and no QE (A96 and A190):
GeForce extension and the appropriate NVDA HAL (10...50) get loaded, but no further acceleration is effective.
(In fact, a tiny advantage seems noticeable in comparison to not loading the kexts, but GUI is far from being as smooth as with the ATIs).

 

[armdn]

Good idea, I think Netkas might help either by supplying source code (it´s very old by now, so perhaps no real big deal for him) or he might be willing to compile it for PPC for us. How about these options, @netkas ? Interested in helping out here... we´d be delighted to hear from you!

About the AppleMacRisc_PE: On G5 it´s AppleMacRisc4PE, so at least this selection is made by... ...kernel? ...Boot.X?
[automerge]1590564152[/automerge]
About the yet "unsupported" Nvidia´s running on software CI and no QE (A96 and A190):
GeForce extension and the appropriate NVDA HAL (10...50) get loaded, but no further acceleration is effective.
(In fact, a tiny advantage seems noticeable in comparison to not loading the kexts, but GUI is far from being as smooth as with the ATIs).

NVDAHAL* group of kext is detectors of what graphic card you have, the GeForce.kext and its GeForceGA.bundle (GeForce Graphic Accelerator) is responsible for QE/CI.

Selection of RiscPE is made kernel by detection of model through IOPCIFamily via IOKit’s PlatformExpert. Platform Expert code also present in XNU.

 

[vddrnnr]

Hi @armdn,

I think I can only change the frameworks in 096 because as @Larsvonhier
said any change of frameworks in 190 breaks boot ( we don't know why ).
I think he also tried it in 190 first and there was no effect but 096 yes.
@Larsvonhier I'm remembering correctly, right?

Best regards,
voidRunner

 

[vddrnnr]

Hi @Larsvonhier and @armdn,

I'm using IOPCIFamily from Leopard but they seem to be the same??

Best regards,
voidRunner

 

[Steven Nixon]

I'm trying to run this on a mac mini G4 1.25GHz model and I get a KP saying "unable to find driver for this platform" I am trying to run the 10A96 installer. This also happens when installing 10A190

 

[armdn]

Hi @armdn,

I think I can only change the frameworks in 096 because as @Larsvonhier
said any change of frameworks in 190 breaks boot ( we don't know why ).
I think he also tried it in 190 first and there was no effect but 096 yes.
@Larsvonhier I'm remembering correctly, right?

Best regards,
voidRunner

Ah! That explain everything! I think in 10A190 Apple started big transition to new code, so that's why Finder so buggy, many frameworks empty, etc..
[automerge]1590588657[/automerge]

Hi @Larsvonhier and @armdn,

I'm using IOPCIFamily from Leopard but they seem to be the same??

Best regards,
voidRunner

That interesting. If you use IOPCIFamily from Leopard, then what disables AGP?! That a new question.

 

[vddrnnr]

Hi @armdn,

I've been reading a few things about the ATI_init from netkas and if
I understook correctly what is happening is that:

1. The graphics cards are being miss detected in the wrong bus ( PCI instead of AGP )
2. Some information that should appear in the IORegistry is missing

These are the two "infos" ( generally speaking) that ATI_init "injects" in the registry on boot
and that make the kexts / frameworks detect properly the graphics card.

In the case of my Radeon 9700 it shows in AGP I don't know if the Geforces are
doing the same ( @Larsvonhier can you check your System Profiles for your system
with a Gefirce and see if it says AGP or PCI ).

I think that if @netkas could "release" the code or help us creating a new version for PPC
it should work as the problem is the same as with Intel Hacks with AGP graphics cards in SL.

Best regards,
voidRunner

 

[Larsvonhier]

I'm trying to run this on a mac mini G4 1.25GHz model and I get a KP saying "unable to find driver for this platform" I am trying to run the 10A96 installer. This also happens when installing 10A190View attachment 919127

Set the checkmark "erase volume" (or similar) in disk utilities when you clone back the image to the destination. This forces a block copy instead of file copy mode. Pls. try again this way, it should work then!

 

[Steven Nixon]

Set the checkmark "erase volume" (or similar) in disk utilities when you clone back the image to the destination. This forces a block copy instead of file copy mode. Pls. try again this way, it should work then!

So modify the installer then create a dmg and write it?

 

[Larsvonhier]

So modify the installer then create a dmg and write it?

Generally there are two ways now: Either fetch the Installer (for A96 or A190) and modify them as described on the first page(s) or get the pre-patched Installer for i.e. A96 (only server build, at the moment). When cloning either of them back to your install volume (that you´d attach to the target system via Firewire or USB (not possible to boot on older Macs from USB!) you´ll have to make sure that you set that checkmark in disk utilities, otherwise boot might fail in many cases.