3.1.4 dual RTG issue (Vampire + ZZ9000)

[ProfPlum]

My A2000 is equipped with both a Vampire and a ZZ9000.
I switch between RTG cards using a script (+reboot) - which basically just swaps Picasso96Settings.

By accident, I noticed that each of the monitor devices has a tool type to specify P96Settings file.

So, I now have 2 settings files. One for the ZZ9000, another for the vampire.
This allows me to select any screen mode via the ScreenMode prefs app.

There is one problem I am running into:
When I select 'Test' for a given screen mode, my computer will hang(?) on a black screen. When I 'use'/'save' a screen mode, all is fine.
[Update/Clarification] It hangs after it returns from the Test Screen. At this point, all I see is a black screen.


Has anyone else run into this issue?


Second question:

When playing a game, how do I know the game is actually using the Vampire RTG. Are screen mode priorities assigned via the Picasso96Mode app ?

[trixster]

Yep, I noticed this issue when using both a zz9000 and voodoo3 in the same machine.

If using the zz9000 as the primary display card, if I selected a game or program that required a voodoo3 screenmode it would switch correctly, but then upon quitting the game the Voodoo3 screen would close but the zz9000 workbench would remain blank (other than the pointer). A handover of sorts wasn’t working properly.

I notified the fw writer for the zz9000 and they issued a custom fw with a fix (based on the current 1.8). So it’s worth you contacting BNU (the fw developer) to see if he can implement this fix into the drivers full time

[ProfPlum]

Originally Posted by trixster

Yep, I noticed this issue when using both a zz9000 and voodoo3 in the same machine.

If using the zz9000 as the primary display card, if I selected a game or program that required a voodoo3 screenmode it would switch correctly, but then upon quitting the game the Voodoo3 screen would close but the zz9000 workbench would remain blank (other than the pointer). A handover of sorts wasn’t working properly.

I notified the fw writer for the zz9000 and they issued a custom fw with a fix (based on the current 1.8). So it’s worth you contacting BNU (the fw developer) to see if he can implement this fix into the drivers full time

So you are saying this is known issue with the ZZ9000 driver.
Thank-you for the info.

Sure. I will speak to Bnu.

[Thomas Richter]

What are the values of the INDISPLAYCHAIN tooltypes of the affected monitor icons?

[ProfPlum]

Originally Posted by Thomas Richter

What are the values of the INDISPLAYCHAIN tooltypes of the affected monitor icons?

There is a DISPLAYCHAIN property. It's set to Yes for both.

[Thomas Richter]

In such a case, it is really an issue of the ZZ9000 firmware not passing the chip set video through. Nothing I can do from the P96 side. From P96, it is just a simple "switch" that gets disabled whenever a board is going "off the chain".

[trixster]

Yes, we tried DISPLAYCHAIN with zz9000/Voodoo3, it did not help. A change to the zz9000 fw was necessary