Repository 32bit  Forum
Repository 64bit  Wiki

Configurare la sospensione alla chiusura del coperchio

Scrivete su questo forum se avete problemi o volete dare buoni consigli sui computer portatili (Laptop).

Moderatore: Staff

Regole del forum
1) Citare sempre la versione di Slackware usata, la versione del Kernel e magari anche la versione della libreria coinvolta. Questi dati aiutano le persone che possono rispondere.
2) Citare il modello preciso del laptop in questione.
3) Leggere attentamente le risposte ricevute
4) Scrivere i messaggi con il colore di default, evitare altri colori.
5) Scrivere in Italiano o in Inglese, se possibile grammaticalmente corretto, evitate stili di scrittura poco chiari, quindi nessuna abbreviazione tipo telegramma o scrittura stile SMS o CHAT.
6) Appena registrati è consigliato presentarsi nel forum dedicato.

La non osservanza delle regole porta a provvedimenti di vari tipo da parte dello staff, in particolare la non osservanza della regola 5 porta alla cancellazione del post e alla segnalazione dell'utente. In caso di recidività l'utente rischia il ban temporaneo.

Messaggioda Karma » gio dic 13, 2007 23:36

PS: l'unico inghippo è dato dalla connessione di rete wifi, perché se accendo il notebook dove non rileva la connessione (fuori casa, ad esempio), quando torno a casa devo riavviare per farlo connettere!


Non credo serva riavviare...
Secondo la mia esperienza basta che rimuovi i moduli della scheda wireless e poi li ricarichi. Almeno per me funziona così.

Karma
Avatar utente
Karma
Linux 2.4
Linux 2.4
 
Messaggi: 285
Iscritto il: lun ago 29, 2005 23:00
Località: Trento
Slackware: 12.0
Kernel: 2.6.23.1
Desktop: KDE 3.5

Messaggioda Alcatraz » ven dic 14, 2007 15:30

Il mio modulo si chiama "ipw3945d", come si fa a rimuoverlo e riavviarlo?

Grazie!
Alcatraz
Linux 2.0
Linux 2.0
 
Messaggi: 126
Iscritto il: ven ott 12, 2007 11:28

Messaggioda syaochan » ven dic 14, 2007 20:58

Di solito i moduli si caricano con modprobe e si rimuovono con l'opzione -r
Avatar utente
syaochan
Linux 2.6
Linux 2.6
 
Messaggi: 659
Iscritto il: sab mag 08, 2004 23:00
Nome Cognome: Christian
Slackware: current 64
Kernel: 2.6.38.7
Desktop: KDE 4.5.5

Messaggioda Karma » ven dic 14, 2007 23:25

Di solito i moduli si caricano con modprobe e si rimuovono con l'opzione -r


oppure usando rmmod ...
Insomma, riassumendo devi fare:

Codice: Seleziona tutto
modprobe -r ipw3945d
modprobe ipw3945d


oppure

Codice: Seleziona tutto
rmmod ipw3945d
modprobe ipw3945d


Buon lavoro!

Karma
Avatar utente
Karma
Linux 2.4
Linux 2.4
 
Messaggi: 285
Iscritto il: lun ago 29, 2005 23:00
Località: Trento
Slackware: 12.0
Kernel: 2.6.23.1
Desktop: KDE 3.5

Messaggioda Alcatraz » dom dic 16, 2007 12:44

Grazie mille! :D
Alcatraz
Linux 2.0
Linux 2.0
 
Messaggi: 126
Iscritto il: ven ott 12, 2007 11:28

Messaggioda K » gio dic 20, 2007 10:25

salve a tutti...
per quanto riguarda il suspend2ram sono riuscito perfettamente....
ma vorrei delle delucidazioni per il resume, infatti alla riapertura del coperchio sembra che qualcosa si riprenda, pero' lo schermo resta tutto nero....
e quindi devo riavviare il tutto..
se puo' servire posto il mio lspci:

00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to AGP Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
02:07.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev a9)
02:07.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev a9)
02:07.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 01)
02:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:09.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)



gli script per la sospensione ovvero acpi_handler.sh




# Programmi e variabili che si useranno in seguito
LOGGER="/usr/bin/logger -t ACPID" # logs to syslog - an echo logs to /var/log/acpid
XGAMMA="/usr/X11R6/bin/xgamma"
XSET="/usr/X11R6/bin/xset"
HDPARM="/sbin/hdparm"
# È necessario mettere l'indirizzo giusto della batteria, dell'alimentatore e del coperchio
BAT_STATE="/proc/acpi/battery/BAT0/state"
BAT_INFO="/proc/acpi/battery/BAT0/info"
AC_STATE="/proc/acpi/ac_adapter/AC/state"
LID_STATE="/proc/acpi/button/lid/LIDO/state"


