LONG: hdparm: nefunkcni -y -Y a kupodivu funkcni -S

[Martin Sittek]

Dobry den vespolek,

mam notebook Asus L7200 a zatouzil jsem naucit se vypinat HDD (planuji
ze si z neho casem udelam fax/zaznamnik - takze bude bezet porad a zda
se mi ze by nebylo spatne alespon vypinat LCD a HDD). Tudiz jsem si
nainstaloval hdpram v.3.6 a zacal jsem nastavovat co se da... (snad s 
rozumem :-).

Predem bych se chtel zeptat, zda je vporadku co jsem nastavil a co 
nedelalo problemy. 

Dle stitku na HDD mam:
Fujitsu - made in thailand
model: MHC 2040 AT
date: 1998-09
id: HTIN  <- nevim jestli je to dulezite

Dle dodaneho manualu by to mel byt:
4GB - 2.5" UltraDMA/33IDE

Dale uvadim co mi o tomto HDD pise bios - podle toho jsem provadel 
nastaveni:

BIOS:                             Mnou nastavene parametry `hdparm`:
Multi-Sector Transfers: 16 sectors                          -m16
LBA Mode Control: Enable                                    nic
32Bit I/O: Enable                                           -c1
Transfer Mode: Fast PIO 4                                   -X12 *
Ultra DMA Mode: Mode 2                                      -X66

* je (pro mne) zajimave, ze nefunguje -p4, nicmene v man se pise:
...This feature is suported in the kernel for only a few "known"
cipsets.. takze predpokladam ze ten muj chipset je 'unknown'.
Pri pouziti -p4 mi to vypise:
attempting to set PIO mode to 4
HDIO_SET_PIO_MODE failed: Function not implemented

Byl bych vdecny, kdyby k vyse uvedenemu nastaveni (ktere chci umistit
do najakeho startovaciho skriptu) mel nekdo nejake zajimave podnety
ci postrehy, bylo-li by mozna je zde uvest. :-) Hlavne mne zajimaji
ty "konfliktni" parametry -p4 versus -X12.

Pro jistotu prikladam (dle meho nazoru) nastaveni zajimavych voleb
u mnou zkompilovaneho jadra:

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_VIA82C586 is not set
# CONFIG_BLK_DEV_CMD646 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m

Snad jeste pridam hdparam -i a -v:

/dev/hda:

 Model=FUJITSU MHC2040AT, FwRev=0818, SerialNo=01099055
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
 RawCHS=7944/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=0(?), BuffSize=0kB, MaxMultSect=16, MultSect=16
 DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
 CurCHS=7944/16/63, CurSects=8007552, LBA=yes, LBAsects=8007552
 tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2 
 IORDY=yes, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4 
 UDMA modes: mode0 mode1 *mode2 


/dev/hda:
 multcount    = 16 (on)
 I/O support  =  1 (32-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  1 (on)
 nowerr       =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 993/128/63, sectors = 8007552, start = 0


No a po tak obsirnem uvodu se konecne dostavam k jadru pudla dotazu.
Po takovemto vastaveni (ale jak jsem po restaru zjistil i bez jakychkoliv
nastaveni) mi funguje jak ma parametr -S - cili disk se po prislusnem
time outu poslusne zastavi a mlci, nicmene se tak nedeje po -Y, coz by melo 
byt podle meho nazoru stejne jako -S ale okamzite. Disk se sice na chvili
zastavi ale pak se zase spusti a vypise toto:

hda: drive not ready for command
hda: status error: status =0x00 { }
hda: drive not ready for command
hda: status error: status =0x00 { }
hda: drive not ready for command
hda: status error: status =0x00 { }
hda: drive not ready for command
ide0: reset: success

Diky za jakekoliv podnety ci rady.

PS: Doufam ze mne neukamenujete za delku tohoto emailu ale snazil jsem
se zde uvest vse potrebne - Snad jsem ani prislis neporusil Meta-FAQ
konference :-)

--
Martin Sittek