Asus W6K00F01

Introduction
This work's aim is getting a reminder covering Gentoo on ASUS-W6F laptop. The working scheme was the following: As result the following things was described: In the addition, the following s/w bindings was described: As it turned out, there is no sense to build preferred s/w kit - portage packages can be broken. Fixing them or building from downloaded sources requires some qualification, so the one thing remains is making a choice between various alternatives. Only same moments described:
 * The rough copy is written online and notices was gotten from other en.gentoo-wiki.com participants;
 * Mediawiki with templates from en.gentoo-wiki.com installed locally following this guide, 0.6.3 used as PHP-interpeter;
 * The similar articles downloaded for offline-work;
 * The work was continued with the article deployed to the locally installed mediawiki;
 * Internet connection by various methods: Ethernet, Wireless and Bluetooth interfaces with network profiling;
 * According to p.41 of specs the following Flash memory cards support - SD/MMC/MS/MS Select, MS Duo (with MS adapter), MS Pro, MS Pro Duo (with MS Pro adapter);
 * Sound;
 * Framebuffer;
 * Power management;
 * Touchpad;
 * Fn+* keys;
 * Printing to remote Windows-host;
 * Bootloader, partitioning, USB-automounting configuration;
 * Boot process stages;
 * Things on which the s/w management depends: profile, gcc setup and portage settings;
 * ru_RU.UTF-8 as system's language, en_EN.UTF-8 manpages.
 * tiling window manager advantages by the example of ;
 * working with multi-volume archives;
 * AudioCD/mp3/DVD etc playback;

Hardware info
cat /proc/cpuinfo

lspci

lsusb

Wireless
To scan wireless networks within your range, you can use the following:

There exists several atoms with different wireless card firmwares, so in the way to find a proper firmware I tried to boot without it: dmesg &#124; grep iwl3945 for file in /usr/portage/net-wireless/iwl3945-ucode/* ; do echo $file && grep doins $file ; done

Bluetooth
[TODO ppp ...]

Localization
There exists more complete manuals how-to get UTF-8 (ru_RU.UTF-8 in my case), for example, here I'll just explain fundamentals. Multilanguage support mean the following things:

Portage compiler cache

 * http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=3#doc_chap3

Portage custom settings
For more stability, only CPU-related global USE flags used

Partitioning & mountpoints
fdisk -l &#124; egrep '/dev/sda[0-9]' &#124; awk '{ print $1 " " ($3-$2)*8225280/1024/1024 "Mb" }'

Bootloader
The package contains a few of valid  atoms, so I want to install atom with new modular version - Grub2. The unmasking, emerging, installing and configuring steps are described below (note that we're still in chroot'ed environment, so grub-install installation target is /dev/hda, not /dev/sda):

Sound
Now we can check volumes for all input/output audio devices by executing:

Also check that volume levels are saving when powering off system: grep SAVE_ON_STOP&#61; /etc/conf.d/alsasound There exists two moments with Audio CD:
 * You can't mount Audio CD, only play audio tracks or grab them to *.wav, *mp3, etc formats.

Note that if you want to play Audio CD's from non-root user, that user must exists in 'audio' group:

Framebuffer support
In the common way the framebuffer support depends of the following things:
 * display's physical capabilities and used graphics card;
 * fbcon driver compiled into kernel, so it running on top of the framebuffer driver;
 * framebuffer driver compiled into kernel or built as kernel module and it's dependencies;

The framebuffer drivers differs by acceleration support, they also have different setup algorythms depending of output type (CRT display or LCD matrix) described by their's manuals. The aim of this subsection's work is get framebuffer with 1280x800 resolution, so first that I trying to do is determine laptop's hardware capabilities. According to manual there exists several states of Gentoo's boot process, so I know two states when I can interact with graphics card manually: vbeinfo
 * bootloader state, when kernel isn't loaded yet (following output is valid for grub bootloader):
 * post-init state, when system is successfully booted:

vbetest

There exists several framebuffer drivers which have a reference to laptop's hardware: The tryout of intelfb gives a screen full of flickering and boot process ends with kernel panic, so I compiled uvesafb as kernel module following uvesafb::installation instructions with two differences:
 * vesafb, the supported video modes limited by Video BIOS, any type of acceleration is missing;
 * uvesafb as enhanced version of vesafb, it's also non-accelerated, but has additional features detailed here;
 * intelfb as native intel framebuffer driver.
 * in the option 2 Userspace VESA VGA graphics support is compiled as kernel module, not to kernel;
 * instead of option 8 there exists the following initscript:

Hibernate
There exists an situation when gentle and well-bred sparks came and says that they need to de-energize your flat. There is nothing for it but you want to restore your machine state with opened programs after turning it off, see S4-state below.

According to chapter 7.3.4 of ACPI specification there exists several power-saving system states: If you're turning your system into the some power-saving state, the system devices that supports only underneath-level states or S0-state only (full-powered) will be powered off. There also exists S5-state (soft-off), similar to S4, but doesn't save RAM-context to disk.
 * S1, when processors aren't executing instructions, but RAM-context is maintained;
 * S2, =S1, but conserve more power;
 * S3, =S2, but conserve more power;
 * S4, RAM-content is saving to disk and system shutdowns, so it doesn't consume any power, only RTC-clock is running off its own small battery.

Nowadays sleep states management is provided by two ways:
 * with power management options enabled in kernel;
 * using ;

I prefer the second method because it contains an power management possibility check: lshal &#124; grep power_management

The two first output lines says that S3 and S4 modes are supported, so let's go to S4 state, swap-partition will be used for RAM-context save and restore, resume= parameter must be added to of grub commandline, see Bootloader chapter.