Welcome, Guest. Please login or register.

Author Topic: Apollo A3000 SCSI confilicts galore  (Read 2338 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Iggy_DrouggeTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2003
  • Posts: 333
    • Show only replies by Iggy_Drougge
    • http://www.kristallpojken.org
Apollo A3000 SCSI confilicts galore
« on: December 13, 2003, 01:11:43 AM »
Just last week, I became the proud owner of an A3000. It came equipped with an Apollo 3040 accelerator and a Merlin graphics card. The machine itself seems to be of a relatively late date, since it has got a HD drive and no traces of a SuperKickstart.
However, as well as the machine works in general, it really seems to hate hard drives, in spite of (or due to?) the existence of two SCSI controllers in the system; one on the motherboard and one on the Apollo. The required Apollo jumper lead between the Kickstart and the SCSI chip is there, so this can't be the culprit.
What happens is that the system takes several minutes to come to the Kickstart (3.1) screen, at least while the Apollo SCSI is enabled. Any attempt to access a drive on the Apollo with HDToolbox fails, with HDToolbox getting stuck on DUN 0, LUN 0.
The internal controller doesn't behave much better. Though I've managed to partition a drive there, the Install 3.1 disk will freeze the computer when trying to put the drive on the WB screen. Similarly, any attempt to format the drive from a DOS prompt will fail sooner or later.
What could possibly be behind this misbehaving SCSI mess? Do I really have to sacrifice a goat in order to make it work?
A4000/25MHz/64MB/20GB/RetinaBLTZ3/FastlaneZ3/CatweaselMKIII/Ariadne/A2301
A3000/40MHz/32MB/6GB/Merlin/Buddha/X-Surf/FrameMachineII+Prism24
Draco60/50MHz/128MB/15GB/Altais/DracoMotion/DV/IOblix+net
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: Apollo A3000 SCSI confilicts galore
« Reply #1 on: December 13, 2003, 02:04:51 AM »
Apollo SCSI is one of the worst SCSI implementations on Amiga. It has no DMA, and it is known for all sorts of weird problems and incompatibilities.

If only possible, stay away from it.

As to the problems with onboard controller, I don't know.
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: Apollo A3000 SCSI confilicts galore
« Reply #2 on: December 13, 2003, 02:20:01 AM »
www.amiga-hardware.com Apollo 3040 page has some interesting info:
Quote
The original 68040.library from Commodore cannot be used with this card, instead you must use the supplied library.

Perhaps you're using wrong 68040.library ?
 

Offline Castellen

Re: Apollo A3000 SCSI confilicts galore
« Reply #3 on: December 13, 2003, 03:10:09 AM »
What exactly does that jumper from the Apollo to the motherboard SCSI controller connect?
Most 3rd party SCSI controllers added via the CPU slot will require a small motherboard modification due to one of the required interrupt lines not being connected to the A3000D CPU slot.

Details here:
http://amiga.serveftp.net/MiscFiles/A3000-INT_2-Modification.LHA

As for using the motherboard SCSI controller, I fitted a 9Gb SCSI2 Seagate Barracuda drive to my A3000 a couple of days ago, and found the Fast Synchronous and SCSI-2 queing modes needed to be enabled for the drive to operate on the controller.
This can be set using one of the many programs from Aminet like SetBatt or SCSIprefsMUI.
 

Offline Iggy_DrouggeTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2003
  • Posts: 333
    • Show only replies by Iggy_Drougge
    • http://www.kristallpojken.org
Re: Apollo A3000 SCSI confilicts galore
« Reply #4 on: December 15, 2003, 01:45:36 PM »
Quote

Piru wrote:
www.amiga-hardware.com Apollo 3040 page has some interesting info:
Quote
The original 68040.library from Commodore cannot be used with this card, instead you must use the supplied library.

Perhaps you're using wrong 68040.library ?


Ciao, Harry, I was using your WhichAmiga as late as yesterday. =)

While I haven't installed any Apollo 68o4o.library, should I really need to install it, considering that I haven't got as far as installing the system yet?
A4000/25MHz/64MB/20GB/RetinaBLTZ3/FastlaneZ3/CatweaselMKIII/Ariadne/A2301
A3000/40MHz/32MB/6GB/Merlin/Buddha/X-Surf/FrameMachineII+Prism24
Draco60/50MHz/128MB/15GB/Altais/DracoMotion/DV/IOblix+net
 

Offline x56h34

  • Hero Member
  • *****
  • Join Date: Sep 2003
  • Posts: 2921
    • Show only replies by x56h34
Re: Apollo A3000 SCSI confilicts galore
« Reply #5 on: December 15, 2003, 05:36:36 PM »
WhichAmiga is great, however it doesn't like Blizzard 1230-IV. It always crashes the system with it in A1200. Other than that, I absolutely love it. :-)
 

Offline Iggy_DrouggeTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2003
  • Posts: 333
    • Show only replies by Iggy_Drougge
    • http://www.kristallpojken.org
