Amiga.org

Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: macto on April 30, 2004, 03:57:05 AM

Title: Troubleshooting an unfamiliar machine ...
Post by: macto on April 30, 2004, 03:57:05 AM
So I'm new to the Amiga.  My new toy is an Amiga 2000 with a GVP Combo 030 and SupraRAM 2000 card.  Until recently I thought that the "random" crashes were the product of a user who is unfamiliar with a system pushing it in unusual ways.  I'm beginning to think otherwise.

But the question is, how do I diagnose the problem?  I'm not very familiar with the machine, so just pulling the GVP card and hoping that the problem will go away is not of much use because I wouldn't know how to use the machine in order to reproduce the problem.  So can somebody suggest something which would use a significant chunk of the machines resources when I pull the card.  The software would have to fit on two 720 kB MS-DOS formatted floppies since removing the controller means removing my hard drive.

In terms of software, I have Workbench 1.3 and 2.0.4 (I have Amiga OS 3.9, but it sounds like it needs a 68020 which would disappear when I pull the GVP card).  The Amiga has a 3.1 ROM.  Unfortunately, I don't Workbench 3.1.

Thank-you for any advice.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on April 30, 2004, 04:20:31 AM
Hi,

How old and large (small) is your HD? If all I mentioned before had no effect, try to reseat all the chips on the MOBO. Do you get any error messages?

Chris

Click on my name to see whats in my system. As of last sunday I will either have to repair or replace my PSU.
I'm ready for more WATTS.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on April 30, 2004, 04:53:02 AM
Hi,

Almost forgot, Have you installed both Boing Bags? With only 1Mb of chip make sure in Prefs/WBPrefs/ Graphics mem = other, not chip.

