ahci.ko in RELENG_8_2, what about atacontrol cap?

Patrick M. Hausen hausen at punkt.de
Sat Apr 2 09:34:31 UTC 2011


Hi, all,

On my system using the "old" ATA driver, I can use a command like this
to get useful information about my disk drives:

------------------------------------------------------------
nas-pmh# atacontrol cap ad4

Protocol              SATA revision 2.x
device model          ST32000542AS
serial number         5XW251QF
firmware revision     CC34
cylinders             16383
heads                 16
sectors/track         63
lba supported         268435455 sectors
lba48 supported       3907029168 sectors
dma supported
overlap not supported

Feature                      Support  Enable    Value           Vendor
write cache                    yes	yes
read ahead                     yes	yes
Native Command Queuing (NCQ)   yes	 -	31/0x1F
Tagged Command Queuing (TCQ)   no	no	31/0x1F
SMART                          yes	yes
microcode download             yes	yes
security                       yes	no
power management               yes	yes
advanced power management      yes	yes	49344/0xC0C0
automatic acoustic management  yes	yes	254/0xFE	254/0xFE
------------------------------------------------------------

When I switch to the new AHCI driver the drives are connected to
the CAM subsystem:

------------------------------------------------------------
nas-pmh# camcontrol devlist
<ST32000542AS CC34>                at scbus0 target 0 lun 0 (ada0,pass0)
<ST32000542AS CC34>                at scbus1 target 0 lun 0 (ada1,pass1)
<ST32000542AS CC34>                at scbus2 target 0 lun 0 (ada2,pass2)
<ST32000542AS CC34>                at scbus3 target 0 lun 0 (ada3,pass3)
<JetFlash Transcend 2GB 8.07>      at scbus4 target 0 lun 0 (da0,pass4)
------------------------------------------------------------

But:

------------------------------------------------------------
nas-pmh# camcontrol inquiry ada0
nas-pmh# camcontrol readcap ada0
(pass0:ahcich0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 
(pass0:ahcich0:0:0:0): CAM status: CCB request was invalid
------------------------------------------------------------


Obvious question: is there a way to get the same information (NCQ support,
write cache status, ...) with the new driver?

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
info at punkt.de       http://www.punkt.de
Gf: Jürgen Egeling      AG Mannheim 108285



More information about the freebsd-stable mailing list