[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: hdparm



Michel a écrit:
Bonjour ,

C'est bizarre , il m'est impossible de passer mes HD en DMA !

Si je lance hdparm -d1 /dev/hda , j'obtiens un joyeux :

/dev/hda:
 setting using_dma to 1 (on)
 HDIO_SET_DMA failed: Operation not permitted
 using_dma    =  0 (off)

Pas glop !

Voici le resultat de hdparm -I /dev/hda :

/dev/hda:

non-removable ATA device, with non-removable media
        Model Number:           Maxtor 6Y080L0
        Serial Number:          Y3HXLAZE
        Firmware Revision:      YAR41BW0
Standards:
        Supported: 1 2 3 4 5 6 7
        Likely used: 7
Configuration:
        Logical         max     current
        cylinders       16383   4047
        heads           16      16
        sectors/track   63      255
        bytes/track:    0               (obsolete)
        bytes/sector:   0               (obsolete)
        current sector capacity: 16511760
        LBA user addressable sectors = 160086528
Capabilities:
        LBA, IORDY(can be disabled)
        Buffer size: 2048.0kB   ECC bytes: 57   Queue depth: 1
Standby timer values: spec'd by standard, no device specific minimum
        r/w multiple sector transfer: Max = 16  Current = 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    NOP cmd
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
           *    look-ahead
           *    write cache
           *    Power Management feature set
                Security Mode feature set
           *    SMART feature set
                SET MAX security extension
                Advanced Power Management feature set
           *    DOWNLOAD MICROCODE cmd
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
                frozen
        not     expired: security count
        not     supported: enhanced erase
HW reset results:
        CBLID- above Vih
        Device num = 0 determined by the jumper
Checksum: correct

Une idee ?

Amicalement

Michel


Desole pour le bruit :(

Apres de longues recherches sur le net , cela venait  de ma
carte mere ( MSI KT3 , chipset VIA KT333 ) mal geree par le
kernel 2.4.18 . En utilisant un 2.4.20-K7 , tout est rentre
dans l'ordre !

Merci pour vos reponses

Amicalement

Michel

--

Tuxophiles, bien sur que nous sommes tuxophiles, et winophobes en plus.
Mais il ne faut pas confondre tuxophilie et tuxo-integrisme, l'amalgame
est fait beaucoup trop rapidement par les winophiles-tuxophobes .



Reply to: