Vieillissement prématuré des disques durs de portables

JLK · Le 09/03/2008, à 03:09

Quatisis a écrit :

Euh oui, pardon ,pardon... j'avais pas lu la totalité des 39 pages de ce topic
Et en effet j'ai craché sur Linux un peu vite. Honte à moi !!!
Ce qui m'étonne, c'est d'avoir bouffé 99% de mon PC en moins de 2 ans... je trouve ça un peu court.

Juste une question : faisais-tu une utilisation intensive de ton disque dur ?
En tout cas fait des backups.

Link31 · Le 09/03/2008, à 04:36

Quatisis a écrit :

J'ai découvert ce topic hier et je m'aperçois qu'il reste 1% de vie à mon PC acheté en juillet 2006 (20 mois).

D'abord la limite est à 600 000 sur la plupart des DD de portables (ça m'étonnerait que les DD de bureau soient affectés par ce problème, de toute façon ils n'iraient pas jusqu'à 270 000 parcages).
Je ne sais pas d'où tu tires ce 1%, probablement du premier 001, mais il est faux. Chez moi, j'ai 069 (+- 21%) pour 69000 parcages, sur un DD prévu pour 600 000 parcages (donc 10%). Smartctl t'aurait prévenue s'il y avait vraiment matière à s'inquiéter, dans la colonne WHEN_FAILED.

Ensuite il ne reste pas 1% de vie à ton PC, il reste plus de 50% de vie à ton disque dur, ce qui n'est pas exactement la même chose

Sorbus · Le 09/03/2008, à 09:30

Le premier chiffre, le 1% en l'occurence pour Quatisis, est l'un des éléments pris en compte dans la documentation Ubuntu francophone. Le nombre de "600000" parcages est théorique. On a repéré que certains modèles de disques dur de portable sont "tarés", théoriquement, pour un maximum de 200000 parcages... C'est le cas du mien.

Il semblerait que le 1er chiffre (49% chez moi, 69% chez Link31, 1% chez Quatisis) évolue en fonction du nombre de parcages théorique maximum pour lequel le modèle de disque dur est théoriquement taré. Ces nombres étant théoriques, ça ne signifie pas que le disque dur n'ait pas une capacité de parcages (beaucoup) plus grande. Mais ça reste une donnée à prendre en compte.

Quatisis · Le 09/03/2008, à 12:21

@JLK
c'est quoi une utilisation intensive ?? Le truc le plus intensif que je fais c'est peut-être l'encodage en DivX des fichiers récupérés sur la Freebox

Sinon j'avoue l'avoir pas mal malmené lors de la dernière install d'Ubuntu en dual boot avec W... : PC tatoué + déjà 3 partitions primaires + une install wifi pas piquée des vers (Broadcom4318 en wpa) ... bref, pas mal de tâtonnements et, bien sûr, de multiples redémarrages... (Je précise que je suis une complète autodidacte, d'où les tâtonnements là où certains n'en auraient pas eus)

@Link31 et Sorbus
En effet je me base sur la doc du Wiki. Mon DD est sans doute théoriquement prévu pour un maximum de 300000 parcages ce qui expliquerait le 1%. Je sais que cette donnée n'est que théorique... mais bon, comme dit Sorbus, elle est à prendre en compte.

@Link31
Comment peux-tu être absolument sûr que ton DD est prévu pour 600000 parcages ?

Link31 a écrit :

Ensuite il ne reste pas 1% de vie à ton PC, il reste plus de 50% de vie à ton disque dur, ce qui n'est pas exactement la même chose wink

Ouais ben je vis peut-être au Pays des Merveilles mais je trouve que c'est quand même pas long la vie d'un DD.;)

Dernière modification par Quatisis (Le 09/03/2008, à 21:29)

Link31 · Le 09/03/2008, à 18:30

Quatisis a écrit :

Comment peux-tu être absolument sûr que ton DD est prévu pour 600000 parcages ?

C'est écrit dans les spécifications du constructeur, dans un PDF trouvé sur son site.

Dernière modification par Link31 (Le 09/03/2008, à 18:32)

atlas95 · Le 09/03/2008, à 19:24

Bonjour, désolé de squatter le topic, mais je ne connaissais pas ces disque dur momentur, avec 256mo de cache, ils sont prévu pour vista ils paraient, linux gère t'il correctement ces disque a gros cache? Je voulais m'acheter un disque dur SSD mais on va encore attendre je pense ..€€..

Richoo · Le 12/03/2008, à 16:23

Bonjour,

Juste une petite suggestion : Est ce que les personnes ayant des problèmes quant au vieillissement du disque aurait installées le paquet "powertop"?

