Hi @all

Things I´ve done:

1. replaced my 2,5 GB Western Digital testing HDD with a Maxtor 120GB
--> All devices are hooked to the sil0680 controller via two 80pole airflow cables.
1. master: maxtor 120GB HDD (DH0: 20GB, DH1:20GB, rest unused)
1. slave : Liteon CDRW 48x
2. master: 30GB Western Digital (for pegxmac)
2. slave : none

in uboot I set the env- variables as metioned in the update 3 documentation
so the sil0680 would be recognised.

The 120GB HDD was FFS2 formated with a blocksize of 2048 and the cacheplugin is activated in the user-startup.
With the idetool the hdd was set to mode 70 (udma 133) after the errors came up I switched to mode 69 (udma 100).

The OS4 installation ran smoothly and fast. OS4 booted fine.
Bur after tryind to install more and more programs the system comes up with an requester "wite error e.g. on block 50354".

Both partitions DH0: & DH1: have this problem.

What have I done wrong?

One thing I forgot to mention:
I changed the original thermaltake "ORB" cpu fan with a zalman vf700 copper
fan. I highly recommend this fan. It needs one small modification on the screw
and fits really good.

have a look:
http://www.zalman.co.kr/eng/product/view.asp?idx=149&code=013

As I have an original G4 7455 with 933MHz I changed the vcore to the recommended voltage of 1,79V (before it was 1,59V). My System is stable as a rock.
My memory (2x 512MB Hynix Ram) has been checked with the ramtester with
no problems.

greetings
zErec

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@zErec


Can you please try to remove the 2nd RAM stick ?

Do you use round IDE cables ? then replace them with flat cables, properly qualified for ultra DMA 133.

Make sure that your master drive is at the end of the cable, and the slave is in the middle.

Regards,
--
Stéphane Guillard

@zErec

Same problem here - A micro amigaone with 256Mb, IBM/Hitachi 160Gb HDD, Sony 52x CDR/W,ATA 133 80 wire cable. If i turn dma on in update3 and download compressed files i get crc errors in unarc (udma0 - udma5), the higher udma settings the more errors... If i set it to udma1 it will find crc errors maybe once a day, if i set it to udma5 1 out of 2 has crc errors.
Is it that the cpu get overheated ? Is it s bug in "Unarc" ? Is it os4 Pre3 ?

_________________

@sg2

My master drive is at the end of the cable, and the slave is in the middle.

I removed the 2nd 512MB RAM stick. The same write errors happend.
After that I opened the idetool again. I noticed that it was set to UDMA133
"MODE 70" again. I was sure I changed it to UDMA100 "MODE 69" before.

So I tried PioMode 4 and everything went okay, no corruption.
Then I tried UDMA 100 same effect. After that UDMA133 failed the test
with write errors again.

So in conclusion UDMA133 doesn´t work for me (maybe the expansive round cables)
After a reboot the mode was set to UDMA133 again. I remembered the variable I set in uboot (setenv sii0680ide_xfer G0E0). I changed it to F0E0. Now everything runs stable with UDMA100.


greetings zErec

Last edited by zErec on 29-Jul-2005 at 08:40 PM.

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@zErec

I guess you did not read all the various files / pages / places where I state that UDMA requires flat cables explicitly qualified.

Anyway, I'm happy that it works for you now.

NB : the uboot envvar is a permanent setting, while idetool changes only until next reboot.

Kind regards,
--
Stéphane

@sg2

"boot envvar is a permanent setting"

if you type "saveenv"

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@sg2

>I guess you did not read all the various files / pages / places
>where I state that UDMA requires flat cables explicitly qualified.

Why doesn't it work for me ? I have a 80 wire flat cable !
I have tried everything and given up... running pio mode.

_________________

@sg2

the via686b works well whit DMA after the fix.

how ever I do have the sii3112ide controller,
this one have lots of problems whit crc errors

even when use it in PIA mode as I'm doing now?

used to use this disk for disk cashe for IB and AWEB whit lots of problems, now I have moved my disk cashe back to my via686b disk that uses DMA whit out any problems, whats up whit that?


7.Workbench:> idetool -l sii3112ide.device
-------------------Unit 0 information------------------------
Flags : $00000187 - present, LBA48 used, supports DMA, ATA, supports cache flush, interrupts used,
Xfer mode : best pio / best dma / current : 12 / 70 / 12
Total blocks : 312581808
Blocksize : 512
Power mode : 2 / idle (ready for operation)
IO1 / IO2 / BMCR @ : $802428 / $802432 / $802450

