Thursday, January 14, 2010

Elonex Webbook screen issue


I got hold of an used old (2008) Elonex Webbook during my holidays with windowz install and as it was free I didn't complained and was really happy for it.

The specs are quite cool:


CPU type VIA C7-M 1600 MhzDisplay Size 10.2" 1024 X 600
RAM 512 MB
Hard Disk 80 GB
Wireless Interfaces 802.11b/g
Ethernet 10/100
Battery run time 2.5 hours
Other Webcam, 3-in-1 memory card reader. 3 USB Ports.
Weight 1304gm
Size (w/h/d mm) 252/183/33 mm



Below a picture (sorry about the quality) of the webbook:




I never thought of having a netbook if I could get a laptop with all the toys but apart of getting used to the keyboard (full qwerty but rather small and keep pressing the wrong keys) I quite like it.

The first week as I was away I used it with Windowz and was impressed for the response time. Will not support loading all the Adobe Premier collection but to walk around, sit on a coffee shop, park bench and surf the web, respond that last email, check the doc/xls file or chat is quite good.

Once back home the first thing I do was upgrade the RAM to 1GB with a spare DIMM I had. Checking the web I found people trying to use 2GB but only 1 seems to be recognized.

Second thing was install Ubuntu. I downloaded Ubuntu Network Remix 9.10 (UNR from now on) and it after a long installation time, it came up with everything running.. or walking. UNR 9.10 make it really slow. I tried to remove packages but not luck. The webbook took ages to move around applications or moving the mouse around to launch something.

As being so slow wouldn't be of any use for me, I decided to go for Ubuntu 8.04 as this was the release that I found the webbook was first offered. By the way it was sold in the UK by the carphone warehouse as free when subscribing to a 3G plan.

Installing Ubuntu/Xubuntu 8.04/8.10/9.04 was simple but with a problem. The screen was dead. Completely blank. The only way to keep using it was connecting an external monitor to the VGA output.

Surfing around I found some posts to change the xorg.conf config (will post it later) it didn't not bring life back to the screen. Neither was trying to download the video driver from VIA in Taiwan or upgrading the openchrome ubuntu package of the versions I installed using apt-get.

The solution was to download the tar.gz of the latest openchrome driver, compile it and install it manually.

The process was as follows:


a) download xf86-video-openchrome-latest.tar.gz from http://www.openchrome.org/trac/wiki/Installation.
b) follow the steps to untar/compile/install
c) tar xvzf xf86-video-openchrome-latest.tar.gz
d) cd xf86-video-openchrome-0.2.904/
e) ./configure --prefix=/usr
f) make
g) sudo -h make install
h) sudo make install
i) close your windows. get out of x (Ctrl+Alt+BkSP) and start x again (startx). Or just simple reboot the laptop.


After this you have lights on the webbook screen but nothing the rate is not ok and cannot see anything. You need now to change your xorg.conf as follows:


rb@rbwebbook:~$
rb@rbwebbook:~$ cd /etc/X11/
rb@rbwebbook:/etc/X11$ more xorg.conf

Section "Device"
Identifier "Configured Video Device"
Driver "OpenChrome"
Option "PanelSize" "1024x600"
Option "ForcePanel"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection


Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection



The key settings here are PanelSize and ForcePanel to make it work.

Below is an picture of the screen working!



As always this post is more for me to remember how to fix this in the future.

2 comments:

Anonymous said...

IS VERY GOOD..............................

Bruce said...

Update for Ubuntu 11.04
The latest driver is already included
however, the screen is useless as before. Use an external monitor and edit the etc/X11/xorg.conf file as specified in http://webbookblog.com/ubuntu-9-10-the-karmic-koala/

You'll find an empty file (i.e. you're creating it!), but don't worry, it will still be used by Ubuntu. Only the Section "Device" section is necessary.

Reboot, and you're away :-)