Differences

This shows you the differences between two versions of the page.

--- doc:appunti:hardware:eeepc_debian [2010/10/31 17:40] – niccolo
+++ doc:appunti:hardware:eeepc_debian [2014/01/17 00:06] (current) – [Optimizing Xfce] niccolo
@@ Line 1: / Line 1: @@
-====== Installing Debian Lenny on the EeePC ======
+====== Debian Lenny on the EeePC ======
 The main source of information is **[[http://debian-eeepc.alioth.debian.org/|Debian for the Asus Eee PC]]**, the following notes is my personal recipe.
 ===== Kernel 2.6.26 on the EeePC 900 =====
@@ Line 175: / Line 173: @@
   * /etc/default/eeepc-acpi-scripts
 ===== Changing the original GRUB menu =====
@@ Line 218: / Line 214: @@
 </file>
-To have the **compose key** help in typing characters that are not present on the keyboard, you can edit /etc/X11/xorg.conf following this example: [[doc:appunti:linux:tux:localizzazione#caratteri_non_presenti_sulla_tastiera]].
+To have the **compose key** help in typing characters that are not present on the keyboard, you can edit /etc/X11/xorg.conf following this example: [[doc:appunti:linux:tux:localizzazione#caratteri_non_presenti_sulla_tastiera_kde_e_non_solo]].
 ===== Controllare la frequenza =====
@@ Line 319: / Line 315: @@
 </code>
-====== Installing Debian Squeeze on the EeePC ======
+====== Debian Squeeze on the EeePC ======
+===== X.org =====
+Default installation does not create an ''/etc/X11/xorg.conf'' file. We can merge some configuration snippet using the **''InputClass''** directive.
+The first is to activate the **touchpad tapping**, the second is to enable the **compose key** (using the menu key) and the **Euro sign** on the Alt-e combination.
+**''/etc/X11/xorg.conf.d/synaptics.conf''**
+<file>
+Section "InputClass"
+    Identifier      "Touchpad"                      # required
+    MatchIsTouchpad "yes"                           # required
+    Driver          "synaptics"                     # required
+    Option          "MinSpeed"              "0.5"
+    Option          "MaxSpeed"              "1.0"
+    Option          "AccelFactor"           "0.075"
+    Option          "TapButton1"            "1"
+    Option          "TapButton2"            "2"     # multitouch
+    Option          "TapButton3"            "3"     # multitouch
+    Option          "VertTwoFingerScroll"   "1"     # multitouch
+    Option          "HorizTwoFingerScroll"  "1"     # multitouch
+    Option          "VertEdgeScroll"        "1"
+    Option          "CoastingSpeed"         "8"
+    Option          "CornerCoasting"        "1"
+    Option          "CircularScrolling"     "1"
+    Option          "CircScrollTrigger"     "7"
+    Option          "EdgeMotionUseAlways"   "1"
+    Option          "LBCornerButton"        "8"     # browser "back" btn
+    Option          "RBCornerButton"        "9"     # browser "forward" btn
+EndSection
+</file>
+**''/etc/X11/xorg.conf.d/compose.conf''**
+<file>
+Section "InputClass"
+    Identifier      "keyboard-all"
+    MatchIsKeyboard "yes"
+    Driver          "evdev"
+    Option          "XkbOptions"  "lv3:ralt_switch, compose:menu, eurosign:e"
+EndSection
+</file>
+Per vedere le ''XkbOptions'' attive usare il comando:
+<code>
+setxkbmap -print
+xkb_keymap {
+        xkb_keycodes  { include "evdev+aliases(qwerty)" };
+        xkb_types     { include "complete"      };
+        xkb_compat    { include "complete"      };
+        xkb_symbols   { include
+            "pc+us+it:2+gr:3+inet(evdev)+level3(ralt_switch)+compose(menu)+eurosign(e)" };
+        xkb_geometry  { include "pc(pc105)"     };
+};
+</code>
+Per impostare le opzioni //una tantum// da riga di comando:
+<code>
+setxkbmap -option lv3:ralt_switch,compose:menu,eurosign:e
+</code>
+===== xfce =====
+I stay with Xfce, also because I got some problem installing Lxde in a KVM virtual machine, where windows move down into the screen, falling out of the bottom border.
+Some useful Xfce plugins:
+  * **''xfce4-xkb-plugin''**
+  * **''xfce4-battery-plugin''**
+  * **''xfce4-mount-plugin''**
+I installed the **network-manager-kde** package, which works into the Xfce systray. To let the Network Manager to start automatically at logon:
+  - Xfce menu, //Settings//, //Session and Startup//
+  - //Application Autostart//, //Add//: **''knetworkmanager''**
+The session management approach **does not work**. Once ''knetworkmanager'' is started, into the //Session// tab of //Session and Startup//, there is the //Save Session// button. Unfortunately the application is not restored at next logon.
+The KDE services approach **does not work** too: there is a //Launch KDE services on startup// into the //Advanced// tab of //Session and Startup//, but ''knetworkmanager'' is not started at logon.
+Adding the user into the **''powerdev''** and **''netdev''** groups, allows to configure the netowrk interface and power down the system.
+FIXME There is a problem if the Xfce panel has the **autohide** option enabled: the ''knetworkmanager'' and ''kwalletmanager'' icons don't get disaplayed correctly into the systray; they are truncated and almost invisible.
+===== Web browser =====
+To choose Mozilla Iceweasel instead of Konqueror:
+<code>
+update-alternatives --config x-www-browser
+</code>
+===== Disk performances =====
+Asus EeePC 900, disk performances measured with **''hdparm -t''**
+^ /dev/sda  | 33.00 MB/sec  | First SSD, 4 Gb  |
+^ /dev/sdb  | 25.46 MB/sec  | Second SSD, 16 Gb  |
+^ /dev/sdc  | 14.51 MB/sec  | MiniSD card, 4 Gb  |
+==== TRIM command ====
+Solid State Disks should support the [[wp>TRIM]] command, this is a command used by the operating system to inform a SSD that a particular sector is no longer used and can be internally wiped.
+It seems that EeePC 900 disks do not support TRIM.
+For on-line operation, Linux kernel supports TRIM starting from 2.6.33. For off-line operation **''hdparm''** supports TRIM starting from version 9.17. With ''hdparm'' sources there is the **''wiper.sh''** script, which can be run in this way:
+<code>
+mount -o ro /dev/sda1 /media/sda1/
+./wiper.sh /dev/sda1 --commit --verbose
+wiper.sh: Linux SATA SSD TRIM utility, version 2.8, by Mark Lord.
+rootdev=/dev/sdc1
+fsmode2: fsmode=read-only
+/dev/sda: DSM/TRIM command not supported, aborting.
+</code>
+==== Journal data writeback ====
+To gain a little in disk performances, you can enable writeback for journal data. Here it is an example for the ''/dev/sdb1'' partition, formatted as ext3 and mounted under ''/home''.
+<code>
+tune2fs -o journal_data_writeback /dev/sdb1
+mount -o remount,data=writeback /dev/sdb1
+</code>
+To enable this option on bootstrap, you have to change **''/etc/fstab''**:
+<file>
+/dev/sda1  /home  ext3  defaults,noatime,data=writeback  0  1
+</file>
+For the root filesystem, it is required also to pass the option to the kernel, using a GRUB parameter. With Debian Squeeze the option is added into **''/etc/default/grub''**:
+<file>
+GRUB_CMDLINE_LINUX_DEFAULT="rootflags=data=writeback quiet"
+GRUB_CMDLINE_LINUX="rootflags=data=writeback"
+</file>
+Run **''update-grub''** to install that option into **''/boot/grub/grub.cfg''**.
+===== WiFi interface =====
+The WiFi interface is supported by the new **ath5k** kernel module. Once loaded, the **wlan0** interface is available.
+The new **''iw(8)''** command can be used to manipulate the device configuration, its purpose is similar to the ''wlanconfig'' command, used with the old ''ath_pci'' kernel module.
+Here it is an example on how to deconfigure/reconfigure the interface from scratch:
+<code>
+iw dev wlan0 del
+iw phy phy1 interface add wlan0 type managed
+</code>
+To use the WiFi interface with **''kismet''**, you need this in the **''/etc/kismet/kismet.conf''** configuration file:
+<file>
+source=ath5k,wlan0,atheros
+</file>
+After exiting ''kismet'', the ''wlan0'' interface must be reconfigured as explained above, and ''knetworkmanager'' should be restarted.