Chris
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: Lemmink on April 30, 2004, 05:49:16 AM
In general it is no Problem running older WBs on a newer Kickstart. Problem comes when a programm that is functional under 2.x but also supports additional features of 3.x detect a 3.1 ROM. It could assume that the WB on top is a least 3.1 too and it starts to pull Tricks meant for 3.1 and up wich a 2.x WB can`t handle.
It will sure be helpfull if you spezify the crashes you accounter a little bit: When does it happen, what says the error message (or is it just a GURU), what programm crashed asf.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: Noster on April 30, 2004, 08:01:53 AM
Hi

I must agree Lemmink. You should use a Workbench according to your Kickstart ROMs, i.e. try to install 3.9 and see if the problems are still present.
And please give detailed informations about the errors occuring.

Noster
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: Castellen on April 30, 2004, 11:27:53 AM
Hardware wise, you can reduce the machine to the most simple usable state possible to eliminate expansions causing the problem.

For software, remove all non standard workbench programs (like MCP, MagicMenu, etc) if you're using any and run workbench in it's most basic form.  If you still have problems, it could be hardware.

Find out if the crashes are random, or only happen after a specific sequence of events, or after a certain time.

As mentioned before, reseat all socketed devices on the motherboard.  Remove essential expansions like the CPU board and clean edge connectors and sockets with proper gold contact cleaning spray.

Monitor power supply 5V rails for dropouts or excessive noise.

Flex the motherboard while it's running and see if light mechanical stress causes problems (usually hilighting contact problems).

If possible, try swapping memory modules for known good ones, or continuously run MemCheck (from Aminet) for a few hours to soak test all memory addresses.

Dunno, could be lots of things...  
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on April 30, 2004, 02:07:08 PM
QuikSanz: Reseating the chips seemed to do the job, but I'm going to wait a few days before reinstalling the SIMMs in the GVP card and SupraRAM card.  This is just to be sure, seeming as the errors are semi-random.

One curious thing though.  The chip at U301 (an 8520A) had pin 40 bent and pin 20 looked odd.  I noticed this when I pulled it out, so I presume that the previous owner left it like that.  Should I be replacing the UART?  I haven't been having trouble with the serial port thus far.

Oh, and I'm sure your A2000 will look much more impressive when I know what half of that stuff is.  :)

On the other comments: I was running a clean install of OS 3.9 and had crashes.  Ditto for 2.0.4, but they didn't seem as common.  I even saw errors with 1.3, which was available on the SupraRAM and GVP diagnostic disks.

As for the nature of the errors, the system would run fine for a while, then any number of things can happen.  Sometimes a guru style error will pop up (8000000n and 8100000n).  Some times the mouse would be frozen and the keyboard unresponsive, including .  Sometimes there would be corruption of the image on the screen, may that be random or a blank block which just floated there.

A broad range of programs would cause or see problems.  The Fonts control panel in OS 3.9 was a consistent source of errors.  The GVP RAM test was another.  In both cases, the machine would have to be running for half an hour or so before things went nuts.  Formatting a partition or even copying a large number of files could cause problems.  Demos would have problems, but I presume that is normal.

Castellen: it sounds like you have a number of good suggestions, but I don't have the equipment to look for noise on the power supply, or replacement RAM modules for the GVP.

Thank-you all.  Hopefully reseating the chips solve the problem.  If not, there is a more complete description of the problem.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: Noster on April 30, 2004, 03:17:20 PM
Hi

@macto

> The chip at U301 (an 8520A) had pin 40 bent and pin 20 looked odd.
> I noticed this when I pulled it out, so I presume that the previous owner left it like that.
> Should I be replacing the UART? I haven't been having trouble with the serial port thus far.

OF CAUSE REPLACE IT, this might be the defect of your system that leads to the crashes!

The 8520 do not only serve the parallel and serial ports, they also contain the systems clocks, several control-lines for the floppy-disk drives and other stuff.
They also generate interrupts! If any of these CIAs is bad, the whole system may be disturbed.

Noster


Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on April 30, 2004, 03:41:29 PM
Okay, the following site labels the pin 40 on u301 (CIA-B) as PPOUT.  Any idea what this means?  What ever it is connected to should be floating at this point.

http://www.amiga-stuff.com/hardware/8520.html

I think I have a few of these lying around from my previous attempts to get an Amiga.  Here's hoping that the CIA wasn't the problem in those cases.  (I presume these are fairly interchangable.)
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: Noster on April 30, 2004, 04:12:49 PM
Hi

> Okay, the following site labels the pin 40 on u301 (CIA-B) as PPOUT.

You mean POUT ? It is connected to the paper-out signal-pin of the parallel interface

Ok, if that signal is missing that should not lead to your problems, but the CIAs are very "unstable", i.e. they are IC's that die very often in an Amiga (have already replaced three of them) so you should replace it nevertheless.

> I presume these are fairly interchangable.

Yes they are. As Paula they have never been changed really and are interchangeable.

Noster
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: Castellen on April 30, 2004, 11:51:39 PM
Pin 40 isn't too major, but pin 20 is the 5V supply to the CIA if I remember correctly.
If this fails, then you will have major problems.  The system will not function without both CIAs working correctly.

You can get replacement parts from an A500 or A3000 as well.  If you use small pliers to straighten the pin, it'll probably be OK.  Remember to use anti static precautions.

I'd be more concerned about those cheap arsed sockets C= decided to use.  If the device pulls out quite easily, it suggests the socket contacts are weak, and possibly intermittent.

You can remove the socket and solder the IC directly into the board, or replace the socket with a machine pin type, which are far more reliable than those dual wipe ones.

As a last ditch effort, you can solder the ICs into the exsisting sockets.  Just flow solder between the IC legs and socket contacts.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: Morley on May 01, 2004, 12:23:14 AM
One thing that can cause occasional guru's, are viri...

They are so rare in the Amiga world now, that most people don't bother thinking about them at all. If you have tested lots of old disks on your A2000, chances are one or several of them were infected and you transferred the virus to your hdd. As most viri are rather out-of-date, most don't work at all or they cause major lock-ups, such as guru's.

Try a decent virus-scanner to check this out before you start resoldering all your IC's  :-)
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on May 01, 2004, 02:24:24 AM
On virii: if you can suggest a way to create a clean boot floppy for OS 3.9, I'll bypass the virus scan for now and do another clean install.  The situation over here is that I have three versions of the OS, one of which is on CD-ROM; a batch of driver/diagnostic diskettes, which I can download fresh copies of; and a few things from Aminet, which I can download fresh copies of.

I replaced the CIA with a pair from an Amiga 1000.  There was no change in the condition of the machine.  At this point, I'm going to pull out the GVP card to see if that critter is causing all of the trouble.  Then I'll consider mainboard problems, and replacing the sockets if need be.  Otherwise I risk damaging something which isn't broken.  I dug around my box of Amiga goodies and found a DataFlyer which will give me a hard drive to play with.  Reducing the machine to an 8 MHz 68000 may be painful, but I'll just keep reminding myself that it is only to figure out where the problem is.

Again, thank-you for all of the advice.  Hopefully I can get to the bottom of this soon.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on May 01, 2004, 02:42:23 AM
@ macto,

Do you have the docs for that accel card? You may want to check jumper settings.If not let me know and I'll check mine, I've kept it as a spare.

Chris
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on May 01, 2004, 03:55:26 AM
I have two sets of documentation, which conflict in a couple of cases!  Okay, the second is just a sheet detailing the jumpers for a revision 3 board.  Does a part number 500025-03 suggest a revision 3 to you?  It does to me.

The differences between the board and the sheet are: CN15 (was on 2-3, should be on 1-2, listed as reserved, now on 1-2), J12 (was open, should be shorted, selects between autoconfig and extended RAM, left open), CN8 (was on 2-3, should be open (!), listed as reserved, is now open).  There is another thing worth noting, the card has a 68030 rather than a 68EC030.

My A2000 currently has the DataFlyer IDE and DataFlyer RAM.   WB 2.0.4 is being installed.  Hopefully that'll tell me whether it is the mainboard or GVP board which is causing the troubles.  At this point I don't know whether to hope that the 2000 or the GVP board is toast.  The 2000 would probably be easier to fix, but a 2000 is still a 2000 without the 68030.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on May 01, 2004, 05:01:29 AM
Hi macto,

Ok, first, that part # does not appear anywhere on my board. However on the back it has a sticker that states "4.10" also etched in there about 2" in from the external connector is "94v-0" now these should be the same as I think there was only 1 run of each model (speed & cpu). Second these settings are original, bought on consignment, came from a high school, original owner. I would suggest removing all other boards unless your HD is IDE. If you HD is IDE, see if you can get a hold of a SCSI one and connect direct to accel card. Much speed gains can be had by doing this. Try to keep as much off the MOBO as possable, you'll want that later when you want graphics card or ethernet. Don't worry, the 32 bit mem clears fast as it has DMA access to the cpu.

Now jumpers, I will only list jumpers that are ON or shorted. J4, J6, J2, J12, J9.
Now for CN's. I will indicate high and low positions with Zorro connector on the bottom.CN7= low, CN15= low, CN14= high. Inside the cpu "can". CN16= low, CN8= no jumper-N/A, CN17= Special white connector-jumper, do not remove.

One more thing. I remember with these boards there was a limit as to how much memory you can have total. It does not remap or readdress like newer cards, so you may still have problems with all the other stuff. I seem to remember having to remove 4Meg when I installed the Picasso IV card. Give it a shot and see what comes of it, Let me know.

Chris

BTW, Picasso IV, is a 4Mb graphics card with built in flicker fixer and scan doubler.





Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on May 01, 2004, 05:35:40 AM
My error, this is a GVP G-Force 030.  I discovered there was a difference when I went in search of a difference between our cards.  Notably, I cannot find a CN17.  The settings are remarkably similar though, so maybe you knew what I was really talking about ...

Anyhow, I will try the GVP card, with the jumpers corrected, in a couple of days.  It is a tight squeeze, and I'm afraid that too much flexing isn't good for it.  Besides, I want to figure out whether the problem is with the mainboard or the GVP card.  I won't be able to figure that out unless I try the system without the GVP card.

As for upgrades, the ethernet card sounds great.  I'm not sure about the video card.  The old monitor reminds me a bit of my old Apple IIgs, only the Amiga is much faster (even with the 68000).
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on May 01, 2004, 05:49:45 AM
Hi macto,

If it is G-Force 030/40Mhz W/O scsi, then yes somewhat different. Combo means with SCSI. It will still speed up  processes however, it will not give faster HD handling. CN17 on my card is under the metal cover that is over the CPU & FPU, bottom left corner of CPU, Marked "MC68EC030RP40B". The FPU should be in the lower left hand corner of this shielded area.

Chris

Have you stripped it down and tried a game that boots from floppy for a while?
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on May 01, 2004, 06:47:54 AM
Well, I do have SCSI.  On the other hand, I don't have the shielding over the CPU and FPU or CN17.  They must have had a couple of revisions of the board or similar products which were identified differently.

The CPU in mine has been replaced.  It is a 68030RC50B.  In other words, it is not the embedded controller version so it has an MMU.  (The crystal is still 40 MHz.)

On stripping her down: the basic problem is software.  Aside from what I mentioned above, I have Directory Opus and Textcraft Plus on floppies.  Everything else comes from Aminet and I don't know how to make bootable floppies yet.  My comprimise: to try running her with the DataFlyer board.  It's even IDE, so I cannot use the same drive.

Then there is the problem of which software to use: the problem appears to be associated with memory in some way.  I don't recall if I mentioned the error numbers popping up, when I was so lucky, they were 80000003, 80000004, and 81000005.  But it doesn't happen straight off, since the machine has to be up for a bit (warmed up, so to speak).  This is evident in the pattern of the crashes, and the GVP RAM diagnostics program bore that out: perfect results when the computer was just turned on, it failed when the tests were done about 1/2 hour  (or so) after it was turned on.  Of course the GVP program only tests GVP RAM, so I wasn't able to figure out if the problem hit the SupraRAM card as well (ie. is this a system wide thing).  The GVP program is also useless when the GVP card is pulled.  While a lot of little things were triggering the problem in OS 3.9, it is still consistent because OS 3.9 uses memory more heavily to start with.  All of this is what leads me to believe it is the GVP card.  On the other hand, I kinda hope it isn't the GVP card because all of the memory is soldered on to the board at this point (ie. I'm having problems with the SIMMs removed).

For what it's worth: the errors the GVP RAM diagnostics program was reporting seemed to involve a failure to flip certain bits (3rd or 4th, I believe).  The problem appeared to be very consistent.

This whole situation is frustrating.  I will tackle it a bit more in the morning.  For now, I need some rest else I'll be as bad off as my Amiga.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on May 01, 2004, 06:56:01 AM
Hi,

See part about mem limit on last post, do you have a scsi drive?

Chris

Type tommorow.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on May 01, 2004, 05:00:46 PM
Morley: I'm doing a sector scan with VirusZ on all of my floppies and the hard drive.  Nothing yet, but the scan is still in progress.  Granted, it is a fresh install seeming as I replaced the GVP card (SCSI) with a DataFlyer (IDE).  Then again, any infection would have to come from those diskettes or files from Aminet seeming as those are my only sources of software.

On to the more probable cause, hardware:

I've been running the system for about 12 hours without an incident.  This is with a base A2000, plus DataFlyer IDE, plus DataFlyer RAM.  The machine hasn't been given a heavy workout, but the serial port, RAM (via the RAM disk), and hard drive have been put to good use.  I downloaded some more generic RAM testing software and will try to leave that running for a few hours this afternoon.  If everything checks out, I'll plug the GVP back in and copy my existing setup over to a fresh SCSI hard drive (so that I can pull the IDE controller) and see what happens.  If that seems to work, I'll conteplate swapping the fresh SCSI hard drive with my old SCSI hard drive to see if the jumpers on the GVP were the problem.  Or maybe I'll avoid pushing my luck if everything works. ;-)

On hard drives:

I have plenty of SCSI units, ranging from 40 MB to 2 GB.  Before the Amiga, I was working with 68k Macs. :nervous:  All of those old Macs had a SCSI controller or two.  IDE drives are actually an oddity for me.

On memory:

What is the limit, and how would the problem manifest itself (eg. irratic errors, undetected memory)?

The with the 6 MB SupraRAM and the 16 MB GVP board and the 1 MB on board, the Workbench was consistently reporting 23 MB RAM.  I don't know if I ever used a quarter of that, but it was there for the taking.  There appears to be some sort of conflict between the SupraRAM board and the DataFlyer RAM card.

Seeming as this problem usually manifests itself after the machine has been running for a while, I'm assuming that there is some sort of thermal problem.  Perhaps it is a bad connection?  Perhaps the circulation is extremely poor and something is over heating (with the GVP board in, the machine is pretty much broken into two compartments, with most of the heat generating stuff (the majority of the RAM, the hard drive, the processor) being tightly packed next to the power supply.

Actually, the speed of this thing isn't too bad with the GVP board removed.  Much slower, to be sure, but I've seen worse.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: Lemmink on May 01, 2004, 09:30:50 PM
From what I have read I think the GVP RAM-Modules have some contactproblems, or one of then is broken. See if the GVP-RAM sit tightly in their sockets. Maybe remove the RAM and clean the contact with pure alcohol useing a Q-tip.
Try running mit the GVP install but without RAM on the card (the first bank is soldered directly to the board I belive, of course you can`t remove that).
Maybe the RAM-modules are too slow, try deactivateing the burstmode, or nowaitstates with the jumpers. I will cost you a little bit of speed, but your system should be more stable after that.

