Sonnet 7200 PCI programming

[torsti76]

Originally Posted by grelbfarlk

Does your ZZ900 have the 2.5V(?) fix done to it? Adding Zorro cards should not improve the situation, get the PCI side working first. Also are you using the Molex drive power connector on the Prometheus busboard?
Again, I'm not sure about what works with the Prometheus, in Wrangler's videos it looks like he's putting the Voodoo in the middle slot and the PPC card in the top.

Yes, I've done the 1.8V fix on the ZZ9000.

Molex power is in place. Will try with the Voodoo and Apocalypse swapped next.

What's really bugging me is that inter-PCI communication seems somewhat defective. I.e. neither Warp3D with the Apocalypse nor, say, OpenPCI ethernet is working properly. The latter needing DMA access to the Voodoo memory, which is for sure initiated by the prometheus.library but seemingly arbitrated by the FPGAs on the board...

[Hedeon]

Use prometheus library 3.1 to test dma. Maybe something was broken in the update. I cannot test as I don't have cards that need DMA.

[trixster]

I have to have a zorro card in place in order to get the zz9000 working with the machine. Without a zorro card there seems to be a clash between Prometheus and zz9000 over address space.

[torsti76]

Originally Posted by Hedeon

Use prometheus library 3.1 to test dma. Maybe something was broken in the update. I cannot test as I don't have cards that need DMA.

Will do, thanks for the tip! OTOH, @Wrangler is using DMA successfully with your version of the library so I still suspect a hardware problem.

[torsti76]

Originally Posted by trixster

I have to have a zorro card in place in order to get the zz9000 working with the machine. Without a zorro card there seems to be a clash between Prometheus and zz9000 over address space.

