Sonnet 7200 PCI programming

[strim]

It's not strictly necessary, but highly recommended. See: https://github.com/Sakura-IT/SonnetA...nd-MMU-library .

[grelbfarlk]

Originally Posted by spudje

No, should I?

You're using CSPPC or MK3? I did say about 20 pages ago that it was necessary for me to use the MMU-Library on my CSPPC. I think a few other people in the thread are doing the same successfully on the Mk3 or CSPPC.

It's pretty much assumed at this point that people are going to be using that. Hedeon unfortunately doesn't have an Apollo 060 (or does he) or a Quikpak 060 (or does he) or any of the other exotic accelerators, that's going to make it really difficult to debug issues since he doesn't have the hardware and their proprietary 060.libraries, but at least he can target mostly the same drivers if we all use the ones with the MMU Library.

If the MMUlib absolutely didn't work on your hardware that would be another story, but I bet Thor would do his best to help you out to get it working.

[spudje]

Ok thx guys. Yes I have CSPPC. So I'll install MMUlib. I hoped I didn't have to because for what I read about this is an installation struggle all by itself. I'll keep you posted.

[Hedeon]

Originally Posted by spudje

Ok thx guys. Yes I have CSPPC. So I'll install MMUlib. I hoped I didn't have to because for what I read about this is an installation struggle all by itself. I'll keep you posted.

Before you do that....

The library was developed (initially) on a system with a normal 060 library. Unconsiously however, it WAS developed on a system with mmu.library installed. It is opened by COP (a 68K debugger) which I have running.

So, the most easy test for now is:

1) Download the mulibs archive from THOR (on Aminet).
2) Just manually install the mmu.library in libs:
3) Restart the Amiga and start without startup-sequence
4) Execute Setpatch and the program called MuScan (from the archive).
5) Check if the PCI memory range is indicated as cache inhibited (see the 512MB Mediator range in ShowConfig).

If so, just add MuScan <>NIL: or something like that to the start of the startup-sequence (after SetPatch). This then initializes the mmu.library during startup which sets the MMU correctly.

I think this is the easiest way that SHOULD work.

[Wrangler]

@grelbfarlk: I can confirm the Sonnet works great with an Apollo 4060!

[spudje]

Thanks Hedoen, that sounds very much doable.

Originally Posted by Hedeon

Before you do that....

2) Just manually install the mmu.library in libs:

To be certain, with 2 you mean simply copy the library file to libs:, correct?

[Hedeon]

Originally Posted by spudje

Thanks Hedoen, that sounds very much doable.



To be certain, with 2 you mean simply copy the library file to libs:, correct?

Yes. And only the mmu.library. Not any of the others.

You can dump the MuScan output in this thread if you are not sure what the output means.

[grelbfarlk]

-Redacted- my experiences were with old versions.
It was my experience somewhere around build ~210 that my system was not reliable with the P5 060 library. Amigenerator for instance would run for 10 minutes and crash, Warp3D would either crash on startup or run for a minute or two if I was lucky. All those problems went away when I also switched to the MMULib 060.library, that might not be the case any longer. I haven't tested this in the last couple months so if it's working for Hedeon then it's fine.

-EDIT-
I tested the CSPPC system tonight, 252 was the last build that works fine for me with MMU 060.library. 275-281 builds crashed with Warp3d, tried a few non Warp3d apps and they seemed to run ok. Will test some more tomorrow.

Originally Posted by Wrangler

@grelbfarlk: I can confirm the Sonnet works great with an Apollo 4060!

Are you also using the MMUlib and/or MMULib 060.library?

[Hedeon]

Grelbfarlk, please don't make it more difficult then it is. You really just need the mmu.library. NOT the 060 libraries.

You might be right, as I only tested it on two CSPPCs and one CSMK2, but let's test the easy solution first.

[spudje]

Yes, I'll first try the easy version. If that doesn't work I'll do the full swing version. When is the question though, busy weekend with other stuff coming up.

[trixster]

Is anyone brave enough to run with the case lid on full time? I'm still a little paranoid that the combined heat of the voodoo 3 and sonnet will cause long term issues.

With that in mind, I've ordered a replacement heatsink/fan for a spare Voodoo3 I have. It's 7mm deep so I hope it'll fit ok with enough clearance for the pci card below.

[grelbfarlk]

Originally Posted by trixster

Is anyone brave enough to run with the case lid on full time? I'm still a little paranoid that the combined heat of the voodoo 3 and sonnet will cause long term issues.

With that in mind, I've ordered a replacement heatsink/fan for a spare Voodoo3 I have. It's 7mm deep so I hope it'll fit ok with enough clearance for the pci card below.

Both of my systems are running with the case on, desktop and tower.

[spudje]

I guess by the time I have it all running I will also be holding my breath when closing things up. But that's why I am considering drilling wholes in the Sonnet bracket and putting some fans in there. Next to the Sonnet & Voodoo I have the CSPPC PPC that joins the heating fun.

[Hedeon]

Originally Posted by trixster

Is anyone brave enough to run with the case lid on full time? I'm still a little paranoid that the combined heat of the voodoo 3 and sonnet will cause long term issues.

With that in mind, I've ordered a replacement heatsink/fan for a spare Voodoo3 I have. It's 7mm deep so I hope it'll fit ok with enough clearance for the pci card below.

I have run it prolonged times with the cover closed. And the A3000 is even more cramped.

HOWEVER:

1) I have blown up 1 Voodoo3 card in that period
2) The chip which does the mouse movements becomes unsettled once in a while which give jittery mouse movements (fixed now 2 times by pressing down on the chip).

I'm running it partly open now (slide open to reveal the PCI slots, bu the zorro slots are still covered) because I have to exchange cards a few times a week. And the cover can only be removed after removing mouse, keyboard.....Call me lazy.

[Hedeon]

Originally Posted by grelbfarlk

-EDIT-
I tested the CSPPC system tonight, 252 was the last build that works fine for me with MMU 060.library. 275-281 builds crashed with Warp3d, tried a few non Warp3d apps and they seemed to run ok. Will test some more tomorrow.

Can you post or point me to an up-to-date MuScan output?

[Wrangler]

Case on here too but with a new heatsink and fan much like the one in your pic. Removing the Voodoo heatsink is "fun".

[spudje]

Originally Posted by grelbfarlk

-EDIT-
I tested the CSPPC system tonight, 252 was the last build that works fine for me with MMU 060.library. 275-281 builds crashed with Warp3d, tried a few non Warp3d apps and they seemed to run ok. Will test some more tomorrow.

Mmm, so maybe my issue is not MMU related. I have the same behaviour without MMUlib.

[Hedeon]

You've tested only with Gears_PPC?

[Wrangler]

Originally Posted by grelbfarlk

Are you also using the MMUlib and/or MMULib 060.library?

This is using MMUlib plus the MMUlib 060.library, and the 4060 runs fine. Although I'm not convinced either one is totally necessary.

[spudje]

Originally Posted by Hedeon

You've tested only with Gears_PPC?

Yes. I'll check with a demo or so too. Not yet in the mood of installing games before I'm sure all works.