Difference between revisions of "Samsung N150"

From ArchWiki
Jump to navigation Jump to search
(added the other type of wireless card)
Line 35: Line 35:
== Wireless networking ==
== Wireless networking ==
The Samsung N150 is sold with two different wireless cards: the Atheros AR9285 and the Realtek 8192E.
The Atheros AR9285 wireless adapter also works out of the box, including full WPA2-PSK support via NetworkManager. Power to the transmitter can be toggled if the {{Package Official|rfkill}} package is installed, if the following script is installed in /usr/local/sbin/rftoggle
= Atheros AR9285 =
This wireless adapter also works out of the box, including full WPA2-PSK support via NetworkManager. Power to the transmitter can be toggled if the {{Package Official|rfkill}} package is installed, if the following script is installed in /usr/local/sbin/rftoggle
Line 49: Line 51:
= Realtek 8192E =
The RTL8192E driver is in the Arch kernel, but firmware is required. It is in the {{Package Official|linux-firmware}} package or also available in the AUR. See also {{Wireless Setup}}.
== Graphics ==
== Graphics ==

Revision as of 13:56, 24 July 2010

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

This article describes the installation and configuration of 64-bit Arch Linux on the Samsung N150 netbook. Based on the output from dmidecode, this material might also be useful for the N210 and N220 models.

Hardware overview

The Samsung N150 netbook is equipped with the Intel Atom N450 ("Pineview") CPU with integrated Intel GMA 3100 GPU and "Pine Trail" chipset. Unlike the prior single-core Intel Atom N2xx and Z series processors, the N450 supports the x86_64 instruction set. Although DMI information suggests the motherboard will accept up to 8 GiB RAM, the integrated memory controller in the Atom N450 can address a maximum of 2 GiB. Since the hardware is limited to a 32-bit address space, the primary benefit to running the 64-bit version of Arch on this system is to take advantage of AUR packages built on more powerful 64-bit systems belonging to the same owner.

Shipping versions of the N150 (as of early March 2010) include the "starter" edition of a proprietary operating system and therefore include only 1 GiB RAM in the form of a single DDR2 667 MhZ SODIMM, which is user-replaceable. Per the DMI information, the unit contains two mini PCI express slots, one of which is populated by the included Atheros AR9285 wireless card. Other versions of this model are apparently available with an integrated 3G WAN adapter installed in the other slot.

External connectivity provided on the system includes 3 USB 2.0 ports, a single VGA port, 10/100 Ethernet (Marvell 88E8040 PCI-E), headphone/microphone jacks, and an integrated card reader (SD/SDHC/MMC). An integrated VGA-resolution webcam is connected to the internal USB controller.


Since netbooks lack optical drives, the preferred installation mechanism is via a USB flash drive. Upon first boot into the 2009.08 installation media, the system will reboot after CPU initialization. Subsequent reboots using the same kernel will not exhibit this behavior, although booting into a later installed kernel may reboot the first time.

This article assumes the entire hard disk will be used for Arch, eliminating the manufacturer-supplied software (including the recovery partitions). It is not entirely clear which partitions are required for the recovery software to function properly: retention of the only first partition, of unknown type, is not sufficient. If a recovery mechanism for the factory-supplied software is desired, a set of recovery DVDs should be created using an external DVD burner prior to installing Arch.

Upon the first installation, cfdisk will exit with an error due to the existing partition layout extending beyond the end of the disk (using Linux default geometries). The solution is to run fdisk and create a new, empty partition table. WARNING: This operation will destroy the current hard disk partitions, effectively causing all data on the hard disk to be lost.

fdisk /dev/sda << EOF

After initializing the drive with an empty partition table, cfdisk will work properly in the Arch installer.

Device configuration

Ethernet (wired)

The Marvell 88E8040 wired 10/100 Ethernet adapter works out of the box with the default kernel. By installing Template:Package Official and delaying network initialization until after the GUI is displayed, the boot process can be expedited.

Wireless networking

The Samsung N150 is sold with two different wireless cards: the Atheros AR9285 and the Realtek 8192E.

Atheros AR9285

This wireless adapter also works out of the box, including full WPA2-PSK support via NetworkManager. Power to the transmitter can be toggled if the Template:Package Official package is installed, if the following script is installed in /usr/local/sbin/rftoggle


blocked=`rfkill list wlan | grep "Soft blocked: yes"`

if [ -z "$blocked" ]; then
   rfkill block wlan
   rfkill unblock wlan

Realtek 8192E

The RTL8192E driver is in the Arch kernel, but firmware is required. It is in the Template:Package Official package or also available in the AUR. See also Template:Wireless Setup.


The Intel GMA 3100 GPU, embedded in the Atom 450 CPU package, works out of the box with Kernel Mode Setting. Early KMS initialization seems to improve boot speed slightly and can be enabled by adding the following to the MODULES line in /etc/mkinitcpio.conf:

