Date: Sat, 05 Jun 2010 08:58:27 +0300 From: Alexander Motin <mav@FreeBSD.org> To: freebsd-amd64@freebsd.org Subject: Re: why does UATA/133 == UATA/100 on amd64? Message-ID: <4C09E783.9090007@FreeBSD.org> In-Reply-To: <mailpost.1275715362.1687265.65062.mailing.freebsd.amd64@FreeBSD.cs.nctu.edu.tw> References: <83a931b7eb25b24c7bcc6396724d9c39.dnswclient@www.dnswatch.com> <mailpost.1275715362.1687265.65062.mailing.freebsd.amd64@FreeBSD.cs.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy wrote: > On 2010-Jun-04 16:36:08 -0700, fbsdmail@dnswatch.com wrote: >> After _finally_ making the correct decisions to install amd64 on an >> AMD64 system. I was able to make/build/install world && kernel, I see >> a difference in drive recognition. > > Can you please do a verbose boot and post the resultant dmesg somewhere > (preferably with your USB DVD drive connected). > >> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >> kernel: ad6: 476940MB <Seagate ST3500630AS 3.AAK> at ata3-master SATA300 > >> kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >> kernel: ad6: setting UDMA100 >> kernel: ad6: 476940MB <Seagate ST3500630AS 3.AAK> at ata3-master UDMA100 >> SATA 3Gb/s > > The 'UDMA' numbers are meaningless for SATA controllers/drives. The 'UDMA' numbers are meaningless for _native_ SATA controllers/drives. They may be not meaningless for legacy SATA devices, using SATA->PATA bridge inside. Some bridges do not support UDMA133 on PATA part, so ata(4) prefers not to use it. But in this case it is indeed meaningless. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C09E783.9090007>