This hint worked for me. Now if some of "Open Firmware" experts can tell us how to make this change permanent so it survive reboot.

---
Andrei Tchijov
Leaping Bytes, LLC

[ Reply to This | # ]

Note: I am *far* from Open Firmware expert, so this may well be completely useless, and I *certainly* wouldn't recommend messing with this without a great deal more prior research, but:

From what I (think I) know, if this were to be made persistent, it would likely be done via nvram (non-volatile ram). You can check nvram variables via `nvram -p` - on my system, this lists a variable "ram-size" as a hex number tht reflects the amount of memory I have installed (0x40000000, or one GiB). I *highly* doubt just changing this to whatever your ram size should be would do it, but it seems like it might potentially be involved.

(Also note - I don't have this particular problem, so my system may be different than that of people who do have the problem.)

[ Reply to This | # ]

I've got a PowerBook G4 with two 1GB DIMMs. Was this the right syntax to use?

0> dev /memory
0> 0 encode-int 40000000 encode-int encode+
2> 40000000 encode-int 40000000 encode-int encode+
4> encode+
2> " reg" delete-property
2> " reg" property
0> mac-boot

That got me booted with both recognized, but when memory usage got to about half (according to Activity Monitor) the system completely froze. Thanks

[ Reply to This | # ]