PPC very unstable

[awe4k]

Hi,

I am having problems with my CSPPC. PPC software is quite unstable, leading to WarpOS crashes every now and then. I have not been able to run a single PPC game, and other PPC software has a tendency to crash. Sometimes I cannot even start AWeb-II (it came with OS3.9).

The setup is:

A4000D
X-Surf (original modem) connected to ADSL
Highway USB card
DCE internal scando+flickerfixer
CSPPC 060/50 + 604e/233
SCSI HD connected to CyberStorm
16Mb on mobo + 64Mb on CSPPC
NOTE: It runs with the case open

OS3.9 (kick 45.57 WB 45.3)
Poseidon V2.?

I get occasional requesters "Please insert volume DFO: in any drive" during bootup, although the jumpers on the mobo are ok.

The WarpOS crashes happen usually "during load operation" and at "memory accesses".

Any clue? Do you need more info to help me?

[nex4060]

I would remove the memory on the mainboard (the 16MB) I have a CSMKII and it was not very happy with the memory on the motherboard, after I removed it many of the crashes disapered.

[Framiga]

all those on an A4000D case? with the original PSU?

PSU fault IMHO. ("Please insert volume DFO: in any drive")

After that post wich model (P5-DCE) and wich WOS revision

[awe4k]

Hello. Yes, all of this is in the original dektop case with the original PSU. I see you suggest a lack of PSU power as one possible cause... could be. What is the cure then? Adapt an AT PSU maybe?

By the way, you mention "PSU fault IMHO. ("Please insert volume DFO: in any drive")". What is "IMHO"? Sorry, if is this an idiot question, but I am idiot. LOL.

CSPPC is from DCE. How can I know which WarpOS version do I have?

Regarding the memory on the mobo, I used to run the computer without it, and I had the same problem

[lorddef]

IMHO = in my humble opinion

Bad slang.

As I remember some people cured A1200 ppc power problems by taking power from a floppy drive power connector straight to the ppc board or something like that.

[patrik]

@awe4k:

I have a rather similar setup in my A4000D and the PSU does not have any problems with that load. I would rather suspect heat related issues as the heatsink/fan combo on the CSPPC are rather under-dimensioned which can become an issue, especially with the 233MHz model. To see if it is a heat related issue, I would advice you to do the following things and see if it gets better:
- Make sure there are a sufficent layer of thermal paste between the PPC and its heatsink (not too much, and not too little ).
- Make sure the PPC heatsink isn't dusty.
- Make sure the PPC fan is working properly.
- As you are running the A4000 without its cover, why not add a fan blowing air down on the CSPPC.

(edit):

Two more things sprung to mind, first - make sure the CSPPC and motherboard FastSlot connectors are clean and that they are connected properly. You should see no spacing between them if you check from the side. Putting some support like some stiff cardboard or similar under the motherboard under the middle section of the FastSlot connector before applying pressure to the CSPPC makes it much easier.

Secondly - the PPC acesses the memory with more aggressive timings than the 060 so try another set of memory and make sure the contacting surfaces on the SIMMs are clean.


/Patrik

[awe4k]

Hello Patrick,

Thanks for your reply. Everything you mention makes a lot of sense.

I'll try and upgrade the cooling on the processors. Also, I will modify the cover of the case in order to increase the cooling with the cover closed, and I'll post pics. I will induct air into the case by means of fans on both sides of the cover, and possibly from the rear too, on top of the "expansion" hole.

I do not know wether the connector of the CPU board is clean or not, but I know that the CS sits properly in its place and is fully inserted. I'd rather avoid the hassle of removing it to check the cleanliness of the contacts. The more I know the A4000's case, the more I like the A2000's case. OH!

In reply to the other post, the memory I have is 60ns, but I'll try another set of SIMMS whenever I have a chance.

Thanks all! I'll re-post in case there were news.

[patrik]

@awe4k:

Here is a good page describing how to improve the cooling of the A4000D case. The improvement in section 1 and 4 suggested on that page are most important as that greatly affects the total amount of air that can flow through the case. The suggested modifications to the powersupply on that page should be sufficent, though here and here you can see some a bit more crazy modifications that can be done to the A4000D powersupply to improve airflow. Whatever you do, make sure you create a balance between the air that can flow in and the air that can flow out of the case.

Some other good things you can do to improve on the air-flow are:
- Remove unused expansions.
- Buy rounded SCSI and IDE-cables and make sure they are not unecessary long.
- Plan and do the cable-routing very well.
- Consider removing the CD-ROM if you have one and use an external model instead, shouldn't be a problem as you have a SCSI-interface.


