Posts Tagged ‘Eee PC’

Eee PC Clicking Sound

Wednesday, June 16th, 2010

I’ve noticed that on battery power the hard disk makes a clicking sound every 20 seconds or so. This symptom has been reported particularly by laptop and netbook users, including those that use Windows (though I gather it’s much less of a problem with Windows users).

A quick summary of the situation. If your Eee PC has a SATA hard disk, chances are you’ve noticed this problem. The simple solution is just to disable Advanced Power Management on the hard disk all together and then get on with your life. There are plenty of other power saving features that work, but it seems that the APM is not well suited to Lucid Lynx (or vice versa).

Ubuntu is telling the hard disk to take it easy and not to chew too much power. But this is really just to lull it into a false sense of security as it doesn’t actually cut the drive any slack. In fact, Lucid has some services which appear to be very demanding on the hard disk. The hard disk keeps trying to take a break but Lucid keeps accessing it. The result is a drive that constantly sleeps and wakes up again (causing the click to be heard, as the disk heads park and then move back into working position again). Luckily this action was actually audible, otherwise I’d have been none the wiser, oblivious to the performance hits until my hard disk finally died from excess wear.

A quick search revealed the following command to instantly stop the clicking:

$ sudo hdparm -B 254 /dev/sda

Where “sda” is your SATA hard disk device of course. That command will buy you some time to figure out what’s really happening. Unless you are feeling adventurous, you’ll probably reach the same conclusion that I have. But lets work through this anyway for the sake of actually understanding a little more about what’s actually going on here.

The following command will tell you lots of stuff about your hard drive that you probably don’t want to have to care about:

$ sudo hdparm -I /dev/sda

You can find just the line we are interested in with this one:

$ sudo hdparm -I /dev/sda | grep "Advanced power management"

Which should yield this, since we ran hdparm with the -B 254 option…

Advanced power management level: 254

This is what we want. But if you reboot and run that command you will see it reverts back to level 128. In fact, if you plug the power back in and then remove it, theoretically it should revert to APM level 128.

To find out what the hard drive has been up to, install the smartmontools package using synaptic or sudo apt-get install smartmontools. Then you can run this command (make sure your terminal window is nice and wide or maximised):

$ sudo smartctl -a /dev/sda

Cool huh? More stuff you don’t want to have to care about. But just have a look at the section titled “Vendor Specific SMART Attributes with Thresholds”. On my Eee PC I had very high “RAW_VALUE” for “Load_Cycle_Count” row.

“Load_Cycle_Count” was 3150 and “Power_On_Hours” was only 56. So I’m assuming this means the drive has averaged one “load cycle” per minute of it’s life. Which is about right, since the clicking only happens on battery power and then it happens about every 20 seconds during this time. So if the clicks coincide with these “load cycle” thingamajigs, this would suggest it’s lived on batteries less than 1/3rd of it’s life, which is about right.

If you don’t like my science, or you have a different interpretation of your own threshold table then you might want to have a look at the SATA known issues wiki page. Meanwhile, on with the show…

With a default Lucid Lynx installation, the APM level 128 setting is triggered by a htparm power management script that lives here… /usr/lib/pm-utils/power.d/95hdparm-apm. If you have another power management package installed such as laptop-mode-tools then your on your own.

The configuration for this and possibly other power management tools lives in /etc/hdparm.conf. To basically disable APM when running on battery power, add the following to the end of the config file…

/dev/sda {
	apm = 254
	apm_battery = 254
}

This tells hdparm to keep the drive at APM level 254 even when it’s running on battery power. Unfortunately, this seems to be the simplest option when running Lucid Lynx on an Eee PC. Apparently Lucid Lynx just doesn’t want to stop molesting the hard disk. Just disable APM for now. Hopefully future UNE releases will address this rather major issue.

I’m planning to test the battery life of the OEM Windows 7 and then compare it with Lucid Lynx without APM. I expect it to be a bit of a hit, but I get the impression it’s not worth the effort to make Lucid Lynx APM friendly. If you are feeling masochistic though, perhaps you can pick up from where this guy left off.. http://forum.eeeuser.com/viewtopic.php?id=85230

I see this as an unfortunate trade off between power consumption and performance. The performance improvement of Ubuntu still far out weighs this issue. To be fair, I first found out how to fix this problem from Windows users. Someone has ported a lot of the functionality of hdparm to a tool called quietHDD to solve this for the Windows platform. At least our solution is supported and bundled with the operating system. I found it interesting anyway to know a bit more about how power management works in Ubuntu.

References:
man hdparm.conf

ASUS Eee PC Support Forums Disabled

Tuesday, June 15th, 2010

Looks like ASUS finally realised the Eee PC forums were dead, so they have quietly removed them. Well sort of. You can still visit the forums if you know the URL. From there it seems you can reply to posts, but you can’t start new threads.

Not such a big deal since you will get much better support from the EeeUser forums anyway. As long as this isn’t a reflection of their long term support plans for the Eee Family in general.

Dual Boot Eee PC

Tuesday, June 8th, 2010

