Re: hdparm not o.k. ?
Am Montag, 19. September 2005 19:38 schrieb Jacob Bresciani:
> The only other thing that jumps to mind is permissions, I assume
> you're running as root or through sudo?
Yes, I am running as root. Directly as root, not sudo.
Hans
>
> Jacob Bresciani
>
>
> "Passwords are like bubble gum, strongest when fresh, should never be
> used by groups and create a sticky mess when left laying around"
>
> -anon
>
> On Sep 19, 2005, at 10:19 AM, Hans wrote:
> > Am Montag, 19. September 2005 19:18 schrieben Sie:
> >> do you have the proper chipset driver for your HD controller or
> >> motherboard loaded? if not then DMA won't work because it won't know
> >> where/how to turn it on.
> >
> > Yes, I have. Chipset is via82xxxx. And the kernel module is loaded !
> >
> > Hans
> >
> >> Knoppix loads a kernel which probably has your MB /HD controller
> >> loaded so at least you know it will work.
> >>
> >> Jacob Bresciani
> >>
> >> "Passwords are like bubble gum, strongest when fresh, should never be
> >> used by groups and create a sticky mess when left laying around"
> >>
> >> -anon
> >>
> >> On Sep 19, 2005, at 10:04 AM, Hans wrote:
> >>> Hi folks,
> >>> I tried to improve my settings of the harddrive. These are the
> >>> original
> >>> settings:
> >>>
> >>> /dev/hda:
> >>> multcount = 16 (on)
> >>> IO_support = 1 (32-bit)
> >>> unmaskirq = 0 (off)
> >>> using_dma = 0 (off)
> >>> keepsettings = 0 (off)
> >>> readonly = 0 (off)
> >>> readahead = 256 (on)
> >>> geometry = 16383/255/63, sectors = 195371568, start = 0
> >>>
> >>> You see, dma is off. When trying to set this to on ( hdparm -d 1 /
> >>> dev/hda), I
> >>> get this error:
> >>>
> >>> /dev/hda:
> >>> setting using_dma to 1 (on)
> >>> HDIO_SET_DMA failed: Operation not permitted
> >>> using_dma = 0 (off)
> >>>
> >>> could there be a bug in hdparm ? When running knoppix in 32-Bit-
> >>> mode it works
> >>> fine.
> >>>
> >>> These are the infos from /dev/hda:
> >>>
> >>> hdparm -i /dev/hda
> >>>
> >>> /dev/hda:
> >>>
> >>> Model=ST9100823A, FwRev=3.01, SerialNo=3LG02H6A
> >>> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.
> >>> 5% }
> >>> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> >>> BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16
> >>> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195371568
> >>> IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
> >>> PIO modes: pio0 pio1 pio2 pio3 pio4
> >>> DMA modes: mdma0 mdma1 mdma2
> >>> UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
> >>> AdvancedPM=yes: unknown setting WriteCache=enabled
> >>> Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:
> >>>
> >>> * signifies the current active mode
> >>>
> >>> Could it be a bug ??? Any clue ??
> >>>
> >>> Best regards
> >>>
> >>> Hans
> >>>
> >>>
> >>> Look at this, please.
> >>>
> >>>
> >>> --
> >>> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
> >>> with a subject of "unsubscribe". Trouble? Contact
> >>> listmaster@lists.debian.org
Reply to: