Skip to main content

Power saving setting on my laptop machine Debian Jessie is running on

I have not paid a little effort on power-saving setting of my laptop machine, but I finally made it to some extent.

After searching around the web pages, the article on the https://forums.bunsenlabs.org/viewtopic.php?id=1920 page reminded me of laptop-mode-tool package and tried it.

At first, I installed laptop-mode-tool, rebooted and launched the powertop.
The following screen capture is its screen:

PowerTOP 2.6.1    Overview   Idle stats   Frequency stats   Device stats   Tunab


>> Bad           Wireless Power Saving for interface wlan0                     
   Bad           Enable Audio codec power management
   Bad           Enable SATA link power management for host0
   Bad           Enable SATA link power management for host1
   Bad           Enable SATA link power management for host2
   Bad           Enable SATA link power management for host3
   Bad           NMI watchdog should be turned off
   Bad           VM writeback timeout
   Good          Autosuspend for unknown USB device 1-1 (8087:0020)
   Good          Autosuspend for unknown USB device 2-1 (8087:0020)
   Good          Autosuspend for USB device EHCI Host Controller [usb1]
   Good          Autosuspend for USB device EHCI Host Controller [usb2]
   Good          Runtime PM for PCI Device Intel Corporation Core Processor QPI
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation 82577LM Gigabit Net
   Good          Runtime PM for PCI Device Intel Corporation Core Processor Inte
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation Core Processor DRAM
   Good          Runtime PM for PCI Device Intel Corporation 82801 Mobile PCI Br
   Good          Runtime PM for PCI Device Intel Corporation Mobile 5 Series Chi
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Runtime PM for PCI Device Intel Corporation Core Processor Quic
   Good          Runtime PM for PCI Device Intel Corporation Core Processor Quic
   Good          Runtime PM for PCI Device Intel Corporation 1st Generation Core
   Good          Runtime PM for PCI Device Intel Corporation 1st Generation Core
   Good          Runtime PM for PCI Device Intel Corporation 1st Generation Core
   Good          Runtime PM for PCI Device Intel Corporation Centrino Advanced-N
   Good          Runtime PM for PCI Device Ricoh Co Ltd CardBus bridge
   Good          Runtime PM for PCI Device Ricoh Co Ltd MMC/SD Host Controller
   Good          Runtime PM for PCI Device Intel Corporation 5 Series/3400 Serie
   Good          Wake-on-lan status for device wlan0
   Good          Wake-on-lan status for device eth0



 <ESC> Exit | <Enter> Toggle tunable | <r> Window refresh                      

The laptop-mode-tool was doing good job, but some items remained untuned.
So, as the article suggested, I added the systemd service like:

# cat /etc/systemd/system/powertop.service
[Unit]
Description=Powertop tunings

[Service]
Type=oneshot
RemainAfterExit=no
ExecStart=/usr/sbin/powertop --auto-tune
Environment="TERM=xterm"

[Install]
WantedBy=multi-user.target
and typed:

sudo systemctl enable powertop.service

This brought a complete setting as long as I watched the powertop 'Tunables' tab.
Have fun!
Labels:

Comments

Post a Comment

Popular posts from this blog

Configuring Network Manager for PPPoE connection

When I'm home, I use fiber-optic line with a dedicated old small router (YAMAHA RT107e) for access to the Internet. But I recently became anxious about the router. If it fails, how can I survive until I get another one? So, I tried to connect my Debian desktop PC to the fiber-optic line without the router. The PC have to talk to the other side of the line with PPPoE but I did not know how. In my PC, the Network Manager manages network configuration. So, I had to configure the Network Manager to utilize the pppoe like : nmcli connection add ifname eth0 connection.type pppoe username USERNAME password PASSWORD
Post a Comment
Read more

Xen on Squeeze failed to start up the X server with an Intel graphics controller

I recently tried to set up Xen on my Squeeze box, with intel 945GM graphics controller. I followed the instruction on Xen - Debian Wiki . I installed the Xen hypervisor, kernel, xen-tools and other stuff, then created a domU image of Ubuntu natty. After that, I rebooted the system. But when X server was about to be launched, the screen became black out,  both keyboard and mouse don't work anymore. I reread the article on the wiki, and figured out the Xorg driver for Intel graphics controller  is suspicious. So, I changed the Xorg driver 'intel' to 'fbdev' wrting /etc/X11/xorg.conf , and rebooted.  This workaround works out! The drawback of the workaround is, 'intel' driver specific features, including DRI and XvMC, are disabled.
1 comment
Read more

Sharing one home directory between the Linux machines with the different display resolutions and different pointing devices, keeping $HOME/.config data for each machine

 Back in 1990's, it was common practice to share one home directory between many UNIX servers using NFS. But it is not in these days. But I have become to want to share my home directory between two different Linux machines: One is  a Debian GNU/Linux installed as a primary OS of a dual boot machine,  and the other is a virtualized Linux box within the Virtualbox running under the Windows 10, a secondary OS of the dual-boot. They have different display resolutions and pointing devices. These differences led me to an annoying problem: if you open GNOME desktop environment, display and pointing device setting became broken. Today's GNOME desktop environment stores most of the settings to the files under $HOME/.config directory. But if you share $HOME/.config between two machines, the stored configuration for a particular machine may become incompatible with other machines with different display resolutions and pointing devices. Indeed, my GNOME desktop has become unusable. To ove
Post a Comment
Read more