Amiga.org

Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: keropi on July 27, 2009, 11:20:10 AM

Title: A2000D + 060 + GoldenGate486slc = no go
Post by: keropi on July 27, 2009, 11:20:10 AM
Hiya!

A friend tries to use a goldengate486slc in an A2000D with a Blizzard2060 accelerator...
The goldengate works fine with the 68000 cpu (adaptor fitted) but when the 2060 gets installed , the gg can no longer operate with a "no bus activity error" ...
We already verified there are correct 060 libs installed and latest gg software...
Is there any suggestion? I really cannot think a reason for it not to work , as I used the very same gg486 on my A4000D that had a CSPPC installed (060 ofcourse)
Any tips? suggestions?
thanks!
Title: Re: A2000D + 060 + GoldenGate486slc = no go
Post by: amigadave on July 28, 2009, 02:36:39 AM
Quote from: keropi;516954
Hiya!

A friend tries to use a goldengate486slc in an A2000D with a Blizzard2060 accelerator...
The goldengate works fine with the 68000 cpu (adaptor fitted) but when the 2060 gets installed , the gg can no longer operate with a "no bus activity error" ...
We already verified there are correct 060 libs installed and latest gg software...
Is there any suggestion? I really cannot think a reason for it not to work , as I used the very same gg486 on my A4000D that had a CSPPC installed (060 ofcourse)
Any tips? suggestions?
thanks!

Are you booting the 2060 without any caches active on the 68060 when you are trying to use the GoldenGate 486slc?  I believe that is noted for any Amiga CPU's above the 68000 in the GG manual, but it has been a very long time since I have used mine.
Title: Re: A2000D + 060 + GoldenGate486slc = no go
Post by: keropi on July 28, 2009, 06:54:53 AM
yes, caches are disabled before starting the goldengate , I forgot to mention that...
it just seems that when the 2060 is on, the gg just dies
Title: Re: A2000D + 060 + GoldenGate486slc = no go
Post by: spirantho on July 28, 2009, 08:04:23 AM
Have you tried all the start-up parameters? I think there's one for using Chip RAM isn't there? So you'd run "digger CHIP" from the shell. Check that parameters available to you.

Also, have you tried booting with no Startup-sequence and just running SetPatch and then Digger? Try "Digger MIN" as well for a minimal startup...