DKB 2632 crash

[SpeedGeek]

The DKB2632 memory is extended memory which configures above 24 bit address space so the 8MB 24 bit/Zorro2 limit is NOT affected by this board! The most likely problem is a voltage drop on the +5 rail when both boards are installed.

Unfortunately, both the DKB2632 and A2630 have some design bugs which make them voltage and heat intolerant (as well as an overclocking nightmare).

... and since, I don't like repeating myself:

http://www.amibay.com/showthread.php?t=33672

[SpeedGeek]

Where did you measure the +5 volt supply? There is significant voltage drop from the PSU connector to mobo to expansion slot. Try measuring it on the A2630 or DKB2632 boards. There should be a small VR in the A2000 PSU you can tweak but if you've got good voltage readings that won't be necessary.

The second problem is the DKB2632 design bugs which result in poor EMI/RFI noise immunity. They are more complicated to solve but you could try moving your expansion boards to the left most slots and rerouting the SCSI cable to see if that helps.

[SpeedGeek]

I have found that the 2632 program has a resident module which seems to be incompatible with 3.x but it only fails on reboot. Its possible (but unlikely) that this resident is not compatible with some older RTG software.

You can test this by booting with no startup-sequence via bootmenu and then run 2632 from the Shell. You could also use 2632 -r to add memory without the resident module.

If that doesn't help try 2632 -m0 which lowers the priority of 2632 memory to the same as auto-config fast memory. It won't be accessed until the auto-config fast memory is used up. This will help determine if the DKB2632 memory is failing itself.

[SpeedGeek]

I would suggest posting your s-s but if the 2632 command fails with no s-s then you clearly have problems with the DKB2632 or the SIMMs themself. You can try the 2632 -d command which will give some you info about the memory config and bank size but won't fix anything.

The next step is to clean or replace the SIMMs and re-seat the socket mounted chips on the DKB2632. You can also try a memory tester program with out running the 2632 command.

[SpeedGeek]

I never tried MMUlib with my DKB2632 but you should be able to edit the MMUconfig file to add non-autoconfig memory with out the 2632 command.

I noticed you have some additional auto-config devices in your Show config report. Is is possible you have some s-s drivers for theses devices which are not compatible with the extended DKB2632 memory?