Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hey that's not true.


(Do note that the above command is for my configuration - 2x1GB, 6x4GB - if you want something different you'll have to adjust it)

You have to check first if the module numbers are recognised though.

This is an OpenFirmware hack btw.

View attachment 2107775

It's not fully 32 because it needs at least 2 sticks of not 4 GB to boot the system (I have 2x1 - but you can in theory put 2x2 as well).

However the speed may be low (I'm not sure - they are 266 for me for the 4GB ones). You can check this info with:

dev /memory

.properties

It all came from here btw:


It's a 64 bit offset - then 32 bit size. You basically need to query it first from .properties and add up the additional sticks.

You want to keep the offsets aligned though and and the size at maximum 0xF0000000 (you are losing like 0x10000000 bytes for each 4GB stick).

If you don't align them akin to my post - the system will crash after peeking past the original low capacity x2 sticks.

And overall I suggest learning Forth:


(But you can just use my command as well - I currently have an ramsc script in boot-command)

\ comment

Your extend ram command

boot sd0:,\\:tbxi



So it extends the ram and then it boots from whatever.

Your boot-command should be:

setenv boot-command boot sd0:,\ramsc

Where ramsc is the file you have put your script in.

NVRAMRC - doesn't work here. You need to do it after that.

And also if you have linux (and use unsupported OS X GPU) I suggest making 2 scripts - one without the boot in the end so you can easily source yourself and boot other OS from the OpenFirmware terminal if needed.

If you have any questions - do please ask but as I've stated in the beginning first post your

" dimm-info" get-active-property

.s

(Check the address here)

ffa322b8 400 dump

(Where ffa322b8 is from above)

This will tell you the ram models - check if they are correct.


TL;DR:

You boot from 2x <4GB sticks (on first 2 slots - which are the one closest to each other on both sides in the center) (hope that succeeds and you don't hear the telephone beep - you may need to try multiple times then - or buy Samsung sticks (or the same on as I have because they worked for me - models here (in the hex dump)- https://forums.macrumors.com/threads/overclocking-the-g5-cpu.2363051/post-31622390 ))

Rest of the sticks are 4GB sticks.

You then have (preferably) a boot-command that runs a script on your disk which extend the registered ram and boot OS.

Then you (preferably) start compiling Webkit on all cores on Gentoo and test if it works (if it hangs and crashes (after you have exceeded your original low capacity sticks size) you probably haven't aligned the offsets and sizes).
Very enlightening! Will definitely delve into this. I thought I had read somewhere that there was an OF hack but couldn't put my finger on it and thought I must have dreamt it until your post, thanks a lot!

Out of curiosity if you don't do the OF hack, do your 4Gb Samsung sticks get detected at all? Did you try anything else other than M395T5160FB4-CE7? Those are low density chips, did you try high density ones? That's what I've tried so far

Cheers,
 
Very enlightening! Will definitely delve into this. I thought I had read somewhere that there was an OF hack but couldn't put my finger on it and thought I must have dreamt it until your post, thanks a lot!

Out of curiosity if you don't do the OF hack, do your 4Gb Samsung sticks get detected at all? Did you try anything else other than M395T5160FB4-CE7? Those are low density chips, did you try high density ones? That's what I've tried so far

Cheers,
Ah so they are slow by nature then? Well then that's all sorted out.

No actually even with the OF hack the slots shows empty in the HW info from OS X (if that's what you're asking).

You need to execute the commands I've shown in OF to see if they are spitting up model number like mine (because I had some cheap ones that didn't even do that).
 
Ah so they are slow by nature then? Well then that's all sorted out.

No actually even with the OF hack the slots shows empty in the HW info from OS X (if that's what you're asking).

You need to execute the commands I've shown in OF to see if they are spitting up model number like mine (because I had some cheap ones that didn't even do that).
I hadn't been keeping up with this great post, my bad!

Yes they are PC2-5300. I had tried Samsung low-density ones too as those seem to be working out of the box in the very last iteration of the iMac G5 - even though they won't show up in ASP on those either

So if I understand this correctly you put this in your ofboot.b file too for Gentoo? I will switch to this post as it's where the action seems to be happening!
 
Well I use yaboot - simply mount it and then I write it there (a text file) - it needs to be recognised from OF - I think yaboot is on an ext2 but not 100% sure.
 
Well I use yaboot - simply mount it and then I write it there (a text file) - it needs to be recognised from OF - I think yaboot is on an ext2 but not 100% sure.
yaboot and grub both use small HFS partitions on Apple platforms (1 Mb in my case but can be more especially if they are made to include /boot) so that they are seen (even though yaboot requires ext2 or ext3 for boot for recent linux distros in my hands, won't work with ext4 on debian 11, Ubuntu 16.10 or OpenSUSE for some reason, even though it works with Ubuntu 16.04) and both use ofboot.b to boot in which I guess the of script can either be pasted in directly in or called, it will be visible in OF as HFS.
 
Hey that's not true.


(Do note that the above command is for my configuration - 2x1GB, 6x4GB - if you want something different you'll have to adjust it)

You have to check first if the module numbers are recognised though.

This is an OpenFirmware hack btw.

View attachment 2107775

It's not fully 32 because it needs at least 2 sticks of not 4 GB to boot the system (I have 2x1 - but you can in theory put 2x2 as well).

However the speed may be low (I'm not sure - they are 266 for me for the 4GB ones). You can check this info with:

dev /memory

.properties

It all came from here btw:


It's a 64 bit offset - then 32 bit size. You basically need to query it first from .properties and add up the additional sticks.

You want to keep the offsets aligned though and and the size at maximum 0xF0000000 (you are losing like 0x10000000 bytes for each 4GB stick).

If you don't align them akin to my post - the system will crash after peeking past the original low capacity x2 sticks.

And overall I suggest learning Forth:


(But you can just use my command as well - I currently have an ramsc script in boot-command)

\ comment

Your extend ram command

boot sd0:,\\:tbxi



So it extends the ram and then it boots from whatever.

Your boot-command should be:

setenv boot-command boot sd0:,\ramsc

Where ramsc is the file you have put your script in.

NVRAMRC - doesn't work here. You need to do it after that.

And also if you have linux (and use unsupported OS X GPU) I suggest making 2 scripts - one without the boot in the end so you can easily source yourself and boot other OS from the OpenFirmware terminal if needed.

If you have any questions - do please ask but as I've stated in the beginning first post your

" dimm-info" get-active-property

.s

(Check the address here)

ffa322b8 400 dump

(Where ffa322b8 is from above)

This will tell you the ram models - check if they are correct.


TL;DR:

You boot from 2x <4GB sticks (on first 2 slots - which are the one closest to each other on both sides in the center) (hope that succeeds and you don't hear the telephone beep - you may need to try multiple times then - or buy Samsung sticks (or the same on as I have because they worked for me - models here (in the hex dump)- https://forums.macrumors.com/threads/overclocking-the-g5-cpu.2363051/post-31622390 ))

Rest of the sticks are 4GB sticks.

You then have (preferably) a boot-command that runs a script on your disk which extend the registered ram and boot OS.

Then you (preferably) start compiling Webkit on all cores on Gentoo and test if it works (if it hangs and crashes (after you have exceeded your original low capacity sticks size) you probably haven't aligned the offsets and sizes).

By chance, do you have an idea how to try fixing this? https://forums.macrumors.com/thread...bootable.2368659/?post=31726881#post-31726881
 
Especially on later G4s for which there is only one DIMM slot available.

The Mac Mini comes to mind but I suppose that could be rationalised on the basis of space constraints. It was bemusing to discover that the Quicksilver has less RAM capacity than the Sawtooth with 1.5GB vs 2GB. I can imagine many Sawtooth users who at the time sold their machine to upgrade to the Quicksilver being annoyed at this odd downgrade in expansion.
 
  • Like
Reactions: B S Magnet
You could also debug via Fireware the kernel (IRC).
How to do that? Not something I’m knowledgeable about :)

(And this is a kernel problem, not kext one? With kexts I had some hope of an easy fix by swapping some.)

P. S. If by being worth you meant gains in performance in 10.5.8, it should be definitely worth it, as you can have x3 faster SSD, and use newer and better ones. It may not be worth with a single machine and dual boot with 10A190, unless a fix is found, of course.
 
Oh come on.

The GeForce FX Go5200, with 64MB VRAM, for a 2005 Mac pro-level laptop, was embarrassing. It used the same GPU as the 12-inch PowerBook in 2003, with its only refinement, in 2004, when VRAM was bumped from 32MB to 64. Its G5 desktop counterpart, the GeForce FX 5200 Ultra, in the 2003 and 2004 Power Mac G5s, was no less disappointing.

The only demerit for the 2005 iBooks having a Mobility Radeon 9550 is Apple only configured it with 32MB VRAM — ostensibly to distinguish the iBooks as being “inferior” to the 12-inch PowerBook. As I’ve written elsewhere on here, the 12-inch PowerBook is basically the 12-inch iBook in terms of chassis, development, design, and core features (like 10/100 Ethernet, FW400, and no more than 512MB onboard RAM), but kitted out differently (cosmetically, and also in terms of updated components like GPU and RAM) than the iBook G4 counterparts and sold at a higher price point.

Like, I’m not a PPC video expert by any metric, but even I could see the GeForce FX 5200 series in Apple products, unless offered as a base model-only option in, say, 2003–04, was a hot mess — especially given how the Mobility Radeon 9200 and 9550 were bundled with the 2005-era iBook G4 and Mac mini G4, respectively.
 
The GeForce FX Go5200, with 64MB VRAM, for a 2005 Mac pro-level laptop, was embarrassing. It used the same GPU as the 12-inch PowerBook in 2003, with its only refinement, in 2004, when VRAM was bumped from 32MB to 64. Its G5 desktop counterpart, the GeForce FX 5200 Ultra, in the 2003 and 2004 Power Mac G5s, was no less disappointing.

The only demerit for the 2005 iBooks having a Mobility Radeon 9550 is Apple only configured it with 32MB VRAM — ostensibly to distinguish the iBooks as being “inferior” to the 12-inch PowerBook. As I’ve written elsewhere on here, the 12-inch PowerBook is basically the 12-inch iBook in terms of chassis, development, design, and core features (like 10/100 Ethernet, FW400, and no more than 512MB onboard RAM), but kitted out differently (cosmetically, and also in terms of updated components like GPU and RAM) than the iBook G4 counterparts and sold at a higher price point.

Like, I’m not a PPC video expert by any metric, but even I could see the GeForce FX 5200 series in Apple products, unless offered as a base model-only option in, say, 2003–04, was a hot mess — especially given how the Mobility Radeon 9200 and 9550 were bundled with the 2005-era iBook G4 and Mac mini G4, respectively.
Any idea why was that the case?

P. S. Myself I kept wondering why Apple used 256 MB in ATI 1900 when there was a 512 MB version for PC.
 
Only a guess: it was cheap.

That was my hunch too.

Also...

Any idea why was that the case?

P. S. Myself I kept wondering why Apple used 256 MB in ATI 1900 when there was a 512 MB version for PC.

As we all know, it has not been above Apple to commit shady behaviour in terms of restricting the capabilities and potential of their products. In the case of PPC video hardware, they blocked the ability of iBooks, iMacs and eMacs to use an external display in dual or "extended desktop mode" in their firmware to push consumers towards the more costly PowerMac range instead. This shady practice was exposed by hacks which enabled the functionality on many of those machines.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.