Welcome, Guest. Please login or register.

Author Topic: Bad CS MK III?  (Read 2927 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline kolla

Re: Bad CS MK III?
« Reply #14 from previous page: January 09, 2017, 03:01:37 AM »
I kinda miss an answer to my question about what versions of the following you have installed:

Version full file C:SetPatch
Version full file LIBS:68040.libray
Version full file LIBS:68060.libray
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline matt3kTopic starter

Re: Bad CS MK III?
« Reply #15 on: January 10, 2017, 04:44:27 AM »
I'm using virusz with the latest xvs.library.  No viruses found...

I looked at virusz and found what you would expect for nonstandard dos.library and a few other items I would suspect.

I would hope that virusz would turn up the ebola and other viruses...  Maybe a new virus has entered the Amiga community, that would explain a great deal frankly...


It does seem really odd.  I just has to be the CS card or the 060.  I'm going to swap out the 060 and if that doesn't fix it send it for repair...



Quote from: Pat the Cat;819344
Hmmm... malware?

I mention it as it seems very suspicious to me that the machine only crashes when you try to mess with the startup-sequence etc, or typing commands directly into a CLI or Shell.

That smells fishy, to me anyway.



Which one, with which database? I doubt it would find anything on a file scan, but you might notice some of the system files aren't the ones that you think are being used.



OK, you already isolated it to the library or the chip, and you are changing the chip anyway, as changing the library had no effect. That makes sense.
 

Offline matt3kTopic starter

Re: Bad CS MK III?
« Reply #16 on: January 10, 2017, 04:52:32 AM »
Quote from: paul1981;819347
Did you try OS3.1 alone? Simplest thing to do would be a Workbench 3 boot floppy with the 060 lib(s) on. Work with a copy obviously, and of course you'll likely have to delete some files to make a bit of room first. Then run software from your hard drive (let's assume your software is virus free). Bare in mind your scsi.device version though and your partition setup etc...I can't be held responsible for any data loss if you directly or indirectly write to your hard drive! I'll assume you already have all of that in mind though as I know you're a clever chap. :)

For novices, perhaps that 911 boot disk would be of help here? I know literally nothing about it except for its existance, but it's likely got all this stuff on.

Unless you cold boot from another device (like floppy) then you really can't rule out Virus infection nor just corruption of some of your system files. But yes, that 060 would need the 060 lib(s) to fully test. In my gallery there's a VirusZ entry which lists all the files needed to fully check your system. It's worth it as I had a link virus infection called 'Ebola' a few years ago on one of my Amigas... VirusZ fixed it.

Out of curiosity, what is wrong with your onboard 030? Does it exhibit the same behaviour you are now seeing on your 060?


I did boot from 3.1 floppy, but I didn't do much testing off the floppy.  It was used to boot for install 3.1.  

I tried scanning with virusz with the latest xvs.library, but I did it from booting from the hard disk.  Will that not provide proper functinality?  It didn't report any viruses.

The SSD is on the Cyberscsi.device so no worries.

The 030 goes to a flashing yellow screen, so i believe it is defective...
 

Offline paul1981

Re: Bad CS MK III?
« Reply #17 on: January 10, 2017, 11:52:42 AM »
Quote from: matt3k;819432
I did boot from 3.1 floppy, but I didn't do much testing off the floppy.  It was used to boot for install 3.1.  

I tried scanning with virusz with the latest xvs.library, but I did it from booting from the hard disk.  Will that not provide proper functinality?  It didn't report any viruses.

The SSD is on the Cyberscsi.device so no worries.

The 030 goes to a flashing yellow screen, so i believe it is defective...


There are further settings in VirusZ to enable scanning of compressed archives etc. but the standard file check of SYS: with default settings would show up any infection if it existed.

It'd be nice to replace that 030... I wish it was socketed for you.
 

Offline Acill

Re: Bad CS MK III?
« Reply #18 on: January 10, 2017, 02:16:58 PM »
Matt, I could replace that 030 if you had another and wanted to risk it, but I would see if you can get another CPU card on loan from someone.

You are in the US? I may be willing to send you an 040 card to test and see how things run. I really suspect that BGA soldered POS socket Phase5 came up with for these cards. They are a major failure point. Replacing them is a pain too, but can be done. I did it once, and dont know if I would want to ever again. It takes soldering one pin at a time and building up a new socket row by row.
Proud Retired Navy Chief!

A4000T - CSPPC - Mediator
Powerbook G4 15", 17"
Powermac G5 2GHZ
AmigaOne X5000
Need Amiga recap or other services in the US? Visit my website at http://www.acill.com and take a look or on facebook at http://facebook.com/acillclassics
 