Regarding RAM on ZII-Cards: The ZII Adressspace can only adress 8 MB, so the total of all the ram on all ZII cards should not exceede 8 MB. The GVP (and most of the other accelerators) put their memmory outside of the ZII autoconfig adresspace, so there is no problem.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on May 01, 2004, 10:31:17 PM
I was running the GVP card with the stock 4 MB for a little while, and still had problems.  I went through the jumpers, and the descriptions in the manuals really didn't say much.  In most cases they used the word "RESERVED", even though it is clearly there for a reason.  Other things, like "autoconfig address space" came up, but I'm not really sure what that means.  A lot of the (online) documentation I do find seems piecemeal, but that may be because I'm jumping into the middle of somebody else's mess.  (I would imagine that very few people would just have the assemblage of equipment I have dumped on them.  Rather they would build it up over time, as any sane person would do.  ;-) )

The autoconfig bit does answer one question: when I put the DataFlyer RAM and SupraRAM cards in, only 8 MB was recognised.  I guess that's why.  Likewise, using the autoconfig RAM jumper on the G-Force 030 card limited the system to 16 MB RAM (8 MB autoconfig on the G-Force 030 and 8 MB non-autoconfig on the G-Force 030, meaning that the DataFlyer RAM and/or SupraRAM would be ignored).  See, I am learning.

