Using the Samsung NC10

[Ɗα√ϵς§]

THERE IS A NEW THREAD HERE FOR PCLOS 2010, WHICH SUPERCEDES THIS THREAD IF YOU ARE USING 2010. The new version is recommended due to changes in the kernel.

http://www.pclinuxos.com/forum/index.php/topic,69132.0.html

I have a Samsung NC10. It's a lovely piece of work, unfortunately it only comes with Windoze. Still I got mine so cheap that it didn't feel like I was paying the M$ Tax!

It comes with Windows XP pre-installed on a 160Gb drive, not bad for a small netbook. What is nice about the Windows installation is that it has not been done in such a way as to resist partition resizing. I was able to shrink the Windows partition down to under 40Gb with no trouble, leaving 120Gb for PCLinuxOS. When you consider that many netbooks have far less storage, it's not bad.

It has the nearest thing I've ever seen on one of this type of machine, to a real keyboard. Real chunky keys with good travel. They come a bit further forward as a result, leaving a rather small touchpad, but to be honest I always plug a mouse in. The touchpad is quite simple to use though.

Because it's not built with Linux in mind, there are a number of issues. Getting the best from this machine has been an ongoing job for me, and I will pass on what I've learned so far.

[Ɗα√ϵς§]

After installing the latest PCLinuxOS, either Mini-Me or 2009.2, you will of course do all the updates, this is important. And follow the instructions here:

http://www.pclinuxos.com/forum/index.php/topic,63698.0.html

to update to KDE4. As "user" go to the KDE4 Control Centre (Configure Your Desktop), and under Look and Feel > Desktop > Desktop Effects, ensure that "Enable Desktop Effects" is unchecked. The onboard graphics aren't up to much, but otherwise the machine can be surprisingly nippy!

You will need to run Synaptic and add the latest kernel, 2.6.27.31, and reboot to that. My experience was that with the 2.6.26.8 kernel, the webcam and detection of plugged in USB devices did not work after returning from suspend or hibernate.

And this is where some of the problems come in. Your wireless will have set itself up to use the madwifi drivers. They connect to the internet, for sure, what they don't do is come back on cleanly when you resume after a suspend or hibernate. So this is where you have to cross your fingers and delve in a bit as root.

Firstly, you need to run Synaptic and REMOVE the dkms-madwifi and madwifi packages. You will then need to edit the following file, as root. From the main menu PC > System > File Tools > Konqueror Super User Mode, and navigate to /etc and edit the file modprobe.preload -- simply right click on it, and choose "open with Kwrite". You need to add a line (anywhere in the list will do): ath5k - it must be on a line by itself with no other punctuation, not so much as a space.

EDIT (NEW): Next, navigate to /etc/modprobe.d and edit the file /etc/modprobe.d/blacklist and remove the line "blacklist ath5k" from it.

When you've done that, navigate to the folder /etc/udev/rules.d/ and delete the file: 70-persistent-net.rules

Then navigate to the folder /etc/sysconfig/network-scripts/ and delete the file: ifcfg-ath0

When you've got this far, you can close Konqueror.

Finally, use the PCLinuxOS Control Centre (Configure your computer) > Network and Internet > Remove a Connection and remove the connection ath0.

After you've done that, you can reboot. There will be no wireless network connection when you do. Don't use the net-applet icon in your system tray, use PCLinuxOS Control Centre > Network and Internet > Set up a new network interface.

Once this is done and you're up and running, you will find that the wireless can recover from a Suspend or Hibernate, and after a few seconds, your wireless will reconnect.

[Ɗα√ϵς§]

POWER SAVING

In order to make best use of the power saving features, it's best to avoid using any superfluous power saving programs. Don't install powersaved or guidance. In the KDE Control Centre, you can set your own preferences on a per-user basis. The only thing missing is a nice icon in the system tray, but never fear, there is a plasmoid that can do everything you want. As a plasmoid, you can put it on your main panel, another panel, or straight onto the desktop. It's called Battery Monitor. It doesn't look much until you click on it and see stuff, including a slider to adjust your screen brightness (to enable the keyboard shortcuts, read ahead). Try not to make it too dark (until you have enabled the keyboard shortcuts) or you won't be able to see the slider or the mouse to turn it up again, but, hey it works!!

[Ɗα√ϵς§]

KEYBOARD

Using the KDE Control Centre, > Personal > Regional and Language > Keyboard Layout, select the keyboard: Samsung SDM 4510P from the drop down list. At this time, this will not enable all keys, but will get the Volume and Mute going. The Touchpad on/off works through the hardware anyway, (EDIT ADD:) as does the Suspend to RAM.

EDIT ADD: I have tried using Keytouch on this machine, but it causes a number of problems, for example, the "A" key stops working!!

As I learn stuff, I will add how to enable further keys.

[Ɗα√ϵς§]

I have made edits to replies 1 and 3, and highlighted them.

[Ɗα√ϵς§]

KEYBOARD PART TWO: PREPARING KEYS FOR USE