AFAIK, Lukas spent lots of time to get the Z III timing right for the ZZ (and there are people saying it's still not entirely correct). But that's only guesswork.

Supposedly, for you Warp3D is working without the two Zorro cards, isn't it?

[trixster]

Yeah, with both zz9000 and prisma removed the ppc/voodoo still work fine for warp3d. I don’t think they affect anything pci side.

With no other zorro cards in the machine I think the zz9000 and Prometheus fight for address space which causes the machine to refuse to boot. The prisma just gets in there first and takes address space which then means there’s no longer a conflict between the Prometheus (immovable object) and zz9000 (unstoppable force). Something like that anyway.

[torsti76]

Originally Posted by trixster

Yeah, with both zz9000 and prisma removed the ppc/voodoo still work fine for warp3d. I don’t think they affect anything pci side.

I'll do some rework on the Buster socket and the FPGA soldering tonight. Wouldn't be the first time with this project my soldering isn't right on spot... ;-)

I also plan on reflashing the Alteras with an explicit erase up front.

With no other zorro cards in the machine I think the zz9000 and Prometheus fight for address space which causes the machine to refuse to boot. The prisma just gets in there first and takes address space which then means there’s no longer a conflict between the Prometheus (immovable object) and zz9000 (unstoppable force). Something like that anyway.

Yeah, seems plausible. I never got the ZZ9000 to run stable in my A4000T, but since Lukas is constantly improving the firmware and drivers, I'm sure all issues will get sorted sooner or later.

[jkdsteve]

EDIT: THIS IS AN AMAZING PIECE OF SOFTWARE, THANK YOU HEDEON (and bug squashers)

Quick question - anyone able to run the StormMESA (3.1?) stuff with 3D hardware acceleration on PPC side? I'm running s Voodoo3 and a 128MB G3 (!) card on a RAMIX but not sure it's fully supported but not up to speed on all the codenames.

If I disable (i.e. rename) WARP3DPPC.library they all run fine, but I'm assuming without 3D access, if I enable it then only 'bounceppc' will run (does not use any 3D HW acceleration anyway AFAIK.)

I am able to get other Warp3DPPC stuff working - Wipeout2097, qlblitzquake_WOS, PaybackWOS to name a few, Freespace - though the colours/screen is odd on that. I can also run Quake for hours so believe is relatively stable.

Note: all of the StormMESA stuff works just fine with the 68k version of Warp3D.library present and loaded.

I am fairly confident in my GFX card and other setup, given what works so far, it took em 2 or 3 days of experimenting, mostly finding out old Quake binaries were a no-0go

I'm not interested in the MESA stuff per-se but I have a lot of the PPC software showing the similar Data Storage Exception error and if there's a solution, that'd be great.

The piece of software I'd love to run is Tornado3D PPC (Have both v2 and v3 from Eyelight) but that's ppclibemu and probably a whole other bunch of issues on top.

NOTE: this is not an A4000T, just happens to have those 3.1.4 ROMS, it's an A4000Di Mediator

Config attached, here's the error:

Task name: 'isosurfppc_PPC' Task address: 6878E520
Exception: Data Storage

SRR0: 68D89790 SRR1: 0000F030 MSR: 00003030 HID0: 0000C0A4
PVR: 800C1104 DAR: 00000000 DSISR: 42000000 SDR1: 07F0000F
DEC: 00079CFB TBU: 00000000 TBL: 455122EE XER: 00000000
CR: 48000828 FPSCR: 82024000 LR: 68D8974C CTR: 68D8B6A8

R0-R3: 03D80018 68820918 68DD12B0 68DD53E0 IBAT0: 0000003E 00000002
R4-R7: 68D89720 00000000 00000000 68DD5740 IBAT1: 640003FF C4000002
R8-R11: 9BC28000 9BC28024 00000000 00100000 IBAT2: 6820003F 00200002
R12-R15: 68644250 68DD53E0 68901CC8 68909248 IBAT3: 00000000 00000000
R16-R19: 68994A40 68DD3260 68994A40 00000000 DBAT0: 0000003E 00000002
R20-R23: 00000000 00000000 68994A40 00000000 DBAT1: 640003FF C4000042
R24-R27: 00000000 00000000 00000000 68DD53E0 DBAT2: 6820003F 00200022
R28-R31: 00000001 00000000 68DD1788 68820918 DBAT3: 00000000 00000000

Task name: 'Tornado3DPPC' Task address: 6873B400
Exception: Data Storage

SRR0: 6883AE50 SRR1: 0000F030 MSR: 00003030 HID0: 0000C0A4
PVR: 800C1104 DAR: 090BF330 DSISR: 42000000 SDR1: 07F0000F
DEC: 00078094 TBU: 00000000 TBL: 6F460537 XER: 00000000
CR: 44000042 FPSCR: 82008000 LR: 6883ADF0 CTR: 6883AA08

R0-R3: 6883AD40 689391E0 68700FA0 6877A108 IBAT0: 0000003E 00000002
R4-R7: 6877A318 00000000 40F0A280 00000000 IBAT1: 640003FF C4000002
R8-R11: 00000000 00000000 00000000 00000000 IBAT2: 6820003F 00200002
R12-R15: 68815110 0D0D0D0D 0E0E0E0E 0F0F0F0F IBAT3: 00000000 00000000
R16-R19: 10101010 11111111 12121212 13131313 DBAT0: 0000003E 00000002
R20-R23: 6874DCB0 00000000 68832A48 6881B9D8 DBAT1: 640003FF C4000042
R24-R27: 00000000 68820D08 00000001 68823538 DBAT2: 6820003F 00200022
R28-R31: 68821CDC 090BF304 090BF304 FFFFFFFF DBAT3: 00000000 00000000

[Hedeon]

I think you need at least FORCEVERSION being set to 3 in the warp3d env settings for stormmesa to work.

And try DisHunkPatch set to 1 in the sonnet ENV settings

[jkdsteve]

Originally Posted by Hedeon

I think you need at least FORCEVERSION being set to 3 in the warp3d env settings for stormmesa to work.

And try DisHunkPatch set to 1 in the sonnet ENV settings

DisHunkPatch does some strange things, like SysSpeed PPC causes kernel panic and coincidentally doesn't solve the issue either!

I've not heard of FORCEVERSION but I tried it and no change, so I went back to basics - what does the basic Warp3D/StormaMESA install do and I found a missing ENVAR from my setup:

LOCKMODE=3 (ENV:MESA\)

I believe this is to do with how MESA/HW accesses the bitmap and lo and behold the PPC demos work super fast now! I am halfway towards my goal and it was a configuration error on my part!

If only there were such magic for Tornado3D

[Hedeon]

StormMESA does not work correctly with Warp3D v4. Trust me if I say you need ForceVersion set to 3.

Also, you don't state which version of the powerpc library you are running.

[grelbfarlk]

It's ENVARC:warp3d/FORCEVERSION=3 to get MESA stuff working.


@jkdsteve: I have Tornado3D running sort of. I can't seem to get the 3D Accelerated mode running as it seems to require CGFX Rave. I'm not sure that it's compatible with Warp3d. There is a library for the Virge and the Permedia, the Virge requires 15-bit modes and the Permedia just fails saying that no modes are available. I'll tinker around with it a bit more.

Originally Posted by jkdsteve

DisHunkPatch does some strange things, like SysSpeed PPC causes kernel panic and coincidentally doesn't solve the issue either!

I've not heard of FORCEVERSION but I tried it and no change, so I went back to basics - what does the basic Warp3D/StormaMESA install do and I found a missing ENVAR from my setup:

LOCKMODE=3 (ENV:MESA\)

I believe this is to do with how MESA/HW accesses the bitmap and lo and behold the PPC demos work super fast now! I am halfway towards my goal and it was a configuration error on my part!

If only there were such magic for Tornado3D

[jkdsteve]

Originally Posted by Hedeon

StormMESA does not work correctly with Warp3D v4. Trust me if I say you need ForceVersion set to 3.

Also, you don't state which version of the powerpc library you are running.

YES, thank you..I did need FORCEVERSION also...I was not rigorous and made two changes at same time, bad!!!

My bad, thought it would be in the reports I attatched, it's 17.13.

[jkdsteve]

Originally Posted by grelbfarlk

@jkdsteve: I have Tornado3D running sort of. I can't seem to get the 3D Accelerated mode running as it seems to require CGFX Rave. I'm not sure that it's compatible with Warp3d. There is a library for the Virge and the Permedia, the Virge requires 15-bit modes and the Permedia just fails saying that no modes are available. I'll tinker around with it a bit more.

Yes, it is not Warp3D compatible but rather has specific libraries for Phase5 S3 and Permedia - this was a killer feature to do quick GL previews but it's not an impact to rendering. I ran that setup for sometime back in the late 90s with a CSPPC233/060 / CVPPC

I can get T3D to load, believe me that was on effort in getting a clean 3.9 system just for the hardware key to be read correctly.

It generally works but as soon as I try and render using the PPC - Data Exception that I showed. It uses PowerUP PPC, hence the need for the emulation.

if you have it rendering using PPC (Legolas.elf in Lothlorien I believe the plugin is called) then I'd love to hear more

[grelbfarlk]

I don't get a crash, but it seems to be failing writing frames to the default location RAM:T/
Changing it to a path on the HDD it renders something, but the images are just a blank pink image. I'm not sure if it's actually using the PPC however.
Under prefs it has PowerUP selected.

[jkdsteve]

Originally Posted by grelbfarlk

I don't get a crash, but it seems to be failing writing frames to the default location RAM:T/
Changing it to a path on the HDD it renders something, but the images are just a blank pink image. I'm not sure if it's actually using the PPC however.
Under prefs it has PowerUP selected.

I get the same when rendering Preview...I don't believe it's doing anything PPC wise on that setting - was intended I think for 3D HW preview perhaps.

Try changing the Render Quality settings to something other than Preview, e.g. Standard or higher.

[grelbfarlk]

Ok yeah seeing the same thing, throwing an exception when using standard renderer. I see something during loading saying it's an unknown powerpc. I tried moving the legolas.elf out of there and just leaving legolas603.elf and instead of throwing an exception it just freezes.

[jkdsteve]

Originally Posted by grelbfarlk

Ok yeah seeing the same thing, throwing an exception when using standard renderer. I see something during loading saying it's an unknown powerpc. I tried moving the legolas.elf out of there and just leaving legolas603.elf and instead of throwing an exception it just freezes.

I honestly do not remember if I *ever* had it working on my CSPPC using ppclibemu under WarpOS though.....it definitely worked on native ppc.library

Interesting that powerpc.library complains about any other version of pplibemu than 0.9d. I have several legacy that I could potentially try.

[grelbfarlk]

There's just not much that was released for ppc.library that is worth running. Now and then I'll use apdf or ProStationAudio (which I'm pretty sure the PPC is just used for MP3 mixdown).

[jkdsteve]

Originally Posted by grelbfarlk

There's just not much that was released for ppc.library that is worth running. Now and then I'll use apdf or ProStationAudio (which I'm pretty sure the PPC is just used for MP3 mixdown).

Yes, used some PowerUp stuff in the early days, datatypes, mega library, ffmpeg, movie players and early scene demos but Tornado3D is literally the only thing I'd need to run out of all of that.

I mean, it was buggy as hell when it did run but is a shame can't see what the old G3 and decent memory speed could do that isn't Quake