SATA question

[Erik Trulsson]

On Sun, Feb 03, 2008 at 01:25:07AM -0800, Ted Mittelstaedt wrote:
> 
> Looks like it isn't detecting it as a generic controller.
> 
> But I think this is the problem.  Note that the system is
> applying ata2 and ata3 to atapci0, and ata0 and ata1 to
> atapci1.  This is backwards, I've not seen this before in
> the ata driver.  Normally, ata0 and ata1 are applied to the
> first controller - atapci0 - and ata2 and ata3 are applied
> to the second controller - atapci1 - and so on.

I have seen that before on one of my computers:

  atapci0: <VIA 6420 SATA150 controller> port 0xd000-0xd007,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc00f,0xb800-0xb8ff irq 20 at device 15.0 on pci0
  ata2: <ATA channel 0> on atapci0
  ata3: <ATA channel 1> on atapci0
  atapci1: <VIA 8237 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0
  ata0: <ATA channel 0> on atapci1
  ata1: <ATA channel 1> on atapci1

It looks like ata0 and ata1 are assigned to whichever interface looks like
the "standard" ATA interface, regardless of in what order various ATA
controllers are detected.



> 
> Søren Schmidt put the support in for this chipset to the
> ata driver.  I'd file a PR and put it down to a driver bug.
> 
> Ted
> 
> 
> > -----Original Message-----
> > From: owner-freebsd-questions at freebsd.org
> > [mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Darryl Hoar
> > Sent: Friday, February 01, 2008 7:06 AM
> > To: 'Ted Mittelstaedt'; freebsd-questions at freebsd.org
> > Subject: RE: SATA question
> >
> >
> > <snip>
> > > -----Original Message-----
> > > From: owner-freebsd-questions at freebsd.org
> > > [mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Darryl Hoar
> > > Sent: Tuesday, January 29, 2008 6:59 AM
> > > To: freebsd-questions at freebsd.org
> > > Subject: SATA question
> > >
> > >
> > > Well,
> > > maybe I spoke to soon.  While looking at dmesg in prep for doing
> > > a custom kernel for my new server, I noticed an oddity.
> > >
> > > ad4 - DMA limited to UDMA33, device found non-ata66 cable.
> > > ad4 - <SAMSUN HE160HJ JF800-24>
> > >
> > > Is this telling me the system recognized my
> > > 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as
> > > a UDMA33 ?
> > >
> >
> > >>No doubt, a pciconf followed by insertion of the ID into the
> > >>ata detection routines would help - assuming your sata chipset
> > >>is supported.
> >
> > >>You don't have the entire dmesg here but it looks like it's
> > >>using the generic driver.
> >
> > >>Ted
> >
> >
> > atapci0: <ServerWorks HT1000 SATA150 controller> port
> > 0xecb0-0xecb7,0xeca0-0xeca
> > 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem
> > 0xefdfe000-0xefdfffff irq 6
> > at d
> > evice 14.0 on pci3
> > ata2: <ATA channel 0> on atapci0
> > ata3: <ATA channel 1> on atapci0
> >
> > atapci1: <ServerWorks HT1000 UDMA100 controller> port
> > 0x1f0-0x1f7,0x3f6,0x170-0x
> > 177,0x376,0x8c0-0x8cf at device 2.1 on pci0
> > ata0: <ATA channel 0> on atapci1
> > ata1: <ATA channel 1> on atapci1
> >
> > acd0: CDRW <HL-DT-STCD-RW/DVD-ROM GCC-T10N/A102> at ata0-master UDMA33
> > 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
> >
> > This is the copied relevant portions of demsg's output. I have only used
> > pciconf to
> > list devices, so am basically unfamilar with it.
> >
> > So, how do I get the system to recognize the drives as SATA ?
> >


-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013 at student.uu.se