Anyone got a spare Beige G3 ROM?

[croissantking]

Have you tried the Radeon 7000?

Do you really not have any other PCI cards? A VillageTronic? Radius?

I really don’t. I had a Voodoo 3 PCI a long time ago…

 

[Snial]

Going back to the title:

Anyone got a spare Beige G3 ROM?​

Does it matter what colour the ROM is?

Bah-dum! Tishhhh!

 

[Phipli]

Going back to the title:

Anyone got a spare Beige G3 ROM?​

Does it matter what colour the ROM is?

Bah-dum! Tishhhh!

I hope you're proud of yourself

 

[joshc]

Going back to the title:

Anyone got a spare Beige G3 ROM?​

Does it matter what colour the ROM is?

Bah-dum! Tishhhh!

 

[croissantking]

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.

 

[croissantking]

Rev A. support for the Rage Pro seems rough - I get some weird behaviour with a second graphics card installed.

 

[Arbee]

Don't PCI graphics cards run out of their own driver in the card's ROM? I guess there could be a bug in some base OF word in Rev A that messes up the card's OF driver though.

 

[croissantking]

Don't PCI graphics cards run out of their own driver in the card's ROM? I guess there could be a bug in some base OF word in Rev A that messes up the card's OF driver though.

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.

 

[Phipli]

Don't PCI graphics cards run out of their own driver in the card's ROM? I guess there could be a bug in some base OF word in Rev A that messes up the card's OF driver though.

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.

 

[croissantking]

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?

 

[Phipli]

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.

 

[croissantking]

For the ATY,mach64_3DUPro, The older ROM has version 1.49 while the newer ROMs have 1.53.

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.

 

[Phipli]

With a monitor connected just to the Rage Pro, after the desktop loads the system will crash with a green screen or no display.

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.

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.

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.