/Patrik

[awe4k]

Hello again,

While it is clear that cooling is an issue, it seems that the problems in my case do not come from this point. I just started the Amiga (thus it is cold), tried to run Heretic II, and this is what I got:

PowerPC Data access exception (load operation)
Page fault - Access to 65757045
The excepting instruction is located at 08BF43F0
Task name: 'Heretic2_PPC5'  Task address: 084ADC70  Task ID: 102

SRR0: 08BF43F0    SRR1:  0000F070     MSR:   00003040    HID0: 0000C084
PVR:  00091203    DAR:   65757045     DSISR: 40000000    SDR1: 08580007
DEC:  0000208E    TBU:   00000000     TBL:   0702C9E2    XER:  00000000
CR:   40000422    FPSCR: 82002000     LR:    08BF4458    CTR:  00000000

R0-R3:   00006163 087E84A0 084AE128 00000000   IBAT0: 00000000 00000000
R4-R7:   08380276 00000400 000003B8 0886C000   IBAT1: 00000000 00000000
R8-R11:  0886D658 08B80000 00000051 00000038   IBAT2: 00000000 00000000
R12-R15: 00000008 087E8E00 083E6048 08BF7080   IBAT3: 00000000 00000000
R16-R19: 08BF7090 08C301C8 08C30DC4 08C300B4   DBAT0: 00000000 00000000
R20-R23: 08BF87E8 08BF848C 08BF8480 08870E44   DBAT1: 00000000 00000000
R24-R27: 08870E9C 08B7A8BC 08C50000 00000000   DBAT2: 00000000 00000000
R28-R31: 08940000 08950000 6575703B 6575703B   DBAT3: 00000000 00000000

F0-F3:     1.0000 E 0      1.0000 E 0     QNAN             5.4979 E-14
F4-F7:     1.0000 E 0      1.0000 E 1      6.7553 E 15     2.1326 E-9  
F8-F11:    3.3333 E-1      2.3090 E-5      3.0000 E 0      2.1474 E 9  
F12-F15:   1.0000 E 0      4.5036 E 15     0               0          
F16-F19:   0               0               0               0          
F20-F23:   0               0               0               4.5036 E 15
F24-F27:   7.8125 E-3      8.0000 E 0      6.5536 E 4      5.2428 E 5  
F28-F31:   3.1250 E-2      2.0000 E 0      3.1415 E 0      8.0361 E 3  

Warp-OS                                              2001 by Sam Jordan

So, my problem comes from somewhere else

[Karlos]

Heretic 2 needs at least 64MB memory just to get out of bed. I wouldn't reccomend it for any system with less than 96MB *directly on the accelerator card*. Motherboard memory is just no good, especially on the A4K.

Try something smaller first:

1) Download the warp3d 4.2 archives and find the Gears demos (there are 680x0 and PPC versions).

2) Choose an 800x600 16-bit workbench screenmode.

3) Run the windowed 680x0 version of gears. Does it work? If not, your warp3d installation may need looking at. You may also have problems with your RTG configuration that affect warp3d. For instance, under CGX you must have the "bitmap cache" option enabled, as well as anything else mentioned in the documentation.

4) If the 680x0 version runs, try the ppc windowed version. If it does not run, your warpos settings may be arwy.

If nothing works, there is also the possibility your firmware on the PPC card is the problem. In my experience, the grexx-enabling versions of the flash totally kill off warp3D on the BVisionPPC/CVisionPPC and may affect other systems as well. Only use them if you have a G-Rexx, otherwise avoid.

-edit-

Hmm, somehow I got the impression you have a CVisionPPC, but I must have been mistaken. You don't say that anywhere :lol:

[patrik]

@awe4k:

Well, you could always make sure you have a clean WarpUp installation by reinstalling it.

Delete this:
LIBS:warp.library
LIBS:warpHW.library
LIBS:powerpc.library
ENVARC:powerpc/
ENV:powerpc/

Download these archives:
WarpUP 4.0
WarpUP 5.1 Update

First install WarpUP 4.0 and then install the WarpUP 5.1 update.

That is pretty much the setup I have which works fine. The only other thing I have done that might be a good idea is to increase the default stack size to 32kB in Prefs/Workbench.

Btw, does for example the Voxelspace Demo in the WarpUP archives work ok for you?


/Patrik