MODULES="intel_agp i915"

Run Template:Codeline to make the configuration effective.

Unlike the prior Samsung N140 model, the N150 does not seem to suffer from display powersaving problems.

Once Fn keys are enabled (see below), Fn+F4 will toggle between LCD only, extended, and cloned modes automatically whenever an external screen is connected to the VGA port.


Like other Samsung laptops and netbooks, direct ACPI control of the backlight is not possible on the N150. Instead, a script can be created to manage backlight settings by changing the PCI configuration of the display adapter. For ease of use with the Fn keys section, this script should be located at /usr/local/sbin/backlight

# increase/decrease/set/get the backlight brightness (range 0-255)
# PCI device on which to operate

# Amount to raise/lower the backlight when called with "up" or "down"

# Minimum backlight value reachable via "down"

# Default backlight level when toggling on
#get current brightness in hex and convert to decimal
var1=`setpci -s $DEVICE F4.B`
case "$1" in
               #calculate new brightness
               var2=`echo "ibase=10; obase=16; a=($var1d+$AMOUNT);if (a<255) print a else print 255" | bc`
               echo "$0: increasing brightness from 0x$var1 to 0x$var2"
               setpci -s $DEVICE F4.B=$var2
               #calculate new brightness
               var2=`echo "ibase=10; obase=16; a=($var1d-$AMOUNT);if (a>$MIN) print a else print $MIN" | bc`
               echo "$0: decreasing brightness from 0x$var1 to 0x$var2"
               setpci -s $DEVICE F4.B=$var2
               #n.b. this does allow "set 0" i.e. backlight off
               echo "$0: setting brightness to 0x$2"
               setpci -s $DEVICE F4.B=$2
               echo "$0: current brightness is 0x$var1"
               if [ $var1d -eq 0 ] ; then
                       echo "toggling up"
                       setpci -s $DEVICE F4.B=$DEFAULT
                       echo "toggling down"
                       setpci -s $DEVICE F4.B=0
               echo "usage: $0 {up|down|set <val>|get|toggle}"
exit 0


Intel HD Audio works out of the box on this model, although the volume for the "speaker" mixer channel needs to be increased from zero. Install the Template:Package Official package to acquire an init script for restoring the volume at boot time.

For N210 owners the internal microphone might not work out of the box. You can use this workaround.

Suspend to RAM (S3 sleep)

With Gnome 2.28 and the Template:Package Official package installed, suspend-to-RAM works out of the box whenever the netbook lid is closed. The suspend process requires up to 30 seconds or so to take effect. Waking from S3 requires activating the power button under the default configuration. Waking upon opening the lid, or pressing a key, can be enabled in the BIOS.

Suspend to disk (hibernate)

Hibernate support with pm-utils does not work reliably. Upon resuming from hibernation, there are ELF header errors related to glibc, effectively preventing any new applications (including /sbin/shutdown) from starting. Moreover, even if this problem can be resolved, the process of resuming from the swap partition (before the errors are observed) is slightly longer than a cold boot.


The Synaptics touchpad works for single-finger operation with scrolling along the right edge out of the box. When Fn+F10 is pressed, the BIOS automatically enables or disables the touchpad hardware. To receive notification of this event, it is useful to install the Template:Package Official package and configure a script to print a message whenever Fn+F10 is pressed (see below for Fn key configuration). This script should be saved in /usr/local/bin/report_touchpad



case "$1" in
      echo "usage: $0 {on|off}"
      exit 2

osd_cat -A center -p middle -f $FONT -d $DELAY << EOF
Touchpad $state

exit 0

To enable tapping, the easiest solution is to install Template:Package Official or Template:Package AUR. Although the literature shipping with the netbook claims multitouch support (for two-finger tap, two-finger scroll, etc.), it does not appear to work properly.