Anyhow, the system seems to be stable without that card.  For the time being, I'm going to set that card aside and get to know my A2000 a little better, both from a technical perspective and from the perspective of software.  Once I know how particular software behaves (ie. when it crashes and why), I'll tackle the GVP board again.  Until then, I'll have a mighty difficult time separating my mistakes (or those of other programmers) from the computers.

I would like to thank everybody for their help thus far.  The problem may remain unsolved, but I learned a lot and will continue plugging at this machine.  Sorry, the machine to my left.  While this machine has a G4, I'd be lying if I said that it was an AmigaOne.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on May 01, 2004, 11:11:49 PM
Hi macto,

The limit for extended memory is 16Mb, Chip mem does not count. Took a while to find the manual. All IC sockets should be filled. It's possible that the card has received a static discharge, Before you got it. That would be too bad an end for a decent accel card. If you can make sure the rest is good, there are lots of second hand ones around, some even at a good deal. Most folks seem to stick to AGA machines, aside from a faster bus there is no real upside to this if you use a graphics card, That is if you use the bus wisely. The A2000 has more expansion than any other and I've read that some nice towers may again be had real soon. Micro A1 and A2000 in one case anybody, talk about being versatile.

Chris
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on May 02, 2004, 03:34:46 AM
I'm not giving up on the critter, I'm just setting it aside until I know a bit more.  Unfortunately, it doesn't look like there is much on this card which can be fixed.  Besides the crystal, CPU, and FPU, the only socketed components are PALs.  You would probably need an identical card to swap those out.  Though I can also inspect it more carefully for physical damage and repair that, assuming that my hands are steady enough for surface mount.

