From The Chakra Project - Wiki

Using a 701 Surf 4 GB SSD with 2 GB RAM

Recommended install, use the usb-img. There is a "modification" I have made where I used the cd iso, and copied the contents to a partition, and made a grub entry. That is a bit detailed for now and time permitting, I can put that info here.

Why not just hard install Arch Chakra to the HD or device? First, I have 2 GB RAM and the live session runs from RAM and it is FAST. My resulting "install" is half the size in GB of a regular install. It is on removable media, so I can still have a native OS on the machine.

If you are using a large capacity SD/USB, You can re-partition it after the install (using dd on the device) so that the Chakra target partition is at least 3GB. The partition will be mounted read only+ with the running system so the only thing you can do is save your session here when you log out. The other partition can be for storage of files. You'll need this because you don't want to store a whole lot in your running home directory... live=fast=but limited space.

+ if you run the remount command, and you know what you are doing, you can, from the running live system from the SD or usb, remount /.livesys/medium/ (hidden) as rw, and you can do so only as root.

Ready?

1. Get the Chakra usb img
2. Boot it
3. Customize it*
4. Logout
5. Save session appears in terminal

<enter> if you only made minimal cosmetic changes, and just installed the LAN driver and maybe wireless driver (all these files are very small and there are not very many).

Use option 1 if you upgraded, installed wine programs, etc. More files = huge saved overlay... this option is slow, but makes for more efficient boots later on. You only should only need to do this once in a while. Go make a sandwich, take a shower, whatever.

To remedy the huge overlay and saving time once all of your major modding is done, see this http://chakra-project.org/wiki/index.php/Helpful_hint_USB_img_and_other_variants_of_running_%22live%22

• Customizing:

First http://wiki.archlinux.org/index.php/CPU_Frequency_Scaling

You will need to use p4_clockmod with the 701. Not sure what the atom uses... but try whichever one inserts with modprobe.

The wireless and wired LAN are supported in CHAKRA ALPHA 2 but ath5k does not seem to be "stable" or fast for me so I blacklisted it. I created the file /etc/modprobe.d/blacklist and added blacklist ath5k I then went with ndiswrapper. None needed for LAN or wifi, unless your wifi is flaky with ath5k like mine was: if so, (see top of post) to blacklist it and use

sudo nano /etc/modprobe.d/blacklist

• blacklist ath5k:

then ctrl-o to write out then ctrl-x to exit

sudo ifconfig wlan0 down
sudo rmmod ath5k

• you'll need your WinXP driver disk:

sudo ndiswrapper -i /PathToFile/xxxx.inf
sudo ndiswrapper -ma
sudo ndiswrapper -mi
sudo depmod -a
sudo ifconfig wlan0 up

(this probably will give you an error, so you will need to reboot AND CHOOSE 'ENTER' OR OPTION '1' WHEN YOU GET THE EXIT SHELL PROMPT.

It should then just come up on the next boot as wlan0 in the WICD tray icon.

• Advanced Customizing: (Any or all or none of these can be done)

• This is quite optional (if you are not having trouble with anything, skip this and save yourself some trouble --> Upgrade most packages except kernels, drivers (video) for anything but intel and bootloader (grub) references.

Note: do might need to do a bit at a time b/c your RAM disk will become too full and you'll crash. - You'll have to use option 1 on saving the overlay... this option remounts the resulting squashfs file on the next boot, [the simple first option just restores everything to your ramdisk and this would not be good. Install things you want (see note above)] -->If you have 512 MB still, don't bother as this will take forever and a day and just install the minimum items you need and don't bother upgrading much.

• kdesu kuser (and create your own login/password) run

sudo passwd root (and create your down sudo / kdesu password)

you will have to add your username to the sudoer's file. This is a bit beyond the scope of this wiki, but I had issues with sudo visudo, (error about vim not being found) so I did a really unacceptable thing and ran "sudo nano /etc/sudoers" and copied the references to the "live user" to the new lines, and then just very carefully wrote over the references to "live" with my new username. Make sure it works before you logout and save your session by "sudoing" some commands. I will get yelled at for doing it this way:-)

As a final step to this, in /usr/sahre/config/kdm/kdmrc, I did a search and replace: replace "live" with your username. Best way:

kdesudo kate /usr/sahre/config/kdm/kdmrc

Some of the FN keys work with the kernel's ACPI, but not all of them so I needed to follow this at the http://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_the_Asus_EEE_PC

One issue after doing this is that you will need to disable some of the acpi scripts in /etc/acpi as per my post here: http://bbs.archlinux.org/viewtopic.php?id=64180 Or Sleep/Wake won't work properly. (issue is that this ACPI conflicts with what powerdevil wants to do with sleep/suspend/hibernate/lidclose/powerbutton)

The wifi button still does not work properly; Fn+F2 will say "wireless on" and won't shut it off However, I had luck with doing this

create a shell script called rfkill and put it in /usr/bin

#!/bin/bash
echo 0 > /sys/class/rfkill/rfkill0/state
exit 0

make this executable. Issue the command from the terminal "sudo rfkill" or if you want to get fancy, you can create a link for it in the menu, and the command should be

kdesu rfkill

Oddly, if you press Fn+F2 again, it will bring it back up.

Something is odd with the toggling so if someone fixes that, then we can amend this.

To bring it back up manually from the command line

sudo echo 1 > /sys/class/rfkill/rfkill0/state

will bring it back up, but for some reason I had to

sudo su

then run the command as "su"

With just with sudo, it gave me a permissions error

If you have a 701 and want to clock up the front side bus from 70% to up to 100%, follow this http://wiki.eeeuser.com/howto:overclockfsb Note: once you unip the tarball, you will have to open /eee-pc/module/eee.c in a text editor (like kate) and follow instructions according to http://code.google.com/p/eeepc-linux/issues/detail?id=10 or it will not compile. Once you modify that file: Enter the directory where the makefile is and run "make" Copy [as root] the resulting eee.ko into /lib/modules/2.6.27-ARCH/kernel/drivers and the rest of the wiki works fine for this. If you do this, you will need to bring the fsb back down to 70% or it won't wake. I created scripts to bring the fsb up and down and added them to a file in /etc/pm/sleep.d

If you can't get the eee.ko to load on b oot, you'll have to create a script that cd's to that directory and then run insmod eee.ko from that directory.