Me wrote:
---
When I try to change to udma100
---
atacontrol mode 0 udma100 biosdma
Master = UDMA33
Slave = BIOSPIO
-
console output after i use atacontrol
-
ad0: DMA
Hi,
Thanks for your response.
Yes, It is a ata cable attached.
This is a Averatec 3050HW Laptop.
with 2 IDE channels.
the HDD is in channel 0 and a CDRW-DVD drive is in
channel 1.
In the bios the drives are deteched on each channel.
the drive was running at UDMA100 in windows.
I have scsi
This will happen sometimes if the cable is reversed. There is one connector
that should be labeled specifically for the motherboard (or is sometimes a
different color). If a standard 3 connector cable, its the one by itself, vs
the 2 that are spaced a few inches apart.
Maybe people reverse the
Ugo Bellavance wrote:
They're brand new cables, from promise, and I don't have this problem
under linux (I get over 40 MB/s transfer rate with hdparm). However, I will
try other cables eventually. If anyone has another idea, please let me
know. Thanks,
Ugo
--
Try getting new cables. I have had a
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
Try getting new cables. I have had a similar problem caused by bad cables
before.
On Thu, 24 Jul 2003 22:57:48 -0400 (EDT)
Ugo Bellavance [EMAIL PROTECTED] wrote:
Hi,
--System
FreeBSD 4.8 release
It is a kernel that I recompiled only to enable SMP.
The same error comes with the generic