Remov Med : no (probably harddisk)
Revision : 08.02D08
Serial # : WD-WCAL9383395
LBA : yes
Tot. Secs : 312581808
Tot. Size : 160041885696 bytes, 156290 mbytes, 156 gbytes
Main features :
IORDY : yes
SMART : enabled
Security mode : not enabled
Power mgmt : supported
Packet cmds : not supported
Write cache : enabled
Look ahead : enabled
Device reset : not supported
Write buffer cmd : supported
Read buffer cmd : supported
Nop cmd : not supported
Download microcode : supported
Read/write DMA queued cmd : not supported
CompactFlash cmd set : not supported
Advance power mgmt : not enabled
Acoustic mgmt : not supported
LBA 48 : supported
Minimum PIO cycle time : 120 ns
Minimum PIO c.t. (IORDY) : 120 ns
DMA : yes
Minimum reg. cycle time : 120 ns
mode 64 ( 16 MB/s) : yes
mode 65 ( 25 MB/s) : yes
mode 66 ( 33 MB/s) : yes
mode 67 ( 44 MB/s) : yes
mode 68 ( 66 MB/s) : yes
mode 69 (100 MB/s) : yes
mode 70 (133 MB/s) : yes
PIO :
mode 8 ( 3 MB/s) : yes (always)
mode 9 ( 5 MB/s) : yes (always)
mode 10 ( 8 MB/s) : yes (always)
mode 11 ( 11 MB/s) : yes
mode 12 ( 16 MB/s) : yes
Xfer S/IRQ: 16 (Max. number of sectors that can be transferred per interrupt on READ/WRITE MULTIPLE commands)
Xfer S/MUL: 16 (Max. number of sectors currently set to transfer on READ/WRITE MULTIPLE commands)

Last edited by NutsAboutAmiga on 30-Jul-2005 at 04:46 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@zErec

Quote:

My master drive is at the end of the cable, and the slave is in the middle.

The master should be in the middle and the slave at the end.

/MoonSire

_________________
www.EtherealWorld.com

@MoonSire

ATA 133 cable:
blu = motherboard
grey = slave
black = master

Set the jumpers correctly to slave and master (try to don't use cable select).

_________________
ikir

@zErec

Quote:
With the idetool the hdd was set to mode 70 (udma 133) after the errors came up I switched to mode 69 (udma 100).


I got similar results with my maxtor drive in udma mode 70. With 69 it works well. I think, that it is poor quality of maxtor.

In winworld this doesnt matter, because its driver autosense problems and drops speed, if needed (in udma modes).

I tried other cable, run memtest and everything seems to be ok in my env. Yeah, as ok as SE can be.

Try avoid maxtor, since it is generally poor quality and it is slow.

System: A1 G3-SE, 512 MB kingston, SIL 0680, ATI 7000, and so on.

@MoonSire

Hi, you should connect like this:

mainboard slave-device master-device
or mainboard none-device master-device

greetings
zErec

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@mlehto

"I got similar results with my maxtor drive in udma mode 70. With 69 it works well. I think, that it is poor quality of maxtor."

Maybe that is the reason but I think there is still room form optimizing the
SIL0680 UDMA drivers or stephane? : O )

zErec

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@mlehto

Quote:"Try avoid maxtor, since it is generally poor quality and it is slow."

It seems almost everytime I read a thread concerning hard disk problems,
eventually the name "Maxtor" shows up.

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

The disk I have problems whit is an (slow) "Western Digital Disk" serial ata

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Western Digital is known for not working with all motherboards.
Even on PC's. Especially on older motherboards.
For example WD created a lot of problems on the classics as well
and was often recommended not to buy for your Amiga.


@Thread

But Maxor creating problems is a new one. Could someone (SG2?)
maybe tell us if this was the hardware not following the UDMA specs
or a fault in the OS4 driver?

My harddrive is a Maxtor DiamondMax 9 80GB 8MB UDMA133 Model: 6Y080P0
I have not noticed any problem with it. But I will try these examples given here.

Last edited by Samwel on 31-Jul-2005 at 12:55 AM.

_________________
/Harry

[SOLD] µA1-C - 750GX 800MHz - 512MB - Antec Aria case

Avatar by HNL_DK!