SATA drive != DMA

I just recently installed Red Hat ES 4 on a NAS server I've built and
I'm having problems with the DMA setup on ide0.

First things first, system configuration:

(1) 80G SATA Seagate Barracuda drive installed on ide0 master
(1) ATAPI cdrom drive on ide1 master

With this configuration, and the 2.6.9-11.ELsmp that comes with the
current install of RHES4, the ata_piix driver is used properly and I can
enable DMA for the SATA drive (didn't check the IDE, don't care).

So I add Areca SATA RAID card and add drivers into the latest kernel
2.6.13 and compile everything no problem.

Now when I boot, the E-IDE driver loads first:

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
hda: ST380817AS, ATA DISK drive
Probing IDE interface ide1...
hdc: CD-224E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=16383/255/63
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4 < hda5 >
hdc: ATAPI 24X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
ACPI: PCI Interrupt 0000:03:0e.0[A] -> GSI 56 (level, low) -> IRQ 177
ARECA RAID: 64BITS PCI BUS DMA ADDRESSING SUPPORTED
scsi0 : ARECA ARC1120 PCI-X 8 PORTS SATA RAID CONTROLLER (RAID6-ENGINE Inside)
Driver Version 1.20.00.07
Vendor: Areca Model: ARC-1120-VOL#00 Rev: R001
Type: Direct-Access ANSI SCSI revision: 03
arcmsr device major number 254
SCSI device sda: 1464843264 512-byte hdwr sectors (750000 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 1464843264 512-byte hdwr sectors (750000 MB)
SCSI device sda: drive cache: write back
sda: sda1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0

then later:

libata version 1.12 loaded.
ata_piix version 1.04
ata_piix: combined mode detected
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 185
ata: 0x1f0 IDE port busy
ata: 0x170 IDE port busy
ata_piix: probe of 0000:00:1f.2 failed with error -16

How can I prevent the E-IDE driver from loading? It's really affecting
the performance of the 80G SATA drive because I can't enable DMA:

$ hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media
Model Number: ST380817AS
Serial Number: 4MR24ENF
Firmware Revision: 3.42
Standards:
Used: ATA/ATAPI-6 T13 1410D revision 2
Supported: 6 5 4 3
Configuration:
Logical max current
cylinders 16383 65535
heads 16 1
sectors/track 63 63
--
CHS current addressable sectors: 4128705
LBA user addressable sectors: 156301488
LBA48 user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 4 Queue depth: 32
Standby timer values: spec'd by Standard, no device specific
minimum
R/W multiple sector transfer: Max = 16 Current = 16
Recommended acoustic management value: 254, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5
udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* FLUSH CACHE EXT command
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
* 48-bit Address feature set
SET MAX security extension
* DOWNLOAD MICROCODE cmd
* SMART self-test
* SMART error logging
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct

$ hdparm -i /dev/hda

/dev/hda:

Model=ST380817AS, FwRev=3.42, SerialNo=4MR24ENF
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no WriteCache=enabled
Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:

* signifies the current active mode

$ hdparm -d 1 /dev/hda

/dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)
using_dma = 0 (off)

$ hdparm -t /dev/hda

/dev/hda:
Timing buffered disk reads: 20 MB in 3.32 seconds = 6.02 MB/sec

This machine has the 82801FBM (ICH6M) SATA controller, and I've read
about the problems with SATA and PATA drives on the same system, but I'm
wondering if I'm overlooking something here because I WASN'T having this
problem when it was just the SATA drive and ATAPI CD-ROM?

