https://wiki.archlinux.org/api.php?action=feedcontributions&user=Flecha&feedformat=atomArchWiki - User contributions [en]2024-03-29T02:31:53ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=ConnMan&diff=438163ConnMan2016-06-15T01:07:39Z<p>Flecha: </p>
<hr />
<div>[[Category:Network configuration]]<br />
[[fr:Connman]]<br />
[[it:Connman]]<br />
[[ja:Connman]]<br />
{{Related articles start}}<br />
{{Related|Network configuration}}<br />
{{Related|Wireless network configuration}}<br />
{{Related|:Category:Network configuration}}<br />
{{Related articles end}}<br />
<br />
[https://01.org/connman ConnMan] is a command-line network manager designed for use with embedded devices and fast resolve times. It is modular through a [http://git.kernel.org/cgit/network/connman/connman.git/tree/plugins plugin architecture], but has native [http://git.kernel.org/cgit/network/connman/connman.git/tree/src/dhcp.c dhcp] and [http://git.kernel.org/cgit/network/connman/connman.git/tree/src/ntp.c ntp] support.<br />
<br />
== Installation ==<br />
<br />
[[Install]] the {{Pkg|connman}} package. {{Pkg|wpa_supplicant}} and {{Pkg|bluez}} are optional dependencies required for Wi-Fi and Bluetooth functionality respectively.<br />
<br />
Before [[enabling]] {{ic|connman.service}}, ensure any existing [[network configuration]] is disabled.<br />
<br />
=== Desktop clients ===<br />
<br />
* {{App|cmst|Qt GUI for ConnMan.|https://github.com/andrew-bibb/cmst|{{AUR|cmst}}}}<br />
* {{App|connman-ncurses|Simple ncurses UI for ConnMan; not all of connman functionality is implemented, but usable (with X or from terminal without X), see the [https://github.com/eurogiciel-oss/connman-json-client/wiki wiki].|https://github.com/eurogiciel-oss/connman-json-client|{{AUR|connman-ncurses-git}}}}<br />
* {{App|connman-notify|Connman event notification client|https://github.com/wavexx/connman-notify|{{AUR|connman-notify}}{{Broken package link|{{aur-mirror|connman-notify}}}}}}<br />
* {{App|ConnMan-UI|GTK3 client applet.|https://github.com/tbursztyka/connman-ui|{{AUR|connman-ui-git}}}}<br />
* {{App|connman_dmenu|Client/frontend for dmenu.|https://github.com/taylorchu/connman_dmenu|{{AUR|connman_dmenu-git}}}}<br />
* {{App|Econnman|Enlightenment desktop panel applet.|http://www.enlightenment.org|{{AUR|econnman}}}}<br />
* {{App|LXQt-Connman-Applet|LXQt desktop panel applet.|https://github.com/surlykke/lxqt-connman-applet|{{AUR|lxqt-connman-applet-git}}}}<br />
* {{App|qconnman-ui|Qt management interface used on O.S. Systems products|https://github.com/OSSystems/qconnman-ui|{{AUR|qconnman-ui-git}}{{Broken package link|{{aur-mirror|qconnman-ui-git}}}}}}<br />
* {{App|connman-gtk| GTK client.|https://github.com/jgke/connman-gtk|{{AUR|connman-gtk}}}}<br />
* {{App|gnome-extension-connman| Gnome3 extension for connman; it contains only some of the functionality without installing connman-gtk.|https://github.com/jgke/gnome-extension-connman|https://extensions.gnome.org/extension/981/connman-extension/}}<br />
<br />
== Usage ==<br />
<br />
{{Expansion|Only Wired and Wi-Fi plugins are described.}}<br />
<br />
ConnMan has a standard command line client {{ic|connmanctl}}. It can run in 2 modes:<br />
*In '''command mode''' commands are entered as arguments to {{ic|connmanctl}} command, just like [[systemctl]].<br />
*'''Interactive mode''' is started by typing {{ic|connmanctl}} without arguments. Prompt will change to {{ic|connmanctl>}} to indicate it is waiting for user commands, just like [[python]] interactive mode. The interactive mode supports tab completion, which makes finding the correct connection easy.<br />
<br />
=== Wired ===<br />
<br />
ConnMan will automatically handle wired connections.<br />
<br />
=== Wi-Fi ===<br />
<br />
{{Note|Make sure the Wi-Fi device is listed in the output of {{ic|ip link show up}}. If it is not listed that means it is not powered on. Use {{ic|Fn}} keys on the laptop to turn it on. You may need to run {{ic|connmanctl enable wifi}}.}}<br />
<br />
==== Connecting to an open access point ====<br />
<br />
The commands in this section show how to run {{ic|connmanctl}} in command mode.<br />
<br />
To scan the network {{ic|connmanctl}} accepts simple names called ''technologies''. To scan for nearby Wi-Fi networks:<br />
<br />
$ connmanctl scan wifi<br />
<br />
To list the available networks found after a scan run (example output): <br />
<br />
{{hc|$ connmanctl services|<br />
*AO MyNetwork wifi_dc85de828967_68756773616d_managed_psk<br />
OtherNET wifi_dc85de828967_38303944616e69656c73_managed_psk <br />
AnotherOne wifi_dc85de828967_3257495245363836_managed_wep<br />
FourthNetwork wifi_dc85de828967_4d7572706879_managed_wep<br />
AnOpenNetwork wifi_dc85de828967_4d6568657272696e_managed_none<br />
}}<br />
<br />
To connect to an open network, use the second field beginning with '''wifi_''':<br />
<br />
$ connmanctl connect wifi_dc85de828967_4d6568657272696e_managed_none<br />
<br />
You should now be connected to the network. Check using {{ic|ip addr}} or {{ic|connmanctl state}}.<br />
<br />
==== Connecting to a protected access point ====<br />
<br />
For protected access points you will need to provide some information to the ConnMan daemon, at the very least a password or a passphrase.<br />
<br />
The commands in this section show how to run {{ic|connmanctl}} in interactive mode, it is required for running the {{ic|agent}} command. To start interactive mode simply type: <br />
<br />
$ connmanctl<br />
<br />
You then proceed almost as above, first scan for any Wi-Fi ''technologies'':<br />
<br />
connmanctl> scan wifi<br />
<br />
To list services:<br />
<br />
connmanctl> services<br />
<br />
Now you need to register the agent to handle user requests. The command is:<br />
<br />
connmanctl> agent on<br />
<br />
You now need to connect to one of the protected services. To do this it is very handy to have a terminal that allows<br />
cut and paste. If you were connecting to OtherNET in the example above you would type:<br />
<br />
connmanctl> connect wifi_dc85de828967_38303944616e69656c73_managed_psk<br />
<br />
The agent will then ask you to provide any information the daemon needs to complete the connection. The <br />
information requested will vary depending on the type of network you are connecting to. The agent<br />
will also print additional data about the information it needs as shown in the example below.<br />
<br />
Agent RequestInput wifi_dc85de828967_38303944616e69656c73_managed_psk<br />
Passphrase = [ Type=psk, Requirement=mandatory ]<br />
Passphrase? <br />
<br />
Provide the information requested, in this example the passphrase, and then type:<br />
<br />
connmanctl> quit<br />
<br />
If the information you provided is correct you should now be connected to the protected access point.<br />
<br />
=== Settings ===<br />
<br />
Settings and profiles are automatically created for networks the user connects to often. They contain fields for the passphrase, essid and other information. Profile settings are stored in directories under {{ic|/var/lib/connman/}} by their service name. To view all network profiles run this command from [[Help:Reading#Regular_user_or_root|root shell]]: <br />
<br />
# cat /var/lib/connman/*/settings<br />
<br />
{{Note|VPN settings can be found in {{ic|/var/lib/connman-vpn/}}.}}<br />
<br />
=== Technologies ===<br />
<br />
Various hardware interfaces are referred to as ''Technologies'' by ConnMan.<br />
<br />
To list available ''technologies'' run: <br />
<br />
$ connmanctl technologies<br />
<br />
To get just the types by their name one can use this one liner:<br />
<br />
$ connmanctl technologies | awk '/Type/ { print $NF }'<br />
<br />
{{Note| The field {{ic|1=Type = tech_name}} provides the technology type used with {{ic|connmanctl}} commands}}<br />
<br />
To interact with them one must refer to the technology by type.<br />
''Technologies'' can be toggled on/off with: <br />
<br />
$ connmanctl enable ''technology_type''<br />
<br />
and:<br />
<br />
$ connmanctl disable ''technology_type''<br />
<br />
For example to toggle off wifi:<br />
<br />
$ connmanctl disable wifi<br />
<br />
{{Warning|connman grabs rfkill events. It is most likely impossible to use {{ic|rfkill}} or {{ic|bluetoothctl}} to (un)block devices, yet hardware keys may still work.[https://git.kernel.org/cgit/network/connman/connman.git/tree/doc/overview-api.txt#n406] Always use {{ic|<nowiki>connmanctl enable|disable</nowiki>}} }}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Avoid changing the hostname ===<br />
By default, ConnMan changes the [http://www.freedesktop.org/software/systemd/man/hostnamectl.html transient hostname] on a per network basis. This can create problems with X authority: If ConnMan changes your hostname to something else than the one used to generate the xauth magic cookie, then it will become impossible to create new windows. Symptoms are error messages like "No protocol specified" and "Can't open display: :0.0". Manually resetting the host name fixes this, but a permanent solution is to prevent ConnMan from changing your host name in the first place. This can be accomplished by adding the following to {{ic|/etc/connman/main.conf}}:<br />
<br />
[General]<br />
AllowHostnameUpdates=false<br />
<br />
Make sure to [[restart]] the {{ic|connman.service}} after changing this file.<br />
<br />
For testing purposes it is recommended to watch the [[systemd#Journal|journal]] and plug the network cable a few times to see the action.<br />
<br />
=== Prefer ethernet to wireless ===<br />
By default ConnMan does not prefer ethernet over wireless, which can lead to it deciding to stick with a slow wireless network even when ethernet is available. You can tell connman to prefer ethernet adding the following to {{ic|/etc/connman/main.conf}}:<br />
<br />
[General]<br />
PreferredTechnologies=ethernet,wifi<br />
<br />
=== Exclusive connection ===<br />
ConnMan allows you to be connected to both ethernet and wireless at the same time. This can be useful as it allows programs that established a connection over wifi to stay connected even after you connect to ethernet. But some peope prefer to have only a single unambiguous connection active at a time. That behavior can be activated by adding the following to {{ic|/etc/connman/main.conf}}:<br />
<br />
[General]<br />
SingleConnectedTechnology=true<br />
<br />
=== Connecting to eduroam ===<br />
<br />
See [[WPA2 Enterprise#connman]].<br />
<br />
=== Avoiding conflicts with local DNS server ===<br />
If you are running a local DNS server, it will likely have problems binding to port 53 (TCP and/or UDP) after installing Connman. This is because Connman includes its own DNS proxy which also tries to bind to those ports. If you see log messages from [[BIND]] or [[dnsmasq]] like <br />
"named[529]: could not listen on UDP socket: address in use"<br />
this could be the problem. To verify which application is listening on the ports, you can execute {{ic|ss -tulpn}} as root.<br />
<br />
To fix this connmand can be started with the options {{ic|-r}} or {{ic|--nodnsproxy}} by [[Systemd#Editing provided units|overriding]] the systemd service file. Create the folder {{ic|/etc/systemd/system/connman.service.d/}} and add the file {{ic|disable_dns_proxy.conf}}:<br />
<br />
[Service]<br />
ExecStart=<br />
ExecStart=/usr/bin/connmand -n --nodnsproxy<br />
<br />
Make sure to [[reload]] the systemd daemon and [[restart]] the {{ic|connman.service}}, and your DNS proxy, after adding this file.<br />
<br />
=== Blacklist interfaces ===<br />
If something like [[Docker]] is creating virtual interfaces Connman may attempt to connect to one of these instead of your physical adapter if the connection drops. A simple way of avoiding this is to blacklist the interfaces you do not want to use. Connman will by default blacklist interfaces starting with {{ic|vmnet}}, {{ic|vboxnet}}, {{ic|virbr}} and {{ic|ifb}}, so those need to be included in the new blacklist as well.<br />
<br />
Blacklisting interface names is also useful to avoid a race condition where connman may access <code>eth#</code> or <code>wlan#</code> before systemd/udev can change it to use a [[Network_configuration#Device_names|predictable interface name]] like <code>enp4s0</code>. Blacklisting the conventional (and unpredictable) interface prefixes makes connman wait until they are renamed.<br />
<br />
If it does not already exist, create {{ic|/etc/connman/main.conf}}:<br />
<br />
[General]<br />
NetworkInterfaceBlacklist=vmnet,vboxnet,virbr,ifb,docker,veth,eth,wlan<br />
<br />
Once {{ic|connman.service}} has been [[systemd#Using units|restarted]] this will also hide all the {{ic|veth#######}} interfaces from GUI tools like Econnman.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Error /net/connman/technology/wifi: Not supported ===<br />
<br />
You need to install {{Pkg|wpa_supplicant}} and then restart connman service: {{ic|systemctl restart connman.service}}.<br />
<br />
== See also ==<br />
<br />
* [https://git.kernel.org/cgit/network/connman/connman.git/tree/doc git repo documentation] - for further detailed documentation</div>Flechahttps://wiki.archlinux.org/index.php?title=Core_dump&diff=432913Core dump2016-04-26T18:54:48Z<p>Flecha: Warning about possible wrong file</p>
<hr />
<div>[[Category:Development]]<br />
[[Category:Security]]<br />
[[ja:コアダンプ]]<br />
A [[wikipedia:Core_dump|core dump]] is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps may be produced on-demand (such as by a [[#Making a core dump|debugger]]), or automatically upon termination. Core dumps are triggered by the kernel in response to program crashes, and may be passed to a helper program (such as [http://www.freedesktop.org/software/systemd/man/systemd-coredump.html systemd-coredump]) for further processing. Core dumps may be useful for developers to debug program crashes, however they are practically useless to the average user, and have been largely obsoleted by modern debuggers.<br />
<br />
== Disabling automatic core dumps ==<br />
Users may wish to disable automatic core dumps for a number of reasons:<br />
* Performance: generating core dumps for memory-heavy processes can waste system resources and delay the cleanup of memory.<br />
* Disk space: core dumps of memory-heavy processes may consume disk space equal to, if not greater, than the process's memory footprint if not compressed.<br />
* Security: core dumps, although typically readable only by root, may contain sensitive data (such as passwords or cryptographic keys), which are written to disk following a crash.<br />
<br />
=== Using systemd ===<br />
<br />
[[systemd]]'s default behavior is to generate core dumps for all processes in {{ic|/var/lib/systemd/coredump}}. This behavior can be overridden by creating a configuration snippet in the {{ic|/etc/systemd/coredump.conf.d/}} directory with the following content[http://www.freedesktop.org/software/systemd/man/coredump.conf.html#Description][https://bbs.archlinux.org/viewtopic.php?pid=1211433]:<br />
<br />
{{Accuracy|[[Systemd#Disabling_application_crash_dumps_journaling]] seems to point to another file: {{ic|/etc/systemd/coredump.conf}}}}<br />
<br />
{{hc|/etc/systemd/coredump.conf.d/custom.conf|<br />
2=[Coredump]<br />
Storage=none}}<br />
<br />
{{Note|Don't forget to include the {{ic|[Coredump]}} section name, otherwise this option will be ignored: {{ic|systemd-coredump[1728]: [/etc/systemd/coredump.conf.d/custom.conf:1] Assignment outside of section. Ignoring.}}}}<br />
<br />
Then reload systemd's configuration.<br />
# systemctl daemon-reload<br />
<br />
This method alone is usually sufficient to disable userspace core dumps, so long as no other programs enable automatic core dumps on the system.<br />
<br />
=== Using ulimit ===<br />
The maximum core dump size is enforced by ulimit. Setting it to zero disables core dumps entirely. [http://www.cyberciti.biz/faq/linux-disable-core-dumps/]<br />
{{hc|/etc/security/limits.conf|<br />
* hard core 0}}<br />
<br />
=== Using sysctl ===<br />
[[sysctl]] can be used to modify the {{ic|fs.suid_dumpable}} kernel parameter. This only applies to suid processes. [http://www.cyberciti.biz/faq/linux-disable-core-dumps/] <br />
{{hc|/etc/sysctl.conf|<br />
2=fs.suid_dumpable = 0}}<br />
<br />
== Making a core dump ==<br />
<br />
To generate a core dump of an arbitrary process, first [[install]] the {{Pkg|gdb}} package. Then find the PID of the running process, for example with ''pgrep'':<br />
<br />
{{hc|1=$ pgrep -f ''firefox''|2=<br />
2071 firefox<br />
}}<br />
<br />
Attach to the process:<br />
<br />
$ gdb -p 2071<br />
<br />
Then at the {{ic|(gdb)}} prompt:<br />
<br />
(gdb) generate-core-file<br />
Saved corefile core.2071<br />
(gdb) quit<br />
<br />
Now you have a coredump file called {{ic|core.2071}}.<br />
<br />
=== Where do they go? ===<br />
<br />
{{Accuracy|systemd modifies the {{ic|kernel.core_pattern}} kernel parameter at runtime, overriding that of {{ic|/usr/lib/sysctl.d/50-coredump.conf}}. See [[#Using systemd]] for a better solution.}}<br />
<br />
The {{ic|kernel.core_pattern}} [[sysctl]] decides where automatic core dumps go:<br />
<br />
$ cat /proc/sys/kernel/core_pattern <br />
|/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e<br />
<br />
The default set in {{ic|/usr/lib/sysctl.d/50-coredump.conf}} sends all core dumps to journald as part of the system logs.<br />
<br />
{{Note| If you do not have full-disk encryption, this means your program's memory will be written to raw disk! This is a potential information leak even if you have encrypted swap.}}<br />
<br />
To retrieve a core dump from the journal, see {{ic|man coredumpctl}}<br />
<br />
== Examining a core dump ==<br />
<br />
Use ''coredumpctl'' to find the corresponding dump:<br />
# coredumpctl list<br />
<br />
You need to uniquely identify the relevant dump. This is possible by specifying a {{ic|PID}}, name of the executable, path to the executable or a journalctl predicate (see {{ic|coredumpctl(1)}} and {{ic|journalctl(1)}} for details). To see details of the core dumps:<br />
# coredumpctl info ''match''<br />
<br />
Pay attention to "Signal" row, that helps to identify crash cause. For deeper analysis you can examine the backtrace using ''gdb'':<br />
# coredumpctl gdb ''match''<br />
<br />
When ''gdb'' is started, use the {{ic|bt}} command to print the backtrace:<br />
(gdb) bt<br />
<br />
== See also ==<br />
<br />
* [http://lcamtuf.coredump.cx/afl/ american fuzzy lop] - An tool for automated tests of the kernel and programs <br />
* [https://lwn.net/Articles/637151/ Filesystem fuzzing] - LWN article about testing filesystems for bugs</div>Flechahttps://wiki.archlinux.org/index.php?title=MegaFuse&diff=349469MegaFuse2014-12-10T21:23:38Z<p>Flecha: </p>
<hr />
<div>{{stub}}<br />
<br />
==Overview==<br />
<br />
Mount your MEGA cloud storage with fuse.<br />
<br />
== Installing ==<br />
<br />
Install {{AUR|megafuse}} (orphan at 10 dec. 2014) or {{AUR|megafuse-git}}, both in [[AUR]].<br />
<br />
== Configuration ==<br />
<br />
You can use either the system level or user level systemd service.<br />
<br />
# systemctl start megafuse@myusername<br />
<br />
or <br />
<br />
$ systemctl --user start megafuse<br />
<br />
Both look for ~/.config/MegaFuse/megafuse.conf, which should look a lot like /usr/share/MegaFuse/megafuse.conf.<br />
You will need an API key, as stated in the conf file.</div>Flechahttps://wiki.archlinux.org/index.php?title=MegaFuse&diff=349466MegaFuse2014-12-10T21:13:23Z<p>Flecha: Created page with "{{stub}} ==Overview== Mount your MEGA cloud storage with fuse. == Installing == Install {{AUR|megafuse}} (orphan at 10 dec. 2014) or {{AUR|megafuse-git}} from AUR. The..."</p>
<hr />
<div>{{stub}}<br />
<br />
==Overview==<br />
<br />
Mount your MEGA cloud storage with fuse.<br />
<br />
== Installing ==<br />
<br />
Install {{AUR|megafuse}} (orphan at 10 dec. 2014) or {{AUR|megafuse-git}} from [[AUR]].<br />
The used repository should be this one: https://github.com/matteoserva/MegaFuse<br />
<br />
== Configuration ==<br />
<br />
You can use either the system level or user level systemd service.<br />
<br />
# systemctl start megafuse@myusername<br />
<br />
or <br />
<br />
$ systemctl --user start megafuse<br />
<br />
Both look for ~/.config/MegaFuse/megafuse.conf, which should look a lot like /usr/share/MegaFuse/megafuse.conf.<br />
You will need an API key, as stated in the conf file.</div>Flechahttps://wiki.archlinux.org/index.php?title=Jumanji&diff=321258Jumanji2014-06-22T18:55:18Z<p>Flecha: New way of setting proxy parameter.</p>
<hr />
<div>[[Category:Web Browser]]<br />
[http://pwmt.org/projects/jumanji/ jumanji] is a web browser that provides a minimalistic and space saving interface as well as an easy usage that mainly focuses on keyboard interaction like ''vimperator'' does.<br />
<br />
== Installation ==<br />
<br />
[[pacman|Install]] one of ''jumanji'' variants from the [[AUR]]:<br />
* {{AUR|jumanji}} - Stable release.<br />
* {{AUR|jumanji-git}} - Development release.<br />
* {{AUR|jumanji-git-gtk2}} - Development release using old GTK+ 2 libraries.<br />
<br />
== Configuration ==<br />
<br />
=== config.h ===<br />
<br />
To modify config.h:<br />
* get jumanji-git PKGBUILD from AUR<br />
* {{ic|makepkg}}<br />
* {{ic|git --git-dir src/jumanji/ init}}<br />
* change src/jumanji/config.def.h<br />
* {{ic|makepkg -e}}<br />
<br />
=== rc file configuration ===<br />
<br />
jumanji allows for a lot of user configuration either by modifying the config.def.h file or through a rc file located at {{ic|~/.config/jumanji/jumanjirc}}. you can set searchengines, homepages, custom stylesheets, user scripts, proxy. Change the default download directory and much more. A sample configuration file below shows how to customize jumanji.<br />
# jumanji configuration<br />
# search engines<br />
searchengine ggl http://www.google.com/search?q=%s<br />
searchengine wiki http://en.wikipedia.org/w/index.php?search=%s<br />
# browser settings<br />
set homepage http://www.google.com/ig<br />
set auto_save 60<br />
set single_instance false<br />
# Use privoxy for adblocking<br />
set proxy localhost:8118 <br />
# look n feel<br />
set font monospace normal 9<br />
set stylesheet file:///home/inxs/.config/jumanji/style.css <br />
# follow hints<br />
script ~/.config/jumanji/scripts/hinting.js<br />
# downloads<br />
set download_dir ~/downloads/<br />
set download_command urxvt -e sh -c "wget --load-cookies ~/.config/jumanji/cookies '%s' -O '%s'";<br />
# keybindings<br />
map <C-,> nav_history previous<br />
map <C-.> nav_history next<br />
bmap ^DD$ quit<br />
<br />
{{Note| Latest version seems to use "proxy localhost:8118" instead of "''set'' proxy localhost:8118".}}<br />
<br />
== Commands ==<br />
<br />
Below are some basic commands that can be used with jumanji <br />
<br />
=== Look and feel ===<br />
<br />
C-m = Toggle status bar<br />
C-n = Toggle tab bar<br />
<br />
=== Page navigation ===<br />
<br />
o = enter url to open in same tab<br />
t = enter url to open in new tab<br />
j = scroll down<br />
k = scroll up<br />
h = scroll left<br />
l = scroll right<br />
C-d = scroll down (half the screen)<br />
C-u = scroll up (half the screen)<br />
space = page down<br />
gg = beginning<br />
G = end<br />
C-o = back<br />
C-i = forward<br />
:stop = stop<br />
r = reload<br />
<br />
=== Zooming ===<br />
<br />
zI = zoom_in<br />
zO = zoom_out<br />
z0 = zoom to original size<br />
<br />
=== Searching ===<br />
<br />
/ = search %s<br />
? = search reverse %s<br />
:open = start a search with your search engine %s (the first one in your jumanjirc is used)<br />
<br />
=== Bookmarks and history ===<br />
<br />
:bmark = insert bookmark (bookmarks are saved in ~/.config/jumanji/bookmarks)<br />
o <tab> = show bookmarks and history to open in same tab<br />
t <tab> = show bookmarks and history to open in new tab<br />
<br />
=== Link following ===<br />
<br />
f = spawn numbers next to each hyperlink. Type the number after typing f to follow the link in the same tab [http://www.pwmt.org/jumanji/faq/]<br />
F = spawn numbers next to each hyperlink. Type the number after typing F to follow the link in a new tab<br />
gh = Go to homepage in the same tab<br />
gH = open homepage in a new tab<br />
gf, C-s = view source<br />
gF = view source in a new tab<br />
<br />
=== Tabs ===<br />
<br />
gt or C-Tab or S-k = go to next tab<br />
gT or C-S-Tab or S-j = go to previous tab<br />
xgt = go to tab number x, where x is any number 0-9<br />
C-w = close tab<br />
<br />
=== Exit ===<br />
<br />
ZZ = exit<br />
C-q = exit<br />
<br />
== See also ==<br />
<br />
* [https://bbs.archlinux.org/viewtopic.php?id=100505 Old, closed forum thread]<br />
* [https://bbs.archlinux.org/viewtopic.php?id=115119 The current forum thread]</div>Flechahttps://wiki.archlinux.org/index.php?title=Pm-utils&diff=319205Pm-utils2014-06-11T13:32:33Z<p>Flecha: </p>
<hr />
<div>{{DISPLAYTITLE:pm-utils}}<br />
[[Category:Power management]]<br />
[[it:Pm-utils]]<br />
[[ru:Pm-utils]]<br />
[[zh-CN:Pm-utils]]<br />
{{Related articles start}}<br />
{{Related|Uswsusp}}<br />
{{Related|TuxOnIce}}<br />
{{Related articles end}}<br />
{{Out of date| Need to address pm-utils relevance compared to systemd's suspend functions}}<br />
{{Warning|1=Hibernating with Pm-utils and than updating systemd is reported to corrupt files:<br />
https://bbs.archlinux.org/viewtopic.php?pid=1423442}}<br />
'''pm-utils''' is a suspend and powerstate setting framework. It is designed to replace such scripts as those provided by the {{ic|powersave}} package.<br />
<br />
pm-utils is a collection of shell scripts that wrap the kernel mode suspend/resume with the various hacks. These hacks are needed to work around bugs in drivers and subsystems that are not yet aware of suspend. It is easily extensible by putting custom hooks into a directory, which can either be done by the system administrator or those hooks can be part of a package, especially if this package needs special attention during a system suspend or power state transition.<br />
<br />
A lesser known feature is one that mimics toggling done by [[Laptop Mode Tools]].<br />
<br />
Used in conjunction with the [[cpupower]] package, notebook (and desktop) owners are provided with a complete power management suite.<br />
<br />
== Installation ==<br />
<br />
[[pacman|Install]] the {{Pkg|pm-utils}} package which is available in the [[official repositories]].<br />
<br />
{{Note|<br />
* If you run into issues when resuming video, it might be necessary to also install {{Pkg|vbetool}} from the [[official repositories]].<br />
* If you are starting from a clean install, make sure that you have {{Pkg|acpi}} installed.<br />
}}<br />
<br />
Run {{ic|pm-suspend}}, {{ic|pm-suspend-hybrid}} or {{ic|pm-hibernate}} as root to trigger suspend manually. The suspend scripts write log to {{ic|/var/log/pm-suspend.log}}.<br />
<br />
=== Installing alternative suspend backend (optional) ===<br />
<br />
The Arch Linux package ships with support for the following backends: {{ic|kernel}}, {{ic|tuxonice}} and {{ic|uswsusp}} which can be seen from command:<br />
pacman -Ql pm-utils | grep module.d<br />
<br />
Suspend backend is specified by the {{ic|SLEEP_MODULE}} configuration variable in {{ic|/etc/pm/config.d}} and defaults to the {{ic|kernel}} backend. To use the alternative suspend backends the respective packages need to be installed. Both of these are available in the [[Arch User Repository]]:<br />
* uswsusp - {{AUR|uswsusp-git}}<br />
* tuxonice - {{AUR|linux-ice}} / [[linux-pf]]<br />
<br />
Furthermore, {{Pkg|pm-utils}} ships with its own video quirks database in {{ic|/usr/lib/pm-utils/video-quirks/}}.<br />
<br />
== Basic configuration ==<br />
<br />
=== Standby/suspend to RAM ===<br />
<br />
In the ideal case, running {{ic|pm-suspend}} as root should initiate suspend to memory, meaning that all running state will be preserved in RAM and all components other than RAM will be shut down to conserve power. Pressing the power button should initiate a resume from this state.<br />
<br />
{{Note|It is always recommended to put your network drivers in SUSPENDED_MODULES because most wireless drivers are known to cause issues after standby. Intel's iwlwifi, Atheros' ath5k and Realtek's r8* drivers were all reported to have issues after resume on the forums. Iwlwifi even drops to 1Mbps connection if it is not reloaded after resume.}} <br />
<br />
In some cases, it is possible that running {{ic|pm-suspend}} causes hangs or other issues. This may be due to specific "misbehaving" modules. If you know which modules could cause such issues, adding a {{ic|SUSPEND_MODULES}} config to {{ic|/etc/pm/config.d/modules}} of the form:<br />
SUSPEND_MODULES="uhci_hd button ehci_hd iwlwifi"<br />
should cause these modules to be specifically unloaded before suspend and reloaded after resume.<br />
<br />
To configure invoking {{ic|pm-suspend}} automatically on power events like laptop lid close, please refer to [[Acpid]].<br />
<br />
=== Hibernation (suspend2disk) ===<br />
<br />
You need to follow instructions in [[Suspend and Hibernate#Hibernation]] in order to set up hibernation.<br />
<br />
Alternatively, if you do not use the {{ic|kernel}} backend, see [[Uswsusp#Configuration]] or [[TuxOnIce#Setting up the bootloader]].<br />
<br />
=== Suspend/hibernate as regular user ===<br />
<br />
Three methods are available to suspend without the need for a root password: using [[Udev]], using UPower, and giving the user the appropriate permissions with [[sudo|visudo]].<br />
<br />
==== UPower method ====<br />
<br />
{{Out of date|1=Since February 2013, the suspend and hibernate functions in UPower have been [http://cgit.freedesktop.org/upower/commit/?id=372c2f8d2922add987683a24b5d69902e05e2f97 deprecated]. As a consequence PM-Utils is no longer a dependency, either. The methods provided below will no longer work.}}<br />
<br />
Install {{Pkg|upower}}. To suspend to RAM:<br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend<br />
<br />
To suspend to disk (hibernate):<br />
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate<br />
<br />
==== User permission method ====<br />
<br />
Because the {{Pkg|pm-utils}} scripts must be run as root, you may want to make the scripts accessible to normal users by running sudo without the root password. To do so, edit the {{ic|/etc/sudoers}} file with {{ic|visudo}} as root. For more information, see [[sudo]].<br />
<br />
Add the following lines, replacing {{ic|''username''}} with your own user name, then save and exit {{ic|visudo}}:<br />
''username'' ALL = NOPASSWD: /usr/sbin/pm-hibernate<br />
''username'' ALL = NOPASSWD: /usr/sbin/pm-suspend<br />
<br />
Or you can enable it for a group, using the following lines, replacing {{ic|''group''}}:<br />
%''group'' ALL = NOPASSWD: /usr/sbin/pm-hibernate<br />
%''group'' ALL = NOPASSWD: /usr/sbin/pm-suspend<br />
<br />
{{Note|These must come after any user privilege specifications, e.g., {{ic|1=username ALL=(ALL) ALL}}, or they will not work.}}<br />
<br />
You can now run the scripts without a password by simply running:<br />
$ sudo pm-hibernate<br />
<br />
or:<br />
<br />
$ sudo pm-suspend<br />
<br />
Also, add yourself to the {{ic|power}} [[Users and groups|group]] so that way using things like applets to do suspend will work. If you do not do this, when you try to use suspend though things like [[GNOME]]'s shutdown applet, your computer will just play a very annoying loud triple beep and lock the screen.<br />
# gpasswd -a ''username'' power<br />
<br />
You should now be able to use your [[Desktop environment]]'s power management tools to automatically suspend or hibernate when doing things like closing the laptop lid, running low on battery power, etc.<br />
<br />
=== Power saving ===<br />
<br />
pm-utils supports running commands depending on whether the system is connected to the AC adapter or not; therefore, a script has to be created inside the folder {{ic|/etc/pm/power.d/}}. An example of such a script can be found in the [http://crunchbanglinux.org/forums/post/110148/#p110148 crunchbang forum]. Be aware that upower must be running in order to detect changing AC states [https://bbs.archlinux.org/viewtopic.php?id=132125 (see more information)].<br />
<br />
==== Change brightness depending on AC state ====<br />
<br />
One possible example looks as follows and changes brightness according to the AC state. Create a file called {{ic|/etc/pm/power.d/00-brightness}} with the following content and change the path to the brightness setting as well as the value written into the file with echo according to your system.<br />
<br />
{{bc|<br />
#!/bin/bash<br />
<br />
case $1 in<br />
true)<br />
echo "Enable screen power saving"<br />
echo 5 > /sys/class/backlight/acpi_video0/device/backlight/acpi_video0/brightness<br />
;;<br />
false)<br />
echo "Disable screen power saving"<br />
echo 14 > /sys/class/backlight/acpi_video0/device/backlight/acpi_video0/brightness<br />
;;<br />
esac<br />
}}<br />
<br />
=== Suspend on idle/inactivity ===<br />
<br />
One method relies on xautolock program. Add following: {{ic|xautolock -time 30 -locker "sudo pm-suspend" -detectsleep &}} to {{ic|~/.xinitrc}}. This implies that {{ic|pm-suspend}} is called after 30 minutes of inactivity.<br />
<br />
=== Using Swap file instead of regular swap partition ===<br />
<br />
If you want use swap file instead of regular swap partition, see [[Swap#Swap file|Swap File]].<br />
<br />
== Advanced configuration ==<br />
<br />
The main configuration file is {{ic|/usr/lib/pm-utils/defaults}}. You ''should not edit this file'', since after a package update it might be overwritten with the default settings. Put your config file into {{ic|/etc/pm/config.d/}} instead.<br />
You can just put a simple text file with<br />
SUSPEND_MODULES="button uhci_hcd"<br />
named {{ic|modules}} or {{ic|config}} into {{ic|/etc/pm/config.d}} and it will override the settings in the system-wide configuration file.<br />
<br />
=== Available variables for use in config files ===<br />
<br />
; SUSPEND_MODULES="button": the list of modules to be unloaded before suspend<br />
; SLEEP_MODULE="tuxonice uswsusp kernel": the default sleep/wake systems to try<br />
; HIBERNATE_MODE="shutdown": forces the system to shut down rather than reboot<br />
<br />
=== Disabling a hook ===<br />
<br />
If a hook is run which you do not like or which you think is not useful or even harmful, we would appreciate a bug report for that.<br />
You can however easily disable hooks by just creating an empty file corresponding to the hook in {{ic|/etc/pm/sleep.d/}}. Say you want to disable the hook {{ic|/usr/lib/pm-utils/sleep.d/45pcmcia}}, you can do this easily by calling<br />
# touch /etc/pm/sleep.d/45pcmcia<br />
Do not set the executable bit on that dummy-hook.<br />
<br />
Note: Make sure you create the dummy files in the appropriate directory. For example if you are trying to disable hooks in /usr/lib/pm-utils/power.d, you will need to place the dummy file in /etc/pm/power.d.<br />
<br />
==== Alternative method ====<br />
<br />
Create a file in {{ic|/etc/pm/config.d}} with the modules you want to blacklist in the {{ic|HOOK_BLACKLIST}} variable.<br />
For example, to manage power saving yourself, use:<br />
HOOK_BLACKLIST="hal-cd-polling intel-audio-powersave journal-commit laptop-mode pcie_aspm readahead sata_alpm sched-powersave xfs_buffer wireless"<br />
<br />
=== Creating your own hooks ===<br />
<br />
{{Note|If you are using systemd, then these hooks located in sleep.d will probably not work. In these cases you want to consider using [[Systemd#Sleep_hooks|sleep hooks]] of systemd.}}<br />
If you want to do something specific to your setup during suspend or hibernate, then you can easily put your own hook into {{ic|/etc/pm/sleep.d}}. The hooks in this directory will be called in alphabetic order during suspend (that is the reason their names all start with 2 digits, to make the ordering explicit) and in the reverse order during resume. The general convention to be followed on number ordering is:.<br />
;00 - 49: User and most package supplied hooks. If a hook assumes that all of the usual services and userspace infrastructure is still running, it should be here.<br />
;50 - 74: Service handling hooks. Hooks that start or stop a service belong in this range. At or before 50, hooks can assume that all services are still enabled.<br />
;75 - 89: Module and non-core hardware handling. If a hook needs to load/unload a module, or if it needs to place non-video hardware that would otherwise break suspend or hibernate into a safe state, it belongs in this range. At or before 75, hooks can assume all modules are still loaded.<br />
;90 - 99: Reserved for critical suspend hooks.<br />
<br />
I am showing a pretty useless demonstration hook here, that will just put some informative lines into your log file:<br />
<br />
#!/bin/bash<br />
case $1 in<br />
hibernate)<br />
echo "Hey guy, we are going to suspend to disk!"<br />
;;<br />
suspend)<br />
echo "Oh, this time we are doing a suspend to RAM. Cool!"<br />
;;<br />
thaw)<br />
echo "Oh, suspend to disk is over, we are resuming..."<br />
;;<br />
resume)<br />
echo "Hey, the suspend to RAM seems to be over..."<br />
;;<br />
*) echo "Somebody is calling me totally wrong."<br />
;;<br />
esac<br />
<br />
Put this into {{ic|/etc/pm/sleep.d/66dummy}}, do a {{ic|chmod +x /etc/pm/sleep.d/66dummy}} and it will spew some useless lines during suspend and resume.<br />
<br />
{{Warning|All the hooks run as root. This means that you need to be careful when creating temporary files, check that the {{ic|PATH}} environment variable is set correctly, etc. to avoid security problems.}}<br />
<br />
== How it works ==<br />
<br />
The concept is quite easy: the main script ({{ic|pm-action}}, called via symlinks as either {{ic|pm-suspend}}, {{ic|pm-hibernate}} or {{ic|pm-suspend-hybrid}}) executes so-called "hooks", executable scripts, in the alphabetical sorted order with the parameter {{ic|suspend}} (suspend to RAM) or {{ic|hibernate}} (suspend to disk).<br />
Once all hooks are done, it puts the machine to sleep. After the machine has woken up again, all those hooks are executed in reverse order with the parameter {{ic|resume}} (resume from RAM) or {{ic|thaw}} (resume from disk).<br />
The hooks perform various tasks, such as preparing the bootloader, stopping the Bluetooth subsystem, or unloading of critical modules.<br />
<br />
Both {{ic|pm-suspend}} and {{ic|pm-hibernate}} are usually called from [[Udev]], initiated by desktop applets like {{Pkg|gnome-power-manager}} or {{ic|kpowersave}}.<br />
<br />
{{Note|{{ic|suspend-hybrid}} is a placeholder right now -- it is not completely implemented.}}<br />
<br />
There is also the possibility to set the machine into high-power and low-power mode, the command {{ic|pm-powersave}} is used with an additional parameter of {{ic|true}} or {{ic|false}}. It works basically the same as the suspend framework.<br />
<br />
The hooks for suspend are placed in<br />
;{{ic|/usr/lib/pm-utils/sleep.d}}: distribution / package provided hooks<br />
;{{ic|/etc/pm/sleep.d}}: hooks added by the system administrator<br />
<br />
The hooks for the power state are placed in <br />
;{{ic|/usr/lib/pm-utils/power.d}}: distribution / package provided hooks<br />
;{{ic|/etc/pm/power.d}}: hooks added by the system administrator<br />
<br />
Hooks in {{ic|/etc/pm/}} take precedence over those in {{ic|/usr/lib/pm-utils/}}, so the system administrator can override the defaults provided by the distribution.<br />
<br />
=== Pm-suspend internals ===<br />
<br />
This outlines the internal actions when {{ic|pm-suspend}} is run, describing how {{ic|pm-utils}} gracefully falls back onto the kernel method if the requirements of other methods are not met.<br />
<br />
$ pm-suspend<br />
<br />
The first step is set-up preliminary variables and source parent scripts:<br />
export STASHNAME=pm-suspend<br />
export METHOD="$(echo ${0##*pm-} |tr - _)"<br />
. "/usr/lib/pm-utils/pm-functions"<br />
<br />
The variable {{Ic|METHOD}} is extracted from the executable name, ''suspend'' from {{ic|pm-suspend}} and ''hibernate'' from {{ic|pm-hibernate}}.<br />
<br />
The location of runtime configuration parameters is defined in {{ic|/usr/lib/pm-utils/pm-functions}} as ''PM_UTILS_RUNDIR="/var/run/pm-utils"'' and ''STORAGEDIR="${PM_UTILS_RUNDIR}/${STASHNAME}/storage"''. Therefore ''STORAGEDIR="/var/run/pm-utils/pm-suspend/storage"''; this is where {{ic|pm-suspend}} will cache its configuration. Disabled hooks are stored as plain text files with the hook name prefixed by "''disable_hook:''". Configuration parameters are appended to the ''parameters'' file:<br />
{{hc|$ ls -lah /var/run/pm-utils/pm-suspend/storage/|<br />
-rw-r--r-- 1 root root 20 May 19 09:57 disable_hook:99video<br />
-rw-r--r-- 1 root root 0 May 19 02:59 parameters<br />
-rw-r--r-- 1 root root 247 May 19 02:59 parameters.rm<br />
-rw-r--r-- 1 root root 9 May 19 02:59 state:cpu0_governor<br />
-rw-r--r-- 1 root root 9 May 19 02:59 state:cpu1_governor<br />
}}<br />
<br />
Then {{Ic|pm-functions}} will source the files located in {{Ic|/etc/pm/config.d/}} in addition to {{ic|/usr/lib/pm-utils/defaults}}. Upon returning, {{Ic|pm-functions}} will proceed to source the files specified by '''$SLEEP_METHOD''' as {{Ic|/usr/lib/pm-utils/module.d/$SLEEP_METHOD[...]}} if they exist:<br />
for mod in $SLEEP_MODULE; do<br />
mod="${PM_UTILS_LIBDIR}/module.d/${mod}"<br />
[ -f "$mod" ] || continue<br />
. "$mod"<br />
done<br />
<br />
Otherwise, if '''$SLEEP_MODULE''' is empty, {{ic|do_suspend()}} will be set to the kernel backend as described above:<br />
if [ -z "$SUSPEND_MODULE" ]; then<br />
if grep -q mem /sys/power/state; then<br />
SUSPEND_MODULE="kernel"<br />
do_suspend() { echo -n "mem" >/sys/power/state; }<br />
elif [ -c /dev/pmu ] && pm-pmu --check; then<br />
SUSPEND_MODULE="kernel"<br />
do_suspend() { pm-pmu --suspend; }<br />
elif grep -q standby /sys/power/state; then<br />
SUSPEND_MODULE="kernel"<br />
do_suspend() { echo -n "standby" >/sys/power/state; }<br />
fi<br />
fi<br />
<br />
Assuming '''$SLEEP_MODULE''' is not empty and {{Ic|uswsusp}} is specified, {{Ic|/usr/lib/pm-utils/module.d/uswsusp}} is executed. This script checks several requirements (these are the requirements for being able to use uswsusp):<br />
* [ -z $SUSPEND_MODULE ]<br />
* command_exists s2ram<br />
* grep -q mem /sys/power/state || ( [ -c /dev/pmu ] && pm-pmu --check; );<br />
If these requirements are met, do_suspend() is defined as:<br />
do_suspend()<br />
{<br />
uswsusp_get_quirks<br />
s2ram --force $OPTS<br />
}<br />
Most importantly, the {{Ic|uswsusp}} module runs:<br />
add_before_hooks uswsusp_hooks<br />
add_module_help uswsusp_help<br />
The first function, ''add_before_hook'' disables the '''pm-utils''' hooks '''99video''' since this functionality is subsumed by '''s2ram'''.<br />
The second function, ''add_module_help'', adds uswsusp-module-specific help, which in essence replaces the help function provided by '''99video'''.<br />
<br />
Back to {{Ic|pm-suspend}}:<br />
command_exists "check_$METHOD" && command_exists "do_$METHOD"<br />
"check_$METHOD"<br />
This verifies that the ''check_suspend'' and ''do_suspend'' methods have been defined. The ''check_suspend'' method simply verifies that $SUSPEND_MODULE is not empty:<br />
<br />
check_suspend() { [ -n "$SUSPEND_MODULE" ]; }<br />
<br />
Lastly, {{Ic|pm-suspend}} must run all hooks that have not been disabled, sync file-system buffers, and run ''do_suspend'':<br />
if run_hooks sleep "$ACTION $METHOD"; then<br />
# Sleep only if we know how and if a hook did not inhibit us.<br />
log "$(date): performing $METHOD"<br />
sync<br />
"do_$METHOD" || r=128<br />
log "$(date): Awake."<br />
<br />
The method ''run_hooks'' is a wrapper for ''_run_hooks'', which the case of {{ic|pm-suspend}} is called as ''run_hooks sleep "suspend suspend"''. Given that:<br />
PARAMETERS="${STORAGEDIR}/parameters"<br />
PM_UTILS_LIBDIR="/usr/lib/pm-utils"<br />
PM_UTILS_ETCDIR="/etc/pm"<br />
<br />
The method ''_run_hooks'', will for each hook in ''"${PM_UTILS_LIBDIR}/$1.d"'' and ''"${PM_UTILS_ETCDIR}/$1.d"'', check that sleep has not been inhibited and update the runtime parameters stored in ''$PARAMETERS'' before running each hook via ''run_hook $hook $2''. In the case of Suspend-to-RAM, all the hooks in ''{/usr/lib/pm-utils/sleep.d/,/etc/pm/sleep.d/}'' will be enumerated, and ''run_hook'' will be passed the parameters ''$hook'' and "''suspend suspend''". The method ''run_hook'' uses the ''hook_ok'' function to verify that the hook has not been disabled before executing the hook with the "''suspend suspend''" parameters.<br />
<br />
== Troubleshooting ==<br />
<br />
If suspend or hibernate did not work correctly, you will probably find some information in the log file {{ic|/var/log/pm-suspend.log}}. For example, which hooks were run and what the output of them was should be in that log file.<br />
<br />
Also, check the output of the {{ic|pm-is-supported}} command. This command (with the {{ic|--hibernate}} or {{ic|--suspend}} flag) will do some sanity checking and report any errors it finds in your configuration. It will not detect all possible errors, but may still be useful.<br />
<br />
=== Segmentation faults ===<br />
<br />
If you experience segmentation faults that might result in an unresponsive system and missing keys then try to set the UUID in the resume-path in {{ic|/boot/grub/menu.lst}} as explained [[#Hibernation (suspend2disk)|above]].<br />
<br />
=== Reboot instead of resume from suspend ===<br />
<br />
This problem started when saving NVS area during suspend was introduced (in 2.6.35-rc4) ([http://www.spinics.net/lists/linux-acpi/msg29521.html mailing list post]). However, it is known that this mechanism does not work on all machines, so the kernel developers allow the user to disable it with the help of the {{ic|1=acpi_sleep=nonvs}} kernel command line option. This option could be pass to the kernel through [[GRUB]] options by editing the file {{ic|/boot/grub/menu.lst}} (GRUB 0.97) on the {{ic|kernel}} line.<br />
<br />
=== Resume from suspend shuts down instead of wake up ===<br />
<br />
On an Acer Aspire AS3810TG, resuming from suspend shuts down the computer instead of waking it up. If you experience a similar issue, try passing the parameter {{ic|1=i8042.reset=1}} to your kernel. In [[GRUB]], the line in {{ic|/boot/grub/grub.cfg}} should be something like this:<br />
linux /vmlinuz-linux root=/dev/vg00/root resume=/dev/vg00/swap i8042.reset=1 ro<br />
<br />
Although I have not tested this, you could also set this parameter live without having to restart by doing:<br />
# sysctl -e -w i8042.reset=1<br />
<br />
=== Blank screen when waking from suspend ===<br />
<br />
Some laptops (e.g. Dell Inspiron Mini 1018) will just show a black screen with no backlight after resuming from suspend. If this happens to you, try going into the BIOS of the laptop and disabling Intel SpeedStep if it is present.<br />
<br />
You could also try, without disabling SpeedStep, creating a quirk in {{ic|/etc/pm/sleep.d/}} with this content (requires {{Pkg|vbetool}}):<br />
{{bc|<br />
#!/bin/sh<br />
#<br />
case "$1" in<br />
suspend)<br />
;;<br />
resume)<br />
sleep 5<br />
vbetool dpms off<br />
vbetool dpms on<br />
;;<br />
*) exit $NA<br />
;;<br />
esac<br />
}}<br />
save it as you want but with a {{ic|00}} in front of the name so this is called last when resuming; remember to {{ic|chmod +x}} the script.<br />
Try adjusting the {{ic|sleep}} time if the other commands are called too soon, or if it works well, you can also try removing that line.<br />
<br />
Some other laptops (e.g. Toshiba Portégé R830) will just show a black screen with no backlight after resuming from suspend, with fans blowing at top speed. If this is what you're seeing, try going into the BIOS and disable the VT-d virtualization setting by switching to "VT-x only".<br />
<br />
=== VirtualBox problems ===<br />
<br />
The VirtualBox kernel modules cause {{ic|pm-suspend}} and {{ic|pm-hibernate}} to fail on some laptops. (See [https://bbs.archlinux.org/viewtopic.php?id=123354 this discussion]). Instead of suspending or hibernating, the system freezes and indicator LEDs blink (the suspend indicator in the case of ThinkPads and the Caps Lock and Scroll Lock indicators in the case of the MSI Wind U100). The {{ic|pm-suspend}} and {{ic|pm-hibernate}} logs appear normal.<br />
<br />
The problem can be fixed by removing the modules before suspension or hibernation and reloading them afterwards. That can be accomplished through a script:<br />
{{bc|1=<br />
#!/bin/sh<br />
<br />
rmmod vboxdrv<br />
pm-hibernate<br />
modprobe vboxdrv<br />
}}<br />
<br />
{{Note|Some users reported that it is sufficient to rebuild the kernel module by running {{ic|vboxbuild}} as root.}}<br />
<br />
=== Hibernate with missing swap partition ===<br />
<br />
If you try to hibernate without an active swap partition, your system will look like it is going into hibernate, and then immediately resume again. There are no error messages warning you that there is no swap partition, even when verbose logging is activated, so this problem can be very hard to debug. On my system, the swap partition was somehow corrupted and deactivated, so this may happen even if you set up a swap partition during install. If hibernate displays this behaviour, make sure that you actually have a swap partition that is being used as such. The output of the {{ic|blkid}} command should look e.g. like<br />
{{hc|# blkid|2=<br />
/dev/sda1: UUID="00000-000-000-0000000" TYPE="ext2" <br />
/dev/sda2: UUID="00000-000-000-0000000" TYPE="ext4"<br />
/dev/sda3: UUID="00000-000-000-0000000" TYPE="ext4"<br />
/dev/sda4: UUID="00000-000-000-0000000" TYPE="swap"<br />
}}<br />
with one of the lines having {{ic|"swap"}} as the type. If this is not the case, consult [[Swap#Swap partition]] for instructions on re-creating/activating the swap partition.<br />
<br />
=== Black screen with unblinking cursor when trying to suspend ===<br />
<br />
If you get a black screen with unblinking cursor when trying to do<br />
$ sudo pm-suspend<br />
have a look at {{ic|/var/log/pm-suspend.log}} and search for "ehci" or "xhci". Some of the names you could find may be "ehci_hd", "xhci_hd" or "ehci_hcd".<br />
<br />
Then as root create the file {{ic|/etc/pm/config.d/modules}} and include this code with the exact name of the ehci or xhci module you found. For example:<br />
SUSPEND_MODULES="ehci_hcd"<br />
Suspend should now be working.<br />
<br />
=== Blank screen issue ===<br />
<br />
Some users have reported having issues with their laptops not resuming after a suspend or hibernate. This is due to the {{ic|autodetect}} hook in "HOOKS" array of the {{ic|/etc/mkinitcpio.conf}} file. This can be disabled using the same method for adding the {{ic|resume}} hook. Just remove {{ic|autodetect}} from the list and follow the steps to build the new image. See [[Pm-utils#Mkinitcpio_Resume_Hook|Resume Hook]] for more details on building the new image.<br />
<br />
{{Note|If you are using [[Plymouth|plymouth]] it may be an other reason to this issue. Adding {{ic|resume}} before {{ic|plymouth}} in "HOOKS" array of the {{ic|/etc/mkinitcpio.conf}} file should fix this.}}<br />
<br />
=== Unable to resume with 64 bit OS ===<br />
<br />
Certain motherboards/BIOS combinations (specifically known are some Zotac ITX boards, perhaps others) will not resume properly from suspend if any 64 bit operating system is installed. The solution is the enter your BIOS setup and Disable the "Memory Remapping Hole" in your DRAM configuration page. This will probably fix the suspend to RAM problem but will probably result in your OS not detecting all of your RAM. <br />
<br />
== Tips and tricks ==<br />
<br />
=== Having the HD power management level automatically set again on resume ===<br />
<br />
Do it like this:<br />
{{hc|/etc/pm/sleep.d/50-hdparm_pm|<nowiki><br />
#!/bin/dash<br />
<br />
if [ -n "$1" ] && ([ "$1" = "resume" ] || [ "$1" = "thaw" ]); then<br />
hdparm -B 254 /dev/sda > /dev/null<br />
fi<br />
</nowiki>}}<br />
<br />
Then run:<br />
# chmod +x /etc/pm/sleep.d/50-hdparm_pm<br />
<br />
If the above [[Bash]] script fails the work, the following may work instead:<br />
{{hc|/etc/pm/sleep.d/50-hdparm_pm|<nowiki><br />
#!/bin/sh<br />
<br />
. "${PM_FUNCTIONS}"<br />
case "$1" in<br />
thaw|resume)<br />
sleep 6<br />
hdparm -B 254 /dev/sda<br />
;;<br />
*)<br />
;;<br />
esac<br />
exit $NA<br />
</nowiki>}}<br />
<br />
Lower {{ic|-B}} switch values may be effective. See [[hdparm]].<br />
<br />
=== Restarting the mouse ===<br />
<br />
On some laptops the mouse will hang after an otherwise successful suspend. One way to remedy this is to force a re-initialization of the PS/2 driver (here {{ic|i8042}}) through a hook in {{ic|/etc/pm/hooks}} (see [[#Creating_your_own_hooks|hooks]])<br />
<br />
#!/bin/sh<br />
echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind<br />
echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind<br />
<br />
=== Add sleep modes to Openbox menu ===<br />
<br />
Openbox users can add the new scripts as additional shutdown options within the Openbox menu by adding the items to a new or existing sub-menu in {{ic|~/.config/openbox/menu.xml}}, for example:<br />
<menu id="64" label="Shutdown"><br />
<item label="Lock"> <action name="Execute"> <execute>xscreensaver-command -lock</execute> </action> </item><br />
<item label="Logout"> <action name="Exit"/> </item><br />
<item label="Reboot"> <action name="Execute"> <execute>sudo shutdown -r now</execute> </action> </item><br />
<item label="Poweroff"> <action name="Execute"> <execute>sudo shutdown -h now </execute> </action> </item><br />
'''<item label="Hibernate"> <action name="Execute"> <execute>sudo pm-hibernate</execute> </action> </item>'''<br />
'''<item label="Suspend"> <action name="Execute"> <execute>sudo pm-suspend</execute> </action> </item>'''<br />
</menu><br />
<br />
=== Handling "sleep" and "power" buttons ===<br />
<br />
"Sleep" and "power" buttons are handled by {{ic|acpid}} in {{ic|/etc/acpi/handler.sh}} (see "button/power" and "power/sleep" entries). You may want to substitute the default actions with calls to {{ic|pm-suspend}} and {{ic|pm-hibernate}}.<br />
<br />
Please note that [[Systemd#ACPI_power_management|systemd]] handles power events on its own and does not use pm-utils or any scripts from {{ic|/etc/pm/*}}.<br />
<br />
=== Locking the screen saver on hibernate or suspend ===<br />
<br />
You may wish to run a screen locking utility when the system suspends (so that a password is required after waking up). This can be done by adding a script to the {{ic|/etc/pm/sleep.d}} folder. Make sure the script is executable (chmod 755) and owned by {{ic|root:root}}.<br />
<br />
A simple example script is:<br />
<br />
{{hc|/etc/pm/sleep.d/00screensaver-lock|<nowiki><br />
#!/bin/sh<br />
#<br />
# 00screensaver-lock: lock workstation on hibernate or suspend<br />
<br />
username= # add username here; i.e.: username=foobar<br />
userhome=/home/$username<br />
export XAUTHORITY="$userhome/.Xauthority"<br />
export DISPLAY=":0"<br />
<br />
case "$1" in<br />
hibernate|suspend)<br />
su $username -c "/usr/bin/slimlock" & # or any other such as /usr/bin/xscreensaver-command -lock<br />
;;<br />
thaw|resume)<br />
;;<br />
*) exit $NA<br />
;;<br />
esac</nowiki>}}<br />
<br />
Replace {{ic|/usr/bin/slimlock}} with the path to your screen locking utility of choice.<br />
<br />
If you do not wish to hard-code your username (e.g., if you have multiple users), then it is necessary to determine the current X11 username and display number. For systems using [[systemd]], you can use [https://github.com/rephorm/xuserrun xuserrun] and the following sleep.d script (be sure to modify the path to xuserrun and your desired screen locker):<br />
<br />
{{hc|/etc/pm/sleep.d/00screensaver-lock|<nowiki><br />
#!/bin/sh<br />
#<br />
# 00screensaver-lock: lock workstation on hibernate or suspend<br />
<br />
case "$1" in<br />
hibernate|suspend)<br />
/path/to/xuserrun /usr/bin/slimlock & # or any other such as /usr/bin/xscreensaver-command -lock<br />
;;<br />
thaw|resume)<br />
;;<br />
*) exit $NA<br />
;;<br />
esac<br />
</nowiki>}}<br />
<br />
If you do not use systemd, the following script includes another method for determining the username and display. It is not robust, and thus includes a fallback to a hard-coded username.<br />
<br />
{{hc|/etc/pm/sleep.d/00screensaver-lock|<nowiki><br />
#!/bin/sh<br />
#<br />
# 00screensaver-lock: lock workstation on hibernate or suspend<br />
<br />
dbus=$(ps aux | grep 'dbus-launch' | grep -v root)<br />
if [[ ! -z $dbus ]]; then<br />
username=$(echo $dbus | awk '{print $1}')<br />
userhome=$(getent passwd $username | cut -d: -f6)<br />
export XAUTHORITY="$userhome/.Xauthority"<br />
for x in /tmp/.X11-unix/*; do<br />
displaynum=$(echo $x | sed s#/tmp/.X11-unix/X##)<br />
if [[ -f "$XAUTHORITY" ]]; then<br />
export DISPLAY=":$displaynum"<br />
fi<br />
done<br />
else<br />
username= # add username here; i.e.: username=foobar<br />
userhome=/home/$username <br />
export XAUTHORITY="$userhome/.Xauthority"<br />
export DISPLAY=":0"<br />
fi<br />
<br />
case "$1" in<br />
hibernate|suspend)<br />
su $USER -c "/usr/bin/slimlock" & # or any other such as /usr/bin/xscreensaver-command -lock<br />
;;<br />
thaw|resume)<br />
;;<br />
*) exit $NA<br />
;;<br />
esac<br />
</nowiki>}}<br />
<br />
{{Note|For the previous scripts to work, TTY lock must be disabled in slimlock. Be sure to set {{ic|tty_lock 0}} in {{ic|/etc/slimlock.conf}}. [https://github.com/joelburget/slimlock/issues/4 Source].}}<br />
<br />
=== Disabling hibernation via polkit ===<br />
<br />
In order to disable hibernation, create a new file in /etc/polkit-1/ called 99-disable-hibernate.rules. Then add the following lines:<br />
<br />
{{hc|99-disable-hibernate.rules|<nowiki><br />
polkit.addRule(function(action, subject) {<br />
if ((action.id == "org.freedesktop.login1.hibernate")) {<br />
return polkit.Result.NO;<br />
}<br />
});<br />
<br />
polkit.addRule(function(action, subject) {<br />
if ((action.id == "org.freedesktop.login1.hibernate-multiple-sessions")) {<br />
return polkit.Result.NO;<br />
}<br />
});<br />
</nowiki>}}<br />
<br />
If you're using KDE, log off once and the hibernation option should be gone.<br />
<br />
== See also ==<br />
<br />
* [http://en.opensuse.org/SDB:Pm-utils OpenSUSE Wiki] - The article from where this was originally sourced (Licensed under GPL)<br />
* [https://wiki.ubuntu.com/UnderstandingSuspend Understanding Suspend] - Ubuntu article explaining how suspending to RAM works<br />
* [http://www.mjmwired.net/kernel/Documentation/power/basic-pm-debugging.txt#178 PM Debugging] - Basic PM debugging<br />
*[[Cpufrequtils]] - CPU Frequency Scaling and CPU Power schemes<br />
*[[Acpid]] - daemon for delivering ACPI events<br />
* [http://superuser.com/questions/298672/linuxhow-to-hibernate-after-a-period-of-sleep Hibernate after sleep] - An example of a custom pm-utils hook where hibernation is triggered after a period of time in suspension</div>Flecha