I really don’t. I had a Voodoo 3 PCI a long time ago…
-
Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.
Anyone got a spare Beige G3 ROM?
- Thread starter Phipli
- Start date
I hope you're proud of yourself
I got it to boot. The Rev A. ROM doesn’t like my 350MHz 750L CPU taken from a B/W G3. It starts fine with a 300MHz 750 CPU.
Rev A. support for the Rage Pro seems rough - I get some weird behaviour with a second graphics card installed.
With a Radeon 7000 installed, two weird things are happening:
- With a monitor connected just to the Rage Pro, after the desktop loads the system will crash with a green screen or no display.
- If one monitor is connected (either to the onboard graphics, or the R7000) it will not show the happy Mac or the early stages of the boot process. It’s behaving as if the primary monitor is the secondary, whichever graphics card it’s connected to.
None of this occurs with the Rev C ROM.
Yeah, there are known issues with that era of drivers. They sometimes conflict with other ATi cards. The 6500 is an example. ATi PCI cards don't seem to work because the built in Rage II causes issues.
Ah, do you think the Rev A G3 ROM might share some of the bugs that afflicted the 6500?
I don't think so, at least, not as badly or in all cases. I have a Rage 128 in a G3 and a Radeon 7000 in another.
Maybe it’s the 1.49 version of the ‘3DUPro’ ROM that’s buggy in that case. All Beige G3s with a Rage Pro would have shipped with a Rev B or C ROM fitted (right?), with the version 1.53 ROM. So I’m presumably using an unofficial combination.
This could be software driver issues. Given you get to the desktop. Try different versions. The ATI drivers for classic Mac OS are a nightmare. Sometimes the crash when the extension loads, sometimes they pause for a minute when they reach the desktop and other stuff.
Do you have the apple version of the driver installed (not visibly ATi branded)? That might be a conflict if you have both.
That's not a huge deal, you can usually muddle through by connecting two monitors, changing the settings, then disconnecting one.
This is probably because it thinks two monitors are connected. Other people have mentioned this.
I picked up the exact ROM pictured (it was from an eBay auction and I bought it) - it’s a confirmed Rev B.
A’s and C’s seem to be more common.
Perhaps that was an unreleased prototype revision that was scrapped in favor of the B&W?
There was some discussion of the elusive Rev 4 ROM awhile ago (earlier this year?), and I think that was the general consensus.
c
Right. That discussion is where the 0x78e842a8 checksum ROM came from.
https://68kmla.org/bb/index.php?threads/the-820-0961-a-mystery-g3-3-3v-flashrom.48746/post-548625
And it mentions the 0x78eb4234 checksum ROM.
https://68kmla.org/bb/index.php?threads/the-820-0961-a-mystery-g3-3-3v-flashrom.48746/post-547621
The checksum refers to the checksum for the first 3 MB of the ROM. There is another checksum used for the entire ROM elsewhere. The Serial Test Manager has a test that performs the checksum for the entire ROM.
https://68kmla.org/bb/index.php?threads/the-820-0961-a-mystery-g3-3-3v-flashrom.48746/post-548608
The algorithm for the entire ROM checksum may be in the DiagnosticsGossamer.s source file.
https://68kmla.org/bb/index.php?threads/skipping-the-startup-memory-test.50699/post-571099
I should look into that algorithm and add it to my rom lists for ROMs that use it.
Similar threads