I’ve done a few of these dual boot installations with impressive results from the latest Ubuntu Netbook Edition. The OEM hard drive layout seems to be quite common across models. Here I’ll document a general approach to take to get your Eee PC set up with dual boot Windows and Ubuntu Netbook Edition.

Make sure you have updated the firmware using the little ASUS updater tool that comes with the OEM Windows. You can find it in the start menu. Here’s the screen shot from the 1005P model…

ASUSUpdate in start menu

Incidentally, this was the first time I’ve touched Windows 7. Nice to know it’s possible to get the classic theme happening, but that didn’t seem to speed it up much. I must admit it seemed to perform a little better than Windows XP. The browser didn’t just hang like it did on my Windows XP Eee Top when I visited some flash intensive sites. Still, it was far less responsive than Ubuntu.

The BIOS update tool is very straight forward. Just be patient while it finds your latest BIOS, downloads and installs it. Having the latest BIOS image generally results in better device support from Ubuntu out of the box.

ASUSUpdate tool

The next thing to do, follow steps 1 & 2 from here… http://www.Ubuntu.com/netbook/get-ubuntu/download

Once you have a USB device with an Ubuntu image on it, insert the USB drive and reboot. During the boot process, usually while Eee PC logo is displayed, press and hold the ESC button. A blue boot menu will eventually be displayed. Select the USB device and press “Enter” to boot the Ubuntu installer image. Once it starts up, click “Try Ubuntu-Netbook 10.04″ and wait for the desktop to load.

Now you need to run Gnome Partition Editor. You can either find it under the System menu, or press Alt+F2 and type “gparted” and hit “Enter”. The screenshot below may be of some assistance in confirming your actions are correct.

Lucid Lynx gparted

Now if you wait a moment you will see a graphical representation of the partitions on your hard disk. It will vaguely resemble something like this.

Eee PC OEM partitions

There are two partitions you’ll want to hang on to. The first one contains OEM Windows (the “C:” drive), the second one is a handy recovery image. If you use Windows to browse the net, you’ll be needing that recovery image to clean out all the root kits and trojans from time to time. Otherwise you might want to keep it in case you ever want to sell the Eee PC to a Windows user who wants a clean image.

Ubuntu needs you to add two new partitions minimum, a swap partition and one for the root directory. Unfortunately, you can only have 4 partitions on the drive, so the last two just have to go.

Optionally, the Windows partition can be reduced in size, this is especially useful if you don’t plan to use it very often. I tend to shrink it to about twice the size of the currently used space. After resizing the Windows partition you’ll need to move the recovery partition so it’s flush against the Windows partition. You can use Gnome Partition Editor to do all these things, so have a play. If you do the wrong thing click the undo button in the tool bar. Once you have something that looks similar to below, press the Apply button (the big tick). It will take some time to perform the operations. Be patient and make sure the netbook it not running on battery power at the time as these operations could be destructive if they fail.

Eee PC dual-boot partitions

If you have resized the Windows partition, Windows will perform a disk check the next time you boot it. This is to be expected, just be patient and let it do it’s thing. It will eventually complete the check and reboot. Windows will start fine.

The next step is to install Ubuntu. From the menu, click “Install Ubuntu-Netbook 10.04″ from the favourites menu. The Wizard will firstly prompt you for your language, timezone and keyboard layout. When you get to step 4, Partitions, select the last option as seen here.

Eee PC dual-boot Lucid Lynx installer partitions

On the next screen all you need to do is set the EXT4 partition as the root as seen below.

Lucid Lynx installer setting root partition

Then just follow the bouncing ball to begin the installation process. Sit back and enjoy the progress bar and obligatory forced advertising as it completes.

Once it’s installed, reboot. You will notice a 10 second menu to select between Ubuntu and Windows. Firstly, some notes about the GRUB menu. The last Windows entry is usually the Windows recovery tool. Don’t use this tool unless you really need to recover your Windows installation. Recovering Windows will lock you out of this boot menu, and you will have to use the USB boot image to recover it in order to regain access to Ubuntu (see Recovering Ubuntu After Installing Windows). I’ve also noticed on the Eee Top that the Windows partition becomes hidden and Windows will not boot after recovery. You can easily use gparted to remove the hidden flag from the partition if this is the case. But enough about Windows.

Boot into Ubuntu (just wait 10 seconds, or press “Enter”). Now visit the HardwareSupport/Machines/Netbooks page and find the model of your Eee PC. Here you will find useful information about getting better device support for your particular model. Or if your model is not listed, add an entry with notes about how perfectly it works.

Enjoy the superior performance of an Ubuntu Eee PC.

Update June 17, 2010: Please ensure you do have a look at the hardware support page linked above. There are some important changes to make to the grub config you’ll need to perform to get hotkeys working correctly. On top of this, check out my recent post on clicking noises and disabling APM. You may need this too if you have a clicking SATA hard drive.

Ubuntu on Touchscreen Eee Top

Thursday, June 3rd, 2010

