On Thu, Jan 31, 2008 at 01:48:00PM -0600, Darryl Hoar wrote:
> 
> 
> > Looked at dmesg, but am unsure of how Freebsd would
> > identify a SATA drive.
> 
> >> it says it's sata like that:
> 
> >> ad10: 305244MB <SAMSUNG HD321KJ CP100-10> at ata5-master SATA300
> >> ad12: 305245MB <SAMSUNG HD321KJ CP100-10> at ata6-master SATA300
> >> ad14: 305245MB <SAMSUNG HD321KJ CP100-10> at ata7-master SATA300
> >> ad18: 476940MB <SAMSUNG HD501LJ CR100-12> at ata9-master SATA300
> >> ad20: 476940MB <SAMSUNG HD501LJ CR100-12> at ata10-master SATA300
> 
> 
> >
> > Wouldn't Freebsd fail to install if it didn't recognize the drives
> > as SATA ?
> >
> >>no. but if it recognizes it as ATA-33 or like this - something is wrong.
> 
> Exactly my problem.  It says
> ad4: DMA limited to UDMA33, device found non-ATA66 cable
> ad4: 152587MB <SAMSUNG HE160HJ JF800-24> at ata2-master UDMA33
> ad6: DMA limited to UDMA33, device found non-ATA66 cable
> ad6: 152587MB <SAMSUNG HE160HJ JF800-24> at ata3-master UDMA33
> 
> Weird.  What would cause this ??


That is usually what happens when the disk controller is one that FreeBSD
does not have support for, so it treats the controller as a "Generic" ATA
controller.  Should normally work fine albeit with somewhat suboptimal
performance.  (And even though it says UDMA33 a SATA controller should still
work at SATA150 speed, so the performance penalty should not be so severe.)



-- 
<Insert your favourite quote here.>
Erik Trulsson
[EMAIL PROTECTED]
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to