As for the G3/G4 Amigas ... I originally got into Macs after picking up an SE to replace my dying 486.  Now the SE is another 68000 running at 8 MHz, so it isn't all that different from my A2000 with respect to performance.  I loved that machine because it was fun to use.  Of course, I upgraded with time.  Most of the 68k models were fun, but the jump to the PowerPC models took away the fun.

Now I can see the same thing happening here: the A2000 is fun.  It may be a virtual cripple compared to what I thought I had (ie. the unreliable GVP card), but it doesn't make much of a difference in my mind.  I learned a long time ago, there is no such thing as a slow machine if you use software which was written for it.  Well, almost.  In my case, making the jump to an A1 would risk tarnishing another platform in my eyes.  Then what would I be left with?  The Atari ST?   :evilgrin:

Granted, the A1 looks neat.  But I do believe that a serial port would be more useful than a parallel port.
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on May 02, 2004, 04:42:39 AM
Hi macto,

Hmm, Sounds familiar. Was the SE the all in monitor type, B/W display? that was the first "PC" I used many years after some classes I took at the local collage when I was in JR High, BIG hard drives, I think they were called "cakes". Then I found Amiga.Most kids these days wouldn't even know what they were looking at, you old timer.

Chris
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: macto on May 02, 2004, 06:26:04 AM
That could have been an SE.  As for big hard drives, it depends upon what you mean by big.  I've seen big hard drives (30 to 60 cm diameter platters), and I've been told that there were even bigger ones.

After dealing with clumsy OSes like MS-DOS, and bloated GUIs like Windows and OS/2, the relative elegance of Mac OS 6 and 7 were a revelation.  While I won't go as far as claiming that the Amiga is a revelation, it is the first time I've seen preemptive multitasking in such a small OS.  I was beginning to think that such was impossible.

Then again, maybe I should check the disk and memory usage.  It is possible that WB 2.0.4 is being less of a resource hog than System 6, so maybe the Amiga is a revelation.   :-o

As for those kids who think I'm an old timer, just give them five or ten years and they'll know what it feels like. :lol:
Title: Re: Troubleshooting an unfamiliar machine ...
Post by: QuikSanz on May 02, 2004, 06:19:24 PM
Hi macto,

"As for those kids who think I'm an old timer, just give them five or ten years and they'll know what it feels like."  

:roflmao:
 
The HD's I'm thinking of were 12" across and 6 disks stacked to about 6-8" high. That was back in the early 70's.

Chris