# Se lo script non sa come gestire questo evento
# scrive nel /var/log/acpid
# può essere utile per trovare 'grep #### /var/log/acpid'
# in alternativa si può sostituire echo con $LOGGER in modo da vederlo in /var/log/messages
no_action ()
{
echo "#### NO ACTION FOR EVENT: " $*
exit 1
}
# Pressione del bottone Sleep
btn_sleep ()
{
$LOGGER "Start Sleeping"
# Questo è un piccolo script creato da me che manda in sistema in sospensione
#/sbin/suspend.sh
}

# AC Adapter plugged in
acad_in ()
{
$LOGGER "AC Adapter plugged IN"

if ps -A | grep -q X
then
$XGAMMA -d 0:0 -gamma 1.0 # set gamma in X to 100%
$XSET -d 0:0 dpms 0 0 600 # shutdown display after 600s
fi
$HDPARM -S 240 /dev/hda > /dev/null 2>&1 # spindown after 20min
$HDPARM -B 255 /dev/hda > /dev/null 2>&1 # disable drive's APM
#echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# $LOGGER "CPU switch mode ondemand"
}


# AC Adapter plugged out
acad_out ()
{
$LOGGER "AC Adapter plugged OUT"

if ps -A | grep -q X
then
$XGAMMA -d 0:0 -gamma 0.7 # set gamma in X to 70%
$XSET -d 0:0 dpms 0 0 120 # shutdown display after 120s
fi
$HDPARM -S 4 /dev/hda > /dev/null 2>&1 # spindown after 20s
$HDPARM -B 1 /dev/hda > /dev/null 2>&1 # enable drives's APM
#echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# $LOGGER "CPU switch mode powersave"
}


# state of battery changed
# shutdown if battery capacity is low
battery ()
{
if grep -q discharging $BAT_STATE
then
BAT_REMAIN=`awk '/remaining/ { print $3 }' $BAT_STATE`
if (($BAT_REMAIN < `awk '/warning/ { print $4 }' $BAT_INFO`))
then
$LOGGER "battery capacity is critically low"
# Nel mio caso faccio sospendere il pc ma si può tranquillamente farlo spegnere
btn_pwr
# btn_pwr # Nel caso in cui lo si voglia far spegnere
fi
fi
}


# powerbutton pressed
btn_pwr ()
{
$LOGGER "Powerbutton pressed"
$LOGGER "shutdown initiated"
/sbin/init 0
}


# lid closed/opened
# Se avete da inserire qualche opzione per quando il coperchio si chiude (tipo metterlo in standby)
btn_lid ()
{
if grep -q open $LID_STATE
then
$LOGGER "Lid opened"
else
$LOGGER "Lid closed"
/etc/acpi/lid.sh
fi
}

# Con i dati ottunuti attraverso il
# tail -f /var/log/acpid | grep received
# si costruisce un case che farà eseguire i vari comandi
case "$*" in
ac_adapter\ AC\ 00000001\ 00000000)
acad_out
;;
ac_adapter\ AC\ 00000000\ 00000001)
acad_in
;;
battery\ BAT0\ 00000081\ 00000001)
battery
;;
battery\ BAT0\ 00000080\ 00000000)
$LOGGER "Battery Plugged Out"
;;
battery\ BAT0\ 00000080\ 00000001)
$LOGGER "Battery Plugged In"
;;
button?lid\ LID0\ 00000080\ ????????)
# the last eight digits count the times the lid was shut
btn_lid
;;
button?power\ PWRF\ 00000080\ ????????)
# the last eight digits count the times the button was pressed
btn_pwr
;;
button?sleep\ SLPB\ 00000080\ ????????)
btn_sleep
;;
*)
no_action
;;
esac



e /etc/acpi/lid.sh:




#!/bin/sh

if [ "`cat /proc/acpi/button/lid/LID/state | grep open`" = "" ]; then
echo -n mem > /sys/power/state
fi



infine xorg.conf:


# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me. :)

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
Load "type1"
Load "freetype"
#Load "speedo"

# This loads the GLX module
Load "glx"
Load "dri"
EndSection
Section "DRI"
mode 0666
EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/share/fonts/local/"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

# ModulePath "/usr/lib/xorg/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "DontZoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

# Set the basic blanking screen saver timeout.

# Option "blank time" "10" # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option "standby time" "20"
# Option "suspend time" "30"
# Option "off time" "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option "EstimateSizesAggresively" "0"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"
# Options "XkbLayout" "it"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

# Set the keyboard auto repeat parameters. Not all platforms implement
# this.

# Option "AutoRepeat" "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

# Option "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

# Option "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
# Option "XkbLayout" "de"
#
# or:
#
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
# Option "XkbOptions" "ctrl:swapcaps"


# These are the default XKB settings for X.Org
#
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

