Re: DMA limited to UDMA33, non-ATA66 cable or device

2004-04-09 Thread Me
en I try to change to udma100 > > --- > > atacontrol mode 0 udma100 biosdma > > Master = UDMA33 > > Slave = BIOSPIO > > - > > console output after i use atacontrol > > -------------

Re: DMA limited to UDMA33, non-ATA66 cable or device

2004-04-09 Thread Jonathan Arnold
limited to UDMA33, non-ATA66 cable or device What does : $ atacontrol list say? It sure looks like you have a PIO device on the same cable as your UDMA hard drive. And are you sure you have a UDMA 100 cable? It should have a blue female plug for the motherboard side. -- Jonathan Arnold (mailto

DMA limited to UDMA33, non-ATA66 cable or device

2004-04-05 Thread Me
-- Dmesg out put --- atapci0: port 0xfc00-0xfc0f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ata0-master: DMA limited to UDMA33, non-ATA66 cable or device ad0: 28615MB [58140/16/6

RE: DMA limited to UDMA33, non-ATA66 cable or device

2003-08-05 Thread Brent Wiese
se > I don't know how to test it (like hdparm in linux). > > --Other data: > > output from dmesg > > atapci1: port > 0x1010-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f > mem 0xf000-0xf000 irq 2 at device 8.0 on pci0 > ad4: DMA limit

Re: DMA limited to UDMA33, non-ATA66 cable or device

2003-07-25 Thread Lucas Holt
There might be another possibility... I ran into a problem once where Solaris would only allow me to use ATA33 on a Sis controller because the controller driver was unstable at ATA66 in solaris. Perhaps its down clocking so to speak. I also had a problem with a promise pci ide controller card

Re: DMA limited to UDMA33, non-ATA66 cable or device

2003-07-25 Thread Rob
#x27;t know how to test it (like hdparm in linux). --Other data: output from dmesg atapci1: port 0x1010-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f mem 0xf000-0xf000 irq 2 at device 8.0 on pci0 ad4: DMA limited to UDMA33, non-ATA66 cable or device ad6: DMA limited to

DMA limited to UDMA33, non-ATA66 cable or device

2003-07-25 Thread Ugo Bellavance
mesg > > atapci1: port > 0x1010-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f > mem 0xf000-0xf000 irq 2 at device 8.0 on pci0 > ad4: DMA limited to UDMA33, non-ATA66 cable or device > ad6: DMA limited to UDMA33, non-ATA66 cable or device > ar0: 1907348M

DMA limited to UDMA33, non-ATA66 cable or device

2003-07-25 Thread Ugo Bellavance
and drives support > udma100. I don't know if it is a bogus error, because > I don't know how to test it (like hdparm in linux). > > --Other data: > > output from dmesg > > atapci1: port > 0x1010-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f &

Re: DMA limited to UDMA33, non-ATA66 cable or device

2003-07-24 Thread Vulpes Velox
-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f > mem 0xf000-0xf000 irq 2 at device 8.0 on pci0 > ad4: DMA limited to UDMA33, non-ATA66 cable or device > ad6: DMA limited to UDMA33, non-ATA66 cable or device > ar0: 1907348MB [65535/255/63] > status: READY subdisk

DMA limited to UDMA33, non-ATA66 cable or device

2003-07-24 Thread Ugo Bellavance
027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f mem 0xf000-0xf000 irq 2 at device 8.0 on pci0 ad4: DMA limited to UDMA33, non-ATA66 cable or device ad6: DMA limited to UDMA33, non-ATA66 cable or device ar0: 1907348MB [65535/255/63] status: READY subdisks: 0 READY ad4: 76319MB [155061/16/6