$ lspci
00:00.0 Host bridge: Intel Corporation E7520 Memory Controller Hub (rev 0c)
00:00.1 Class ff00: Intel Corporation E7525/E7520 Error Reporting Registers (rev 0c)
00:01.0 System peripheral: Intel Corporation E7520 DMA Controller (rev 0c)
00:02.0 PCI bridge: Intel Corporation E7525/E7520/E7320 PCI Express Port A (rev 0c)
00:04.0 PCI bridge: Intel Corporation E7525/E7520 PCI Express Port B (rev 0c)
00:06.0 PCI bridge: Intel Corporation E7520 PCI Express Port C (rev 0c)
00:1c.0 PCI bridge: Intel Corporation 6300ESB 64-bit PCI-X Bridge (rev 02)
00:1d.0 USB Controller: Intel Corporation 6300ESB USB Universal Host Controller (rev 02)
00:1d.1 USB Controller: Intel Corporation 6300ESB USB Universal Host Controller (rev 02)
00:1d.4 System peripheral: Intel Corporation 6300ESB Watchdog Timer (rev 02)
00:1d.5 PIC: Intel Corporation 6300ESB I/O Advanced Programmable Interrupt Controller (rev 02)
00:1d.7 USB Controller: Intel Corporation 6300ESB USB2 Enhanced Host Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 0a)
00:1f.0 ISA bridge: Intel Corporation 6300ESB LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 6300ESB SATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 6300ESB SMBus Controller (rev 02)
01:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A (rev 09)
01:00.1 PIC: Intel Corporation 6700/6702PXH I/OxAPIC Interrupt Controller A (rev 09)
01:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B (rev 09)
01:00.3 PIC: Intel Corporation 6700PXH I/OxAPIC Interrupt Controller B (rev 09)
02:02.0 PCI bridge: Intel Corporation 80331 [Lindsay] I/O processor (rev 0a)
02:03.0 RAID bus controller: Marvell Technology Group Ltd. MV88SX6081 8-port SATA II PCI-X Controller (rev 03)
03:0e.0 RAID bus controller: Areca Technology Corp. ARC-1120 8-Port PCI-X to SATA RAID Controller
07:01.0 Ethernet controller: Intel Corporation 82541GI/PI Gigabit Ethernet Controller (rev 05)
07:02.0 Ethernet controller: Intel Corporation 82541GI/PI Gigabit Ethernet Controller (rev 05)
08:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)

I'm tempted to try uncommenting 'ATA_ENABLE_ATAPI' in
include/linux/libata.h and disabling 'GENERIC_IDE' but I'm concerned about stability.. :-/

Is there something I'm readily missing here?

You should do "hdparm -d 1 /dev/hda" as root. And what is /dev/sda ? Maybe you can access your disk thought it ?

me thinks hdparm is still for ide

http://axljab.homelinux.org/Hdparm

Originally posted by CyberIron I just recently installed Red Hat ES 4 on a NAS server I've built and I'm having problems with the DMA setup on ide0. First things first, system configuration: (1) 80G SATA Seagate Barracuda drive installed on ide0 master (1) ATAPI cdrom drive on ide1 master

Usually (depends on bios) when a SATA disk is in "SATA mode" (or "native mode" or whatever) it is recognised as ide2+
Are you sure that it is not in "IDE mode" in BIOS ?

Originally posted by CyberIron With this configuration, and the 2.6.9-11.ELsmp that comes with the current install of RHES4, the ata_piix driver is used properly and I can enable DMA for the SATA drive (didn't check the IDE, don't care).

Is the disk recognised as /dev/sda ?
DMA should be enabled by default.

Originally posted by CyberIron So I add Areca SATA RAID card and add drivers into the latest kernel 2.6.13 and compile everything no problem. Now when I boot, the E-IDE driver loads first: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Probing IDE interface ide0... hda: ST380817AS, ATA DISK drive libata version 1.12 loaded. ata_piix version 1.04 ata_piix: combined mode detected ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 185 ata: 0x1f0 IDE port busy ata: 0x170 IDE port busy ata_piix: probe of 0000:00:1f.2 failed with error -16

There is an option that says to use ide support for sata which conflicts with libata.
Check your .config file. When you compiled your kernel did you enable "CONFIG_BLK_DEV_IDE_SATA" ?

Originally posted by CyberIron How can I prevent the E-IDE driver from loading? It's really affecting the performance of the 80G SATA drive because I can't enable DMA

Add "ide0=noprobe" to the kernel parameters (eg. in /etc/grub.conf). This
prevents the compiled-in IDE driver from detecting your controller and leave
the way free for the SATA module loaded in initrd.

Thank you for the reply. I was unaware of the "0 reply" feature, and will take heed of it in the future.

I have scoured the net regarding my error, but it always seems to come up without solid answers.

In all cases the drives in question are either SCSI or SATA. Most of the replys have to do with compiling a fresh kernel with SCSI and SATA support built in, rather than modulals. This doesn't really apply to me though, as I have installed off a live CD. Am I doomed?

Seagate SATA drives and SATA controllers do not mix well. I mean enabling DMA with a SATA Seagate drive is a pain. I suggest IDE o SATA drives from Western Digital or Hitachi. Western Digital and Hitachi drives are the best for a data server that needs low accessing times or for a desktop system.

You can make the software for the controller be a module. If you want to automatically mount it at boot up, you have to include it in the ramdisk file or initrd.