Difference between revisions of "ASUS Eee PC 1015pn"

From ArchWiki
Jump to: navigation, search
m (Wireless: fixed kmod blacklisting link)
(update Pkg/AUR templates)
(Tag: wiki-scripts)
(38 intermediate revisions by 12 users not shown)
Line 1: Line 1:
[[Category:ASUS (English)]]
+
[[Category:ASUS]]
This page includes general information regarding Asus EEE PC 1015pn and related notes on installing/using Arch Linux on it.
+
Asus 1015PN is a dual-core netbook with Nvidia IOn graphics for better gaming. It works fine with Linux OSs. This article provides some information on hardwares specs and some knowledge base about it.
 
 
=System Specs=
 
  
 +
== System Specs ==
 
*'''CPU:'''  Intel Atom Dual-Core N550 (1.5 GHz)
 
*'''CPU:'''  Intel Atom Dual-Core N550 (1.5 GHz)
  
*'''RAM:''' 1GB 1066MHz DDR3 (up to 2GB)
+
*'''RAM:''' 1GB 1066MHz DDR3 (up to 2GB 1333Mhz)
  
 
*'''HDD:''' 250 GB, 5400 RPM
 
*'''HDD:''' 250 GB, 5400 RPM
  
*'''GPU:''' nVidia ION2 with Optimus
+
*'''GPU:''' nVidia GT218 ION2 with Optimus (Intel GMA 3150 built into the CPU)
  
 
*'''Display:''' 10.1" 1024 x 600 pixels LCD display
 
*'''Display:''' 10.1" 1024 x 600 pixels LCD display
Line 16: Line 15:
 
*'''Wireless:''' BCM4313
 
*'''Wireless:''' BCM4313
  
*'''Bluetooth:''' TODO
+
*'''Bluetooth:''' Working (confirmed in linux 3.6.5)
  
*'''Webcam:''' Working (remenber to add yourself to video group)
+
*'''Webcam:''' Working (remember to add yourself to video group)
  
*'''Card Reader:''' TODO
+
*'''Card Reader:''' Working
  
 
*'''Extras:''' 3 USB 2.0 ports, Bluetooth 3
 
*'''Extras:''' 3 USB 2.0 ports, Bluetooth 3
  
=HDD important issue=
+
== HDD important issue ==
 
