hdparm -i /dev/hdc -> Operation not permitted - Debian

This is a discussion on hdparm -i /dev/hdc -> Operation not permitted - Debian ; Hello, I was wonderign if someone could tell me if I am stupid or not: My PC's DVD writer is running in PIO Mode 4 as it seems - Writing with 2* results in unbearable CPU-load. ################################## lappi:/home/ruediger# hdparm -i ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: hdparm -i /dev/hdc -> Operation not permitted

  1. hdparm -i /dev/hdc -> Operation not permitted

    Hello,

    I was wonderign if someone could tell me if I am stupid or not:
    My PC's DVD writer is running in PIO Mode 4 as it seems - Writing with 2*
    results in unbearable CPU-load.
    ##################################
    lappi:/home/ruediger# hdparm -i /dev/hdc

    /dev/hdc:

    Model=MAT****ADVD-RAM UJ-840S, FwRev=1.00, SerialNo=
    Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
    RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
    BuffType=unknown, BuffSize=0kB, MaxMultSect=0
    (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
    IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
    PIO modes: pio0 pio1 pio2 pio3 pio4
    DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
    UDMA modes: udma0 udma1 *udma2
    AdvancedPM=no
    Drive conforms to: Unspecified: ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5
    ATA/ATAPI-6

    * signifies the current active mode
    ##################################
    So, in theory, the drive is running in UDMA2 mode - but burning an image
    shouldn't result in 100% CPU load then, or? Especially at 2* speed.
    ##################################
    lappi:/home/ruediger# hdparm -d1 /dev/hdc

    /dev/hdc:
    setting using_dma to 1 (on)
    HDIO_SET_DMA failed: Operation not permitted
    using_dma = 0 (off)
    ##################################
    Funnily the controllers module is in the kernel and DMA is active - my
    harddisk runs smoothly on the same controller.
    Aside from those problem, I also have no 3d accelleration, though DRI is
    loaded... but - anyway. Here is some output which might help you helping
    me:
    ##################################
    lappi:/home/ruediger# lsmod
    Module Size Used by
    arc4 1600 1
    ieee80211_crypt_wep 3840 1
    i915 17920 1
    rfcomm 36700 6
    l2cap 23108 5 rfcomm
    ipv6 246464 10
    parport_pc 25476 0
    lp 9476 0
    parport 33672 2 parport_pc,lp
    battery 8260 0
    pcmcia 33316 2
    eth1394 18120 0
    psmouse 37060 0
    ohci_hcd 19972 0
    ohci1394 32628 0
    yenta_socket 24652 2
    rsrc_nonstatic 12224 1 yenta_socket
    pcmcia_core 37520 3 pcmcia,yenta_socket,rsrc_nonstatic
    ipw2200 70376 0
    firmware_class 8384 2 pcmcia,ipw2200
    ieee80211 20680 1 ipw2200
    ieee80211_crypt 4484 2 ieee80211_crypt_wep,ieee80211
    tpm_atmel 4608 0
    tpm_nsc 5440 0
    tpm 8352 2 tpm_atmel,tpm_nsc
    snd_intel8x0m 15428 1
    snd_intel8x0 30304 1
    snd_ac97_codec 94332 2 snd_intel8x0m,snd_intel8x0
    snd_ac97_bus 1856 1 snd_ac97_codec
    snd_pcm_oss 48928 0
    snd_mixer_oss 17600 1 snd_pcm_oss
    snd_pcm 84360 4
    snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_ oss
    snd_timer 22404 1 snd_pcm
    snd 49764 11
    snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_ oss,snd_mixer_oss,snd_pcm,snd_timer
    snd_page_alloc 8712 3 snd_intel8x0m,snd_intel8x0,snd_pcm
    ehci_hcd 30344 0
    hci_usb 14160 6
    bluetooth 44868 15 rfcomm,l2cap,hci_usb
    usbhid 28612 0
    uhci_hcd 31568 0
    usbcore 116160 6 ohci_hcd,ehci_hcd,hci_usb,usbhid,uhci_hcd
    intel_agp 20316 1
    ntfs 204624 2
    vfat 11008 2
    fat 47004 1 vfat
    i810 21184 0
    drm 69976 3 i915,i810
    agpgart 30024 3 intel_agp,drm
    lappi:/home/ruediger# lspci
    0000:00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML
    Express Processor to DRAM Controller (rev 03)
    0000:00:02.0 VGA compatible controller: Intel Corporation Mobile
    915GM/GMS/910GML Express Graphics Controller (rev 03)
    0000:00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML
    Express Graphics Controller (rev 03)
    0000:00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
    Family) PCI Express Port 1 (rev 04)
    0000:00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
    Family) USB UHCI #1 (rev 04)
    0000:00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
    Family) USB UHCI #2 (rev 04)
    0000:00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
    Family) USB UHCI #3 (rev 04)
    0000:00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
    Family) USB UHCI #4 (rev 04)
    0000:00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
    Family) USB2 EHCI Controller (rev 04)
    0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4)
    0000:00:1e.2 Multimedia audio controller: Intel Corporation
    82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 04)
    0000:00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
    AC'97 Modem Controller (rev 04)
    0000:00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface
    Bridge (rev 04)
    0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA
    Controller (rev 04)
    0000:00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
    SMBus Controller (rev 04)
    0000:06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG (rev
    05)
    0000:06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
    RTL-8139/8139C/8139C+ (rev 10)
    0000:06:09.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus
    Controller
    0000:06:09.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE
    1394 Host Controller
    0000:06:09.3 Mass storage controller: Texas Instruments PCIxx21 Integrated
    FlashMedia Controller
    0000:06:09.4 0805: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621,
    PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) Controller
    ##################################
    Input welcome.
    --
    Sincerely

    Ruediger


  2. Re: hdparm -i /dev/hdc -> Operation not permitted

    On Sun, 22 Jan 2006 12:40:26 +0100, Ruediger wrote:

    > Hello,
    >
    > I was wonderign if someone could tell me if I am stupid or not:
    > My PC's DVD writer is running in PIO Mode 4 as it seems - Writing with 2*
    > results in unbearable CPU-load.


    Hi,

    I saw this old post and wondered if you got it fixed.

    Try running

    hdparm /dev/hdX

    That should tell how it sets your drives.

    I have a single cpu that has high cpu usage while burning. I have a much
    slower dual cpu that uses maybe about 12% while burning. I have never
    figured it out as both machines have dma set and everything looks great.

    Steve

  3. Re: hdparm -i /dev/hdc -> Operation not permitted


    SteveSch wrote:
    > On Sun, 22 Jan 2006 12:40:26 +0100, Ruediger wrote:
    >
    > > Hello,
    > >
    > > I was wonderign if someone could tell me if I am stupid or not:
    > > My PC's DVD writer is running in PIO Mode 4 as it seems - Writing with 2*
    > > results in unbearable CPU-load.

    >
    > Hi,
    >
    > I saw this old post and wondered if you got it fixed.
    >
    > Try running
    >
    > hdparm /dev/hdX
    >
    > That should tell how it sets your drives.
    >
    > I have a single cpu that has high cpu usage while burning. I have a much
    > slower dual cpu that uses maybe about 12% while burning. I have never
    > figured it out as both machines have dma set and everything looks great.
    >
    > Steve


    That's not only a Laptop (notice "Mobile") but its also a DVD-RAM drive
    -- UDMA > DMA


  4. Re: hdparm -i /dev/hdc -> Operation not permitted

    SteveSch wrote:

    > On Sun, 22 Jan 2006 12:40:26 +0100, Ruediger wrote:
    >
    >> Hello,
    >>
    >> I was wonderign if someone could tell me if I am stupid or not:
    >> My PC's DVD writer is running in PIO Mode 4 as it seems - Writing with 2*
    >> results in unbearable CPU-load.

    >
    > Hi,
    >
    > I saw this old post and wondered if you got it fixed.
    >
    > Try running
    >
    > hdparm /dev/hdX
    >
    > That should tell how it sets your drives.
    >
    > I have a single cpu that has high cpu usage while burning. I have a much
    > slower dual cpu that uses maybe about 12% while burning. I have never
    > figured it out as both machines have dma set and everything looks great.
    >
    > Steve


    That problem is still not fixed - I found out in the meantime that, whilst
    the chipset is an Intel I915 stating to be accessing SATA to utilize
    harddrive and DVD-RAM drive, it is not SATA, but standard, parallel ATA
    which is used. I think I need to recompile my kernel to kill off the SATA
    driver, as it is not loaded over bootparameter or /etc/modules.
    pitily I will need to edit /etc/fstab before doing so, as there all drives
    are entered as /dev/sda

    It is funny that debian itself identified the drive as SATA during install,
    the DVDRAM as PATA, and that after booting into the new system I had to
    compile a kernel with SATA driver integrated to keep it working - else I
    got a kernel panic for the drives not being found...

    The trick with the single/dual CPU difference comes from advanced
    board-components: Most dual-CPU boards use more sophisticated memory
    architectures, so they produce far less overhead with transferring the data
    than a cheap standard single-cpu system.
    At work I have a dual-cpu sparc - I can can burn a DVD there at 8* speed -
    top says system is 97.3% idle....
    Its an SCSI Harddisk and SCSI-converted IDE-DVD-burner...
    --
    Sincerely

    Ruediger


  5. Re: hdparm -i /dev/hdc -> Operation not permitted

    Hello,

    Ruediger wrote:
    >> On Sun, 22 Jan 2006 12:40:26 +0100, Ruediger wrote:
    >>> I was wonderign if someone could tell me if I am stupid or not:
    >>> My PC's DVD writer is running in PIO Mode 4 as it seems - Writing with 2*
    >>> results in unbearable CPU-load.

    >
    > That problem is still not fixed - I found out in the meantime that, whilst
    > the chipset is an Intel I915 stating to be accessing SATA to utilize
    > harddrive and DVD-RAM drive, it is not SATA, but standard, parallel ATA
    > which is used.


    I had similar trouble with my D810 and found out that passing
    libata.atapi_enabled=1 as a kernel parameter solves the problem.
    I'm running 2.6.15.1.

    IIRC the hdd is native sata while the dvd-burner is pata behind a sata
    to pata bridge. The hdd needs sata support in the kernel while the
    dvd-burner can also be used through some legacy ide interface which does
    not support setting dma modes. With libata you can access the burner via
    sata and setting dma becomes possible.

    HTH

    Regards,

    Thomas

+ Reply to Thread