Samsung NC10

From ArchWiki
Revision as of 13:38, 21 March 2009 by John schaf (Talk | contribs) (Audio)

Jump to: navigation, search

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Samsung NC10#)

Introduction

This article aims on providing the informations on installing and setting up Arch Linux on the Samsung NC10.

A lot of the information is derived from the Arch Forum and several hints scattered around in the ArchWiki.

Installation

As all other netbooks the NC10 doesn't have an optical drive so you have to install Arch Linux either through an USB pen drive or via an external USB CD-ROM drive.

Before you can start the process of installation you have to disable acpi. To do so edit the bootline by pressing e in the GRUB menu. Then append

acpi=off

to the kernel line. This is only for installation - once arch is installed you don't need the option anymore.

The installation itself is pretty much straightforward and you can use the Beginners_Guide if you need detailed informations.

Configure your installation

Network

With the kernel version >=2.6.27 both, LAN and WLAN work out-of-the-box.

For LAN the module sky2 is used. The Atheros AR242x wireless chipset uses the module ath5k. To avoid conflicts you should blackmask the other wifi modules:

  • ath_hal
  • ath_pci
  • wlan

Video

The Video controller is a typical Intel chipset that works with the xf86-video-intel driver.

To save some interrupts and therefore power you can disable dri in your xorg.conf. This disables 3D effects but if you don't need them this could be an option.

Section "Device"
Option "NoDRI"
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 945GME Express Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection

External VGA

External VGA works out of the box with xrandr

in order to prevent problems when switching to console or when unplugging the external monitor, make sure to specify the frequency along with the mode, for example :

xrandr --output VGA --mode 1280x1024 --rate 60

Dual head positioning works also perfectly : Xorg#Multi-monitor_setups

Tweaks

Are there any?

Audio

The audio device is an Intel HD and should work without modifications.

Since alsa 1.0.19 distributed in archlinux extra repository, you don't need to manually install alsa driver. Everything is working out of the box: onboard microphone and speakers, audio off on earphone plugging.

Troubleshooting :

If the volume is too low, or lower than in Windows run alsamixer, and set "front" to 100%.

If the microphone does not work, press F4 in alsamixer and play with the settings (boost to 0, digital and capture to mid-values, and input to front-mic should be a sane default). Note that settings can be saved with "alsactl store"

One user reported that he had to disable every snd module in his rc.conf except for two: snd_hda_intel and snd_pcm_oss.

[deprecated] if the speakers don't mute when you plug in headphones, you may need to compile alsa (i use v1.0.18a ,here)

Extract the tar.bz2 and open a console on alsa source folder

1.execute this command : ./configure --with-cards=hda-intel --with-oss=yes --with-sequencer=yes
2.execute this command : make
3.execute this command : sudo make install
4.get alsa-utils with pacman
5.configure sound volume with alsamixer , reboot , and enjoy :)

Suspend and Hibernate

If you want to use Suspend to Ram using pm-utils you'll need the following command to resume properly:

pm-suspend --quirk-vbestate-restore

Note: Pm-suspend should work correctly without any quirks at the moment.

You can use this command not only to suspend from terminal but also in combination with acpid

If after closing the lid your machine doesn't wake up from suspend correctly and needs to be resumed multiple times, you can try using the following workaround. This is an excerpt from /etc/acpid/handler.sh file:

    button/lid)
       if [ `/bin/awk '{print $2}' /proc/acpi/button/lid/LID0/state` = closed ]; then
           /usr/sbin/pm-suspend
       fi
       ;;

In contrast hibernate works without "modifications" (except the ones mentioned in the pm-utils article).

If you are a kde4/kdemod user you can take advantage of powerdevil (included in kdemod-core/kdemod-kdebase-workspace since release 4.2). Screen brightness, cpu scaling, suspend and hibernate all work flawlessly, without any hack.

Fn Keys

You need at least kernel 2.6.28.4 to get the Fn keys to work correctly.

(Volume Controls worked out of the box in kdemod 4.2)

To bind the Fn keys to action, read Extra_Keyboard_Keys#The_quick_way and also Extra Keyboard Keys in Xorg

As an example, here is how to bind the keys for volume control :

1) install xbindkeys (and xbacklight for brightness controlls):

pacman -S xbindkeys xbacklight

2) crate a config file in your home directory :

vi .xbindkeysrc

3) with the following content :

"amixer sset Master 2+ &"
    m:0x0 + c:176
"amixer sset Master 2- &"
    m:0x0 + c:174
#"amixer sset Master 0 &"
"amixer sset Master toggle &"
    m:0x0 + c:160
#"sudo pm-suspend"
#    m:0x0 + c:223
"xbacklight +10"
    m:0x0 + c:233
"xbacklight -10"
    m:0x0 + c:232

4) run xbindkeys :

xbindkeys

and volume control should work within an X session !

to add aditional bindings, you can get the codes of most of the Fn-keys with

xbindkeys -k

For the keys that are not recongnized, see

dmesg |tail

to make the kernel recognize them.

(If your Screen is not bright enough, boot into Windows and set the Brightness to maximum)

(you can adjust Brightness during the boot process without returning into Windows and you need to set maximun brightness on battery only mode)

Saving Power

Needs to be written