Difference between revisions of "Samsung NC10"

From ArchWiki
Jump to: navigation, search
(Audio)
(wikify some external links, use https for archlinux.org)
(48 intermediate revisions by 20 users not shown)
Line 1: Line 1:
[[Category:Laptops (English)]]
+
[[Category:Samsung]]
[[Category:Getting and installing Arch (English)]]
+
This article aims to provide information on installing and setting up Arch Linux on the Samsung NC10.
[[Category:HOWTOs (English)]]
+
{{stub}}
+
  
=Introduction=
+
A lot of the information is derived from the [https://bbs.archlinux.org/viewtopic.php?id=58117 Arch Forum], and from several hints scattered around in the ArchWiki.
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 [http://bbs.archlinux.org/viewtopic.php?id=58117 Arch Forum] and several hints scattered around in the ArchWiki.
+
==Common Issues==
  
=Installation=
+
* using KMS (as of xorg-video-intel 2.8.1), No brightness control with xbacklight. ([https://bbs.archlinux.org/viewtopic.php?id=74914 workaround with setpci], the issue might be solved with the next intel driver 2.9)
 +
* On kernel 2.6.29 :
 +
** webccam works perfectly.
 +
** All fn-keys can be bound, except fn-f4
 +
** suspend to ram and to disk work perfectly (without any quirks)
 +
** rfkill controls for bluetooth and Wifi do not work (but it's possible to write a script to do it and bind it to the propper key with xbindkeys)
 +
* On kernel 2.6.30 :
 +
** webcam stopped working correctly.
 +
** fastboot feature (not NC10 specific)
 +
* On kernel 2.6.31 :
 +
** webcam is working again
 +
** rfkill interface is working.
 +
* On kernel 3.6.2-1 and 3.6.3-1:
 +
** system will not boot unless acpi=off is added as kernel parameter
 +
** "dmesg | grep microcode" will show "Atom PSE erratum detected", see [[Microcode|Microcode]] page for a solution
  
As all other netbooks the NC10 doesn't have an optical drive so you have to install Arch Linux either through an [[Install_from_USB_stick|USB pen drive]] or via an external USB CD-ROM drive.
+
==Installation==
  
Before you can start the process of installation you have to disable acpi.  
+
Use the USB image provided at the official download locations or the ISO if you have an external optical drive. You can also use unetbootin to easily create a boot device. If you use an usbkey, be aware that you must (arguably) format it in FAT32.
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==
  
=Configure your installation=
+
===Network===
==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:
+
LAN uses the sky2 module and should work out-of-the-box. Kernels prior to 2.6.37 use the ath5k module for WLAN. Later kernels use brcmsmac/brcmfmac and may require blacklisting bcma. See [[Broadcom wireless#brcmsmac/brcmfmac]] for details.
* ath_hal
+
* ath_pci
+
* wlan
+
  
==Video==
+
===Video===
 +
 
 +
===Initial Brightness===
 +
The brightness can be set with the following command:
 +
 
 +
setpci -s 00:02.1 F4.B=FF
 +
 
 +
 
 +
Where FF is the highest level of brightness. This parameter moves in the range 00 to FF. Don't set it too low otherwise your backlight will turn off!
 +
 
 +
===Graphics Adapter===
 
The Video controller is a typical Intel chipset that works with the xf86-video-intel driver.
 
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.
+
To save some interrupts, and therefore power, you can disable dri in your xorg.conf. This disables 3D effects; however if you do not need them this could be an option.
 
  Section "Device"
 
  Section "Device"
 
  Option "NoDRI"
 
  Option "NoDRI"
Line 42: Line 55:
 
  EndSection
 
  EndSection
  
===External VGA===
+
====External VGA====
External VGA works out of the box with xrandr
+
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 :
+
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
 
  xrandr --output VGA --mode 1280x1024 --rate 60
Line 51: Line 64:
 
Dual head positioning works also perfectly : [[Xorg#Multi-monitor_setups]]
 
Dual head positioning works also perfectly : [[Xorg#Multi-monitor_setups]]
  
===Tweaks===
+
===Audio===
Are there any?
+
The audio device is an Intel HD.  You will need to follow the instructions at [[ALSA#No_Sound_with_Onboard_Intel_Sound_Card]] to get output from the main speakers.
  
==Audio==
+
Since alsa 1.0.19 distributed in archlinux extra repository, you do not need to manually install alsa driver. Everything is working out of the box: onboard microphone and speakers, audio off on earphone plugging.
The audio device is an Intel HD and should work without modifications. 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.
+
  
the speakers don't mute when you plug in headphones, you need to compile alsa (i use v1.0.18a ,[ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.18a.tar.bz2 here])  
+
'''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 sensible 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 do not mute when you plug in headphones, you may need to compile alsa (i use v1.0.18a ,[ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.18a.tar.bz2 here])  
  
 
Extract the tar.bz2 and open a console on alsa source folder
 
Extract the tar.bz2 and open a console on alsa source folder
Line 67: Line 89:
 
  5.configure sound volume with alsamixer , reboot , and enjoy :)
 
  5.configure sound volume with alsamixer , reboot , and enjoy :)
  
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.
+
===Suspend and Hibernate===
 
+
If you want to use Suspend to RAM using [[pm-utils]] then you'll need the following command to resume properly:
==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
 
  pm-suspend --quirk-vbestate-restore
  
Line 86: Line 106:
 
In contrast hibernate works without "modifications" (except the ones mentioned in the [[pm-utils|pm-utils article]]).
 
In contrast hibernate works without "modifications" (except the ones mentioned in the [[pm-utils|pm-utils article]]).
  
==Fn Keys==
+
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.
 +
 
 +
Right after resume you may notice (i.e. in powertop) lost support for C2 and C4 CPU states. Don't panic. Those modes are likely to return within several minutes.
 +
 
 +
===Fn Keys===
 
You need at least kernel 2.6.28.4 to get the Fn keys to work correctly.
 
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)
 
(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#Using_your_Desktop_Environment_tools|Extra Keyboard Keys in Xorg]]
+
To bind the Fn keys to action, read [[Extra_Keyboard_Keys#The_quick_way]] and also [[Extra_Keyboard_Keys_in_Xorg#Using_your_Desktop_Environment_tools|Extra Keyboard Keys in Xorg]]. The suspend key (Fn+ESC) and disable touchpad (Fn+F10) keys should work out of the box. Note that suspend key is handled in /etc/acpi/handler.sh (see "power/sleep" case entry). If you use pm-utils, you should substitute the default action with the call to pm-suspend or pm-hibernate.
  
 
As an example, here is how to bind the keys for volume control :
 
As an example, here is how to bind the keys for volume control :
  
1) install xbindkeys (and xbacklight for brightness controlls):
+
1) install ''xbindkeys'' (and ''xbacklight'' from package ''xorg-server-utils'' for brightness control):
  pacman -S xbindkeys xbacklight
+
  pacman -S xbindkeys xorg-server-utils
  
 
2) crate a config file in your home directory :
 
2) crate a config file in your home directory :
Line 115: Line 139:
 
  "xbacklight -10"
 
  "xbacklight -10"
 
     m:0x0 + c:232
 
     m:0x0 + c:232
 +
For your NC10 Fn keysums may differ. If any Fn keys do not work with the above .xbindkeysrc, you should check the keysum values with
 +
xbindkeys -k
  
 
4) run xbindkeys :
 
4) run xbindkeys :
 
  xbindkeys
 
  xbindkeys
and volume control should work within an X session !
+
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  
+
To add additional bindings, you can get the codes of most of the Fn-keys with  
 
  xbindkeys -k
 
  xbindkeys -k
  
Line 131: Line 157:
 
(you can adjust Brightness during the boot process without returning into Windows and you need to set maximun brightness on battery only mode)
 
(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==
+
===Power saving===
Needs to be written
+
See [[power saving]].
 +
 
 +
===BIOS===
 +
There is no official support from Samsung on how to upgrade your BIOS from anything else than Windows XP / 7, although there's an exellent guide on how to update your BIOS without Windows installed on your computer at all on Vorias forum:
 +
http://www.voria.org/forum/viewtopic.php?t=248

Revision as of 15:39, 4 December 2012

This article aims to provide information on installing and setting up Arch Linux on the Samsung NC10.

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

Common Issues

  • using KMS (as of xorg-video-intel 2.8.1), No brightness control with xbacklight. (workaround with setpci, the issue might be solved with the next intel driver 2.9)
  • On kernel 2.6.29 :
    • webccam works perfectly.
    • All fn-keys can be bound, except fn-f4
    • suspend to ram and to disk work perfectly (without any quirks)
    • rfkill controls for bluetooth and Wifi do not work (but it's possible to write a script to do it and bind it to the propper key with xbindkeys)
  • On kernel 2.6.30 :
    • webcam stopped working correctly.
    • fastboot feature (not NC10 specific)
  • On kernel 2.6.31 :
    • webcam is working again
    • rfkill interface is working.
  • On kernel 3.6.2-1 and 3.6.3-1:
    • system will not boot unless acpi=off is added as kernel parameter
    • "dmesg | grep microcode" will show "Atom PSE erratum detected", see Microcode page for a solution

Installation

Use the USB image provided at the official download locations or the ISO if you have an external optical drive. You can also use unetbootin to easily create a boot device. If you use an usbkey, be aware that you must (arguably) format it in FAT32.

Configure your installation

Network

LAN uses the sky2 module and should work out-of-the-box. Kernels prior to 2.6.37 use the ath5k module for WLAN. Later kernels use brcmsmac/brcmfmac and may require blacklisting bcma. See Broadcom wireless#brcmsmac/brcmfmac for details.

Video

Initial Brightness

The brightness can be set with the following command:

setpci -s 00:02.1 F4.B=FF


Where FF is the highest level of brightness. This parameter moves in the range 00 to FF. Don't set it too low otherwise your backlight will turn off!

Graphics Adapter

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; however if you do not 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

Audio

The audio device is an Intel HD. You will need to follow the instructions at ALSA#No_Sound_with_Onboard_Intel_Sound_Card to get output from the main speakers.

Since alsa 1.0.19 distributed in archlinux extra repository, you do not 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 sensible 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 do not 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 then 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.

Right after resume you may notice (i.e. in powertop) lost support for C2 and C4 CPU states. Don't panic. Those modes are likely to return within several minutes.

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. The suspend key (Fn+ESC) and disable touchpad (Fn+F10) keys should work out of the box. Note that suspend key is handled in /etc/acpi/handler.sh (see "power/sleep" case entry). If you use pm-utils, you should substitute the default action with the call to pm-suspend or pm-hibernate.

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

1) install xbindkeys (and xbacklight from package xorg-server-utils for brightness control):

pacman -S xbindkeys xorg-server-utils

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

For your NC10 Fn keysums may differ. If any Fn keys do not work with the above .xbindkeysrc, you should check the keysum values with

xbindkeys -k

4) run xbindkeys :

xbindkeys

and volume control should work within an X session!

To add additional 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)

Power saving

See power saving.

BIOS

There is no official support from Samsung on how to upgrade your BIOS from anything else than Windows XP / 7, although there's an exellent guide on how to update your BIOS without Windows installed on your computer at all on Vorias forum: http://www.voria.org/forum/viewtopic.php?t=248