# Option "Protocol" "Auto"

# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option "Protocol" "imPS/2"
Option "ZAxis Mapping" "4 5"
Option "Emulate3Buttons" "no"

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection

# Some examples of extended input devices

# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Synaptics touchpad
#Section "InputDevice"
#
# Identifier "MouseSynaptics"
# Driver "synaptics"
# Option "Device" "/dev/input/mouse1"
# Option "Protocol" "auto-dev"
# Option "LeftEdge" "1900"
# Option "RightEdge" "5400"
# Option "TopEdge" "1900"
# Option "BottomEdge" "4000"
# Option "FingerLow" "25"
# Option "FingerHigh" "30"
# Option "MaxTapTime" "100" #the touch-click is off!
# Option "MaxTapMove" "100"
# Option "VertScrollDelta" "100" #vertical scroll (0 to disable)
# Option "HorizScrollDelta" "0" #horizontal scroll (0 to disable)
# Option "MinSpeed" "0.09"
# Option "MaxSpeed" "0.22"
# Option "AccelFactor" "0.0017"
# Option "SHMConfig" "on"
#EndSection
# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 50.0

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
Identifier "Intel 82852/855GM"
Driver "i810"
Option "XAANoOffscreenPixmaps" "true"
#Option "AddARGBGLXVisuals" "true"
Option "DRI" "true"
#Option "DisableGLXRootClipping" "true"
#Option "TripleBuffer" "true"
#Option "RenderAccel" "true"
#Option "AllowGLXWithComposite" "true"
BusID "PCI:0:2:0"
#Option "NoAccel" "false"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "Intel 82852/855GM"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
Option "AIGLX" "true"
# InputDevice "MouseSynaptics" "AlwaysCore" # IMPORTANT!
EndSection
Section "Extensions"
Option "Composite" "Enable"
Option "DAMAGE" "true"
EndSection
Avatar utente
K
Linux 1.0
Linux 1.0
 
Messaggi: 57
Iscritto il: sab ott 14, 2006 9:49
Località: latronico
Slackware: 12.0

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda tigerwalk » mer mar 05, 2008 10:50

Salve,
ho seguito questa discussione ed anche a me (Toshiba satellite A100), la prima volta che chiudo lo schermo funziona, dalla volta successiva devo spegnere brutalmente perchè non esce dal suspend.
Ho ovviato facendo uno script col comando echo -n mem > /sys/power/state che funziona invece tutte le volte che lo avvio.
La mia richiesta è che vorrei avviare lo script da utente, senza diventare root, ho cercato di editare /etc/sudoers ma senza risultati:
Codice: Seleziona tutto
# grep -vE '(^[[:space:]]*($|(#|!|;|//)))' /etc/sudoers
root    ALL=(ALL) ALL
tigerwalk       All=(ALL) ALL
  %wheel        ALL=(ALL)       ALL
Cmnd_Alias suspend=/usr/bin/suspend.sh
User_Alias UTENTI_suspend=tigerwalk
UTENTI_SUSPEND tiger=NOPASSWD:suspend

Siccome non sono una cima (anzi!), potreste indicarmi come modificare il sudoers affinchè possa avviare lo script da utente?
Grazie!
Avatar utente
tigerwalk
Linux 2.6
Linux 2.6
 
Messaggi: 870
Iscritto il: lun feb 25, 2008 22:08
Località: Napoli
Nome Cognome: Giuliano della Vecchia
Slackware: 13.1
Kernel: 2.6.33.4-tiger
Desktop: kde4/fluxbox

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda alessiodf » mer mar 05, 2008 11:06

tigerwalk ha scritto:Salve,
ho seguito questa discussione ed anche a me (Toshiba satellite A100), la prima volta che chiudo lo schermo funziona, dalla volta successiva devo spegnere brutalmente perchè non esce dal suspend.
Ho ovviato facendo uno script col comando echo -n mem > /sys/power/state che funziona invece tutte le volte che lo avvio.
La mia richiesta è che vorrei avviare lo script da utente, senza diventare root, ho cercato di editare /etc/sudoers ma senza risultati:
Codice: Seleziona tutto
# grep -vE '(^[[:space:]]*($|(#|!|;|//)))' /etc/sudoers
root    ALL=(ALL) ALL
tigerwalk       All=(ALL) ALL
  %wheel        ALL=(ALL)       ALL
Cmnd_Alias suspend=/usr/bin/suspend.sh
User_Alias UTENTI_suspend=tigerwalk
UTENTI_SUSPEND tiger=NOPASSWD:suspend

Siccome non sono una cima (anzi!), potreste indicarmi come modificare il sudoers affinchè possa avviare lo script da utente?
Grazie!


aggiungi questo:
Codice: Seleziona tutto
TUO_UTENTE NOME_HOST=(root) NOPASSWD: /dove/hai/messo/lo/script.sh


