try turning off dma on the affected drive...see if it boots correctly
> At 21:40 -0500 12/01/2003, Aaron Myles Landwehr wrote:
>>I have the same problem with my asus p4s8x mobo on freebsd 4.9 and
>>priorIf i disable dma the cd will boot.;
>>5.1 works correctly(with dma enabled).
>>from the case
At 21:40 -0500 12/01/2003, Aaron Myles Landwehr wrote:
>I have the same problem with my asus p4s8x mobo on freebsd 4.9 and
>priorIf i disable dma the cd will boot.;
>5.1 works correctly(with dma enabled).
>from the cases i've seen...they all include an ASUS motherboard...
>-aaron<[EMAIL PROTECT
At 00:22 + 12/02/2003, Lee Harr wrote:
>>I've got both 4.9 and 5.1 loaded on my new ASUS A7N8X Deluxe
>>with two 160Gb disks on the primary ATA controller.
>>
>
>>it hangs during kernel boot after the
>>message:
>>
>>ad1: READ command timeout tag=0 serv=0 - resetting
>>ata0: resetting devices
>
I've got both 4.9 and 5.1 loaded on my new ASUS A7N8X Deluxe
with two 160Gb disks on the primary ATA controller.
it hangs during kernel boot after the
message:
ad1: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices
Yup. I have the same thing.
What I do is go in to the BIOS a
I have the same problem with my asus p4s8x mobo on freebsd 4.9 and
priorIf i disable dma the cd will boot.;
5.1 works correctly(with dma enabled).
from the cases i've seen...they all include an ASUS motherboard...
-aaron<[EMAIL PROTECTED]>
> I've got both 4.9 and 5.1 loaded on my new ASUS A7N8X
I've got both 4.9 and 5.1 loaded on my new ASUS A7N8X Deluxe
with two 160Gb disks on the primary ATA controller. 5.1 does
much better handling both ATA disks. When I run 4.9 with the
second disk connected, it hangs during kernel boot after the
message:
ad1: READ command timeout tag=0 serv=0 - r