With the 2.6.27.31 kernel (and later), a number of keys on the keyboard are detected but not given an output which can be used by KDE4. Fortunately we have a program that can fix that! It's called "xmodmap". Firstly, open your file manager (Dolphin - just your normal user) and ensure it is set to View > Show Hidden Files. Right click in space to create an empty file called .Xmodmap (notice the dot). Then right click on it, and paste in the following contents:

Code: [Select]

keycode 212 = XF86MonBrightnessUp
keycode 101 = XF86MonBrightnessDown
keycode 241 = F22
keycode 214 = F24
keycode 159 = F25
keycode 151 = F27
keycode 171 = F28
keycode 243 = F29

and save! Note that the available F keys are named by adding 20 to the number without the Fn. The Fn-F3 for Euro is a Windows kludge, producing a series of keypresses (ALT-0,1,2,8), so I've decided to leave it alone.

EDIT: Now navigate to .kde4/Autostart and create a file: 14_setkeys

Right click on it and add the following content:

Code: [Select]

#/bin/sh
xmodmap ~/.Xmodmap

After saving it, right click on it, select Properties, and choose the Permissions tab, tick "is executable" and OK. Click on it to run it now. It will automatically run every time you boot into KDE4.

Despite the encouraging keyname, the Brightness Keys won't work in KDE4 at this time. But you can, now, get the battery monitor key working. I mentioned above using the "Battery Monitor" applet. Well right kick on its icon/plasmoid, and you will be able to set up a Keyboard Shortcut. Use Fn-F2, this will show as F22.

We're making progress!

[flux]

I have here netbooks with fn-keys which were not recognized by default, but there was a message like

Code: [Select]

atkbd.c: Unknown key pressed (translated set 2, code 0xaa on isa0060/serio0).
atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.

in /var/log/messages after pressing the fn-key.

With this message you can enable the fn-keys in this way (as root in a terminal or as user with 'sudo'):

Code: [Select]

setkeycodes e02a nnn
nnn is a number e. g. 128

To have the correct number here you have to check at first your keyboard and free keycodes with:

Code: [Select]

xmodmap -pke
But the nnn is not identical with the keycodes! Just choose 128 and check with

Code: [Select]

xev
the given keycode (could be e. g. 234). If this keycode (I assume 234) is not used (in the output of xmodmap -pke) you can use the nnn = 128 for the unknown key shown in /var/log/messages.

Afterwards the fn-key can be used for mapping a command to it (via .Xmodmap or xbindkeysrc).

I hope that I could describe it in a correct and understandable way ... English is not easy ...

flux.

[Ɗα√ϵς§]

Flux: Once you add the 2.6.27.31 kernel in the NC10, there are no more unknown keys. I've sat there in the past with the situation you describe, with other extended keyboards in the past, but you do not need to do this with the NC10. You will not get error reports because they do produce codes. The problem is that the next stage, via xmodmap, still needs to be allocated.

[flux]

My post was just a generic description of "what can be" or "what could be" ... and my way to solve it. Not more ...

flux.

[Ɗα√ϵς§]

EDIT: There are two ways to get the backlight keys working. One is in the advanced tips section mentioned here. The advanced method uses direct addressing to the hardware. Advantage - very fast response. If you read further down this page the non-advanced method uses a program called xbacklight. This works a little more slowly but works in conjunction with the power-saving system and is recommended for all but power users.

I've put the advanced tips here:

http://www.pclinuxos.com/forum/index.php/topic,64911.0.html

This is in the advanced users section, and is suitable only for those who are prepared to b0rk their system!

[Ɗα√ϵς§]

Note that I made an error now corrected in reply #5, the file is created in ~/.kde4/Autostart

[Ɗα√ϵς§]

BACKLIGHT KEYS

Firstly, you will need to install the following packages:

xbindkeys
xbacklight

Next open Konqueror (Super User Mode), and navigate to /usr/local/bin

Right click and create a text file, backlight-toggle

Now right click on the backlight-toggle logo, and open with KWrite. Cut and paste in the following code:

Code: [Select]

#/bin/bash
#by davecs

#get existing brightness
BRTNESS=`xbacklight -get | cut -d "." -f1`

if [ "$BRTNESS" = "100" ] ; then
   BRTNESS2=0
else
   Y=$(( $BRTNESS / 33 ))
   Y=$(( $Y + 1 ))
   Y=$(( $Y * 33 ))
   Y=$(( $Y + 1 ))
   BRTNESS2=$Y
fi

xbacklight -set $BRTNESS2

Right click again on the icon > Properties > Permissions > and check "is executable".

Close the root konqueror, and open a normal Dolphin and set under View > Show Hidden Files. Create a file called .xbindkeysrc , right click on the resulting icon and open with KWrite. Cut and paste in the following:

Code: [Select]

