Differences

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

--- doc:appunti:hardware:eeepc_debian [2010/10/31 21:11] – niccolo
+++ doc:appunti:hardware:eeepc_debian [2010/11/07 11:26] – 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 319: / Line 315: @@
 </code>
-====== Installing Debian Squeeze on the EeePC ======
+====== Debian Squeeze on the EeePC ======
 ===== X.org =====
@@ Line 363: / Line 359: @@
 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 =====
@@ Line 397: / Line 413: @@
 ===== Disk performances =====
-Asus EeePC 900, performances measured with **''hdparm -t''**
+Asus EeePC 900, disk performances measured with **''hdparm -t''**
 ^ /dev/sda  | 33.00 MB/sec  | First SSD, 4 Gb  |
@@ Line 403: / Line 419: @@
 ^ /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.