Arrrgh! (FastATA 4000 MK-VI 8.0 and issues with keyboard.)

[danbeaver]

Sounds like you may need someone to either fully test or repair the motherboard, cause something ain't quite right.  Anyone near you with an A4000D you could do a swapsies with and test out their PSU with your MB and then your PSU with their MB?  Or ya could just send the MB to Anthony Hoffman; his turn around time is damn quick despite the distance.

[yurif74]

Amiga 4000 does NEED the pwr_ok signal (reported _fail on a4000 schematics)
I noticed that the atx psu pwr_ok line is "only" 3.66 volts.. afaik it should be a logic level 1 (5 volt)
this signal tell to the amiga that the psu is operating good.
your atx do not need the 3.3v to be connected at all, because it doesn't shut down when you tested voltage on a4000 power connector with hdd, fdd and cd connected. They required only +5v and +12v to operate.
juri

[slaapliedje]

I actually had my motherboard recapped and tested last year by Amigakit, and I haven't had any problems with it except this FastATA card.  

So it sounds to me like that 3.66v output is not sufficient for the A4000 to say "Hey, I have power" instead it gives me a big "!@#$ you, I'm turning off!"

Like I had said, even the PSU turns off at that point.  Maybe I'll see if I can dig up another PSU to test with, I'm almost 100% sure it's not the Amiga, and it is the PSU.  At least with that I can just find a cheaper solution.  I'll probably use this PSU in a separate project (been thinking of building a steam machine )

slaapliedje

[danbeaver]

Hmm,

OK, replace the CF connector (and card if it fails on a PC), or pm me your address and I'll send you a CF connector and 64MB CF card.
Assume the motherboard is not at fault.
Find another ATX-style to test to see if it is the Silverstone (which is a fornicating rip off if it is the Silverstone).

[slaapliedje]

Yeah, I'll rip an older ATX out of a computer I have sitting in my pile of parts when I get home and test that out.  

Ha ha, yeah, that Silverstone was 95 bucks, I wanted it 'cause it was modular and I was hoping I could get rid of some of the non-needed cabling, though I find it crappy that all the 4-pin Molex cables I have are 8-pin except the one that came with it, and it needs a 6-pin.  I have several modular power supplies 'cause they're awesome.

I may just have to go with the non-modular PSU that you suggested.

Will PM you, Thanks!

slaapliedje

[yurif74]

Are there any news? did you tried a different psu with success??

Juri

[slaapliedje]

Different PSU, no success.  Though, at least I did get it to boot, but the FastATA still has the issue.

I think AllegroCDFS screwed up my system, 'cause now it won't fully boot, even on the hard drive that is just IDE and connected via the normal IDE connector.

But otherwise, I received the CF card adapter and 64mb card from Danbeaver (Thanks again!) and connected it up.  Seemed like it was working fine, didn't lock up when I started the fastata.driver up, when I tried copying over a smaller file, then deleting it, it worked.  Then I copied over a larger file and it said 'cannot output to..' or something like that, and now it's giving me a checksum error  

I'm almost 100% sure the Transcend 32GB CF card is not compatible with the voltages or something, because it overheats on this adapter as well (the other adapter completely stopped working, I think it may have gotten hot enough to fry something).

