Hinweis: Das Forum wird geschlossen! Neue Registrierungen sind nicht mehr möglich!

 Zurück zu Pro-Linux   Foren-Übersicht   FAQ     Suchen    Mitgliederliste
[x] Probleme mit DMA-Modus

 
Neuen Beitrag schreiben   Auf Beitrag antworten    Pro-Linux Foren-Übersicht -> Hardware
Vorheriges Thema anzeigen :: Nächstes Thema anzeigen  
Autor Nachricht
Lateralus
prolinux-forum-admin


Anmeldungsdatum: 05.05.2004
Beiträge: 1238

BeitragVerfasst am: 02. Feb 2005 0:45   Titel: [x] Probleme mit DMA-Modus

Ich habe Probleme, bei meinen Laufwerken den DMA-Modus zu aktivieren:

Code:

Luna root # hdparm -d 1 /dev/hda
/dev/hda:
 setting using_dma to 1 (on)
 HDIO_SET_DMA failed: Operation not permitted
 using_dma    =  0 (off)


Das gleiche mit hd{b,c,d}.

Ich arbeite mit Gentoo Linux 2004.2 Kernel 2.6.7. DMA müsste einkompiliert worden sein:

Code:

Luna root # grep DMA /boot/config-2.6.7-gentoo-r11
CONFIG_GENERIC_ISA_DMA=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y


Code:

Luna root # hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media
        Model Number:       Maxtor 4D060H3                         
        Serial Number:      D30ET7VE           
        Firmware Revision:  DAH017K0
Standards:
        Used: ATA/ATAPI-6 T13 1410D revision 0
        Supported: 6 5 4 3
Configuration:
        Logical         max     current
        cylinders       16383   4047
        heads           16      16
        sectors/track   63      255
        --
        CHS current addressable sectors:   16511760
        LBA    user addressable sectors:  120069936
        device size with M = 1024*1024:       58627 MBytes
        device size with M = 1000*1000:       61475 MBytes (61 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        bytes avail on r/w long: 57     Queue depth: 1
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        Advanced power management level: unknown setting (0x0000)
        Recommended acoustic management value: 192, current value: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5
             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
           *    SMART feature set
           *    Device Configuration Overlay feature set
           *    Automatic Acoustic Management feature set
                SET MAX security extension
                Advanced Power Management feature set
           *    DOWNLOAD MICROCODE cmd
           *    SMART self-test
           *    SMART error logging
HW reset results:
        CBLID- above Vih
        Device num = 0 determined by the jumper
Checksum: correct

Luna root # hdparm -I /dev/hdb

/dev/hdb:

ATA device, with non-removable media
        Model Number:       Maxtor 6Y160P0                         
        Serial Number:      Y452B7BE           
        Firmware Revision:  YAR41BW0
Standards:
        Supported: 7 6 5 4
        Likely used: 7
Configuration:
        Logical         max     current
        cylinders       16383   64761
        heads           16      1
        sectors/track   63      255
        --
        CHS current addressable sectors:   16514055
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors:  320173056
        device size with M = 1024*1024:      156334 MBytes
        device size with M = 1000*1000:      163928 MBytes (163 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 1
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        Advanced power management level: unknown setting (0x0000)
        Recommended acoustic management value: 192, current value: 254
        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
           *    FLUSH CACHE EXT command
           *    Mandatory FLUSH CACHE command
           *    Device Configuration Overlay feature set
           *    48-bit Address feature set
           *    Automatic Acoustic Management feature set
                SET MAX security extension
                Advanced Power Management feature set
           *    DOWNLOAD MICROCODE cmd
           *    SMART self-test
           *    SMART error logging
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
HW reset results:
        CBLID- above Vih
        Device num = 1 determined by the jumper
Checksum: correct



Hat jemand Tipps?


Zuletzt bearbeitet von Lateralus am 02. Feb 2005 16:40, insgesamt 1-mal bearbeitet
 
Benutzer-Profile anzeigen Private Nachricht senden

jochen
prolinux-forum-admin


Anmeldungsdatum: 14.01.2000
Beiträge: 699
Wohnort: Jülich

BeitragVerfasst am: 02. Feb 2005 8:00   Titel:

" HDIO_SET_DMA failed: Operation not permitted " ?!?

Da fallen mir nur zwei Punkte ein.

1. Hast Du unterstützung für den IDE-Controller des Boards mit einkompiliert? Deine Infos sind prima, aber Angaben über Board/Chipsatz/Chipsatztreiber im Kernel fehlen.

2. Arbeitest Du mit irgendwelchen Security Features wie SELinux u.ä.? Das könnte das "Operation not permitted" vielleicht erklären...

Jochen
_________________
Die grösste Lüge der EDV? "Mal eben..."
 
Benutzer-Profile anzeigen Private Nachricht senden Website dieses Benutzers besuchen

Lateralus
prolinux-forum-admin


Anmeldungsdatum: 05.05.2004
Beiträge: 1238

BeitragVerfasst am: 02. Feb 2005 16:38   Titel:

Der Controller-Treiber war nicht einkompiliert. Vielen Dank für die Hilfe!
 
Benutzer-Profile anzeigen Private Nachricht senden

huibuh
Gast





BeitragVerfasst am: 03. Feb 2005 0:09   Titel:

wenn du dma im kernel hast musst du es auch nicht extra aktivieren. hatte ich auch zuerst, ist aber nicht notwendig.
habe es aus der /etc/conf.d/local.start rausgenommen , nur das dma im kernel aktiviert, selbe durchsatzrate.
 

Beiträge vom vorherigen Thema anzeigen:   
     Pro-Linux Foren-Übersicht -> Hardware Alle Zeiten sind GMT + 1 Stunde
Seite 1 von 1

 
Gehen Sie zu:  

Powered by phpBB © phpBB Group
pro_linux Theme © 2004 by Mandaxy