J'avais ce petit problème en effet, mais je ne m'en était pas rendu compte tout de suite. En suivant les tutoriels (http://doc.ubuntu-fr.org/laptop_mode?s=laptop%20mode) j'ai pu régler ce problème, mais j'ai dans la même foulée désinstaller powertop je ne peux donc pas savoir si la résolution de mon problème était soit de part le tutoriel (un peu quand même ) ou par la désinstallation du paquet.

J'ai penser à ce paquet car il est censé augmenter l'autonomie de la batterie en effectuant plusieurs réglages et n'ayant pas fait très attention au départ à quoi ceux-ci correspondaient, je me demande ci un de ces réglages augmenteraient le nombre de parçage de tête.

Donc si une personne pouvait confirmer ou infirmer mes dires j'en serai plus que satisfait.

Merci

Astrolivier · Le 12/03/2008, à 17:41

salut,

cet apres midi je reviens du boulot, et je redemarre mon portable
20 min apres l avoir eteind.
et la c est la cata, gros fsck avec plein d erreure, j ai une debian testing,
une feisty et une gusty, toutes pareilles

j ai meme eu un bsod avec gusty (je mettrai la photo plus tard)

je laisse sous debian, fsck de 1h30, finissant par une(des?) erreure

serait ce en rapport avec le fil de ce sujet ???

PS: vive les live cd, j ai mis un vieux mint gusty, comme ca j ai la radio

edit: portable 2ans, pratiquement tout le temps allume, peu de travail intensif

Dernière modification par Astrolivier (Le 12/03/2008, à 17:49)

ft · Le 12/03/2008, à 22:45

Petite info : retour des clics du disque sous Hardy depuis hier... Snif.

reeth · Le 13/03/2008, à 21:23

Un petit retour comme prévu

Le 06/01/2008, à 17:20 (époque où je n'avais rien modifié et où j'étais sous kubuntu)

reeth a écrit :

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   052   048   034    Pre-fail  Always       -       194115269
  3 Spin_Up_Time            0x0003   096   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2747
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   077   060   030    Pre-fail  Always       -       8697652779
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6361
 10 Spin_Retry_Count        0x0013   100   100   034    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   020    Old_age   Always       -       2790
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       2790
193 Load_Cycle_Count        0x0032   007   007   000    Old_age   Always       -       186867
194 Temperature_Celsius     0x0022   042   051   000    Old_age   Always       -       42 (Lifetime Min/Max 0/10)
195 Hardware_ECC_Recovered  0x001a   052   048   000    Old_age   Always       -       194115269
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 TA_Increase_Count       0x0032   100   253   000    Old_age   Always       -       0

Ce qui signifierai qu'il me reste encore environ 210h de fonctionnement (3.5%). Je commence un peu à m'inquiéter, même si j'ai fais des copies de sauvegarde. J'ai aussi remarqué que j'étais passé de 008 à 007 en environ 2 mois.

Maintenant (sous debian sid, sans réglage particulier, mais le hdparm à 254) :

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   051   048   034    Pre-fail  Always       -       150765725
  3 Spin_Up_Time            0x0003   096   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2996
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -       8712757852
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6848
 10 Spin_Retry_Count        0x0013   100   100   034    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   020    Old_age   Always       -       2904
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       2904
193 Load_Cycle_Count        0x0032   007   007   000    Old_age   Always       -       187213
194 Temperature_Celsius     0x0022   042   051   000    Old_age   Always       -       42 (0 10 0 0)
195 Hardware_ECC_Recovered  0x001a   051   048   000    Old_age   Always       -       150765725
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 TA_Increase_Count       0x0032   100   253   000    Old_age   Always       -       0

J'ai donc toujours ce "007"%, alors que j'ai 187213 (+346 LCC) pour 6848 (+487 POH) c'est à dire maintenant 0,71 LCC/H en 65 jours (whaou 7h30/jour!!, je me pensais pas aussi accro ).

Mon DD n'a pas bougé, il n'a pas de problèmes de surchauffe, et il n'est pas mort au bout de 210h.

Voilà pour ma petite expérience.

DiCiCat · Le 13/03/2008, à 21:32

Ce qui confirme donc que le probleme est bien reglé dans debian

reeth · Le 13/03/2008, à 23:08

Pour mon disque dur, je ne m'avancerais pas au point de dire qu'il n'y a plus de problèmes, mais à mon avis tu as raison

esboy · Le 15/03/2008, à 19:39

avec ce résultat, il faut que je fasse quelque chose ou bien est-ce que je n'ai pas de problème ?

9 Power_On_Hours 0x0012 093 093 000 Old_age Always - 3386
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1190
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 154
193 Load_Cycle_Count 0x0012 086 086 000 Old_age Always - 149588

j'ai ce disque dur depuis 14 mois, dont 5 ou 6 sous ubuntu (avant, il était sous XP)

utodeb · Le 18/03/2008, à 08:42

Bonjour,
Juste pour info en ce qui me concerne sous hardy le LCC ne bouge plus du tt sur secteur et je n'ai fait aucune manip

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HTS541616J9SA00
Serial Number:    SB2441SJC8DR4E
Firmware Version: SB4OC70P

dimanche 16 mars 2008, 20:19:05 (UTC+0100)
193 Load_Cycle_Count        0x0012   097   097   000    Old_age   Always       -       32149
194 Temperature_Celsius     0x0002   253   253   000    Old_age   Always       -       20 (Lifetime Min/Max 10/49)
lundi 17 mars 2008, 07:34:25 (UTC+0100)
193 Load_Cycle_Count        0x0012   097   097   000    Old_age   Always       -       32150
194 Temperature_Celsius     0x0002   229   229   000    Old_age   Always       -       24 (Lifetime Min/Max 10/49)
mardi 18 mars 2008, 07:35:53 (UTC+0100)
193 Load_Cycle_Count        0x0012   097   097   000    Old_age   Always       -       32150
194 Temperature_Celsius     0x0002   177   177   000    Old_age   Always       -       31 (Lifetime Min/Max 10/49)

KnuX · Le 18/03/2008, à 10:41

Tu as upgrade vers la hardy ou une installation fraîche ?

Sachant qu'il conserve le fichier de configuration de laptop-mode dans le cas où tu ne lui indique pas de le remplacer

utodeb · Le 18/03/2008, à 15:32

Salut,
C'est une install toute fraiche ^^

utodeb · Le 18/03/2008, à 21:46

Re,
En fait ce soir en arrivant j'ai regarder plus en détail cette histoire et donc sous hardy laptop-mode est présent par défaut ce qui n'étais pas mon cas sous gutsy il me semble...
Je poste les deux laptop-mode.conf

Gutsy

###############################################################################
#
# Configuration for Laptop Mode Tools
# -----------------------------------
#
# There is a "system" to the configuration setting names:
#    CONTROL_something=0/1   Determines whether Laptop Mode Tools controls 
#                            something
#    LM_something=value      Value of "something" when laptop mode is active
#    NOLM_something=value    Value of "something" when laptop mode is NOT
#                            active
#    AC_something=value      Value of "something" when the computer is running
#                            on AC power
#    BATT_something=value    Value of "something when the computer is running
#                            on battery power
#
# There can be combinations of LM_/NOLM_ and AC_/BATT_ prefixes, but the
# available prefixes are different for each setting. The available ones are 
# documented in the manual page, laptop-mode.conf(8). If there is no LM_/
# NOLM_ in a setting name, then the value is used independently of laptop
# mode state, and similarly, if there is no AC_/BATT_, then the value is used
# independently of power state.
#
# Some options only work on ACPI systems. They are marked ACPI-ONLY.
#
# Note that this configuration file is a fragment of bash shell script: you
# can use all the features of the bash scripting language to achieve your
# desired configuration.
#
# 
# IMPORTANT: Laptop Mode Tools modules have separate configuration files, that
# can be found in /etc/laptop-mode/conf.d. Please look through these
# configuration files as well!
#
###############################################################################



###############################################################################
# Configuration debugging
# -----------------------
###############################################################################


#
# Set this to 1 if you want to see a lot of information when you start/stop 
# laptop_mode.
#
VERBOSE_OUTPUT=0



###############################################################################
# When to enable laptop mode
# --------------------------
#
# "Laptop mode" is the mode in which laptop mode tools makes the computer
# consume less power. This includes the kernel "laptop_mode" feature, which
# allows your hard drives to spin down, as well as various other settings which
# can be tweaked by laptop mode tools. You can enable or disable all of these
# settings using the CONTROL_... options further down in this config file.
###############################################################################


#
# Enable laptop mode when on battery power.
#
ENABLE_LAPTOP_MODE_ON_BATTERY=1


#
# Enable laptop mode when on AC power.
#
ENABLE_LAPTOP_MODE_ON_AC=1 #0


#
# Enable laptop mode when the laptop's lid is closed, even when we're on AC
# power? (ACPI-ONLY)
#
ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=1 #0



###############################################################################
# When to enable data loss sensitive features
# -------------------------------------------
#
# When data loss sensitive features are disabled, laptop mode tools acts as if
# laptop mode were disabled, for those features only.
#
# Data loss sensitive features include:
# - laptop_mode (i.e., delayed writes)
# - hard drive write cache
#
# All of the options that follow can be set to 0 in order to prevent laptop
# mode tools from using them to stop data loss sensitive features. Use this
# when you have a battery that reports the wrong information, that confuses
# laptop mode tools.
#
# Disabling data loss sensitive features is ACPI-ONLY.
###############################################################################


#
# Disable all data loss sensitive features when the battery level (in % of the
# battery capacity) reaches this value.
#
MINIMUM_BATTERY_CHARGE_PERCENT=3


#
# Disable data loss sensitive features when the battery reports its state
# as "critical".
#
DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1


###############################################################################
# Controlled hard drives and partitions
# -------------------------------------
#
# For spinning down your hard drives, laptop mode will remount file systems and
# adjust hard drive spindown timeouts. These parameters specify which
# devices and partitions are affected by laptop mode.
###############################################################################


#
# The drives that laptop mode controls.
# Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
# wildcard, which will get you all your IDE and SCSI/SATA drives.
#
HD="/dev/[hs]d[abcdefgh]"


#
# The partitions (or mount points) that laptop mode controls.
# Separate the values by spaces. Use "auto" to indicate all partitions on drives
# listed in HD. You can add things to "auto", e.g. "auto /dev/hdc3". You can
# also specify mount points, e.g. "/mnt/data".
#
PARTITIONS="auto /dev/mapper/*"


#
# If this is enabled, laptop mode tools will assume that SCSI drives are
# really SATA drives that only _look_ like SCSI drives, and will use hdparm
# to control them. Set this to 0 if you have /dev/sd devices and you want
# laptop mode tools to use the "sdparm" command to control them. 
#
ASSUME_SCSI_IS_SATA=1


###############################################################################
# Hard drive behaviour settings
# -----------------------------
#
# These settings specify how laptop mode tools will adjust the various
# parameters of your hard drives and file systems.
###############################################################################


#
# Maximum time, in seconds, of work that you are prepared to lose when your
# system crashes or power runs out. This is the maximum time that Laptop Mode
# will keep unsaved data waiting in memory before spinning up your hard drive.
#
LM_BATT_MAX_LOST_WORK_SECONDS=600
LM_AC_MAX_LOST_WORK_SECONDS=600 #360


#
# Should laptop mode tools control readahead?
#
CONTROL_READAHEAD=1


#
# Read-ahead, in kilobytes. You can spin down the disk while playing MP3/OGG
# by setting the disk readahead to a reasonable size, e.g. 3072 (3 MB).
# Effectively, the disk will read a complete MP3 at once, and will then spin 
# down while the MP3/OGG is playing. Don't set this too high, because the 
# readahead is applied to _all_ files that are read from disk.
#
LM_READAHEAD=3072
NOLM_READAHEAD=128


#
# Should laptop mode tools add the "noatime" option to the mount options when 
# laptop mode is enabled?
#
CONTROL_NOATIME=1 #0


#
# Should laptop mode tools control the hard drive idle timeout settings?
#
CONTROL_HD_IDLE_TIMEOUT=1


#
# Idle timeout values. (hdparm -S)
# Default is 2 hours on AC (NOLM_HD_IDLE_TIMEOUT_SECONDS=7200) and 20 seconds
# for battery and for AC with laptop mode on.
#
LM_AC_HD_IDLE_TIMEOUT_SECONDS=200
LM_BATT_HD_IDLE_TIMEOUT_SECONDS=200
NOLM_HD_IDLE_TIMEOUT_SECONDS=7200


#
# Should laptop mode tools control the hard drive power management settings?
#
CONTROL_HD_POWERMGMT=1


#
# Power management for HD (hdparm -B values)
#
BATT_HD_POWERMGMT=1
LM_AC_HD_POWERMGMT=254
NOLM_AC_HD_POWERMGMT=255


#
# Should laptop mode tools control the hard drive write cache settings?
#
CONTROL_HD_WRITECACHE=1


#
# Write cache settings for HD (hdparm -W values)
#
NOLM_AC_HD_WRITECACHE=1
NOLM_BATT_HD_WRITECACHE=0
LM_HD_WRITECACHE=1



###############################################################################
# CPU frequency scaling and throttling
# ------------------------------------
#
# Laptop mode tools can automatically adjust your kernel CPU frequency
# settings. This includes upper and lower limits and scaling governors.
# There is also support for CPU throttling, on systems that don't support
# frequency scaling.
#
# This feature only works on 2.6 kernels.
###############################################################################


#
# Should laptop mode tools control the maximum CPU frequency?
#
CONTROL_CPU_FREQUENCY=0


#
# Legal values are "slowest" for the slowest speed that your
# CPU is able to operate at, "fastest" for the fastest speed,
# "medium" for some value in the middle, or any value listed in
# /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
# The "governor" can be any governor installed on your system, this usually
# includes "ondemand", "conservative", and "performance". The
# "IGNORE_NICE_LOAD" setting specifies that background programs that have
# a low priority ("nice level") should not cause the CPU frequency to
# be increased. (You generally want this to be enabled in battery mode.)
#
BATT_CPU_MAXFREQ=medium
BATT_CPU_MINFREQ=slowest
BATT_CPU_GOVERNOR=ondemand
BATT_CPU_IGNORE_NICE_LOAD=1
LM_AC_CPU_MAXFREQ=fastest
LM_AC_CPU_MINFREQ=slowest
LM_AC_CPU_GOVERNOR=ondemand
LM_AC_CPU_IGNORE_NICE_LOAD=1
NOLM_AC_CPU_MAXFREQ=fastest
NOLM_AC_CPU_MINFREQ=slowest
NOLM_AC_CPU_GOVERNOR=performance
NOLM_AC_CPU_IGNORE_NICE_LOAD=0


#
# Should laptop mode tools control the CPU throttling? This is only useful
# on processors that don't have frequency scaling.
# (Only works when you have /proc/acpi/processor/CPU*/throttling.)
#
CONTROL_CPU_THROTTLING=0


#
# Legal values are "maximum" for the maximum (slowest) throttling level,
# "minimum" for minimum (fastest) throttling level, "medium" for a value
# somewhere in the middle (this is usually 50% for P4s), or any value listed
# in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
# this may be _very_ slow (in fact, with P4s it slows down the processor
# by a factor 8).
#
BATT_CPU_THROTTLING=medium
LM_AC_CPU_THROTTLING=medium
NOLM_AC_CPU_THROTTLING=minimum



###############################################################################
# Syslog configuration control
# ----------------------------
# 
# Syslog daemons have a tendency to sync their log files when entries are
# written to them. This causes disks to spin up, which is not very nice when
# you're trying to save power. The syslog.conf can be tweaked to *not* sync
# a given file, by prepending the log file name with a dash, like this:
#
# 	mail.*		-/var/log/mail/mail.log
#
# Using the following options, you can let laptop mode switch between
# different syslog configurations depending on whether you are working on
# battery or on AC power. To set this up, start by configuring these options
# for your syslog daemon, and then run lm-syslog-setup to create the various
# files. Then edit the laptop mode-specific syslog configuration files to
# remove the syncs only when laptop mode is active.
###############################################################################


#
# Should laptop mode tools control which syslog.conf should be used?
#
CONTROL_SYSLOG_CONF=1


#
# Laptop mode tools controls syslog.conf by replacing /etc/syslog.conf (or
# whatever you specify in SYSLOG_CONF) by a link to the files configured here.
# NOTE: these files are NOT created by default, and if they do not
# exist this feature will not work. You can run the script
# /usr/sbin/lm-syslog-setup to set things up.
#
LM_AC_SYSLOG_CONF=/etc/syslog-on-ac-with-lm.conf
NOLM_AC_SYSLOG_CONF=/etc/syslog-on-ac-without-lm.conf
BATT_SYSLOG_CONF=/etc/syslog-on-battery.conf


#
# Signal this program when syslog.conf has been replaced.
#
SYSLOG_CONF_SIGNAL_PROGRAM=syslogd


#
# This is the syslog configuration file that should be replaced by a link to
# the other files.
#
SYSLOG_CONF=/etc/syslog.conf



###############################################################################
# X display settings
# ------------------
#
# Using these settings, you can let laptop mode tools control the X display
# standby timeouts.
#
# This requires that you have installed the "xset" utility. It is part of the
# X.org server distribution and included in the package xorg-server-utils.
#
# The X settings are not automatically applied on login, and this is
# impossible fix for the user, since laptop mode tools must operate as root.
# Therefore, it is recommended to add the following line to /etc/X11/Xsession
# as well:
#
#   /usr/sbin/laptop_mode force
#
###############################################################################


#
# Should laptop mode tools control DPMS standby settings for X displays?
#
CONTROL_DPMS_STANDBY=0


#
# These settings specify the standby timeout for the X display,
# in seconds. The suspend and poweroff timeouts are somewhat
# larger values derived from these values.
#
BATT_DPMS_STANDBY=300
LM_AC_DPMS_STANDBY=1200
NOLM_AC_DPMS_STANDBY=1200



###############################################################################
# Terminal settings
# -----------------
#
# Using these settings, you can let laptop mode tools control the terminal
# blanking timeouts. This only works for linux virtual consoles.
#
###############################################################################


#
# Should laptop mode tools control terminal blanking settings?
#
CONTROL_TERMINAL=0


#
# Terminal device files that should be affected. (One terminal is enough, this
# affects all consoles. )
#
TERMINALS="/dev/tty1"


#
# These settings specify the blanking and powerdown timeouts. Note that
# the powerdown timeout is counted from the moment the screen is blanked,
# i.e. BLANK_MINUTES=2 and POWERDOWN_MINUTES=5 means the screen powers
# down after 7 minutes of inactivity. The range for all these settings is
# 1 to 60 minutes, or 0 to disable.
#
BATT_TERMINAL_BLANK_MINUTES=1
BATT_TERMINAL_POWERDOWN_MINUTES=2
LM_AC_TERMINAL_BLANK_MINUTES=10
LM_AC_TERMINAL_POWERDOWN_MINUTES=10
NOLM_AC_TERMINAL_BLANK_MINUTES=10
NOLM_AC_TERMINAL_POWERDOWN_MINUTES=50


###############################################################################
# LCD brightness settings
# -----------------------
#
# Using these settings, you can make laptop mode tools automatically adjust
# your LCD's brightness settings. The settings are extremely simple -- they
# only allow for the execution of a command, nothing more. The reason for this
# is that LCD brightness settings are very different between laptop vendors.
#
# Suggestions for commands:
#
#  * If your system has the file "/proc/acpi/video/VID/LCD/brightness" (VID may
#    be VID1 or similar), use this file as BRIGHTNESS_OUTPUT, and use
#    the command "echo <value>". The possible values can be listed using the
#    command:
#
#       cat /proc/acpi/video/VID/LCD/brightness
#
#  * If you have a file /sys/class/backlight/.../brightness, then you can use
#    that file as BRIGHTNESS_OUTPUT, and the command "echo <value>".
#
#    As far as I understand it the values are between 0 and
#    the value contained in the file /sys/class/backlight/.../max_brightness.
#
#  * For Toshiba laptops, use the command "toshset" with the -lcd or -inten
#    command. Read the toshset(1) manual page for more information on the
#    parameters for this command. If you use this command, set
#    BRIGHTNESS_OUTPUT to "/dev/null".
#
###############################################################################


#
# Should laptop mode tools control LCD brightness?
#
CONTROL_BRIGHTNESS=0


#
# Commands to execute to set the brightness on your LCD
#
BATT_BRIGHTNESS_COMMAND="echo [value]"
LM_AC_BRIGHTNESS_COMMAND="echo [value]"
NOLM_AC_BRIGHTNESS_COMMAND="echo [value]"
BRIGHTNESS_OUTPUT="/proc/acpi/video/VID/LCD/brightness"


###############################################################################
# Auto-hibernation settings
# -------------------------
#
# Using these settings, you can make laptop mode tools automatically put your
# computer into hibernation when the battery level goes critically low.
#
# This feature only works on ACPI, and only works on computers whose batteries
# give off battery events often enough.
###############################################################################


#
# Should laptop mode tools perform auto-hibernation?
#
ENABLE_AUTO_HIBERNATION=0


#
# The hibernation command that is to be executed when auto-hibernation
# is triggered.
#
HIBERNATE_COMMAND=/usr/sbin/hibernate


#
# Auto-hibernation battery level threshold, in percentage of the battery's
# total capacity.
#
AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT=2


#
# Enable this to auto-hibernate if the battery reports that its level is
# "critical".
#
AUTO_HIBERNATION_ON_CRITICAL_BATTERY_LEVEL=1



###############################################################################
# Start/Stop Programs settings
# ----------------------------
#
# Laptop mode tools can automatically start and stop programs when entering
# various power modes. Put scripts accepting "start" and "stop" parameters
# in the directories /etc/laptop-mode/batt-stop, batt-start, lm-ac-stop,
# lm-ac-start, nolm-ac-stop and nolm-ac-start. Laptop mode will call the
# scripts in a state-"stop" directory with the "stop" parameter when entering
# the state in question, and it will call the same scripts with the "start"
# parameter when leaving the state. Scripts in a state-"start" directory are
# called with the "start" parameter when the specified state is entered, and
# with the "stop" parameter when the specified state is left.
###############################################################################


#
# Should laptop mode start and stop programs? 
#
CONTROL_START_STOP=1



###############################################################################
# Settings you probably don't want to touch
# -----------------------------------------
#
# It is usually not necessary to change these parameters. They are included
# for completeness' sake.
###############################################################################


#
# Change mount options on partitions in PARTITIONS? You don't really want to
# disable this. If you do, then your hard drives will probably not spin down
# anymore.
#
CONTROL_MOUNT_OPTIONS=1


#
# Dirty synchronous ratio.  At this percentage of dirty pages the process
# which calls write() does its own writeback.
#
LM_DIRTY_RATIO=60
NOLM_DIRTY_RATIO=40


#
# Allowed dirty background ratio, in percent.  Once DIRTY_RATIO has been
# exceeded, the kernel will wake pdflush which will then reduce the amount
# of dirty memory to dirty_background_ratio.  Set this nice and low, so once
# some writeout has commenced, we do a lot of it.
#
LM_DIRTY_BACKGROUND_RATIO=1
NOLM_DIRTY_BACKGROUND_RATIO=10


#
# kernel default settings -- don't touch these unless you know what you're 
# doing.
#
DEF_UPDATE=5
DEF_XFS_AGE_BUFFER=15
DEF_XFS_SYNC_INTERVAL=30
DEF_XFS_BUFD_INTERVAL=1
DEF_MAX_AGE=30


#
# This must be adjusted manually to the value of HZ in the running kernel
# on 2.4, until the XFS people change their 2.4 external interfaces to work in
# centisecs. This can be automated, but it's a work in progress that still
# needs some fixes. On 2.6 kernels, XFS uses USER_HZ instead of HZ for
# external interfaces, and that is currently always set to 100. So you don't
# need to change this on 2.6.
#
XFS_HZ=100


#
# Seconds laptop mode has to to wait after the disk goes idle before doing
# a sync.
#
LM_SECONDS_BEFORE_SYNC=2

et hardy mnt

###############################################################################
#
# Configuration for Laptop Mode Tools
# -----------------------------------
#
# There is a "system" to the configuration setting names:
#    CONTROL_something=0/1   Determines whether Laptop Mode Tools controls 
#                            something
#    LM_something=value      Value of "something" when laptop mode is active
#    NOLM_something=value    Value of "something" when laptop mode is NOT
#                            active
#    AC_something=value      Value of "something" when the computer is running
#                            on AC power
#    BATT_something=value    Value of "something when the computer is running
#                            on battery power
#
# There can be combinations of LM_/NOLM_ and AC_/BATT_ prefixes, but the
# available prefixes are different for each setting. The available ones are 
# documented in the manual page, laptop-mode.conf(8). If there is no LM_/
# NOLM_ in a setting name, then the value is used independently of laptop
# mode state, and similarly, if there is no AC_/BATT_, then the value is used
# independently of power state.
#
# Some options only work on ACPI systems. They are marked ACPI-ONLY.
#
# Note that this configuration file is a fragment of bash shell script: you
# can use all the features of the bash scripting language to achieve your
# desired configuration.
#
# 
# IMPORTANT: Laptop Mode Tools modules have separate configuration files, that
# can be found in /etc/laptop-mode/conf.d. Please look through these
# configuration files as well!
#
###############################################################################



###############################################################################
# Configuration debugging
# -----------------------
###############################################################################


#
# Set this to 1 if you want to see a lot of information when you start/stop 
# laptop_mode.
#
VERBOSE_OUTPUT=0



###############################################################################
# When to enable laptop mode
# --------------------------
#
# "Laptop mode" is the mode in which laptop mode tools makes the computer
# consume less power. This includes the kernel "laptop_mode" feature, which
# allows your hard drives to spin down, as well as various other settings which
# can be tweaked by laptop mode tools. You can enable or disable all of these
# settings using the CONTROL_... options further down in this config file.
###############################################################################


#
# Enable laptop mode when on battery power.
#
ENABLE_LAPTOP_MODE_ON_BATTERY=1


#
# Enable laptop mode when on AC power.
#
ENABLE_LAPTOP_MODE_ON_AC=0


#
# Enable laptop mode when the laptop's lid is closed, even when we're on AC
# power? (ACPI-ONLY)
#
ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0



###############################################################################
# When to enable data loss sensitive features
# -------------------------------------------
#
# When data loss sensitive features are disabled, laptop mode tools acts as if
# laptop mode were disabled, for those features only.
#
# Data loss sensitive features include:
# - laptop_mode (i.e., delayed writes)
# - hard drive write cache
#
# All of the options that follow can be set to 0 in order to prevent laptop
# mode tools from using them to stop data loss sensitive features. Use this
# when you have a battery that reports the wrong information, that confuses
# laptop mode tools.
#
# Disabling data loss sensitive features is ACPI-ONLY.
###############################################################################


#
# Disable all data loss sensitive features when the battery level (in % of the
# battery capacity) reaches this value.
#
MINIMUM_BATTERY_CHARGE_PERCENT=3


#
# Disable data loss sensitive features when the battery reports its state
# as "critical".
#
DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1


###############################################################################
# Controlled hard drives and partitions
# -------------------------------------
#
# For spinning down your hard drives, laptop mode will remount file systems and
# adjust hard drive spindown timeouts. These parameters specify which
# devices and partitions are affected by laptop mode.
###############################################################################


#
# The drives that laptop mode controls.
# Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
# wildcard, which will get you all your IDE and SCSI/SATA drives.
#
HD="/dev/[hs]d[abcdefgh]"


#
# The partitions (or mount points) that laptop mode controls.
# Separate the values by spaces. Use "auto" to indicate all partitions on drives
# listed in HD. You can add things to "auto", e.g. "auto /dev/hdc3". You can
# also specify mount points, e.g. "/mnt/data".
#
PARTITIONS="auto /dev/mapper/*"


#
# If this is enabled, laptop mode tools will assume that SCSI drives are
# really SATA drives that only _look_ like SCSI drives, and will use hdparm
# to control them. Set this to 0 if you have /dev/sd devices and you want
# laptop mode tools to use the "sdparm" command to control them. 
#
ASSUME_SCSI_IS_SATA=1


###############################################################################
# Hard drive behaviour settings
# -----------------------------
#
# These settings specify how laptop mode tools will adjust the various
# parameters of your hard drives and file systems.
###############################################################################


#
# Maximum time, in seconds, of work that you are prepared to lose when your
# system crashes or power runs out. This is the maximum time that Laptop Mode
# will keep unsaved data waiting in memory before spinning up your hard drive.
#
LM_BATT_MAX_LOST_WORK_SECONDS=600
LM_AC_MAX_LOST_WORK_SECONDS=360


#
# Should laptop mode tools control readahead?
#
CONTROL_READAHEAD=1


#
# Read-ahead, in kilobytes. You can spin down the disk while playing MP3/OGG
# by setting the disk readahead to a reasonable size, e.g. 3072 (3 MB).
# Effectively, the disk will read a complete MP3 at once, and will then spin 
# down while the MP3/OGG is playing. Don't set this too high, because the 
# readahead is applied to _all_ files that are read from disk.
#
LM_READAHEAD=3072
NOLM_READAHEAD=128


#
# Should laptop mode tools add the "noatime" option to the mount options when 
# laptop mode is enabled?
#
CONTROL_NOATIME=0


#
# Should laptop mode tools control the hard drive idle timeout settings?
#
CONTROL_HD_IDLE_TIMEOUT=1


#
# Idle timeout values. (hdparm -S)
# Default is 2 hours on AC (NOLM_HD_IDLE_TIMEOUT_SECONDS=7200) and 20 seconds
# for battery and for AC with laptop mode on.
#
LM_AC_HD_IDLE_TIMEOUT_SECONDS=20
LM_BATT_HD_IDLE_TIMEOUT_SECONDS=20
NOLM_HD_IDLE_TIMEOUT_SECONDS=7200


#
# Should laptop mode tools control the hard drive power management settings?
#
CONTROL_HD_POWERMGMT=0


#
# Power management for HD (hdparm -B values)
#
BATT_HD_POWERMGMT=1
LM_AC_HD_POWERMGMT=254
NOLM_AC_HD_POWERMGMT=254


#
# Should laptop mode tools control the hard drive write cache settings?
#
CONTROL_HD_WRITECACHE=0


#
# Write cache settings for HD (hdparm -W values)
#
NOLM_AC_HD_WRITECACHE=1
NOLM_BATT_HD_WRITECACHE=0
LM_HD_WRITECACHE=0



###############################################################################
# CPU frequency scaling and throttling
# ------------------------------------
#
# Laptop mode tools can automatically adjust your kernel CPU frequency
# settings. This includes upper and lower limits and scaling governors.
# There is also support for CPU throttling, on systems that don't support
# frequency scaling.
#
# This feature only works on 2.6 kernels.
###############################################################################


#
# Should laptop mode tools control the maximum CPU frequency?
#
CONTROL_CPU_FREQUENCY=0


#
# Legal values are "slowest" for the slowest speed that your
# CPU is able to operate at, "fastest" for the fastest speed,
# "medium" for some value in the middle, or any value listed in
# /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
# The "governor" can be any governor installed on your system, this usually
# includes "ondemand", "conservative", and "performance". The
# "IGNORE_NICE_LOAD" setting specifies that background programs that have
# a low priority ("nice level") should not cause the CPU frequency to
# be increased. (You generally want this to be enabled in battery mode.)
#
BATT_CPU_MAXFREQ=medium
BATT_CPU_MINFREQ=slowest
BATT_CPU_GOVERNOR=ondemand
BATT_CPU_IGNORE_NICE_LOAD=1
LM_AC_CPU_MAXFREQ=fastest
LM_AC_CPU_MINFREQ=slowest
LM_AC_CPU_GOVERNOR=ondemand
LM_AC_CPU_IGNORE_NICE_LOAD=1
NOLM_AC_CPU_MAXFREQ=fastest
NOLM_AC_CPU_MINFREQ=slowest
NOLM_AC_CPU_GOVERNOR=performance
NOLM_AC_CPU_IGNORE_NICE_LOAD=0


#
# Should laptop mode tools control the CPU throttling? This is only useful
# on processors that don't have frequency scaling.
# (Only works when you have /proc/acpi/processor/CPU*/throttling.)
#
CONTROL_CPU_THROTTLING=0


#
# Legal values are "maximum" for the maximum (slowest) throttling level,
# "minimum" for minimum (fastest) throttling level, "medium" for a value
# somewhere in the middle (this is usually 50% for P4s), or any value listed
# in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
# this may be _very_ slow (in fact, with P4s it slows down the processor
# by a factor 8).
#
BATT_CPU_THROTTLING=medium
LM_AC_CPU_THROTTLING=medium
NOLM_AC_CPU_THROTTLING=minimum



###############################################################################
# Syslog configuration control
# ----------------------------
# 
# Syslog daemons have a tendency to sync their log files when entries are
# written to them. This causes disks to spin up, which is not very nice when
# you're trying to save power. The syslog.conf can be tweaked to *not* sync
# a given file, by prepending the log file name with a dash, like this:
#
# 	mail.*		-/var/log/mail/mail.log
#
# Using the following options, you can let laptop mode switch between
# different syslog configurations depending on whether you are working on
# battery or on AC power. To set this up, start by configuring these options
# for your syslog daemon, and then run lm-syslog-setup to create the various
# files. Then edit the laptop mode-specific syslog configuration files to
# remove the syncs only when laptop mode is active.
###############################################################################


#
# Should laptop mode tools control which syslog.conf should be used?
#
CONTROL_SYSLOG_CONF=0


#
# Laptop mode tools controls syslog.conf by replacing /etc/syslog.conf (or
# whatever you specify in SYSLOG_CONF) by a link to the files configured here.
# NOTE: these files are NOT created by default, and if they do not
# exist this feature will not work. You can run the script
# /usr/sbin/lm-syslog-setup to set things up.
#
LM_AC_SYSLOG_CONF=/etc/syslog-on-ac-with-lm.conf
NOLM_AC_SYSLOG_CONF=/etc/syslog-on-ac-without-lm.conf
BATT_SYSLOG_CONF=/etc/syslog-on-battery.conf


#
# Signal this program when syslog.conf has been replaced.
#
SYSLOG_CONF_SIGNAL_PROGRAM=syslogd


#
# This is the syslog configuration file that should be replaced by a link to
# the other files.
#
SYSLOG_CONF=/etc/syslog.conf



###############################################################################
# X display settings
# ------------------
#
# Using these settings, you can let laptop mode tools control the X display
# standby timeouts.
#
# This requires that you have installed the "xset" utility. It is part of the
# X.org server distribution and included in the package xorg-server-utils.
#
# The X settings are not automatically applied on login, and this is
# impossible fix for the user, since laptop mode tools must operate as root.
# Therefore, it is recommended to add the following line to /etc/X11/Xsession
# as well:
#
#   /usr/sbin/laptop_mode force
#
###############################################################################


#
# Should laptop mode tools control DPMS standby settings for X displays?
#
CONTROL_DPMS_STANDBY=0


#
# These settings specify the standby timeout for the X display,
# in seconds. The suspend and poweroff timeouts are somewhat
# larger values derived from these values.
#
BATT_DPMS_STANDBY=300
LM_AC_DPMS_STANDBY=1200
NOLM_AC_DPMS_STANDBY=1200



###############################################################################
# Terminal settings
# -----------------
#
# Using these settings, you can let laptop mode tools control the terminal
# blanking timeouts. This only works for linux virtual consoles.
#
###############################################################################


#
# Should laptop mode tools control terminal blanking settings?
#
CONTROL_TERMINAL=0


#
# Terminal device files that should be affected. (One terminal is enough, this
# affects all consoles. )
#
TERMINALS="/dev/tty1"


#
# These settings specify the blanking and powerdown timeouts. Note that
# the powerdown timeout is counted from the moment the screen is blanked,
# i.e. BLANK_MINUTES=2 and POWERDOWN_MINUTES=5 means the screen powers
# down after 7 minutes of inactivity. The range for all these settings is
# 1 to 60 minutes, or 0 to disable.
#
BATT_TERMINAL_BLANK_MINUTES=1
BATT_TERMINAL_POWERDOWN_MINUTES=2
LM_AC_TERMINAL_BLANK_MINUTES=10
LM_AC_TERMINAL_POWERDOWN_MINUTES=10
NOLM_AC_TERMINAL_BLANK_MINUTES=10
NOLM_AC_TERMINAL_POWERDOWN_MINUTES=50


###############################################################################
# LCD brightness settings
# -----------------------
#
# Using these settings, you can make laptop mode tools automatically adjust
# your LCD's brightness settings. The settings are extremely simple -- they
# only allow for the execution of a command, nothing more. The reason for this
# is that LCD brightness settings are very different between laptop vendors.
#
# Suggestions for commands:
#
#  * If your system has the file "/proc/acpi/video/VID/LCD/brightness" (VID may
#    be VID1 or similar), use this file as BRIGHTNESS_OUTPUT, and use
#    the command "echo <value>". The possible values can be listed using the
#    command:
#
#       cat /proc/acpi/video/VID/LCD/brightness
#
#  * If you have a file /sys/class/backlight/.../brightness, then you can use
#    that file as BRIGHTNESS_OUTPUT, and the command "echo <value>".
#
#    As far as I understand it the values are between 0 and
#    the value contained in the file /sys/class/backlight/.../max_brightness.
#
#  * For Toshiba laptops, use the command "toshset" with the -lcd or -inten
#    command. Read the toshset(1) manual page for more information on the
#    parameters for this command. If you use this command, set
#    BRIGHTNESS_OUTPUT to "/dev/null".
#
###############################################################################


#
# Should laptop mode tools control LCD brightness?
#
CONTROL_BRIGHTNESS=0


#
# Commands to execute to set the brightness on your LCD
#
BATT_BRIGHTNESS_COMMAND="echo [value]"
LM_AC_BRIGHTNESS_COMMAND="echo [value]"
NOLM_AC_BRIGHTNESS_COMMAND="echo [value]"
BRIGHTNESS_OUTPUT="/proc/acpi/video/VID/LCD/brightness"


###############################################################################
# Auto-hibernation settings
# -------------------------
#
# Using these settings, you can make laptop mode tools automatically put your
# computer into hibernation when the battery level goes critically low.
#
# This feature only works on ACPI, and only works on computers whose batteries
# give off battery events often enough.
###############################################################################


#
# Should laptop mode tools perform auto-hibernation?
#
ENABLE_AUTO_HIBERNATION=0


#
# The hibernation command that is to be executed when auto-hibernation
# is triggered.
#
HIBERNATE_COMMAND=/usr/sbin/hibernate


#
# Auto-hibernation battery level threshold, in percentage of the battery's
# total capacity.
#
AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT=2


#
# Enable this to auto-hibernate if the battery reports that its level is
# "critical".
#
AUTO_HIBERNATION_ON_CRITICAL_BATTERY_LEVEL=1



###############################################################################
# Start/Stop Programs settings
# ----------------------------
#
# Laptop mode tools can automatically start and stop programs when entering
# various power modes. Put scripts accepting "start" and "stop" parameters
# in the directories /etc/laptop-mode/batt-stop, batt-start, lm-ac-stop,
# lm-ac-start, nolm-ac-stop and nolm-ac-start. Laptop mode will call the
# scripts in a state-"stop" directory with the "stop" parameter when entering
# the state in question, and it will call the same scripts with the "start"
# parameter when leaving the state. Scripts in a state-"start" directory are
# called with the "start" parameter when the specified state is entered, and
# with the "stop" parameter when the specified state is left.
###############################################################################


#
# Should laptop mode start and stop programs? 
#
CONTROL_START_STOP=1



###############################################################################
# Settings you probably don't want to touch
# -----------------------------------------
#
# It is usually not necessary to change these parameters. They are included
# for completeness' sake.
###############################################################################


#
# Change mount options on partitions in PARTITIONS? You don't really want to
# disable this. If you do, then your hard drives will probably not spin down
# anymore.
#
CONTROL_MOUNT_OPTIONS=1


#
# Dirty synchronous ratio.  At this percentage of dirty pages the process
# which calls write() does its own writeback.
#
LM_DIRTY_RATIO=60
NOLM_DIRTY_RATIO=40


#
# Allowed dirty background ratio, in percent.  Once DIRTY_RATIO has been
# exceeded, the kernel will wake pdflush which will then reduce the amount
# of dirty memory to dirty_background_ratio.  Set this nice and low, so once
# some writeout has commenced, we do a lot of it.
#
LM_DIRTY_BACKGROUND_RATIO=1
NOLM_DIRTY_BACKGROUND_RATIO=10


#
# kernel default settings -- don't touch these unless you know what you're 
# doing.
#
DEF_UPDATE=5
DEF_XFS_AGE_BUFFER=15
DEF_XFS_SYNC_INTERVAL=30
DEF_XFS_BUFD_INTERVAL=1
DEF_MAX_AGE=30


#
# This must be adjusted manually to the value of HZ in the running kernel
# on 2.4, until the XFS people change their 2.4 external interfaces to work in
# centisecs. This can be automated, but it's a work in progress that still
# needs some fixes. On 2.6 kernels, XFS uses USER_HZ instead of HZ for
# external interfaces, and that is currently always set to 100. So you don't
# need to change this on 2.6.
#
XFS_HZ=100


#
# Seconds laptop mode has to to wait after the disk goes idle before doing
# a sync.
#
LM_SECONDS_BEFORE_SYNC=2

Voila bonne soirée

kikislater · Le 18/03/2008, à 21:59

oh làlà, t'aurais pu nous donner simplement les différence entre les deux mais bon c pas grâve. Merci quand même

Link31 · Le 18/03/2008, à 22:11

--- gutsy   2008-03-18 21:05:32.998384038 +0100
+++ hardy   2008-03-18 21:07:08.242679905 +0100
@@ -71,14 +71,14 @@ ENABLE_LAPTOP_MODE_ON_BATTERY=1
 #
 # Enable laptop mode when on AC power.
 #
-ENABLE_LAPTOP_MODE_ON_AC=1 #0
+ENABLE_LAPTOP_MODE_ON_AC=0


 #
 # Enable laptop mode when the laptop's lid is closed, even when we're on AC
 # power? (ACPI-ONLY)
 #
-ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=1 #0
+ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0



@@ -167,7 +167,7 @@ ASSUME_SCSI_IS_SATA=1
 # will keep unsaved data waiting in memory before spinning up your hard drive.
 #
 LM_BATT_MAX_LOST_WORK_SECONDS=600
-LM_AC_MAX_LOST_WORK_SECONDS=600 #360
+LM_AC_MAX_LOST_WORK_SECONDS=360


 #
@@ -191,7 +191,7 @@ NOLM_READAHEAD=128
 # Should laptop mode tools add the "noatime" option to the mount options when
 # laptop mode is enabled?
 #
-CONTROL_NOATIME=1 #0
+CONTROL_NOATIME=0


 #
@@ -205,15 +205,15 @@ CONTROL_HD_IDLE_TIMEOUT=1
 # Default is 2 hours on AC (NOLM_HD_IDLE_TIMEOUT_SECONDS=7200) and 20 seconds
 # for battery and for AC with laptop mode on.
 #
-LM_AC_HD_IDLE_TIMEOUT_SECONDS=200
-LM_BATT_HD_IDLE_TIMEOUT_SECONDS=200
+LM_AC_HD_IDLE_TIMEOUT_SECONDS=20
+LM_BATT_HD_IDLE_TIMEOUT_SECONDS=20
 NOLM_HD_IDLE_TIMEOUT_SECONDS=7200


 #
 # Should laptop mode tools control the hard drive power management settings?
 #
-CONTROL_HD_POWERMGMT=1
+CONTROL_HD_POWERMGMT=0


 #
@@ -221,13 +221,13 @@ CONTROL_HD_POWERMGMT=1
 #
 BATT_HD_POWERMGMT=1
 LM_AC_HD_POWERMGMT=254
-NOLM_AC_HD_POWERMGMT=255
+NOLM_AC_HD_POWERMGMT=254


 #
 # Should laptop mode tools control the hard drive write cache settings?
 #
-CONTROL_HD_WRITECACHE=1
+CONTROL_HD_WRITECACHE=0


 #
@@ -235,612 +235,7 @@ CONTROL_HD_WRITECACHE=1
 #
 NOLM_AC_HD_WRITECACHE=1
 NOLM_BATT_HD_WRITECACHE=0
-LM_HD_WRITECACHE=1
-
-
-
-###############################################################################
-# CPU frequency scaling and throttling
-# ------------------------------------
-#
-# Laptop mode tools can automatically adjust your kernel CPU frequency
-# settings. This includes upper and lower limits and scaling governors.
-# There is also support for CPU throttling, on systems that don't support
-# frequency scaling.
-#
-# This feature only works on 2.6 kernels.
-###############################################################################
-
-
-#
-# Should laptop mode tools control the maximum CPU frequency?
-#
-CONTROL_CPU_FREQUENCY=0
-
-
-#
-# Legal values are "slowest" for the slowest speed that your
-# CPU is able to operate at, "fastest" for the fastest speed,
-# "medium" for some value in the middle, or any value listed in
-# /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
-# The "governor" can be any governor installed on your system, this usually
-# includes "ondemand", "conservative", and "performance". The
-# "IGNORE_NICE_LOAD" setting specifies that background programs that have
-# a low priority ("nice level") should not cause the CPU frequency to
-# be increased. (You generally want this to be enabled in battery mode.)
-#
-BATT_CPU_MAXFREQ=medium
-BATT_CPU_MINFREQ=slowest
-BATT_CPU_GOVERNOR=ondemand
-BATT_CPU_IGNORE_NICE_LOAD=1
-LM_AC_CPU_MAXFREQ=fastest
-LM_AC_CPU_MINFREQ=slowest
-LM_AC_CPU_GOVERNOR=ondemand
-LM_AC_CPU_IGNORE_NICE_LOAD=1
-NOLM_AC_CPU_MAXFREQ=fastest
-NOLM_AC_CPU_MINFREQ=slowest
-NOLM_AC_CPU_GOVERNOR=performance
-NOLM_AC_CPU_IGNORE_NICE_LOAD=0
-
-
-#
-# Should laptop mode tools control the CPU throttling? This is only useful
-# on processors that don't have frequency scaling.
-# (Only works when you have /proc/acpi/processor/CPU*/throttling.)
-#
-CONTROL_CPU_THROTTLING=0
-
-
-#
-# Legal values are "maximum" for the maximum (slowest) throttling level,
-# "minimum" for minimum (fastest) throttling level, "medium" for a value
-# somewhere in the middle (this is usually 50% for P4s), or any value listed
-# in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
-# this may be _very_ slow (in fact, with P4s it slows down the processor
-# by a factor 8).
-#
-BATT_CPU_THROTTLING=medium
-LM_AC_CPU_THROTTLING=medium
-NOLM_AC_CPU_THROTTLING=minimum
-
-
-
-###############################################################################
-# Syslog configuration control
-# ----------------------------
-#
-# Syslog daemons have a tendency to sync their log files when entries are
-# written to them. This causes disks to spin up, which is not very nice when
-# you're trying to save power. The syslog.conf can be tweaked to *not* sync
-# a given file, by prepending the log file name with a dash, like this:
-#
-#     mail.*        -/var/log/mail/mail.log
-#
-# Using the following options, you can let laptop mode switch between
-# different syslog configurations depending on whether you are working on
-# battery or on AC power. To set this up, start by configuring these options
-# for your syslog daemon, and then run lm-syslog-setup to create the various
-# files. Then edit the laptop mode-specific syslog configuration files to
-# remove the syncs only when laptop mode is active.
-###############################################################################
-
-
-#
-# Should laptop mode tools control which syslog.conf should be used?
-#
-CONTROL_SYSLOG_CONF=1
-
-
-#
-# Laptop mode tools controls syslog.conf by replacing /etc/syslog.conf (or
-# whatever you specify in SYSLOG_CONF) by a link to the files configured here.
-# NOTE: these files are NOT created by default, and if they do not
-# exist this feature will not work. You can run the script
-# /usr/sbin/lm-syslog-setup to set things up.
-#
-LM_AC_SYSLOG_CONF=/etc/syslog-on-ac-with-lm.conf
-NOLM_AC_SYSLOG_CONF=/etc/syslog-on-ac-without-lm.conf
-BATT_SYSLOG_CONF=/etc/syslog-on-battery.conf
-
-
-#
-# Signal this program when syslog.conf has been replaced.
-#
-SYSLOG_CONF_SIGNAL_PROGRAM=syslogd
-
-
-#
-# This is the syslog configuration file that should be replaced by a link to
-# the other files.
-#
-SYSLOG_CONF=/etc/syslog.conf
-
-
-
-###############################################################################
-# X display settings
-# ------------------
-#
-# Using these settings, you can let laptop mode tools control the X display
-# standby timeouts.
-#
-# This requires that you have installed the "xset" utility. It is part of the
-# X.org server distribution and included in the package xorg-server-utils.
-#
-# The X settings are not automatically applied on login, and this is
-# impossible fix for the user, since laptop mode tools must operate as root.
-# Therefore, it is recommended to add the following line to /etc/X11/Xsession
-# as well:
-#
-#   /usr/sbin/laptop_mode force
-#
-###############################################################################
-
-
-#
-# Should laptop mode tools control DPMS standby settings for X displays?
-#
-CONTROL_DPMS_STANDBY=0
-
-
-#
-# These settings specify the standby timeout for the X display,
-# in seconds. The suspend and poweroff timeouts are somewhat
-# larger values derived from these values.
-#
-BATT_DPMS_STANDBY=300
-LM_AC_DPMS_STANDBY=1200
-NOLM_AC_DPMS_STANDBY=1200
-
-
-
-###############################################################################
-# Terminal settings
-# -----------------
-#
-# Using these settings, you can let laptop mode tools control the terminal
-# blanking timeouts. This only works for linux virtual consoles.
-#
-###############################################################################
-
-
-#
-# Should laptop mode tools control terminal blanking settings?
-#
-CONTROL_TERMINAL=0
-
-
-#
-# Terminal device files that should be affected. (One terminal is enough, this
-# affects all consoles. )
-#
-TERMINALS="/dev/tty1"
-
-
-#
-# These settings specify the blanking and powerdown timeouts. Note that
-# the powerdown timeout is counted from the moment the screen is blanked,
-# i.e. BLANK_MINUTES=2 and POWERDOWN_MINUTES=5 means the screen powers
-# down after 7 minutes of inactivity. The range for all these settings is
-# 1 to 60 minutes, or 0 to disable.
-#
-BATT_TERMINAL_BLANK_MINUTES=1
-BATT_TERMINAL_POWERDOWN_MINUTES=2
-LM_AC_TERMINAL_BLANK_MINUTES=10
-LM_AC_TERMINAL_POWERDOWN_MINUTES=10
-NOLM_AC_TERMINAL_BLANK_MINUTES=10
-NOLM_AC_TERMINAL_POWERDOWN_MINUTES=50
-
-
-###############################################################################
-# LCD brightness settings
-# -----------------------
-#
-# Using these settings, you can make laptop mode tools automatically adjust
-# your LCD's brightness settings. The settings are extremely simple -- they
-# only allow for the execution of a command, nothing more. The reason for this
-# is that LCD brightness settings are very different between laptop vendors.
-#
-# Suggestions for commands:
-#
-#  * If your system has the file "/proc/acpi/video/VID/LCD/brightness" (VID may
-#    be VID1 or similar), use this file as BRIGHTNESS_OUTPUT, and use
-#    the command "echo <value>". The possible values can be listed using the
-#    command:
-#
-#       cat /proc/acpi/video/VID/LCD/brightness
-#
-#  * If you have a file /sys/class/backlight/.../brightness, then you can use
-#    that file as BRIGHTNESS_OUTPUT, and the command "echo <value>".
-#
-#    As far as I understand it the values are between 0 and
-#    the value contained in the file /sys/class/backlight/.../max_brightness.
-#
-#  * For Toshiba laptops, use the command "toshset" with the -lcd or -inten
-#    command. Read the toshset(1) manual page for more information on the
-#    parameters for this command. If you use this command, set
-#    BRIGHTNESS_OUTPUT to "/dev/null".
-#
-###############################################################################
-
-
-#
-# Should laptop mode tools control LCD brightness?
-#
-CONTROL_BRIGHTNESS=0
-
-
-#
-# Commands to execute to set the brightness on your LCD
-#
-BATT_BRIGHTNESS_COMMAND="echo [value]"
-LM_AC_BRIGHTNESS_COMMAND="echo [value]"
-NOLM_AC_BRIGHTNESS_COMMAND="echo [value]"
-BRIGHTNESS_OUTPUT="/proc/acpi/video/VID/LCD/brightness"
-
-
-###############################################################################
-# Auto-hibernation settings
-# -------------------------
-#
-# Using these settings, you can make laptop mode tools automatically put your
-# computer into hibernation when the battery level goes critically low.
-#
-# This feature only works on ACPI, and only works on computers whose batteries
-# give off battery events often enough.
-###############################################################################
-
-
-#
-# Should laptop mode tools perform auto-hibernation?
-#
-ENABLE_AUTO_HIBERNATION=0
-
-
-#
-# The hibernation command that is to be executed when auto-hibernation
-# is triggered.
-#
-HIBERNATE_COMMAND=/usr/sbin/hibernate
-
-
-#
-# Auto-hibernation battery level threshold, in percentage of the battery's
-# total capacity.
-#
-AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT=2
-
-
-#
-# Enable this to auto-hibernate if the battery reports that its level is
-# "critical".
-#
-AUTO_HIBERNATION_ON_CRITICAL_BATTERY_LEVEL=1
-
-
-
-###############################################################################
-# Start/Stop Programs settings
-# ----------------------------
-#
-# Laptop mode tools can automatically start and stop programs when entering
-# various power modes. Put scripts accepting "start" and "stop" parameters
-# in the directories /etc/laptop-mode/batt-stop, batt-start, lm-ac-stop,
-# lm-ac-start, nolm-ac-stop and nolm-ac-start. Laptop mode will call the
-# scripts in a state-"stop" directory with the "stop" parameter when entering
-# the state in question, and it will call the same scripts with the "start"
-# parameter when leaving the state. Scripts in a state-"start" directory are
-# called with the "start" parameter when the specified state is entered, and
-# with the "stop" parameter when the specified state is left.
-###############################################################################
-
-
-#
-# Should laptop mode start and stop programs?
-#
-CONTROL_START_STOP=1
-
-
-
-###############################################################################
-# Settings you probably don't want to touch
-# -----------------------------------------
-#
-# It is usually not necessary to change these parameters. They are included
-# for completeness' sake.
-###############################################################################
-
-
-#
-# Change mount options on partitions in PARTITIONS? You don't really want to
-# disable this. If you do, then your hard drives will probably not spin down
-# anymore.
-#
-CONTROL_MOUNT_OPTIONS=1
-
-
-#
-# Dirty synchronous ratio.  At this percentage of dirty pages the process
-# which calls write() does its own writeback.
-#
-LM_DIRTY_RATIO=60
-NOLM_DIRTY_RATIO=40
-
-
-#
-# Allowed dirty background ratio, in percent.  Once DIRTY_RATIO has been
-# exceeded, the kernel will wake pdflush which will then reduce the amount
-# of dirty memory to dirty_background_ratio.  Set this nice and low, so once
-# some writeout has commenced, we do a lot of it.
-#
-LM_DIRTY_BACKGROUND_RATIO=1
-NOLM_DIRTY_BACKGROUND_RATIO=10
-
-
-#
-# kernel default settings -- don't touch these unless you know what you're
-# doing.
-#
-DEF_UPDATE=5
-DEF_XFS_AGE_BUFFER=15
-DEF_XFS_SYNC_INTERVAL=30
-DEF_XFS_BUFD_INTERVAL=1
-DEF_MAX_AGE=30
-
-
-#
-# This must be adjusted manually to the value of HZ in the running kernel
-# on 2.4, until the XFS people change their 2.4 external interfaces to work in
-# centisecs. This can be automated, but it's a work in progress that still
-# needs some fixes. On 2.6 kernels, XFS uses USER_HZ instead of HZ for
-# external interfaces, and that is currently always set to 100. So you don't
-# need to change this on 2.6.
-#
-XFS_HZ=100
-
-
-#
-# Seconds laptop mode has to to wait after the disk goes idle before doing
-# a sync.
-#
-###############################################################################
-#
-# Configuration for Laptop Mode Tools
-# -----------------------------------
-#
-# There is a "system" to the configuration setting names:
-#    CONTROL_something=0/1   Determines whether Laptop Mode Tools controls
-#                            something
-#    LM_something=value      Value of "something" when laptop mode is active
-#    NOLM_something=value    Value of "something" when laptop mode is NOT
-#                            active
-#    AC_something=value      Value of "something" when the computer is running
-#                            on AC power
-#    BATT_something=value    Value of "something when the computer is running
-#                            on battery power
-#
-# There can be combinations of LM_/NOLM_ and AC_/BATT_ prefixes, but the
-# available prefixes are different for each setting. The available ones are
-# documented in the manual page, laptop-mode.conf(8). If there is no LM_/
-# NOLM_ in a setting name, then the value is used independently of laptop
-# mode state, and similarly, if there is no AC_/BATT_, then the value is used
-# independently of power state.
-#
-# Some options only work on ACPI systems. They are marked ACPI-ONLY.
-#
-# Note that this configuration file is a fragment of bash shell script: you
-# can use all the features of the bash scripting language to achieve your
-# desired configuration.
-#
-#
-# IMPORTANT: Laptop Mode Tools modules have separate configuration files, that
-# can be found in /etc/laptop-mode/conf.d. Please look through these
-# configuration files as well!
-#
-###############################################################################
-
-
-
-###############################################################################
-# Configuration debugging
-# -----------------------
-###############################################################################
-
-
-#
-# Set this to 1 if you want to see a lot of information when you start/stop
-# laptop_mode.
-#
-VERBOSE_OUTPUT=0
-
-
-
-###############################################################################
-# When to enable laptop mode
-# --------------------------
-#
-# "Laptop mode" is the mode in which laptop mode tools makes the computer
-# consume less power. This includes the kernel "laptop_mode" feature, which
-# allows your hard drives to spin down, as well as various other settings which
-# can be tweaked by laptop mode tools. You can enable or disable all of these
-# settings using the CONTROL_... options further down in this config file.
-###############################################################################
-
-
-#
-# Enable laptop mode when on battery power.
-#
-ENABLE_LAPTOP_MODE_ON_BATTERY=1
-
-
-#
-# Enable laptop mode when on AC power.
-#
-ENABLE_LAPTOP_MODE_ON_AC=1 #0
-
-
-#
-# Enable laptop mode when the laptop's lid is closed, even when we're on AC
-# power? (ACPI-ONLY)
-#
-ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=1 #0
-
-
-
-###############################################################################
-# When to enable data loss sensitive features
-# -------------------------------------------
-#
-# When data loss sensitive features are disabled, laptop mode tools acts as if
-# laptop mode were disabled, for those features only.
-#
-# Data loss sensitive features include:
-# - laptop_mode (i.e., delayed writes)
-# - hard drive write cache
-#
-# All of the options that follow can be set to 0 in order to prevent laptop
-# mode tools from using them to stop data loss sensitive features. Use this
-# when you have a battery that reports the wrong information, that confuses
-# laptop mode tools.
-#
-# Disabling data loss sensitive features is ACPI-ONLY.
-###############################################################################
-
-
-#
-# Disable all data loss sensitive features when the battery level (in % of the
-# battery capacity) reaches this value.
-#
-MINIMUM_BATTERY_CHARGE_PERCENT=3
-
-
-#
-# Disable data loss sensitive features when the battery reports its state
-# as "critical".
-#
-DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1
-
-
-###############################################################################
-# Controlled hard drives and partitions
-# -------------------------------------
-#
-# For spinning down your hard drives, laptop mode will remount file systems and
-# adjust hard drive spindown timeouts. These parameters specify which
-# devices and partitions are affected by laptop mode.
-###############################################################################
-
-
-#
-# The drives that laptop mode controls.
-# Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
-# wildcard, which will get you all your IDE and SCSI/SATA drives.
-#
-HD="/dev/[hs]d[abcdefgh]"
-
-
-#
-# The partitions (or mount points) that laptop mode controls.
-# Separate the values by spaces. Use "auto" to indicate all partitions on drives
-# listed in HD. You can add things to "auto", e.g. "auto /dev/hdc3". You can
-# also specify mount points, e.g. "/mnt/data".
-#
-PARTITIONS="auto /dev/mapper/*"
-
-
-#
-# If this is enabled, laptop mode tools will assume that SCSI drives are
-# really SATA drives that only _look_ like SCSI drives, and will use hdparm
-# to control them. Set this to 0 if you have /dev/sd devices and you want
-# laptop mode tools to use the "sdparm" command to control them.
-#
-ASSUME_SCSI_IS_SATA=1
-
-
-###############################################################################
-# Hard drive behaviour settings
-# -----------------------------
-#
-# These settings specify how laptop mode tools will adjust the various
-# parameters of your hard drives and file systems.
-###############################################################################
-
-
-#
-# Maximum time, in seconds, of work that you are prepared to lose when your
-# system crashes or power runs out. This is the maximum time that Laptop Mode
-# will keep unsaved data waiting in memory before spinning up your hard drive.
-#
-LM_BATT_MAX_LOST_WORK_SECONDS=600
-LM_AC_MAX_LOST_WORK_SECONDS=600 #360
-
-
-#
-# Should laptop mode tools control readahead?
-#
-CONTROL_READAHEAD=1
-
-
-#
-# Read-ahead, in kilobytes. You can spin down the disk while playing MP3/OGG
-# by setting the disk readahead to a reasonable size, e.g. 3072 (3 MB).
-# Effectively, the disk will read a complete MP3 at once, and will then spin
-# down while the MP3/OGG is playing. Don't set this too high, because the
-# readahead is applied to _all_ files that are read from disk.
-#
-LM_READAHEAD=3072
-NOLM_READAHEAD=128
-
-
-#
-# Should laptop mode tools add the "noatime" option to the mount options when
-# laptop mode is enabled?
-#
-CONTROL_NOATIME=1 #0
-
-
-#
-# Should laptop mode tools control the hard drive idle timeout settings?
-#
-CONTROL_HD_IDLE_TIMEOUT=1
-
-
-#
-# Idle timeout values. (hdparm -S)
-# Default is 2 hours on AC (NOLM_HD_IDLE_TIMEOUT_SECONDS=7200) and 20 seconds
-# for battery and for AC with laptop mode on.
-#
-LM_AC_HD_IDLE_TIMEOUT_SECONDS=200
-LM_BATT_HD_IDLE_TIMEOUT_SECONDS=200
-NOLM_HD_IDLE_TIMEOUT_SECONDS=7200
-
-
-#
-# Should laptop mode tools control the hard drive power management settings?
-#
-CONTROL_HD_POWERMGMT=1
-
-
-#
-# Power management for HD (hdparm -B values)
-#
-BATT_HD_POWERMGMT=1
-LM_AC_HD_POWERMGMT=254
-NOLM_AC_HD_POWERMGMT=255
-
-
-#
-# Should laptop mode tools control the hard drive write cache settings?
-#
-CONTROL_HD_WRITECACHE=1
-
-
-#
-# Write cache settings for HD (hdparm -W values)
-#
-NOLM_AC_HD_WRITECACHE=1
-NOLM_BATT_HD_WRITECACHE=0
-LM_HD_WRITECACHE=1
+LM_HD_WRITECACHE=0



@@ -933,7 +328,7 @@ NOLM_AC_CPU_THROTTLING=minimum
 #
 # Should laptop mode tools control which syslog.conf should be used?
 #
-CONTROL_SYSLOG_CONF=1
+CONTROL_SYSLOG_CONF=0


 #

jeff22 · Le 23/03/2008, à 15:35

bonjour, je suis aussi victime tu probleme des disque dur je suis a 100000 parcage des tetes
mais ca augmente assez vite soit plus de 100 / heure en moment d'inactivité

le laptop-mode pose problème sur mon ordi qui sous hardi des son activation la memoire vive et la swap se charge sans limite jusqu'a avoir des out of memory
le fait de kill le processus retabli la situation

j'ai enfaite une autre solution avec hdparm
en tapant la commande suivante

sudo hdparm -B 255 /dev/sda

ca desactive la gestion d'énergie et donc plus parcage des tetes
mais je suis obliger de la retaper a chaque demarrage car le disque dur n'en prend pas réellement compte

je cherche de l'aide pour modifier mon /etc/hdparm.com ou une solution pour lancer la comande a chaque demarrage

voila mon /etc/hdparm.conf

## This is the default configuration for hdparm for Debian.  It is a 
## rather simple script, so please follow the following guidelines :)
## Any line that begins with a comment is ignored - add as many as you 
## like.  Note that an in-line comment is not supported.  If a line 
## consists of whitespace only (tabs, spaces, carriage return), it will be
## ignored, so you can space control fields as you like.  ANYTHING ELSE
## IS PARSED!!  This means that lines with stray characters or lines that 
## use non # comment characters will be interpreted by the initscript.  
## This has probably minor, but potentially serious, side effects for your 
## hard drives, so please follow the guidelines.  Patches to improve 
## flexibilty welcome.  Please read /usr/share/doc/hdparm/README.Debian for 
## notes about known issues, especially if you have an MD array.
##
## Note that if the init script causes boot problems, you can pass 'nohdparm' 
## on the kernel command line, and the script will not be run.
##
## Uncommenting the options below will cause them to be added to the DEFAULT
## string which is prepended to options listed in the blocks below.
##
## If an option is listed twice, the second instance replaces the first.
##
## /sbin/hdparm is not run unless a block of the form:
##      DEV {
##         option
##         option
##         ...
##      }
## exists.  This blocks will cause /sbin/hdparm OPTIONS DEV to be run.
## Where OPTIONS is the concatenation of all options previously defined
## outside of a block and all options defined with in the block.

# -q be quiet
quiet 
# -a sector count for filesystem read-ahead
#read_ahead_sect = 12
# -A disable/enable the IDE drive's read-lookahead feature
#lookahead = on
# -b bus state
#bus = on
# -B apm setting
#apm = 255
# -c enable (E)IDE 32-bit I/O support - can be any of 0,1,3
#io32_support = 1
# -d disable/enable the "using_dma" flag for this drive
#dma = off
# -D enable/disable the on-drive defect management
#defect_mana = off
# -E cdrom speed
#cd_speed = 16
# -k disable/enable the "keep_settings_over_reset" flag for this drive
#keep_settings_over_reset = off
# -K disable/enable the drive's "keep_features_over_reset" flag
#keep_features_over_reset = on
# -m sector count for multiple sector I/O
#mult_sect_io = 32
# -P maximum sector count for the drive's internal prefetch mechanism
#prefetch_sect = 12
# -r read-only flag for device
#read_only = off
# -s Turn on/off power on in standby mode
#poweron_standby = off
# -S standby (spindown) timeout for the drive
#spindown_time = 24
# -u interrupt-unmask flag for the drive
#interrupt_unmask = on
# -W Disable/enable the IDE drive's write-caching feature
#write_cache = off
# -X IDE transfer mode for newer (E)IDE/ATA2 drives
#transfer_mode = 34
# -y force to immediately enter the standby mode
#standby
# -Y force to immediately enter the sleep mode
#sleep
# -Z Disable the power-saving function of certain Seagate drives
#disable_seagate
# -M Set the acoustic management properties of a drive
#acoustic_management
# -p Set the chipset PIO mode
# chipset_pio_mode
# --security-freeze Freeze the drive's security status
# security_freeze
# --security-unlock Unlock the drive's security
# security_unlock = PWD
# --security-set-pass Set security password
# security_pass = password
# --security-disable Disable drive locking
# security_disable
# --user-master Select password to use
# user-master = u
# --security-mode Set the security mode
# security_mode = h

# Root file systems.  Please see README.Debian for details
# ROOTFS = /dev/hda

## New note - you can use straight hdparm commands in this config file 
## as well - the set up is ugly, but it keeps backwards compatibility
## Additionally, it should be noted that any blocks that begin with 
## the keyword 'command_line' are not run until after the root filesystem
## is mounted.  This is done to avoid running blocks twice.  If you need 
## to run hdparm to set parameters for your root disk, please use the 
## standard format.

#Samples follow:
#First three are good for devfs systems, fourth one for systems that do 
#not use devfs.  The fifth example uses straight hdparm command line
#syntax.  Any of the blocks that use command line syntax must begin with
#the keyword 'command_line', and no attempt is made to validate syntax.  
#It is provided for those more comfortable with hdparm syntax. 

#/dev/discs/disc0/disc {
#	mult_sect_io = 16
#	write_cache = off
#	spindown_time = 240
#}

#/dev/discs/disc1/disc {
#	mult_sect_io = 32
#	spindown_time = 36
#	write_cache = off
#}

#/dev/cdroms/cdrom0 {
#	dma = on		   
#	interrupt_unmask = on
#	io32_support = 0
#}

#/dev/hda {
#	mult_sect_io = 16
#	write_cache = off
#	dma = on
#}


#command_line {
#       hdparm -q -m16 -q -W0 -q -d1 /dev/hda
#}

merci d'avance

Dernière modification par jeff22 (Le 23/03/2008, à 15:36)

Namour · Le 23/03/2008, à 15:41

http://doc.ubuntu-fr.org/laptop_mode

suis le tuto...
pour ma part, j'ai mis :
BATT_HD_POWERMGMT=255
LM_AC_HD_POWERMGMT=255
NOLM_AC_HD_POWERMGMT=255

et ça ne parque plus (que ce soit sur batterie ou sur AC)

Flex · Le 25/03/2008, à 19:32

Bonjour

Je suis un peu perplexe. Mon disque dur est un Seagate Momentus 5400.2 120 GB. Smartmontools et Everest m'indiquent 63900 parcages pour 2270 heures d'utilisation (très largement sous Windows) soit une moyenne d'environ 28 parcages par heure, ce qui me semble assez élevé mais raisonnable par rapport à ce qui a été dit ici.

Cependant, pour les parcages, il est indiqué un taux d'usure de 31 %, ce qui donne un maximum théorique d'un peu plus de 200000 parcages seulement et limite donc le temps d'utilisation à 7000 heures en tout. J'ai lu qu'il existe des disques durs tarés à 200000 parcages (notamment les Seagate...), ce qui semble être le cas de mon HD. Ma question est tout simplement : pourquoi ? Est-ce que Seagate sous-estime très largement la valeur théorique maximale de parcages de ses disques ou ces derniers tiennent-ils réellement moins longtemps que d'autres marques de disques durs (ce qui devrait quand même être signalé quelque part) ?

Je précise indépendamment de tout ça que je suis touché par le problème sous Ubuntu 7.10 : je monte à plus de 100 parcages par heure.

Merci de m'avoir lu

jeff22 · Le 26/03/2008, à 23:05

jeff22 a écrit :

bonjour, je suis aussi victime tu probleme des disque dur je suis a 100000 parcage des tetes
mais ca augmente assez vite soit plus de 100 / heure en moment d'inactivité

le laptop-mode pose problème sur mon ordi qui sous hardi des son activation la memoire vive et la swap se charge sans limite jusqu'a avoir des out of memory
le fait de kill le processus retabli la situation

j'ai enfaite une autre solution avec hdparm
en tapant la commande suivante

sudo hdparm -B 255 /dev/sda

ca desactive la gestion d'énergie et donc plus parcage des tetes
mais je suis obliger de la retaper a chaque demarrage car le disque dur n'en prend pas réellement compte

je cherche de l'aide pour modifier mon /etc/hdparm.com ou une solution pour lancer la comande a chaque demarrage

voila mon /etc/hdparm.conf

## This is the default configuration for hdparm for Debian.  It is a 
## rather simple script, so please follow the following guidelines :)
## Any line that begins with a comment is ignored - add as many as you 
## like.  Note that an in-line comment is not supported.  If a line 
## consists of whitespace only (tabs, spaces, carriage return), it will be
## ignored, so you can space control fields as you like.  ANYTHING ELSE
## IS PARSED!!  This means that lines with stray characters or lines that 
## use non # comment characters will be interpreted by the initscript.  
## This has probably minor, but potentially serious, side effects for your 
## hard drives, so please follow the guidelines.  Patches to improve 
## flexibilty welcome.  Please read /usr/share/doc/hdparm/README.Debian for 
## notes about known issues, especially if you have an MD array.
##
## Note that if the init script causes boot problems, you can pass 'nohdparm' 
## on the kernel command line, and the script will not be run.
##
## Uncommenting the options below will cause them to be added to the DEFAULT
## string which is prepended to options listed in the blocks below.
##
## If an option is listed twice, the second instance replaces the first.
##
## /sbin/hdparm is not run unless a block of the form:
##      DEV {
##         option
##         option
##         ...
##      }
## exists.  This blocks will cause /sbin/hdparm OPTIONS DEV to be run.
## Where OPTIONS is the concatenation of all options previously defined
## outside of a block and all options defined with in the block.

# -q be quiet
quiet 
# -a sector count for filesystem read-ahead
#read_ahead_sect = 12
# -A disable/enable the IDE drive's read-lookahead feature
#lookahead = on
# -b bus state
#bus = on
# -B apm setting
#apm = 255
# -c enable (E)IDE 32-bit I/O support - can be any of 0,1,3
#io32_support = 1
# -d disable/enable the "using_dma" flag for this drive
#dma = off
# -D enable/disable the on-drive defect management
#defect_mana = off
# -E cdrom speed
#cd_speed = 16
# -k disable/enable the "keep_settings_over_reset" flag for this drive
#keep_settings_over_reset = off
# -K disable/enable the drive's "keep_features_over_reset" flag
#keep_features_over_reset = on
# -m sector count for multiple sector I/O
#mult_sect_io = 32
# -P maximum sector count for the drive's internal prefetch mechanism
#prefetch_sect = 12
# -r read-only flag for device
#read_only = off
# -s Turn on/off power on in standby mode
#poweron_standby = off
# -S standby (spindown) timeout for the drive
#spindown_time = 24
# -u interrupt-unmask flag for the drive
#interrupt_unmask = on
# -W Disable/enable the IDE drive's write-caching feature
#write_cache = off
# -X IDE transfer mode for newer (E)IDE/ATA2 drives
#transfer_mode = 34
# -y force to immediately enter the standby mode
#standby
# -Y force to immediately enter the sleep mode
#sleep
# -Z Disable the power-saving function of certain Seagate drives
#disable_seagate
# -M Set the acoustic management properties of a drive
#acoustic_management
# -p Set the chipset PIO mode
# chipset_pio_mode
# --security-freeze Freeze the drive's security status
# security_freeze
# --security-unlock Unlock the drive's security
# security_unlock = PWD
# --security-set-pass Set security password
# security_pass = password
# --security-disable Disable drive locking
# security_disable
# --user-master Select password to use
# user-master = u
# --security-mode Set the security mode
# security_mode = h

# Root file systems.  Please see README.Debian for details
# ROOTFS = /dev/hda

## New note - you can use straight hdparm commands in this config file 
## as well - the set up is ugly, but it keeps backwards compatibility
## Additionally, it should be noted that any blocks that begin with 
## the keyword 'command_line' are not run until after the root filesystem
## is mounted.  This is done to avoid running blocks twice.  If you need 
## to run hdparm to set parameters for your root disk, please use the 
## standard format.

#Samples follow:
#First three are good for devfs systems, fourth one for systems that do 
#not use devfs.  The fifth example uses straight hdparm command line
#syntax.  Any of the blocks that use command line syntax must begin with
#the keyword 'command_line', and no attempt is made to validate syntax.  
#It is provided for those more comfortable with hdparm syntax. 

#/dev/discs/disc0/disc {
#	mult_sect_io = 16
#	write_cache = off
#	spindown_time = 240
#}

#/dev/discs/disc1/disc {
#	mult_sect_io = 32
#	spindown_time = 36
#	write_cache = off
#}

#/dev/cdroms/cdrom0 {
#	dma = on		   
#	interrupt_unmask = on
#	io32_support = 0
#}

#/dev/hda {
#	mult_sect_io = 16
#	write_cache = off
#	dma = on
#}


#command_line {
#       hdparm -q -m16 -q -W0 -q -d1 /dev/hda
#}

merci d'avance

personne pour m'aider svp

Mitchnumber1 · Le 27/03/2008, à 01:46

1000° post sur ce fil!! Je sais, je sers à rien. dsl

Link31 · Le 27/03/2008, à 02:17

Mitchnumber1 a écrit :

1000° post sur ce fil!! Je sais, je sers à rien. dsl

Raté, le tien est le #999

jeff22 a écrit :

personne pour m'aider svp

D'après ce que je peux lire dans les commentaires du fichier de configuration, il faudrait ajouter :

command_line {
       hdparm -B 255 /dev/sda
}

Dernière modification par Link31 (Le 27/03/2008, à 02:20)

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#976 Le 09/03/2008, à 03:09

Re : Vieillissement prématuré des disques durs de portables

#977 Le 09/03/2008, à 04:36

Re : Vieillissement prématuré des disques durs de portables

#978 Le 09/03/2008, à 09:30

Re : Vieillissement prématuré des disques durs de portables

#979 Le 09/03/2008, à 12:21

Re : Vieillissement prématuré des disques durs de portables

#980 Le 09/03/2008, à 18:30

Re : Vieillissement prématuré des disques durs de portables

#981 Le 09/03/2008, à 19:24

Re : Vieillissement prématuré des disques durs de portables

#982 Le 12/03/2008, à 16:23

Re : Vieillissement prématuré des disques durs de portables

#983 Le 12/03/2008, à 17:41

Re : Vieillissement prématuré des disques durs de portables

#984 Le 12/03/2008, à 22:45

Re : Vieillissement prématuré des disques durs de portables

#985 Le 13/03/2008, à 21:23

Re : Vieillissement prématuré des disques durs de portables

#986 Le 13/03/2008, à 21:32

Re : Vieillissement prématuré des disques durs de portables

#987 Le 13/03/2008, à 23:08

Re : Vieillissement prématuré des disques durs de portables

#988 Le 15/03/2008, à 19:39

Re : Vieillissement prématuré des disques durs de portables

#989 Le 18/03/2008, à 08:42

Re : Vieillissement prématuré des disques durs de portables

#990 Le 18/03/2008, à 10:41

Re : Vieillissement prématuré des disques durs de portables

#991 Le 18/03/2008, à 15:32

Re : Vieillissement prématuré des disques durs de portables

#992 Le 18/03/2008, à 21:46

Re : Vieillissement prématuré des disques durs de portables

#993 Le 18/03/2008, à 21:59

Re : Vieillissement prématuré des disques durs de portables

#994 Le 18/03/2008, à 22:11

Re : Vieillissement prématuré des disques durs de portables

#995 Le 23/03/2008, à 15:35

Re : Vieillissement prématuré des disques durs de portables

#996 Le 23/03/2008, à 15:41

Re : Vieillissement prématuré des disques durs de portables

#997 Le 25/03/2008, à 19:32

Re : Vieillissement prématuré des disques durs de portables

#998 Le 26/03/2008, à 23:05

Re : Vieillissement prématuré des disques durs de portables

#999 Le 27/03/2008, à 01:46

Re : Vieillissement prématuré des disques durs de portables

#1000 Le 27/03/2008, à 02:17

Re : Vieillissement prématuré des disques durs de portables

Pied de page des forums