Re: Apollo A3000 SCSI confilicts galore
« Reply #6 on: July 19, 2004, 06:16:11 AM »
I've performed the INT2 modification, to no avail.
Lately, I tried to reinstall the HD. OS3.1 just hanged when loading WB and putting all disk icons on the screen. Then I tried 2.1, and lo and behold, it works!
OTOH, when running Eagleplayer (the only prog I'm running thus far, save KingCON), it will only play three songs, then the screen turns black. I reset, play three songs, and the same thing occurs, like clockwork. Really interesting machine I've got.
A4000/25MHz/64MB/20GB/RetinaBLTZ3/FastlaneZ3/CatweaselMKIII/Ariadne/A2301
A3000/40MHz/32MB/6GB/Merlin/Buddha/X-Surf/FrameMachineII+Prism24
Draco60/50MHz/128MB/15GB/Altais/DracoMotion/DV/IOblix+net
 

Offline Brian

  • Hero Member
  • *****
  • Join Date: Mar 2003
  • Posts: 1604
    • Show only replies by Brian
    • http://www.syntaxsociety.se
Re: Apollo A3000 SCSI confilicts galore
« Reply #7 on: July 19, 2004, 09:15:25 AM »
Have you tried a different CPU card? and the 040 lib is needed at boot or it will crash on you. I sugest you make a special Install disk on a different Amiga and put the apollos 040.lib on it. Then take that install disk to the A3000 and boot from it.

I had to do a simmular thing with my A4000 with CSPPC060. Created a custom install disk with the 060lib and dummy 040 lib etc or the A4000 wouldn't work ok. (I actually made the disk on and for my A1200 with B1260 in the first place and just reused it for my A4000.)

Offline Orjan

  • Hero Member
  • *****
  • Join Date: Sep 2003
  • Posts: 515
    • Show only replies by Orjan
Re: Apollo A3000 SCSI confilicts galore
« Reply #8 on: July 19, 2004, 09:42:48 AM »

@Iggy

Try pulling out the accellerator and see if you can use the internal SCSI. If you can use it without the card, then something seems to be out of order with the accellerator. Don“t forget to change the jumpers on the motherboard.
\\"Memory is like an orgasm. It\\\'s a lot better if you don\\\'t have to fake it.\\"
- Seymore Cray, on virtual memory.
 

Offline Iggy_DrouggeTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2003
  • Posts: 333
    • Show only replies by Iggy_Drougge
    • http://www.kristallpojken.org
Re: Apollo A3000 SCSI confilicts galore
« Reply #9 on: July 30, 2004, 01:04:34 PM »
Oh! I had no idea that I needed a special 68040.library that badly (bought it all second-hand). Once I find a download, I'll report how it works out.
A4000/25MHz/64MB/20GB/RetinaBLTZ3/FastlaneZ3/CatweaselMKIII/Ariadne/A2301
A3000/40MHz/32MB/6GB/Merlin/Buddha/X-Surf/FrameMachineII+Prism24
Draco60/50MHz/128MB/15GB/Altais/DracoMotion/DV/IOblix+net
 

Offline Iggy_DrouggeTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2003
  • Posts: 333
    • Show only replies by Iggy_Drougge
    • http://www.kristallpojken.org
Re: Apollo A3000 SCSI confilicts galore
« Reply #10 on: July 30, 2004, 01:06:13 PM »
I'd have done that, but I have no idea how to set the jumpers. This is my first A3000 of my own and my first third-party accelerator.
A4000/25MHz/64MB/20GB/RetinaBLTZ3/FastlaneZ3/CatweaselMKIII/Ariadne/A2301
A3000/40MHz/32MB/6GB/Merlin/Buddha/X-Surf/FrameMachineII+Prism24
Draco60/50MHz/128MB/15GB/Altais/DracoMotion/DV/IOblix+net
 

Offline Iggy_DrouggeTopic starter

  • Sr. Member
  • ****
  • Join Date: Jul 2003
  • Posts: 333
    • Show only replies by Iggy_Drougge
    • http://www.kristallpojken.org
Re: Apollo A3000 SCSI confilicts galore
« Reply #11 on: July 01, 2005, 11:35:36 PM »
A very late update, but things have been proceeding slowly with the A3000, what with it being a nightmare to dismantle. However, it is mostly cured now, after a year of troubles.

After finding the German manual in PDF format, I found out the correct jumper settings, and removed the accelerator, to which the computer responded well. I could finally install OS 3.1.
I then reinserted the Apollo, then installed the correct 68040.library, and it ran with intermittent crashes.
The final clue? Upon ocular inspection, I noticed that the single screw holding the 3040 down was holding it in an awkward, tilted position. This is because ACT never really seemed to have the A3000 in mind when designing the 3040. While there are four holders for accelerators, just as on the A4000, the rear pair are situated far off towards the rear, presumably in order to accomodate Commodore's original cards. The 3040 only has one screw hole in the front, and that is thus the only one holding it down. The solution is to add a plate for distancing beneath the board and the screw, as well as adding some pillows under the rear portions of the card, for support. It is now held fairly well in a horizontal position.

These mechanical adjustments made the machine basically stable, but nevertheless it would give up after a certain amount of time running, after which it would lock up and refuse to restart unless left turned off for at least half an hour. Waking it up too early would result in checksum errors on the hard drive. My friends say that this is due to my old DMAC, which will overheat when stressed. I have moved the system onto an IDE drive connected to a Buddha, and the machine runs fine.

I write this update for the sake of archival, in case someone else should encounter any problems of this kind.
A4000/25MHz/64MB/20GB/RetinaBLTZ3/FastlaneZ3/CatweaselMKIII/Ariadne/A2301
A3000/40MHz/32MB/6GB/Merlin/Buddha/X-Surf/FrameMachineII+Prism24
Draco60/50MHz/128MB/15GB/Altais/DracoMotion/DV/IOblix+net