Well it’s been a while, but I once again have a useful nugget of information for the world. I bought a cheap Eee Top last year, and installed Ubuntu on it. It did have a few minor dramas. I wasted days trying to get the touchscreen working, with limited and unreliable results. I actually suspect Ubuntu was having issues with the USB bus since I was getting spammed with dmsg log entries in the terminal window. Sometimes my USB keyboard or mouse would stop working.

Anyway it was depressing and I don’t want to go into it too much now I’ve got my mojo back on the latest version of Ubuntu, which is working awesomely. This time it took me only 30 minutes to find some working instructions to get the touchscreen up and running. No package compiling required this time, though there was xorg config file hacking involved.

Here’s the procedure on an out of the box Lucid Lynx install. Install the evtouch driver.

$ sudo apt-get install xserver-xorg-input-evtouch

Tell udev to create us the symlink for the touchscreen device.

$ echo 'echo KERNEL==\"event*\", SUBSYSTEM==\"input\", ATTRS{idVendor}==\"1bfd\", ATTRS{idProduct}==\"1688\", SYMLINK+=\"input/evtouch\" > /etc/udev/rules.d/69-touchscreen.rules' | sudo sh

Now I was surprised to discover I didn’t have an xorg.conf file. I found you can generate one with “X -configure” command. The catch is you need to kill GDM before you do so. So here’s the drill:

Ctrl+Alt+F1 and login to the terminal

$ sudo killall gdm-binary
$ sudo X -configure

Now copy the generated xorg.conf.new to /etc/X11/xorg.conf.

Edit xorg.conf so it looks similar to mine (changes highlighted):

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
	InputDevice    "Touch0"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules"
	FontPath     "/usr/share/fonts/X11/misc"
	FontPath     "/usr/share/fonts/X11/cyrillic"
	FontPath     "/usr/share/fonts/X11/100dpi/:unscaled"
	FontPath     "/usr/share/fonts/X11/75dpi/:unscaled"
	FontPath     "/usr/share/fonts/X11/Type1"
	FontPath     "/usr/share/fonts/X11/100dpi"
	FontPath     "/usr/share/fonts/X11/75dpi"
	FontPath     "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
	FontPath     "built-ins"
EndSection

Section "Module"
	Load  "extmod"
	Load  "dbe"
	Load  "dri"
	Load  "dri2"
	Load  "glx"
	Load  "record"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "InputDevice"
	Identifier	"Touch0"
	Driver		"evtouch"
	Option		"device"	"/dev/input/evtouch"
	Option		"MinX"	"1"
	Option		"MinY"	"1"
	Option		"MaxX"	"4096"
	Option		"MaxY"	"4096"
	Option		"ReportingMode" "Raw"
	Option	"Emulate3Buttons" "false"
	Option	"Emulate3Timeout" "50"
	Option	"SendCoreEvents" "on"
	Option	"MoveLimit" "0"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: : integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "NoAccel"            	# [<bool>]
        #Option     "SWcursor"           	# [<bool>]
        #Option     "ColorKey"           	# 
        #Option     "CacheLines"         	# 
        #Option     "Dac6Bit"            	# [<bool>]
        #Option     "DRI"                	# [<bool>]
        #Option     "NoDDC"              	# [<bool>]
        #Option     "ShowCache"          	# [<bool>]
        #Option     "XvMCSurfaces"       	# 
        #Option     "PageFlip"           	# [<bool>]
	Identifier  "Card0"
	Driver      "intel"
	VendorName  "Intel Corporation"
	BoardName   "Mobile 945GME Express Integrated Graphics Controller"
	BusID       "PCI:0:2:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	SubSection "Display"
		Viewport   0 0
		Depth     1
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     4
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     8
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     15
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

And that’s that. Reboot.

References:

http://wiki.linuxmce.org/index.php/ASUS_EeeTop_ET1602

http://ubuntuforums.org/showthread.php?t=1428788

I’m going to have to post soon about my experiences with Lucid Lynx so far, now that the dust has well and truly settled. There is not much to criticise that I have come across, but I have a new found approach to distribution upgrades to share. I’ve also completely given up on KDE in favour of Gnome with Cairo Dock.

Distinct lack of Linux Eee PC

Wednesday, May 6th, 2009

Tonight I spent some time looking around for places that sell Linux Netbooks again. Amazon had quite a few good deals, that sadly wouldn’t ship to Australia.

In the country I only found a few outlets. Penta and YouPrice are selling the 901 model with 20GB SSD for I think one or two hundred dollars more than what they are worth these days. I seen some people selling the Acer Aspire One with Linux. No one is selling the top end Netbooks with Linux here.

I remember seeing the prototype for the Touch Book a while back. Looks like they are just about ready for the market. I think I’ll hold out for these to hit the shores. Fingers crossed they don’t have Windows support by the time they reach Australia, the distributors wont order the Linux model if the current state of the market is anything to go by. More than likely we wont even see these before someone else releases a knockoff with Windows on it. Then I’ll be out of luck for sure.

Update: Actually it wasn’t the Touch Book prototype I’d seen, it was the Crunch Pad. However, I think the Touch Book looks a little superior with it’s detachable keyboard. Both are rather sexy!