For n220 owners (these parameters haven't been tested on n150 but it migth work), these touchpad rules enable multitouch (/etc/hal/fdi/policy/11-x11-synaptics.fdi)

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
                <match key="info.capabilities" contains="input.touchpad">
                        <merge key="input.x11_driver" type="string">synaptics</merge>
                        <merge key="input.x11_options.TapButton1" type="string">1</merge>
                        <merge key="input.x11_options.TapButton2" type="string">2</merge>
                        <merge key="input.x11_options.TapButton3" type="string">3</merge>

                        <merge key="input.x11_options.SHMConfig" type="string">true</merge>

                        <merge key="input.x11_options.VertEdgeScroll" type="string">false</merge>
                        <merge key="input.x11_options.PalmDetect" type="string">false</merge>

                        <merge key="input.x11_options.VerteScrollDelta" type="string">100</merge>

                        <merge key="input.x11_options.VertTwoFingerScroll" type="string">true</merge>
                        <merge key="input.x11_options.HorizTwoFingerScroll" type="string">true</merge>
                        <merge key="input.x11_options.EmulateTwoFingerMinZ" type="string">40</merge>
                        <merge key="input.x11_options.EmulateTwoFingerMinW" type="string">5</merge>


CPU frequency scaling

To improve power management to some degree, CPU frequency scaling can be enabled. This mechanism requires a few modules to be loaded at boot time from /etc/rc.conf:

MODULES=(acpi-cpufreq cpufreq-ondemand cpufreq-powersave)

Toggling between the performance, ondemand, and powersave governors can be accomplished via the following script, installed to /usr/local/sbin/cpufreq_toggle


current=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor`

if [ "$current" == "performance" ]; then
elif [ "$current" == "ondemand" ]; then

echo "$future" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "$future" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo "$future"

For reporting the current governor choice via an on-screen display (useful if enabling the Fn+F8 performance switching shortcut), the following wrapper script can be installed as /usr/local/bin/cpufreq_toggle_osd



state=`sudo /usr/local/sbin/cpufreq_toggle`
message="CPU Performance State Unknown"

if [ "$state" == "performance" ]; then
   message="Performance Mode"
elif [ "$state" == "powersave" ]; then
   message="Low Power Mode"
elif [ "$state" == "ondemand" ]; then
   message="Automatic Mode"

osd_cat -A center -p middle -f $FONT -d $DELAY << EOF

exit 0

By default, the system will boot with CPU frequency scaling set to use the performance governor. To enable the ondemand governor at the end of the boot process, append the following to /etc/rc.local

echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

Fn keys

Several of the special Fn key combinations work out of the box with the N150, but most do not. Unusual scancodes are reported to the kernel, which does not know how to convert these codes to keycodes natively. Worse, many of the scancodes produce a key press event without a corresponding key release event. Appending the following lines to /etc/rc.local will enable all Fn keys and map them properly:

setkeycodes e002 227   # Fn+F4 maps to switchvidmode
setkeycodes e003 236   # Fn+F2 maps to battery
setkeycodes e004 148   # Fn+F5 maps to prog1
setkeycodes e006 238   # Fn+F9 maps to wlan
setkeycodes e008 225   # Fn+Up maps to brightnessup
setkeycodes e009 224   # Fn+Dn maps to brightnessdown
setkeycodes e031 149   # Fn+F7 maps to prog2
setkeycodes e033 202   # Fn+F8 maps to prog3
setkeycodes e077 191   # Fn+F10 maps to F21 whenever the touchpad is enabled
setkeycodes e079 192   # Fn+F10 maps to F22 whenever the touchpad is disabled

# Ensure key release events occur for all except Fn+F7, which properly reports a key release for some reason
echo 130,131,132,134,136,137,179,247,249 > /sys/devices/platform/i8042/serio0/force_release

To enable hotkeys to change backlight, wireless, and system performance settings, it is necessary to give regular users certain permissions via the sudo command. Run visudo as root and add the following to the Cmnd alias specifications:

Cmnd_Alias NETBOOK_CMDS = /usr/local/sbin/backlight, /usr/local/sbin/rftoggle, /usr/local/sbin/cpufreq_toggle

Then add the following to the bottom of the file:


Now custom keyboard shortcuts can be added to Gnome by means of the "Keyboard Shortcuts" preferences.

Name Command Key
Touchpad disabled /usr/local/bin/report_touchpad off Press Fn+F10 while touchpad enabled
Touchpad enabled /usr/local/bin/report_touchpad on Press Fn+F10 while touchpad disabled
Toggle CPU frequency scaling /usr/local/bin/cpufreq_toggle_osd Fn+F8
Raise backlight sudo /usr/local/sbin/backlight up Fn+Up arrow
Lower backlight sudo /usr/local/sbin/backlight down Fn+Down arrow
Toggle wireless sudo /usr/local/sbin/rftoggle Fn+F9
Toggle backlight sudo /usr/local/sbin/backlight toggle Fn+F5

Reducing boot time

In order to make the netbook boot as quickly as possible, timeouts can be minimized and services can be started in the background. Two Grub modifications are helpful: reduce the timeout to 2 seconds, and add the "quiet" option to suppress some kernel output (those printk's take time). These modifications are made in /boot/grub/menu.lst

timeout    2
# (0) Arch Linux
title  Arch Linux
root   (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro quiet
initrd /kernel26.img

Note that it might be a good idea not to add "quiet" to the fallback image, in case the kernel output is needed at boot time to diagnose a problem.

Backgrounding startup processes in /etc/rc.conf can be a bit trickier, especially when one daemon depends upon others. However, it is possible to take advantage of known "delays" in the boot process (e.g. starting X11) that allow services such as NetworkManager to start in the background well before they will be needed.

DAEMONS=(syslog-ng !network hal @networkmanager @sensors @alsa !netfs @crond)

With the above tweaks, Gdm is ready for login 37-38 seconds after a cold boot (including BIOS and Grub timeouts).