I ended up ordering another (SanDisk this time, which I've seen recommended) 32GB CF card, along with a CF card adapter just like the one Dan sent me (again, many thanks!) so I can send the one back to him.  This is very frustrating, seems that just about all the hardware that I've received from this purchase has issues.

Oh, the above tests were with the stock PSU.

slaapliedje

[yurif74]

Different PSU, no success.  Though, at least I did get it to boot, but the FastATA still has the issue.

So it isn't psu related and i can confirm it!
i've a Cyberstorm MK1 with 68060@50mhz (no overclock) and i'm having your problem (can't go further PIO MODE 3) yesterday happened something really strange, a friend came to me with a standard A3640 to try it (his amiga have serious problems and he want to check if the CPU card was ok) tested ok, his A3640 cpu card was ok, so he asked me if i fixed my problem with fastata, and while talking i showed to him the problem, i setted to PIO MODE 5 and... nothing!! WHAT?? YES!! with a stock A3640 Fastata works PERFECTLY in PIO MODE 5!! (i'm getting a little bit under 6mb/s of transfer rate!) then i reinserted my CSMK1.. amiga locked.. after few second.. i had to re insert the A3640 to switch back to PIO MODE 3! now my amiga is working with the CSMK1 in pio mode 3... too bad!

[slaapliedje]

Holy %&$#?@!%&$#?@!%&$#?@!%&$#?@!, I have the exact same hardware then!  Interesting, I still have my A3640 and can swap them out and will confirm if that's the issue or not.

I tested the Transcend 32GB CF card in a USB card reader and it still gets hot, but seems to read/write just fine.  

I bet you anything it's incompatible with something on the Cyberstorm MK1 then, either the 060 library or just the way it works.  Anyone have any ideas on that?

slaapliedje

P.S.  Wow, I didn't swear that much, just one four letter word.  Guess A-eon turned on the filter and messed it up?

[yurif74]

...I bet you anything it's incompatible with something on the Cyberstorm MK1 then, either the 060 library or just the way it works.  Anyone have any ideas on that?...

from elbox:
•                      Automatic                      processor type recognition
                    The FastATA 4000 MK-VI CF/SATA controller automatically detects                      type of processor and optimises and modifies some software                      routines in order to achieve the highest possible data transfer                      rate between the controller and the computer memory.

now afaik workbench recognize the 68060 as 68040 until setpatch is called... i've the fastata.driver command BEFORE the setpatch command..
it's very late here now, but tomorrow i've some free time and i will do some experiments.. then i let know

Juri

[slaapliedje]

from elbox:
•Automatic                      processor type recognition
                    The FastATA 4000 MK-VI CF/SATA controller automatically detects                      type of processor and optimises and modifies some software                      routines in order to achieve the highest possible data transfer                      rate between the controller and the computer memory.

now afaik workbench recognize the 68060 as 68040 until setpatch is called... i've the fastata.driver command BEFORE the setpatch command..
it's very late here now, but tomorrow i've some free time and i will do some experiments.. then i let know

Juri

I will somehow find a way to pay you if that is the fix!  I'll give it a shot hopefully in an hour or so.  Stuck at work 'til then.  Though if that's the fix, I'm going to be pissed off at Elbox.  I would think the installer would put FastATA.Driver after setpatch anyhow.

slaapliedje

[yurif74]

I will somehow find a way to pay you if that is the fix!  I'll give it a shot hopefully in an hour or so.  Stuck at work 'til then.  Though if that's the fix, I'm going to be pissed off at Elbox.  I would think the installer would put FastATA.Driver after setpatch anyhow.

slaapliedje

slaapliedjeeeeeeeeee

put beer on ice! I placed fastata.driver after setpatch and cpu command and.. fixed!

[slaapliedje]

D'oh!  I'm still not having any luck.  I can get it to boot off of the Emergency disk I've created, and it'll read at PIO mode 4, but as soon as I try to write anything to it, it freezes.

PIO Mode 0 is the only thing I can get to work, but then it won't boot off the CF Card.  Granted this is my 32GB one that was overheating (seems to not do that so much now) and the errors I get when it tries to boot is 'C: not an executable, cannot load' or something like that.

Anyone have any ideas?

slaapliedje

[Ancalimon]

On my A1200 with Blizzard 060, ata3.driver is the second command on my Startup-Sequence after blizkick. I have two reboots.

-------------
Blizkick * MODULE FixGetMsg LocalFast MoveVBR MuMove4k romupdate.idtag exec.library FastFileSystem card.resource misc.resource FileSystem.resource ram-handler console.device shell-seg trackdisk.device intuition.library layers.library SoftSCSI extresbuf=300000

C:ATA3.driver QUIET RESIDENT
C:stack 8192
SetPatch NOROMUPDATE QUIET

When I run ATA3Prefs after cold booting with no startup-sequence, ATA3Prefs says "68060 PROCESSOR DETECTED". I can set both my harddrives to PIO4 (but no PIO5 although it says max supported PIO5).  No need for setpatch. Resident tag is ticked.

I think you might have a different problem. Not sure but maybe something related to max transfer rates or maybe even the file system... Just guessing.

[slaapliedje]

Unfortunately, the ata3.driver and fastata.driver are completely different.  I don't see anything on the boot up (if I remove QUIET) except for the Drive, Size, and Speed.  

I added the C:CPU060 line right above it and after SetPatch, and it now spews out a bunch of stuff about the 060 being loaded up but it still locks up with anything other than PIO 0.

I should have my new CF card adapter and card later today when I get home, so I'll give those a try and see if it will give me a more stable system.

slaapliedje

[yurif74]

afrer some testing i had to switch back to PIO 4 because with pio mode 5 even if drivetest report "OK,no errors" i have a lot of checksum errors and locks.. with PIO 4 all appear to be ok. one little difference is that my A4000 mount a fastata mkvi with rom 7.0 (but i do not think that's the problem) have you tried to remove setpatch command? just for try, or another version of setpatch/fastata.driver
i've a lot of sh*it that loads on my amiga 4000: mmu, mui, poseidon, cybervision, modified cyberstorm libraries.. when i've some free time i will try to unload all, and put another hdd with clean workbench install and only fastata driver (ofcourse stock cyberstorm libraries from install floppy) i would try os3.9 too