Showing posts with label Aspire One. Show all posts
Showing posts with label Aspire One. Show all posts

Thursday, September 25, 2008

Improving the Firefox experience

There are a few things you can do to improve your browsing experience.
First of all the most important one, press F11 to maximize the viewing
area! In Firefox 3 everything will disappear, even the navigation bar
at the top. Moving the cursor towards the few remaining pixels brings
it back, beautiful. If you prefer to have it visible all the time enter
about:config in the address bar and change browser.fullscreen.autohide
to false.

The only thing that's been bothering me with the full
screen mode is the lack of the status bar, especially when hovering
over links to check the destination. The status bar can be brought
back. Open a terminal and launch the profile manager.

/opt/firefox/firefox -profilemanager -no-remote

You
will see the name of the profile you are currently using. Close the
profile manager and type the following in the terminal, substituting myprofile with the name of your profile.

cd /home/user/.mozilla/firefox/*myprofile/chrome
mousepad userChrome-example.css


Enter the following line at the end of the file you just opened and save it.
#status-bar {visibility: visible !important;}

mv userChrome-example.css userChrome.css

Now
another thing that makes browsing difficult, if you don't have a mouse,
is the touchpad. Especially right clicking, changing tabs and so forth.
Fortunately Firefox has quite a few touchpad friendly shortcuts.

CTRL + LEFT CLICK » open link in a new tab

CTRL + T » open new tab
CTRL + W » close tab

CTRL + N » open new window
CTRL + SHIFT + W » close window

CTRL + TAB » switch to next tab
CTRL + SHIFT + TAB » switch to previous tab

ALT + LEFT » back
ALT + RIGHT » forward

CTRL + L » select address bar
CTRL + K » select search bar


Mastering
all those shortcuts makes for a smooth and fast browsing experience. If
you really want to go hardcore press F7 to bring up a small cursor. Now
you'll barely need the touchpad at all. Makes browsing a bit tedious, i
wouldn't recommend it.

Very useful on the small screen is the
zoom feature. Firefox 3 zooms the whole page, keeping the layout 1:1,
which can lead to garbled images. Most of the time it's better to just
zoom the text, you can toggle this behaviour with browser.zoom.full in
about:config. Everything is saved for each domain individually, making
it really nice to customize your preferred font size.

CTRL + + » Zoom In
CTRL + - » Zoom Out
CTRL + 0 » Default


One last thing, enter about:robots in the address bar.

Upgrading to OpenOffice 2.4 on Acer Aspire One Linux

The AA1 ships with OpenOffice 2.3, with no available upgrade path,
because 2.4 is only supported in Fedora 9, while the AA1 is based on
Fedora 8. There is a solution besides downloading the tar archive from
their website, but it requires some work. You can take a look at the release notes for 2.4 first to see if it's worth your time.

First of all remove all unnecessary language packs as described here,
it makes upgrading much easier. Then some packages have to be
downloaded. Create a directory in Downloads, name it OpenOffice, and
save all files there.

The packages needed are calc, core, impress, writer, latex, hunspell, hyphen, hyphen-en, mythes-en, nspr and nss. Also needed is the language package, for english being langpack-en. If you need another language you'll have to edit the download path and replace en with your language code. All available languages can be seen here. Download the corresponding version of hunspell, hyphen and mythes in addition to the english ones. If in doubt which one to choose get the latest fc9 version available.

Now go into the terminal.

cd Downloads/OpenOffice
sudo rpm -U *rpm


If
you only receive two errors, about libcrypto.so.7 and libssl.so.7, all
went well and you can continue. If not make sure you downloaded all
required packages and retry.

sudo ln -s /lib/libcrypto.so.6 /lib/libcrypto.so.7
sudo ln -s /lib/libssl.so.6 /lib/libssl.so.7


Upgrading
OpenOffice also replaces all icons with low resolution official icons,
so the original ones need to be backed up. Don't forget the dot at the
end of the line.

sudo cp /usr/share/icons/hicolor/48x48/apps/openofficeorg* .

Now everything can be installed.

sudo rpm -U --force --nodeps *rpm

Put the original icons back in place.

sudo cp openofficeorg* /usr/share/icons/hicolor/48x48/apps
sudo gtk-update-icon-cache -f /usr/share/icons/hicolor


The only thing left to do is to edit the desktop files, and to remove %U on line number nine.

sudo mousepad /usr/share/applications/openoffice.org-1.9-writer.desktop
sudo mousepad /usr/share/applications/openoffice.org-1.9-calc.desktop
sudo mousepad /usr/share/applications/openoffice.org-1.9-impress.desktop


That's it, OpenOffice has been upgraded to version 2.41, the latest available.

Dependency problems on Acer Aspire One Linux

As you may already know the AA1 comes with a custom version of Linpus
Linux, which is a custom version of Fedora. If you take a look at the
source RPMs provided by Acer you will notice about 50 modified packages, recognizable by an lp
suffix in their filename. I have already found one package modified
directly by Acer where the original filename was not modified, so there
may be more. And since neither Acer nor Linpus keep their own
repositories the only choice is to use the Fedora ones if you want to
update or install a package. As a result you'll run into dependency
problems now and then.



I will try to resolve them as i stumble upon them.



#1 gecko-libs

You will receive the following error whenever you try to install a
package that is somehow related to Firefox, or more precisely its gecko
engine: Missing Dependency: gecko-libs = 1.8.1.16. A package that triggers it is epiphany.
It can be resolved. First of all Firefox 2 has to be removed, which can
only be done via rpm, or else half the system will go with it. Forcing
it via rpm however breaks a few packages. To satisfy their needs a
Fedora version of Firefox 2 is installed and a symlink to the excpected
library path created. Finally yelp is updated, and that's it.



sudo rpm -e --nodeps firefox

sudo yum install firefox

sudo ln -s /usr/lib/firefox-2.0.0.16/* /usr/lib/mozilla

sudo yum install yelp




#2 notification-daemon-xfce

It manifests itself via the following message: notification-daemon-xfce conflicts with notify-daemon. The good news is that for most packages the problem is fixed with procedure #1. I can only trigger it now via sudo yum update,
which is not recommended anyway because it will turn your system into
Fedora 8 if you're lucky or break it if you're not. Use yum only to
update selected packages, and even then make sure it's not updating one
of the modified ones. I'll put this one hold until another package
complains about it.



#3 gnome-menus

This depedency problem is triggered via f-spot or evolution, displaying the following error message.



file
/usr/share/desktop-directories/Internet.directory from install of
gnome-menus-2.20.3-1.fc8 conflicts with file from package
xfdesktop-acer-lp-1522.no_spot.mcs_patched

file /usr/share/desktop-directories/Settings.directory from install of
gnome-menus-2.20.3-1.fc8 conflicts with file from package
xfdesktop-acer-lp-1522.no_spot.mcs_patched




It's fairly easy to fix. Just download gnome-menus and redhat-menus and
force their installation. Then restore the original content of the
conflicting files.



sudo yum install yum-utils

sudo yumdownloader gnome-menus redhat-menus

cp /usr/share/desktop-directories/* .

sudo rpm -U --force gnome*rpm redhat*rpm

sudo mv *.directory /usr/share/desktop-directories




#4 gtk2-devel

Not really a dependency problem but more of a general problem.
Installing gtk2-devel automatically updates the custom gtk2, which
breaks the desktop. Just download it and force the installation via rpm.



sudo yum install yum-utils

sudo yumdownloader --disablerepo=updates,updates-newkey gtk2-devel

sudo rpm --force --nodeps -i gtk2-devel*rpm




#5 libpulse

This problem only occured recently and is triggered if you try to install VLC, with the following error message.



Error: Missing Dependency: libpulse.so.0(PULSE_0) is needed by package vlc

Error: Missing Dependency: libopendaap.so.0 is needed by package vlc-core

Error: Missing Dependency: libdvdnav.so.4 is needed by package vlc-core




An explanation can be found here, the solution is to simply use the line below.



sudo yum install fedora-release

Tuesday, September 9, 2008

Installing Windows XP from USB

Case In Point


You’ve got this Acer laptop with a
malfunctioning DVD drive. Specifically, you removed it from its bay and
now Windows XP crashes when you plug it back in. Knowledge Base article
310664 matches it to a tee.


Provided solution: update to Service Pack 1, or disable DMA in the BIOS. Current situation: running SP2 and blessed with a “user-friendly” BIOS that doesn’t allow you to disable DMA.


Your luck just ran out, but - being the geek that you are - you
don’t whine about it. Instead, you come up with this bright idea: let’s
install Linux, that’ll work some magic! And so you get Gentoo Linux installed using a home-brewn LiveUSB distribution. And much to your dismay, proper hotplugging implementation for your laptop is lacking. Curses.


So finally, you call the support line to have them collect your
laptop for repair. One problem here: you’re betting they won’t like
seeing Linux boot up and, hoping to forego additional service costs,
it’s up to you to reinstall Windows XP.


One problem here: you don’t have a working CD-ROM drive to install Windows XP off, and from experience you know that Windows XP won’t install from an external drive. Blasted!


Enter the cavalry.


Disclaimer


The procedure here is provided without any warranty or support
whatsoever. It worked for me and so it might for you. It also might
blast you and your laptop to pieces. Some of the procedures described here can wipe all of your data. Thought I’d warn you.


I don’t mean to be inventive here, either. In fact, all the
technology has been laid out for us and is readily available. All I’m
doing is wrapping it all up in writing. Shouts out to everyone who
provided the technology!


That being said, let’s get down to business.


Ground Zero: Ingredients


You’ll be needing ample space on a USB storage device like a
thumbdrive or external disk drive. 1 GB of storage will suffice.
Possibly, you could access the setup files from a network share in
which case you’ll only need a 256 MB thumbdrive, but I haven’t tried
that.


Personally, I booted off a 512 MB thumbdrive and put the Windows XP
setup files on an external disk drive. So a combination will do just
fine, but just make sure that you’ve got sufficient USB ports: all USB devices will need to be plugged in and stay plugged in while we’re booted into BartPE later on!


You’ll also need a bunch of software, including a valid copy of
Windows XP. The other software components can be downloaded freely:



Q: Why Windows 2003 Server Service Pack 1? I want to install XP!


A: Well that’s exactly the trick, though it’s a bit technical.
During booting, Windows resets the USB port and loses your boot device.
That’s why an installation from USB normally fails. But by using
Windows 2003 Server’s ramdisk feature in the early phases of booting,
we circumvent that problem.


Don’t be mislead though: you’ll be installing Windows XP all the
same. It’s just that we’ll be using two Windows 2003 Server files from
the Service Pack to do it.


You can also perform a Windows 2003 Server installation using this
exact same procedure, save that you’ll be needing to update to Windows
2003 Server Service Pack 1 instead of Windows XP SP2, below. That’s
assuming, of course, that you’ve got a valid copy of Windows 2003
Server.


You will also need an already functional Windows system to prep the
USB disk from. In addition, your target system (the one that needs
reinstalling) should support booting from USB. Virtually all modern
ones do though.


Finally, not all cheaper USB devices properly support being booted from. The BartPE forums have a partial list of ones that don’t.


Step One: Preparing the Windows XP Setup Files


For this procedure to work correctly, you’ll need Windows XP to be
at Service Pack 1 or Service Pack 2. Many newer Windows XP CDs already
have either one included.


You can check by inserting the CD-ROM and looking at the files in the top folder. There should be a file named WIN51P.SP1 or WIN51P.SP2.
If you see either one, fast forward to step two.If there is no such
file, or you’ve got a SP1 CD that you would like to update to SP2,
proceed as follows:


  1. Copy the Windows XP CD-ROM to a location on your hard drive. We’ll be assuming C:\winxpcd. I strongly advise you to use such a vanilla CD. Users have reported strange happenings with custom XP distributions.
  2. Download the Windows XP Service Pack 2 Network Installation Package.
  3. Unpack Windows XP SP2 by running WindowsXP-KB835935-SP2-ENU.exe -x. Note the -x parameter that will allow you to specify a location to unpack to. We’ll be assuming C:\winxpsp2.
  4. Integrate SP2 into the setup files by running C:\winxpsp2\i386\update\update.exe /integrate:c:\winxpcd.

If your system needs special drivers to operate, this would be the
time to include them (called “slipstreaming”). Doing so isn’t exactly
trivial and should only be necessary if you, say, require non-standard SATA support. The process is beyond the scope of this article, but fortunately Google is your friend.


Step Two: Prepping BartPE


First we’ll prep the USB drive we’ll be using for booting. This is
by far the largest step in the process, though it shouldn’t be
difficult for anyone to follow. It requires a functional Windows system.


  1. Install BartPE. We’ll be assuming that you install to C:\pebuilder.
  2. Unpack PE2USB to C:\pebuilder.
  3. Unpack Windows 2003 SP1 by running WindowsServer2003-KB889101-SP1-x86-ENU.exe -x (that’s assuming that you downloaded the English version). Note the -x parameter that will allow you to specify a location to unpack to. We’ll be assuming C:\server2003sp1.
  4. Create a folder named C:\pebuilder\srsp1.
  5. Copy C:\server2003sp1\i386\setupldr.bin to C:\pebuilder\srsp1.
  6. Expand and copy ramdisk.sys by running expand -r C:\server2003sp1\i386\ramdisk.sy_ C:\pebuilder\srsp1.
  7. Start PE Builder from the Start Menu. Point “Source:” to the location of your Windows XP setup files containing SP1 or SP2.
  8. Make sure the “Output:” is set to “BartPE”. If using SP2: go into the Plugins configuration dialog and enable “RpcSS needs to launch DComLaunch Service First - SP2 only”.
  9. Hit “Build”.
  10. When it’s done building, insert the USB drive you intend to boot from and run C:\pebuilder\pe2usb -f [drive:], replacing [drive:] with the location of your USB drive. This will destroy any data on your USB drive!
    The drive shouldn’t be partitioned any larger than 1 GB. If it is, then
    repartition it using Computer Management in the Control Panel.
  11. Copy the Windows XP setup files to the USB drive (or another USB
    device if you have insufficient space left). You’ll only need the i386 folder.

If no errors occured in the process, you should now be all set to boot from USB!


Note: it’s possible to use Windows 2003 Server as the operating
system to boot from, but I don’t recommend it. Many of BartPE’s
included utilities won’t work properly.


Step Three: Configuring the BIOS


You should now reboot and go into the BIOS configuration to boot
from USB. Instructions for doing so wildly from system to system, but
generally entail the following:


  1. Reboot the system.
  2. While booting (before Windows starts loading), get into the BIOS
    configuration screen by hitting something like F1, F2, Delete or
    Escape. Hotkey instructions are generally provided on the screen.
  3. Go to the section that contains your boot devices.
  4. With your USB drive plugged in, the USB drive should be listed. If
    it isn’t, your system might not support booting from USB. Assuming that
    it is supported (as is the case with virtually all modern hardware),
    promote your USB drive to the primary boot device.
  5. Exit from the BIOS configuration, saving all changes.

If you’re completely new to BIOS configuration, BIOS for Beginners
over at Tom’s Hardware might be a good primer. Be aware though, that
you can seriously screw up your system by providing incorrect settings!


Step Four: Booting into BartPE


Assuming that you properly configured your BIOS and your USB device
supports booting, BartPE should now load. Depending on the speed of
your USB device, this may take a while.


If it isn’t working, then double-check the following before making a scene:


  • Is your BIOS properly configured for booting from the USB disk? (Is the USB device listed and does it have top priority?)
  • Have you correctly prepared the USB disk in step two? (Restart the procedure.)
  • Does your USB stick properly support being booted from? (Try another one!)

Step Five: Prepping the Hard Disk


You need to make sure that your hard drive is partitioned and
formatted properly. Especially if you’ve had Linux or some other
operating system on it, you’ll need to repartition and format it.
BartPE contains DiskPart for disk partitioning and A43 File Manager to format your drive.


If you are sure that your hard drive is set up properly (i.e. it has
only run Windows, it contains a valid FAT or NTFS partition) then you
can safe yourself the hassle and skip this step.


This procedure will destroy any data on the hard drive.


To repartition:


  1. From the Go menu, navigate to DiskPart.
  2. Enter the commands needed to repartition your drive. For example, try the following: select disk 0 (select the first disk), clean (purges the entire drive, essentially resetting it), create partition primary (creates a single partition from the entire disk), assign (assign the partition a drive letter), exit (quits DiskPart).

This procedure will destroy any data on the hard drive.


To format:


  1. From the Go menu, navigate to the A43 File Manager.
  2. Right-click on the target drive (e.g. C:) and click Format. Should be self-explanatory.

Step Six: Launching Windows XP Setup


With your drive all ready, you can now launch the Windows XP setup
with a few custom parameters. Let’s assume that the files are available
at D:\i386.


Plugging in a device now won’t work. Remember that all USB
devices will need to be plugged in right from the start while using
BartPE.


  1. Run D:\i386\winnt32.exe /syspart:C: /tempdrive:C: /makelocalsource. Replace C: with the drive you want to install Windows to.
  2. Proceed with the installation. When asked to convert the
    installation volume to NTFS, answer No. The setup program incorrectly
    believes that your USB drive (which is formatted as FAT) needs
    conversion.

The setup program will then silently close, which might make you
think that something went wrong. Don’t worry though. Reboot your
system, remove the USB drive(s) and – if all went well – you can now
finish setting up Windows XP. Congratulations!

Monday, September 8, 2008

Install Ubuntu Hardy Heron (8.04.1) on the Acer Aspire One

Fully functional:

  • Suspend / Resume
  • Video (with desktop effects)
  • Wireless Networking
  • Wired Networking
  • Webcam
  • USB
  • Silent Fan

Partial Function:

  • Card Readers (only work if card in when booting)
  • Audio - there is sound, issues detailed below

Not Functional:

  • Hibernate on A110L
  • Card Reader power saving
  • wifi power saving
  • wifi kill switch

Prerequisites:

Before you begin you will need the following:

  • A copy of 8.04.1 Hardy Heron.
    This is the latest version. If you downloaded the ISO a while ago, it may be 8.04.0. The original 8.04.0 release will not even boot.

  • An external USB CD-ROM. If not:

Note on using this guide

This guide was written with Ubuntu in mind. Generally everything works the same with the other variants of the distribution (Kubuntu, Xubuntu). For ease of use gedit is the text editor we’ll be using. If you are using a variant please substitute a different text editor (kate for Kubuntu, mousepad for Xubuntu or just use vim/emacs/nano).

Step One: Preparation

(Skip this step if you have an external USB CD-ROM)

If we don’t have any external USB CD-ROM the first thing we need to do is create a bootable copy of the Ubuntu LiveCD on a memory key. This will be our install media for the Aspire One. Its actually pretty similar to creating recovery media for Linpus Lite (the included version of Linux).

Download and copy the LiveUSB .deb file from the link above to a memory key (you can use the same one we we are going to format to create the install media, we only need this file once), and remove the memory key. The LiveUSB software should only be installed when booted off the LiveCD environment, so we do that next.

Boot to the 8.04.1 Live CD on your other computer, and choose the first option off the boot menu (Try Ubuntu). When you reach the desktop insert the memory key with the LiveUSB software one it and double click. Follow the prompts to install it. Now we can create our bootable USB key. Start the LiveUSB application from System -> Administration -> Install LiveUSB. Select the target device (my two keys were listed by a human readable name, so it was easy to find) and click Execute. It will give you a warning about data loss, so double check that you selected the correct device and continue.

Once that is done, you can shut down the other computer and remove the memory key.

Step Two: Install Ubuntu

Shut down your Aspire One and insert the external USB CD-ROM or the memory key that we just used. Turn it on and tap F12 to bring up the boot menu.

With a CD-ROM, choose the USB CD-ROM option. With the bootable memory key created, choose the USB HDD option. This will boot you to the USB CD-ROM/LiveUSB stick, and allow you to install Ubuntu. Install it like normal if you have the hard disk Aspire One. If you have the SDD Aspire One, for good performance and to increase the life of the SSD use a non-journaled filesystem (suggestion: EXT2). If you have already installed with EXT3 then follow this post: http://www.aspireoneuser.com/forum/viewtopic.php?f=5&t=164&st=0&sk=t&sd=a&start=10#p1177 to convert to EXT2. Installation (file copy) will take a LONG time (hour +). If your not currently connected to the internet on a wired connection, you may get an error about setting up a mirror. Don’t worry about it if you do however, its non-fatal.

Step 3: Tweak / Fix

So now we should have an installed Ubuntu system. At this point wire your One into the network. If you use DHCP it should pick up an IP address automatically. The first thing you will want to do is updates, since the wireless driver needs to be reinstalled after every kernel update. Open a terminal (Applications -> Accessories -> Terminal). Do the updates:

sudo apt-get update
sudo apt-get upgrade

WIRELESS:

Now we need to disable the hardware drivers that Ubuntu tries to use before the ones we make will function. So go to System -> Administration -> Hardware Drivers and uncheck everything. It should prompt us to reboot, so lets do it now.

We need to grab the wireless driver, and the things we need to build it, from a terminal:

mkdir source
cd source
wget http://snapshots.madwifi.org/madwifi-hal-0.10.5.6/madwifi-hal-0.10.5.6-r3835-20080801.tar.gz
tar -xzvf madwifi-hal-0.10.5.6-r3835-20080801.tar.gz
cd madwifi-hal-0.10.5.6-r3835-20080801
sudo apt-get install build-essential linux-headers-$(uname -r)

And we build and install:

make
sudo make install
sudo modprobe ath_pci

In order to have the wireless work after reboot, add the following line to /etc/modules (”sudo gedit /etc/modules”) to automatically load the module when booting:

ath_pci

You should now have working wireless. However you may want to do the following to prevent problems (the symbol mismatch) when the module is loaded:

Add ath_hal to the DISABLED_MODULES= stanza in /etc/default/linux-restricted-modules-common

(i.e. ‘DISABLED_MODULES=”ath_hal”‘)

Every time there is a kernel update you will need to perform the following steps to make the wireless work. Go to the directory (madwifi-hal-0.10.5.6-r3835-20080801) and run:

make clean
make
sudo make install

WIRELESS LED:

To get your awesome wireless led to blink for you based on traffic, put these lines in /etc/rc.local, just above the string exit 0 (below doesn’t work).

sysctl -w dev.wifi0.ledpin=3
sysctl -w dev.wifi0.softled=1

The led on the front will now do the association blink, as well as blink based on wireless traffic.

The wifi kill switch uses these keycodes (also to use in rc.local):

/usr/bin/setkeycodes e055 159
/usr/bin/setkeycodes e056 158

CARD READER:

According to DebianAcerOne the following command enables the card reader:

setpci -d 197b:2381 AE=47

The card reader works fine if cards are inserted before booting.

  • it might help to suspend/resume
  • a static entry for the device /dev/mmcblk01p in /etc/fstab might help
  • powersaving can be done with the jmb38x_d3e.sh script

USB MOUNT:

(Do this step only if you get an error inserting a USB stick)

If you insert a memory key, you may notice an error and that it cannot be mounted. This is due to the CD-ROM entry in the fstab. Since we don’t have an optical drive on the One we will comment that out. From a terminal again:

sudo gedit /etc/fstab

You should see a line that looks like:

/dev/sdb        /media/cdrom0   udf,iso9660 user,noauto,exec 0       0

add a hash in front:

#/dev/sdb        /media/cdrom0   udf,iso9660 user,noauto,exec 0       0

Reboot, and automount should work.

NOISE (FAN CONTROL)

Bios v0.3114 doesn’t manage correctly Fan speed, resulting in a very noisy AA0. Solution:

 chmod a+x acerfand
sudo cp acer_ec.pl acerfand /usr/local/bin/
  • To run it straight away:
 sudo acerfand
  • To run it at boot:
 sudo gedit /etc/rc.local

Insert the following line above the exit 0 at the bottom:

 /usr/local/bin/acerfand

The fan is not completely disabled. When the default temperature is reached (60ºC), fan works again. According to Intel, the Atom chip could work until 99ºC.

Optional: Above instructions will work fine, but if you want to define another temperature:

  • Create an /etc/acerfand.conf file. The file is just a shell script that sets up to three values. eg:
INTERVAL=5
FANOFF=60
FANAUTO=70

Those are the default values, if the /etc/acerfand.conf file isn’t found.

INTERVAL is the polling interval in seconds

FANOFF is the temperature (in Celsius Degrees) at or below which to turn the fan off, if it’s currently on auto

FANAUTO is the temperature (in Celsius Degrees) at or above which to turn the fan to auto, if it’s currently off

More information from the original source, AspireOne Wiki.

OPTIMIZING SSD PERFORMANCE:

(Skip this step if you have the hard disk Acer Aspire One)

The performance of the SSD drive can be significantly improved by a few tweaks described in an article by Jason Perlow (Tweek #1 is not working with Ubuntu on the Aspire One). The most important of these are described here.

Change the file system mount options on SSDs to “noatime”

Edit /etc/fstab (sudo gedit /etc/fstab) and change the the option “relatime” to “noatime”. The line for the root partition should then be something like:

UUID=f0ae2c59-83d2-42e7-81c4-2e870b6b255d / ext2 noatime,errors=remount-ro 0 1

Use the “noop” I/O scheduler

Edit /boot/grub/menu.lst using your favorite editor, and add “elevator=noop” as an option. The default kernel configuration, found in the last part of the file should be something like:

title           Ubuntu 8.04.1, kernel 2.6.24-19-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=f0ae2c59-83d2-42e7-81c4-2e870b6b255d ro quiet splash elevator=noop
initrd /boot/initrd.img-2.6.24-19-generic
quiet

In order for the changes to remain when updating the kernel, also in menu.lst, find the line

# defoptions=quiet splash

and add “elevator=noop” as an option:

# defoptions=elevator=noop quiet splash

REDUCING SSD WEAR:

(Skip this step if you have the hard disk Acer Aspire One)

Frequent writes to the SSD will cause failure eventually. We can reduce the number of writes to the SSD my moving our logs to a temporary filesystem in RAM that gets destroyed at ever reboot. Now this means your logs will not be persistent across reboots making debugging difficult in some cases. This step is optional of course, so if you need the logs for an extended period of time do not follow these steps.

Open your fstab again, and add the following lines:

sudo gedit /etc/fstab
tmpfs /var/log/apt tmpfs defaults 0 0
tmpfs /var/log tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults 0 0
tmpfs /var/tmp tmpfs defaults 0 0

AUDIO:

Out of the box there are various issues with the sound. These range from headphone detection not functioning correctly, to the internal MIC not working. There are solutions to these problems. Currently, however, there is no known way to get everything working at once. All of the steps begin the same way, rebuilding ALSA:

sudo apt-get install module-assistant
sudo m-a update
sudo m-a prepare
sudo m-a a-i alsa
sudo alsa force-unload
sudo depmod -ae
sudo modprobe snd-hda-intel

Add the following line to the end of /etc/modules in order to ensure that the module is loaded during bootup:

snd-hda-intel

Now we need to make a choice. To have the internal MIC non-functional (external works), but sound working after suspend and resume, we edit /etc/modprobe.d/alsa-base (sudo gedit /etc/modprobe.d/alsa-base) and add the following line to the bottom:

options snd-hda-intel model=toshiba

Reboot for that to take effect.

To have the internal MIC function correctly, but no sound after suspending and resuming the computer add or change the following to the /etc/modprobe.d/alsa-base as before:

options snd-hda-intel model=auto

Again, reboot for this to take effect.

For some unknown reason some people don’t hear any sound with either option. If you experience this problem you might want to use the option in /etc/modprobe.d/alsa-base as before to the following to resolve this problem:

options snd-hda-intel model=acer

If you experience crackling sound after rebooting, insert the following line in /etc/modprobe.d/blacklist:

blacklist snd_pcsp

Optional: The default sound level is low. Open a terminal and type alsamixer to adjust volume.

TWEAKS TO MAKE BETTER USE OF THE ASPIRE ONE’S SMALL SCREEN:

There are various methods that will help you make better use of the Aspire One’s small screen. One of the most important is being able to move windows that are too large to fit on the screen at once. To move a hidden part of the window into view, click and drag with the left mouse button on any part of the window while holding down the ALT key. However, you won’t be able to drag windows so the top of the window is above the top of the screen. To fix that, enter the following in a terminal window:

gconftool-2 –set /apps/compiz/plugins/move/allscreens/options/constrain_y –type bool 0

Since the Aspire One’s screen has almost twice as much resolution horizontally as vertically, having panels on both the top and bottom is not ideal. You may want to remove the top or bottom panels, make them smaller, or move them so that they are vertical, on the left and right side, instead of horizontal on top and bottom.

HIBERNATE:

In some set-ups, using hibernate has been reported to cause file corruption.

TWEAKS FOR POWERSAVING (Optional):

Add the following to the /etc/rc.local file:

# Economize the SSD
sysctl -w vm.swappiness=1 # Strongly discourage swapping
sysctl -w vm.vfs_cache_pressure=50 # Don't shrink the inode cache aggressively

# As in the rc.last.ctrl of Linpus
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate_max > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate

echo 3000 > /proc/sys/vm/dirty_writeback_centisecs
echo 20 > /proc/sys/vm/dirty_ratio
echo 10 > /proc/sys/vm/dirty_background_ratio

echo 1 > /sys/devices/system/cpu/sched_smt_power_savings
echo 10 > /sys/module/snd_hda_intel/parameters/power_save
echo 5 > /proc/sys/vm/laptop_mode

#Decrease power usage of USB while idle
[ -L /sys/bus/usb/devices/1-5/power/level ] && echo auto > /sys/bus/usb/devices/1-5/power/level
[ -L /sys/bus/usb/devices/5-5/power/level ] && echo auto > /sys/bus/usb/devices/5-5/power/level

NETBOOK REMIX (Optional):

To install Ubuntu Netbook remix -

  • Insert the following into /etc/apt/sources.list:
deb http://ppa.launchpad.net/netbook-remix-team/ubuntu hardy main
deb-src http://ppa.launchpad.net/netbook-remix-team/ubuntu hardy main
  • then execute
sudo apt-get update
sudo apt-get install go-home-applet human-netbook-theme maximus ume-launcher window-picker-applet
  • Add maximus as startup program (system > preferences > sessions > startup programs)

  • Change the desktop theme to Human-Netbook (system > preferences > appearance > theme)

  • Delete the bottom panel
  • Reconfigure the top panel to contain the following items -
    • Go Home Applet
    • Window Picker Applet
    • Notification Area
    • Mixer Applet
    • Clock
  • There is a bug in the ume-launcher after resuming from suspend. To work around this place the following in /etc/pm/sleep.d/01UMELauncher -
#
# Copyright 2008 Matteo Collina
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of version 2 of the GNU General Public License as
# published by the Free Software Foundation.

export DISPLAY=:0.0

TMPFILE=/tmp/.launcher/resume-event

case "$1" in
suspend|hibernate)
rm -rf $TMPFILE
echo "Removed resume-notify file"
;;
resume|thaw)
touch $TMPFILE
echo "Created resume-notify file"
;;
esac

exit $?
  • Make the above file executable -
sudo chmod +x /etc/pm/sleep.d/01UMELauncher

Flash 9.0.48 (Optional, recommended for 512M of RAM):

Ubuntu Hardy installs flash version 9.0.115, this version needs a lot of memory to work and makes ‘AspireOne’ slower than it is. A good option is to come back to the last fast official version of flash (9.0.48). Just download ‘Flash player 9 (99MB)’ file from:

http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_14266&sliceId=2

In this file there are a lot of old flash versions, navigate to 9r48 and uncompress this folder. Double click ‘flash-player installer’, choose ‘Run in terminal’ and follow the instructions.

Saturday, September 6, 2008

Installing Windows XP on the Asus EEE pc using a single USB flash drive.

Please note this tutorial works on all computers not just the Asus EEE PC.
To complete this tutorial you need a 32bit version of Windows XP or Windows Vista installed on your home PC.

What you'll need:
USB_PREP8 (alternative download)
PeToUSB (alternative download)

Bootsect.exe (alternative download)
Special
Note: If you use the program Nlite be sure to keep the manual
installation files as the USB_prep8 script relies on these files.


Extract the files in Bootsect.zip
The next step is to extract USB_prep8 and PeToUSB.
Next copy the PeToUSB executable into the USB_prep8 folder.
Inside of the USB_prep8 folder double click the executable named usb_prep8.cmd.

The window that opens will look like this:



Press any key to continue

You next window will look like this:
These settings are preconfigured for you all you need to do now is click start.
Once
the format is complete DO NOT close the window just leave everything as
it is and open a command prompt from your start menu (type cmd in the
search bar or run box depending on your version of windows.).

Inside of the command windows go to the directory you have bootsect.exe saved.
(use the cd directoryname command to switch folders)

Now
type "bootsect.exe /nt52 R:" NOTE R: is the drive letter for my USB
stick if yours is different you need to change it accordingly. What
this part does is write the correct boot sector to your USB stick, this
allows your PC to boot from the USB stick without it nothing works.
Please
note: When running the bootsect.exe command you cannot have any windows
open displaying the content of your USB stick, if you have a window
open bootsect.exe will be unable to lock the drive and write the
bootsector correctly.

If all went well you should see "Bootcode was successfully updated on all targeted volumes."

Now you can close this command prompt (don't close the usbprep8 one by mistake) and the petousb window.

You window you see now should look like this:

If it doesn't try pressing enter.

Now you need to enter the correct information for numbers 1-3.
Press
1 and then enter. A folder browse window will open for you to browse to
the location of you XP setup files (aka your cdrom drive with xp cd in)
Press 2 and enter a letter not currently assigned to a drive on your PC
Press 3 and enter the drive letter of your USB stick
Press 4 to start the process.

The
script will ask you if its ok to format drive T:. This is just a temp
drive the program creates to cache the windows installation files.
Press Y then enter.

Once it's done formating press enter to
continue again, you can now see the program copying files to the temp
drive it created. Once this is done press enter to continue again.

Next you will see a box pop up asking you to copy the files to USB drive yes/no you want to click yes.

Once
the script has completed copy files a popup window asking if you would
like to USB drive to be preferred boot drive U: select YES on this
window.

Now select yes to unmount the virtual drive.

Ok we are done the hard part, close the usbprep8 window.

Now make sure your EEE pc is configured with USB as the primary boot device.
Insert your USB drive and boot up the EEE.

On the startup menu you have two options, select option number 2 for text mode setup.

From
this point on it is just like any other windows XP installation
delete/recreate the primary partition on your EEE pc and format it
using NTFS. Make sure you delete ALL partitions and recreate a single
partition or you will get the hal.dll error message.

Once the
text mode portion of setup is complete it will boot into the GUI mode
(you can press enter after the reboot if your too excited to wait the
30 seconds)

Once the GUI portion of setup is complete you will
again have to boot into GUI mode this will complete the XP installation
and you will end up at you XP desktop. It is very important that you DO
NOT REMOVE THE USB STICK before this point. Once you can see your start
menu it is safe to remove the usb stick and reboot your pc to make sure
everything worked.

This method has advantages over all current
no cdrom methods of installing XP to the EEE. You do not have to copy
setup files in DOS to the SSD and install from there. It gives you
access to the recovery console by booting into text mode setup, and it
gives you the ability to run repair installations of XP if you have
problems later on.

I hope this worked out for you and please post feedback to the comments section.
Please
note due to the amount of comments this article has received you must
now click on "Post a Comment" below the existing comments to view the
most recent feedback in a popup window.

Friday, September 5, 2008

Another solution for SSD: EWF?

I've implemented EWF (more information here: http://msdn.microsoft.com/en-us/library/ms838511.aspx) in Windows XP SP3. Performance now is well acceptable.

Steps to a happy XP experience

After installing, removing XP and installing XP again, I thought I'd outline the steps to making XP perform well.

  1. Disable D2D in Bios
  2. Purchase and install extra 1 GB of RAM for 1.5 GB total
  3. NLite an XP Service Pack 3 CD
  4. Gather the Aspire One drivers. Grab the latest Intel Chipset/VGA drivers from the Intel site
  5. Install XP, formatting the SSD to FAT32
  6. Install the drivers
  7. Turn off Paging
  8. Turn off System Restore
  9. Install Firefox 3 and you're set :)
instantptr.com