dove TUO_UTENTE e' li nome del tuo utente
e NOME_HOST e' il nome del tuo pc :p
Avatar utente
alessiodf
Linux 2.6
Linux 2.6
 
Messaggi: 823
Iscritto il: ven ott 14, 2005 20:04
Località: Roma
Slackware: current
Kernel: 2.6.26.4
Desktop: Kde 4.1

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda tigerwalk » mer mar 05, 2008 11:21

Grazie per la rapida risposta!
Dopo l'aggiunta ch mi hai consigliato:
Codice: Seleziona tutto
$ ./suspend.sh
./suspend.sh: line 2: /sys/power/state: Permission denied

:cry:
Avatar utente
tigerwalk
Linux 2.6
Linux 2.6
 
Messaggi: 870
Iscritto il: lun feb 25, 2008 22:08
Località: Napoli
Nome Cognome: Giuliano della Vecchia
Slackware: 13.1
Kernel: 2.6.33.4-tiger
Desktop: kde4/fluxbox

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda JohnnyMnemonic » mer mar 05, 2008 11:25

Ero io ad aver posto il problema del secondo "riavvio", ma ora si è risolto grazie all'aggiornamento del kernel presumo, ora uso il 2.6.24.2, magari puoi provare anche tu
Avatar utente
JohnnyMnemonic
Staff
Staff
 
Messaggi: 2732
Iscritto il: sab set 04, 2004 23:00
Località: Bologna
Nome Cognome: Giuseppe Palmiotto
Slackware: 14.0
Kernel: 3.5.5-thanatos

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda tigerwalk » mer mar 05, 2008 11:28

JohnnyMnemonic ha scritto:Ero io ad aver posto il problema del secondo "riavvio", ma ora si è risolto grazie all'aggiornamento del kernel presumo, ora uso il 2.6.24.2, magari puoi provare anche tu

Io uso il kernel 2.6.24.3, potresti postare il .config relativo all'ACPI? Grazie
Avatar utente
tigerwalk
Linux 2.6
Linux 2.6
 
Messaggi: 870
Iscritto il: lun feb 25, 2008 22:08
Località: Napoli
Nome Cognome: Giuliano della Vecchia
Slackware: 13.1
Kernel: 2.6.33.4-tiger
Desktop: kde4/fluxbox

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda JohnnyMnemonic » mer mar 05, 2008 11:39

Codice: Seleziona tutto
#
# Power management options
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_SMP_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION_SMP_POSSIBLE=y
# CONFIG_HIBERNATION is not set
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
# CONFIG_APM is not set
Avatar utente
JohnnyMnemonic
Staff
Staff
 
Messaggi: 2732
Iscritto il: sab set 04, 2004 23:00
Località: Bologna
Nome Cognome: Giuseppe Palmiotto
Slackware: 14.0
Kernel: 3.5.5-thanatos

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda tigerwalk » mer mar 05, 2008 11:45

Grazie mille, adesso confronto con la mia!
Avatar utente
tigerwalk
Linux 2.6
Linux 2.6
 
Messaggi: 870
Iscritto il: lun feb 25, 2008 22:08
Località: Napoli
Nome Cognome: Giuliano della Vecchia
Slackware: 13.1
Kernel: 2.6.33.4-tiger
Desktop: kde4/fluxbox

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda tigerwalk » mer mar 05, 2008 11:58

In effetti differiscono solo per questa voce
Codice: Seleziona tutto
CONFIG_ACPI_TOSHIBA=y

che a te è disattivata, che dici, mi conviene ricompilare oppure è ininfluente?

@alessiodf
ho riprovato commentando le righe che avevo messo io e funziona dando
Codice: Seleziona tutto
sudo ./suspend.sh

senza chiedere la password.
Grazie.
Avatar utente
tigerwalk
Linux 2.6
Linux 2.6
 
Messaggi: 870
Iscritto il: lun feb 25, 2008 22:08
Località: Napoli
Nome Cognome: Giuliano della Vecchia
Slackware: 13.1
Kernel: 2.6.33.4-tiger
Desktop: kde4/fluxbox

Re: Configurare la sospensione alla chiusura del coperchio

Messaggioda JohnnyMnemonic » mer mar 05, 2008 12:06

Beh considerando che il mio è HP e il tuo Toshiba, tentar non nuoce
Avatar utente
JohnnyMnemonic
Staff
Staff
 
Messaggi: 2732
Iscritto il: sab set 04, 2004 23:00
Località: Bologna
Nome Cognome: Giuseppe Palmiotto
Slackware: 14.0
Kernel: 3.5.5-thanatos

PrecedenteProssimo

Torna a Laptop

Chi c’è in linea

Visitano il forum: Bing [Bot] e 2 ospiti