Offline Oldsmobile_Mike

Re: Bad CS MK III?
« Reply #19 on: January 10, 2017, 03:42:56 PM »
My .02 cents... I hate building a "house of cards" on a shaky foundation.  Get that '030 replaced and see what other issues the motherboard may have before pointing fingers at one component or another.  Try rebuilding the system piece-by-piece, from the ground up, and see when the issue occurs.

Of course, if you can just swap in another CPU or processor card and the issue disappears, then you're golden.  :)

Also, here's a link to that Amiga911 disk Paul mentioned, earlier:  http://amiga911maker.site11.com/index-1280.htm   Might have something helpful on it?
Amiga 500: 2MB Chip|16MB Fast|30MHz 68030+68882|3.9|Indivision ECS|GVP A500HD+|Mechware card reader + 8GB CF|Cocolino|SCSI DVD-RAM
Amiga 2000: 2MB Chip|136MB Fast|50MHz 68060|3.9|Indivision ECS + GVP Spectrum|Mechware card reader + 8GB CF|AD516|X-Surf 100|RapidRoad|Cocolino|SCSI CD-RW
 Amiga videos and other misc. stuff at https://www.youtube.com/CompTechMike/videos
 

Offline kolla

Re: Bad CS MK III?
« Reply #20 on: January 10, 2017, 03:51:50 PM »
From what I recall, yellow screen means that the CPU is ok, but that it detects something else is wrong. Faulty CPU is just a black screen, iirc.

EDIT: Ah, here it is
http://wiki.classicamiga.com/Amiga_boot_error_code_colours
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline kolla

Re: Bad CS MK III?
« Reply #21 on: January 10, 2017, 05:18:40 PM »
Btw - on A3000, isn't there a jumper on the mobo that you need to swap when acc card is used (or not)? I have two A3000 myself, so I ought to know :p
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline matt3kTopic starter

Re: Bad CS MK III?
« Reply #22 on: January 10, 2017, 06:06:27 PM »
Quote from: kolla;819461
Btw - on A3000, isn't there a jumper on the mobo that you need to swap when acc card is used (or not)? I have two A3000 myself, so I ought to know :p


Lucky guy :).

Yes, the jumpers are required to use the CS.
 

Offline matt3kTopic starter

Re: Bad CS MK III?
« Reply #23 on: January 10, 2017, 06:07:12 PM »
Quote from: kolla;819457
From what I recall, yellow screen means that the CPU is ok, but that it detects something else is wrong. Faulty CPU is just a black screen, iirc.

EDIT: Ah, here it is
http://wiki.classicamiga.com/Amiga_boot_error_code_colours


Pretty sure it is the FPU that isn't working...  Thanks for the correction.
 

Offline matt3kTopic starter

Re: Bad CS MK III?
« Reply #24 on: January 10, 2017, 06:10:59 PM »
Quote from: Oldsmobile_Mike;819455
My .02 cents... I hate building a "house of cards" on a shaky foundation.  Get that '030 replaced and see what other issues the motherboard may have before pointing fingers at one component or another.  Try rebuilding the system piece-by-piece, from the ground up, and see when the issue occurs.

Of course, if you can just swap in another CPU or processor card and the issue disappears, then you're golden.  :)

Also, here's a link to that Amiga911 disk Paul mentioned, earlier:  http://amiga911maker.site11.com/index-1280.htm   Might have something helpful on it?


Yes, I agree fully Mike.  Pretty sure it's the FPU, so I suppose I could find someone to fix the board...  

I have a warp engine, but the dang mediator isn't compatible with it...  Suppose I could use the warp engine without the mediator... since I know the mediator isn't the issue...  Will give that a go.  Thanks Mike.

I built a 3.1 disk with the libs on it to install 3.9, I can try working off the floppy later and see what happens...
 

Offline amiadudeorwat

Re: Bad CS MK III?
« Reply #25 on: January 11, 2017, 02:34:52 AM »
Quote from: matt3k;819465
Yes, I agree fully Mike.  Pretty sure it's the FPU, so I suppose I could find someone to fix the board...  

I have a warp engine, but the dang mediator isn't compatible with it...  Suppose I could use the warp engine without the mediator... since I know the mediator isn't the issue...  Will give that a go.  Thanks Mike.

I built a 3.1 disk with the libs on it to install 3.9, I can try working off the floppy later and see what happens...

The Warp Engine works with the Mediator on the A4000.