# For the benefit of emacs users: -*- shell-script -*-
###########################
# xbindkeys configuration #
###########################
#
# Version: 1.8.3
#
# If you edit this file, do not forget to uncomment any lines
# that you change.
# The pound(#) symbol may be used anywhere for comments.
#
# To specify a key, you can use 'xbindkeys --key' or
# 'xbindkeys --multikey' and put one of the two lines in this file.
#
# The format of a command line is:
#    "command to start"
#       associated key
#
#
# A list of keys is in /usr/include/X11/keysym.h and in
# /usr/include/X11/keysymdef.h
# The XK_ is not needed.
#
# List of modifier:
#   Release, Control, Shift, Mod1 (Alt), Mod2 (NumLock),
#   Mod3 (CapsLock), Mod4, Mod5 (Scroll).
#
# The release modifier is not a standard X modifier, but you can
# use it if you want to catch release events instead of press events

# By defaults, xbindkeys does not pay attention with the modifiers
# NumLock, CapsLock and ScrollLock.
# Uncomment the lines above if you want to pay attention to them.

#keystate_numlock = enable
#keystate_capslock = enable
#keystate_scrolllock= enable

"xbacklight +5"
  m:0x0 + c:212

"xbacklight -5"
  m:0x0 + c:101

"xbacklight -set 100"
  m:0x4 + c:212

"xbacklight -set 60"
  m:0x4 + c:101

"/usr/local/bin/backlight-toggle"
  m:0x0 + c:159

##################################
# End of xbindkeys configuration #
##################################

Now navigate to .kde4/Autostart and right click on the file 14_setkeys you created earlier. add the following line:

xbindkeys

And save. Now if you log out and log in, your Brightness keys will be working.

Fn+up/Fn+down work as you'd expect, Ctrl-Fn-Up sets a "powered" default of 100% brightness, and Ctrl-Fn-Down sets a "battery" default of 60% brightness. Fn-F5 cycles through 0, 34%, 67%, 100% brightness.

[Ɗα√ϵς§]

USING THE WIRELESS KEY

At present, the kernel does not have a function to switch the wireless on and off, as with, for example, the eeePC 900. I'm not sure that simply disabling it by unloading the necessary module will necessarily save power, it will be possibly working but not connected to anything. I could be wrong. In any case, the whole point of a netbook is a portable internet machine.

My use of the Wireless Key is to get the dialog up to pick signals and log into one. This is normally root level. So in order to make it available to non-root users without a password, we have to use "sudo". That is not the way we normally do things, but in this case it will be buried in a text file, and will be invisible in day to day use.

Firstly you have to make a change to the file at /etc/sudoers which can only be edited as root, and it's dangerous to make an error. Normally you should only edit it using the program visudo, which can only be run as root. This will ensure that any mistakes are captured. There is a simpler way, but first I suggest you make a copy of the file /etc/sudoers on a memory stick, and if you mess up and your system is b0rked, you can run a live CD and put the original file back! Note that you'll need to drag /etc/sudoers from a Root File Manager, it's that sensitive that it won't even let you copy it from a user level one.

After backing up sudoers, open a terminal as root. PC > System > Terminals > Terminal Super User Mode

You will be prompted for the root password, it will not display as you type it, when typed press ENTER. You should find the prompt contains the word "root" to show you are in root mode. Now type in the following line and press ENTER. It must be typed EXACTLY as shown, with TWO "greater than" signs. You can highlight the line below and use the mouse middle button in the terminal to make it so:

Code: [Select]

echo 'ALL localhost = NOPASSWD: /usr/sbin/drakroam' >> /etc/sudoers
Once you've done that, close the terminal and open your own Home folder, set to show hidden files as before, right click on .xbindkeysrc and open with kwrite. Add the following pair of lines after the other pairs:

Code: [Select]

"sudo /usr/sbin/drakroam"
  m:0x0 + c:243

Save. Now log out and in. Pressing Fn+F9 will now result in the wireless signals chooser coming up.

This leaves F4 (ostensibly for Internal/External Monitor which I cannot test) and F7/F8 which you can add stuff to. Ideas anyone?

[Ɗα√ϵς§]

You may notice that if you switch on the NC10 without the power connected, you get a very dull screen. This uses the "hardware" method of setting the brightness, and all attempts to vary it can only make it duller.

In order to get the hardware brightness setting back to 100%, so you can adjust it fully using the brightness up/down controls etc, you need to edit the file:

/etc/rc.d/rc.local

Run Konqueror Super User Mode, navigate to /etc/rc.d, right click on rc.local and open with kwrite. Add the following line:

setpci -s 00:02.1 F4.B=FF

Save. Now when you boot the computer the brightness will always come on 100%. You can now adjust it all the way using the keys set up earlier, and the slider on the battery monitor, to turn the screen down to save power. In certain lighting conditions, a dull screen will not be usable and you'll have to put up with the battery running down more quickly.

[rick0612]

davecs,

The rc.local edit caused my keyboard to act strangely. I had to press the Fn key to get a p or 7, 8, 9, 0 (zero) or anything other than blue key.

After removing that line and rebooting, everything is OK again.

Rick.