Leopard on G4 PowerMac3,1

[TechAndOSWorld]

Hello, I recently obtained a Sawtooth G4 (400MHz AGP), and I'm trying to install Leopard on one of the internal drives (for multiple reasons). But I can't get anything to boot.

No matter what I try, I always get the same exact kernel panic, with the error: "Unable to find driver for this platform: \"PowerMac3,1\".\n".
I tried booting from my retail DVD using LeopardAssist first, no luck. I then tried the same DVD but entered the commands manually in OF, same result. Installers downloaded from the internet also give me the same kernel panic, and so does Sorbet Leopard.

I've read posts from people who've managed to get Leopard running on their 400MHz G4s before, so I know it's possible. I just can't get it to boot on mine.

(And please, keep the comments telling me to install Tiger to yourself, I need it for some Leopard-only utilities.)

 

[Amethyst1]

Do you have OS 9 on the Sawtooth to apply the last firmware update?

http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/Power_Mac_G4/G4_FW_Update_4.2.8.smi.bin

 

[TechAndOSWorld]

yeah, I have 9.2.2 on it, but I've never updated the firmware on a PowerPC Mac before.

 

[Amethyst1]

yeah, I have 9.2.2 on it, but I've never updated the firmware on a PowerPC Mac before.

Extract the updater using StuffIt Expander, launch it and follow the instructions.

 

[TechAndOSWorld]

before I try to install it, is there a way I could dump the original firmware, in case I want to go back? I have a drive with some Mac OS X Developer Previews on it, which I'd like to be able to use in the future.

 

[eyoungren]

If you can pull the drive from the G4 and put it in an external case OR, put the Mac in Target Disk Mode and connect a firewire cable to another PowerPC Mac you could install Leopard from that Mac on to the drive and when finished put the drive back in the G4.

Of course this is assuming you have another PowerPC Mac (that is already running or capable of running Leopard), an external case and/or a Firewire cable.

And lastly, if this firmware update is necessary, you may end up with the same result after all is said and done anyway.

 

[LightBulbFun]

before I try to install it, is there a way I could dump the original firmware, in case I want to go back? I have a drive with some Mac OS X Developer Previews on it, which I'd like to be able to use in the future.

@joevt has some tools for dumping Mac BootROM's ill tag him to let him link to the latest versions (also because depending on your older BootROM version he may be interested in it for his bootrom collection and research)

 

[joevt]

My flashrom to dump the current rom requires Mac OS X 10.3 to 10.5
https://68kmla.org/bb/index.php?threads/netboot-os-9-from-a-modern-linux-server.48553/post-545788
I'm looking for any rom dumps that aren't in the "List of Power Macs.txt" file.
https://www.dropbox.com/scl/fi/ac99...ey=3aveaoq3gk89p3ka8m6xs5iua&st=3eho8nok&dl=0

I suppose you could use Open Firmware and telnet to dump the current rom. In the first post at the thread linked below, search for "rom dump", then follow the links:
https://forums.macrumors.com/thread...l-work-in-a-beige-power-macintosh-g3.2303689/

 

[TechAndOSWorld]

My flashrom to dump the current rom requires Mac OS X 10.3 to 10.5
https://68kmla.org/bb/index.php?threads/netboot-os-9-from-a-modern-linux-server.48553/post-545788
I'm looking for any rom dumps that aren't in the "List of Power Macs.txt" file.
https://www.dropbox.com/scl/fi/ac99...ey=3aveaoq3gk89p3ka8m6xs5iua&st=3eho8nok&dl=0

I suppose you could use Open Firmware and telnet to dump the current rom. In the first post at the thread linked below, search for "rom dump", then follow the links:
https://forums.macrumors.com/thread...l-work-in-a-beige-power-macintosh-g3.2303689/

I dumped it with flashrom for Tiger, but it's version 3.2.4f1, which you seem to have already.

 

[joevt]

I dumped it with flashrom for Tiger, but it's version 3.2.4f1, which you seem to have already.

Can you run the doonerom command to check the model number and checksums?

source "mac_rom_checksums.sh"
doonerom "therom.rom"

 

[Project Alice]

This 100% looks like a firmware issue to me. You said it has 3.2.4f1 on it? 4.2.8 is the latest one. I'm surprised its booting Tiger. My sawtooth wouldn't boot anything higher than 10.3 before I updated it.
Update the firmware using the directions in the update download. Leopard doesn't need anything special to work on a sawtooth besides bypassing the cosmetic 867MHz check in the installer.

Also, if your Mac still has a Rage 128 in it I would recommend replacing that too. Almost literally any other GPU that works in there will be better. Leopard has no out of the box support for that GPU, and the "hacks" that enable acceleration for it don't help all that much. The only reason they exist, is for the Rage 128 laptops capable of running Leopard.

before I try to install it, is there a way I could dump the original firmware, in case I want to go back? I have a drive with some Mac OS X Developer Previews on it, which I'd like to be able to use in the future.

This shouldn't be a problem, the OS X DP's will work on it regardless of the new firmware. That firmware update is mostly for running OS X in the first place. If anything it'll make sure the DP's work properly.

 

[TechAndOSWorld]

Can you run the doonerom command to check the model number and checksums?

source "mac_rom_checksums.sh"
doonerom "therom.rom"

the dump I got is in a .bin file, not .rom. but I ran the command, and here's the result:

2000.0217 "" 1024 dc61c45e.3db43071.3ec03864.e57fbfd5 √ "macrom.bin"

 

[joevt]

the dump I got is in a .bin file, not .rom. but I ran the command, and here's the result:

2000.0217 "" 1024 dc61c45e.3db43071.3ec03864.e57fbfd5 √ "macrom.bin"

The only 324f1 ROM I have is from the 3.2.4f1 firmware updaters. The checksum of the first part matches but not the other 3 parts. Can you PM me a copy of that ROM? I would like to see why the other parts are different. Maybe this Mac had a CPU upgrade that required a firmware patch?

 

[joevt]

I hadn't dumped the 3.2.4f1 firmware updaters before now. I should check the other firmware updaters.

The 3.2.4f1 firmware updaters have time stamp 02/18/00 09:44:35 while @TechAndOSWorld 's Sawtooth G4 AGP has time stamp 02/18/00 09:44:51

That is the only difference I could find. The difference is 16 seconds. The time stamp exists in Open Firmware in a couple places.

It also exists in the RTAS-BE section which is some kind of executable format that is loaded by a RTAS Open Firmware section.
The file command says the format of the RTAS-BE section is executable (RISC System/6000 V3.1) or obj module.

This rom is now the earliest I have that has Open Firmware code to boot FireWire and USB.