+
See [[Laptop#Hard drive spin down problem]].
With the Western Digital hard drive (not SSD), there is an important issue: using the APM (Advanced Power Management) there are too nomerous spin-down, that can damage the hard drive. To confirm this issue, you have to install {{Package Official|smartmontools}}:
 
# pacman -S smartmontools
 
And you have to run multiple times this command (once in a minute for like 5 minutes):
 
# smartctl -a /dev/sda|grep Load_Cycle_Count
 
If the number under Load_Cycle_Count is increasing in a small amount of time (1 or 2 in a minute) you have this issue.
 
 
 
==Method 1==
 
The problem is easily solvable using laptop-mode-tools. In your {{Filename|/etc/laptop-mode/laptop-mode.conf}}, you have to set:
 
#
 
# Should laptop mode tools control the hard drive power management settings?
 
#
 
CONTROL_HD_POWERMGMT=1
 
 
#
 
# Power management for HD (hdparm -B values)
 
#
 
BATT_HD_POWERMGMT=255
 
LM_AC_HD_POWERMGMT=255
 
NOLM_AC_HD_POWERMGMT=255
 
This disable all power management systems of the hard drive cause a light heat up (maybe). The same behaviour can be obtained running this command:
 
# hdparm -B 255 /dev/sda
 
the 255 number is the power-management level, in a range of 1-255 where 1 is maximum powersaving and 255 powersaving disabled. However setting the value to 253 causes a lot of spin-down. Setting the spin-down feature (it parks the heads away from disk) however can save the hard disk in case of a fall.
 
 
 
==Method 2==
 
This method correct this issue once and for all :
 
[http://www.synology.com/support/faq_show.php?lang=enu&q_id=407 WDIDLE3]
 
 
 
= nVidia ION 2 with Optimus =
 
  
 +
== nVidia ION 2 with Optimus ==
 
Optimus doesn't work at all but it is possible to choose which graphical card will be used on next reboot.
 
Optimus doesn't work at all but it is possible to choose which graphical card will be used on next reboot.
  
 
You can get 2 'modes' :
 
You can get 2 'modes' :
  
*By default (if you do not do anything) the machine starts with the Nvidia beeing the only VGA controller visible (so it will use the ION chip).
+
* By default (if you do not do anything) the machine starts with the Nvidia beeing the only VGA controller visible (so it will use the ION chip).
*Using some tools you can start with the Intel and Nvidia VGA controller visible. In this mode the Intel controller is used and it is possible to power-down the Nvidia part.
+
* Using some tools you can start with the Intel and Nvidia VGA controller visible. In this mode the Intel controller is used and it is possible to power-down the Nvidia part.
 
 
 
 
To switch between those modes you will need {{Package AUR|acpi_call-git}}.
 
  
== Installing acpi_call ==
+
To switch between those modes you will need the {{Ic|acpi_call}} kernel module.
  
 +
=== Installing acpi_call kernel module ===
 +
This module is provided by {{AUR|acpi_call-git}}{{Broken package link|{{aur-mirror|acpi_call-git}}}}, or its dkms version, {{AUR|acpi_call-git-dkms}}{{Broken package link|package not found}}. Both are available in [[AUR]].
  
Manual Install:
+
Build and install on of these packages and then load the module.
git clone http://github.com/mkottman/acpi_call.git
 
cd acpi_call
 
make
 
sudo insmod acpi_call.ko
 
  
'''OR'''
+
Make sure you add {{Ic|acpi_call}} into {{ic|/etc/modules-load.d/}}, in order to have the module available in every reboot.
  
Install {{Package AUR|acpi_call-git}} from the [[AUR]].
+
=== Selecting Video Card ===
Add {{Codeline|acpi_call}} module into {{Filename|/etc/rc.conf}}.
+
The ACPI method \OSGS is used for selecting the video card for the next boot. The first argument to it determines the card(s) to be enabled. Only the two rightmost bits are used. If bit 0 is enabled, the intel card is enabled as well. Bit 1 correspondends with the nvidia card. If no bits are enabled, only the nvidia card will be enabled. Hence:
  
 +
* \OSGS 3 - enable Intel + Nvidia (Optimus mode)
 +
* \OSGS 2 (or even \OSGS 0x00) - enable Nvidia only (discrete mode)
 +
* \OSGS 1 - enable Intel only (integrated mode)
  
== Selecting Video Card ==
+
Using the acpi_call module, you can execute these commands. Example: to select Intel + Nvidia on next reboot:
To select Intel + Nvidia on next reboot :
+
  echo '\OSGS 3' > /proc/acpi/call
  echo "\OSGS 0x03" > /proc/acpi/call
 
  
Note: You will need to do this at each boot as long as you want to stay with the Intel part (If you do not do this the Eee will start with only the Nvidia Ion part).
 
  
 +
Note: You will need to do this at each boot as long as you want to stay with the Intel part (If you do not do this the Eee will start with only the Nvidia Ion VGA controller).
 +
Adding the above command to /etc/rc.local will run the command on every boot (for the next boot). This is ideal if you want to run X on the Intel VGA controller.
  
 
You can check the current mode with :
 
You can check the current mode with :
Line 91: Line 61:
 
  cat /proc/acpi/call
 
  cat /proc/acpi/call
  
For example if the result is 0x30003 :
+
Substract 0x30000 from the result and interpret the remaining two bits as the first argument passed to \OSGS. Thus:
*First byte 0x03 means mode 3 (returnvalue &= 3)
+
 
*Logical AND with 0x10000 and right-bitshift 16 bytes gives whether Optimus is supported (1=true, 0=false): here 1
+
* 0x30003 - intel + nvidia are on (Optimus mode)
 +
* 0x30002 - only the nvidia card is on (discrete mode)
 +
* 0x30001 - only the intel card is on (integrated mode)
  
 +
After reboot you can see which controllers are enabled with:
 +
lspci -nn | grep '\[03'
  
After reboot you can see with lspci that the Intel VGA controller is visible. You can now power down the ion part with (you'll need the acpi_call module loaded):
+
You can now power down the ion part with (you'll need the acpi_call module loaded):
 
  echo "\_SB.PCI0.P0P4.DGPU.DOFF" > /proc/acpi/call
 
  echo "\_SB.PCI0.P0P4.DGPU.DOFF" > /proc/acpi/call
 +
Note: when the nvidia card is the only enabled card, the above function does nothing.
  
 
Note: When leaving suspend you need to do this again because the Nvidia part reactivates itself.
 
Note: When leaving suspend you need to do this again because the Nvidia part reactivates itself.
Line 110: Line 85:
 
   if lsmod | grep -q acpi_call; then
 
   if lsmod | grep -q acpi_call; then
 
           stat_busy 'Swith per ACPI_CALL to Optimus'
 
           stat_busy 'Swith per ACPI_CALL to Optimus'
           echo "\OSGS 0x03" > /proc/acpi/call
+
           echo "\OSGS 0x03" > /proc/acpi/callrayt5
 
           echo "\_SB.PCI0.P0P4.DGPU.DOFF" > /proc/acpi/call
 
           echo "\_SB.PCI0.P0P4.DGPU.DOFF" > /proc/acpi/call
 
           echo "\AMW0.DSTS 0x90013" > /proc/acpi/call
 
           echo "\AMW0.DSTS 0x90013" > /proc/acpi/call
Line 127: Line 102:
 
   fi
 
   fi
  
== Check consumption==
+
=== Check consumption ===
 
You can check consumption with:  
 
You can check consumption with:  
  cat /proc/acpi/battery/BAT0/state
+
  cat /sys/class/power_supply/BAT0/current_now
  
*Before disabling: ~1700mA.
+
* Before disabling: ~1700mA.
*After disabling: ~1000mA.
+
* After disabling: ~1000mA.
  
 
As you can see this method saves a lot of battery!
 
As you can see this method saves a lot of battery!
  
= ACPI =
+
== ACPI ==
 +
As of kernel 3.1, appending {{Ic|1=acpi_osi=Linux}} to the kernel line in your bootloader configuration file (e.g. grub, lilo, syslinux...) is no longer necessary to enable ACPI. The proper modules should be automatically called at boot.
 +
 
 +
== Wireless ==
 +
 
 +
For BCM4313 there are the following drivers available:
 +
 
 +
* proprietary {{AUR|broadcom-wl}} driver or, its dkms version {{Pkg|broadcom-wl-dkms}}, both available in AUR.
 +
 
 +
* open source {{Ic|brcm80211}} driver directly included in the Linux kernel, since version 3.0.0  (recommended)
 +
 
 +
 
 +
In case you use the open source brcm80211 driver provided by Linux kernel, make sure you add {{Ic|bcma}} to a [[blacklist]] file, otherwise you will have a conflict between drivers which will block the {{Ic|brcm80211}} driver and that will make your wireless card be unavailable.
 +
 
 +
== Bumblebee ==
 +
The 1015pn can be configured to run automatically on the Intel video card, turn on and use the Nvidia part for specific processes when requested, and otherwise leave the Nvidia part turned off.
 +
 
 +
First, install {{AUR|acpi_call-git}}{{Broken package link|{{aur-mirror|acpi_call-git}}}} from the [[AUR]].
 +
Add {{Ic|acpi_call}} module into {{ic|/etc/modules-load.d/}}.
  
To enable ACPI, you need to edit {{Filename|/boot/grub/menu.lst}} and add {{Codeline|acpi_osi<nowiki>=</nowiki>Linux}} to the kernel line like so:
+
Lets make use of systemd's tmpfiles to ensure that the Intel VGA controller is used on every subsequent boot.
  
  kernel /boot/vmlinuz-linux root=/dev/sda1 ro acpi_osi=Linux
+
{{hc|/etc/tmpfiles.d/acpi_call.conf|
 +
w /proc/acpi/call - - - - \OSGS 0x03}}
  
This enabled you to trigger devices in {{Filename|/sys/devices/platform/eeepc/}}.
+
Next, install and configure [[Bumblebee]]. Finally, remove any automated or otherwise scripted acpi calls to turn off the Nvidia VGA controller.
  
=Wireless=
+
Power management of the Nvidia VGA controller can also be handled by Bumblebee. Please note, however, that Bumblebee support for power management is currently experimental. To use automatic power management of the Nvidia card, first go to {{ic|/etc/bumblebee/bumblebee.conf}}, and change ENABLE_POWER_MANAGEMENT=Y and STOP_SERVICE_ON_EXIT=Y.
 +
This gives Bumblebee permission to turn on and off the Nvidia card. Stop service on exit means that the Nvidia card will be turned off when not currently being used by any process.
  
Kernel >= 2.6.37 include the required module natively.
+
Next, two new files, {{ic|cardon}} and {{ic|cardoff}}, must be created in {{ic|/etc/bumblebee/}}, with the following contents:
  
Note: The Broadcom BCM4313 card requires the [http://aur.archlinux.org/packages.php?ID=42670 compat-wireless-brcm80211] module which is available in the AUR if kernel <=2.6.36
+
{{hc|cardon|\_SB.PCI0.P0P4.DGPU.DON}}
  
For kernel 3.0 or higher, wireless card seems to be blocked due to a bug. To solve this issue, you can try [[Kernel_modules#Blacklisting|blacklisting]] the kernel module {{Codeline|bcma}}.
+
{{hc|cardoff|\_SB.PCI0.P0P4.DGPU.DOFF}}
  
=To Do=
+
These are the acpi calls that Bumblebee will use to dynamically control the power of the Nvidia card. Now if bumblebee is included in the {{Ic|MODULES}} section of {{Ic|/etc/rc.conf}}, Bumblebee will automatically power down the Nvidia VGA controller unless it is being used with the optirun command.
# Manage to get the {{Package Official|xf86-video-intel}} and {{Package Official|nvidia}} packages installed (specific libgl being used by each one)
 
# Get the Bluetooth working, without kernel panic attacks.
 
  
= Links =
+
== Links ==
 
*[http://linux-hybrid-graphics.blogspot.com/ http://linux-hybrid-graphics.blogspot.com/]
 
*[http://linux-hybrid-graphics.blogspot.com/ http://linux-hybrid-graphics.blogspot.com/]
 +
*[https://sites.google.com/site/mtrons/howtos/eeepc-1015pn https://sites.google.com/site/mtrons/howtos/eeepc-1015pn]
 +
*[https://github.com/Bumblebee-Project/acpi_call https://github.com/Bumblebee-Project/acpi_call]
 +
*[https://github.com/Bumblebee-Project/Bumblebee https://github.com/Bumblebee-Project/Bumblebee]
 +
*[http://wireless.kernel.org/en/users/Drivers/brcm80211 http://wireless.kernel.org/en/users/Drivers/brcm80211]
 +
*[http://www.asus.com/Notebooks_Ultrabooks/Eee_PC_1015PN http://www.asus.com/Notebooks_Ultrabooks/Eee_PC_1015PN]

Revision as of 08:14, 3 June 2017

Asus 1015PN is a dual-core netbook with Nvidia IOn graphics for better gaming. It works fine with Linux OSs. This article provides some information on hardwares specs and some knowledge base about it.

System Specs

  • CPU: Intel Atom Dual-Core N550 (1.5 GHz)
  • RAM: 1GB 1066MHz DDR3 (up to 2GB 1333Mhz)
  • HDD: 250 GB, 5400 RPM
  • GPU: nVidia GT218 ION2 with Optimus (Intel GMA 3150 built into the CPU)
  • Display: 10.1" 1024 x 600 pixels LCD display
  • Wireless: BCM4313
  • Bluetooth: Working (confirmed in linux 3.6.5)
  • Webcam: Working (remember to add yourself to video group)
  • Card Reader: Working
  • Extras: 3 USB 2.0 ports, Bluetooth 3

HDD important issue

See Laptop#Hard drive spin down problem.

nVidia ION 2 with Optimus

Optimus doesn't work at all but it is possible to choose which graphical card will be used on next reboot.

You can get 2 'modes' :

  • By default (if you do not do anything) the machine starts with the Nvidia beeing the only VGA controller visible (so it will use the ION chip).
  • Using some tools you can start with the Intel and Nvidia VGA controller visible. In this mode the Intel controller is used and it is possible to power-down the Nvidia part.

To switch between those modes you will need the acpi_call kernel module.

Installing acpi_call kernel module

This module is provided by acpi_call-gitAUR[broken link: archived in aur-mirror], or its dkms version, acpi_call-git-dkmsAUR[broken link: package not found]. Both are available in AUR.

Build and install on of these packages and then load the module.

Make sure you add acpi_call into /etc/modules-load.d/, in order to have the module available in every reboot.

Selecting Video Card

The ACPI method \OSGS is used for selecting the video card for the next boot. The first argument to it determines the card(s) to be enabled. Only the two rightmost bits are used. If bit 0 is enabled, the intel card is enabled as well. Bit 1 correspondends with the nvidia card. If no bits are enabled, only the nvidia card will be enabled. Hence:

  • \OSGS 3 - enable Intel + Nvidia (Optimus mode)
  • \OSGS 2 (or even \OSGS 0x00) - enable Nvidia only (discrete mode)
  • \OSGS 1 - enable Intel only (integrated mode)

Using the acpi_call module, you can execute these commands. Example: to select Intel + Nvidia on next reboot:

echo '\OSGS 3' > /proc/acpi/call


Note: You will need to do this at each boot as long as you want to stay with the Intel part (If you do not do this the Eee will start with only the Nvidia Ion VGA controller). Adding the above command to /etc/rc.local will run the command on every boot (for the next boot). This is ideal if you want to run X on the Intel VGA controller.

You can check the current mode with :

echo "\AMW0.DSTS 0x90013" > /proc/acpi/call
cat /proc/acpi/call

Substract 0x30000 from the result and interpret the remaining two bits as the first argument passed to \OSGS. Thus:

  • 0x30003 - intel + nvidia are on (Optimus mode)
  • 0x30002 - only the nvidia card is on (discrete mode)
  • 0x30001 - only the intel card is on (integrated mode)

After reboot you can see which controllers are enabled with:

lspci -nn | grep '\[03'

You can now power down the ion part with (you'll need the acpi_call module loaded):

echo "\_SB.PCI0.P0P4.DGPU.DOFF" > /proc/acpi/call

Note: when the nvidia card is the only enabled card, the above function does nothing.

Note: When leaving suspend you need to do this again because the Nvidia part reactivates itself.

rc script to disable nvidia:

 #!/bin/bash
 
 . /etc/rc.conf
 . /etc/rc.d/functions
 
 
 if lsmod | grep -q acpi_call; then
         stat_busy 'Swith per ACPI_CALL to Optimus'
         echo "\OSGS 0x03" > /proc/acpi/callrayt5
         echo "\_SB.PCI0.P0P4.DGPU.DOFF" > /proc/acpi/call
         echo "\AMW0.DSTS 0x90013" > /proc/acpi/call
         result=$(cat /proc/acpi/call)
         case "$result" in
         0x30003)
                 stat_done
         ;;
         *)
                 stat_fail
         ;;
         esac
 else
         stat_busy 'ACPI_CALL mod not loaded'
         stat_fail
 fi

Check consumption

You can check consumption with:

cat /sys/class/power_supply/BAT0/current_now
  • Before disabling: ~1700mA.
  • After disabling: ~1000mA.

As you can see this method saves a lot of battery!

ACPI

As of kernel 3.1, appending acpi_osi=Linux to the kernel line in your bootloader configuration file (e.g. grub, lilo, syslinux...) is no longer necessary to enable ACPI. The proper modules should be automatically called at boot.

Wireless

For BCM4313 there are the following drivers available:

  • open source brcm80211 driver directly included in the Linux kernel, since version 3.0.0 (recommended)


In case you use the open source brcm80211 driver provided by Linux kernel, make sure you add bcma to a blacklist file, otherwise you will have a conflict between drivers which will block the brcm80211 driver and that will make your wireless card be unavailable.

Bumblebee

The 1015pn can be configured to run automatically on the Intel video card, turn on and use the Nvidia part for specific processes when requested, and otherwise leave the Nvidia part turned off.

First, install acpi_call-gitAUR[broken link: archived in aur-mirror] from the AUR. Add acpi_call module into /etc/modules-load.d/.

Lets make use of systemd's tmpfiles to ensure that the Intel VGA controller is used on every subsequent boot.

/etc/tmpfiles.d/acpi_call.conf
w /proc/acpi/call - - - - \OSGS 0x03

Next, install and configure Bumblebee. Finally, remove any automated or otherwise scripted acpi calls to turn off the Nvidia VGA controller.

Power management of the Nvidia VGA controller can also be handled by Bumblebee. Please note, however, that Bumblebee support for power management is currently experimental. To use automatic power management of the Nvidia card, first go to /etc/bumblebee/bumblebee.conf, and change ENABLE_POWER_MANAGEMENT=Y and STOP_SERVICE_ON_EXIT=Y. This gives Bumblebee permission to turn on and off the Nvidia card. Stop service on exit means that the Nvidia card will be turned off when not currently being used by any process.

Next, two new files, cardon and cardoff, must be created in /etc/bumblebee/, with the following contents:

cardon
\_SB.PCI0.P0P4.DGPU.DON
cardoff
\_SB.PCI0.P0P4.DGPU.DOFF

These are the acpi calls that Bumblebee will use to dynamically control the power of the Nvidia card. Now if bumblebee is included in the MODULES section of /etc/rc.conf, Bumblebee will automatically power down the Nvidia VGA controller unless it is being used with the optirun command.

 Links