Friday, June 4, 2010

Asus eee 1001P and Linux Fedora 13

I wanted to share with everyone some my Fedora 13 installation experience.
It seems that everyone is installing the netbook version of Ubuntu but I have been a long time user of the Redhat type Linux. For a good number of years I used Mandriva (known then as "Mandrake") and was really pleased but since Fedora 10 there has been a gradual improvement. Fedora seems to have the latest and greatest out there and the system is well tailored together. Fedora 13 definitely creates a new step up and I'm rather pleased.
The first day I received my Asus 1001P I started off with preparing it for a dual boot OS. I am not anti Windows, I think at times it could be useful and I believe it still may have a certain edge with battery life over Linux. In addition- the starter edition loads up FAST and seems to be pretty snappy, so I recommend keeping it around.

Preparing for dual-boot
I used under Windows a program called "Easus", the home edition is free for private use and seems to only limit you on creating new partitions (which I did from Windows or Linux itself). I recommend the following:
  • Shrink Windows to 40GB partition.
  • Boot in to Linux rescue and create an extended volume.
  • Create a 40GB Linux partition (Could be less, in reality I'm using maybe 6GB-10GB).
  • Create a 512MB partition (for SWAP). 
Go back in to Windows, load up Easus- grow the "data" volume to Maximum, should be around 140GB.
Use Easus to format the 140GB "data" partition to Fat32 (This is used as a shared partition between the two OS's). This strategy will allow you to format Linux and re-install without affecting the data partition and also allow you to to a restore operation at boot time to restore your Windows partition from the hidden partition on disk and not lose data.

You are now ready to install Fedora 13.
Installation process should be pretty streight forward. I installed from a USBkey image (8GB) containing the entire DVD image. I did this "livecd-iso-to-disk" utility on the ISO image of Fedora (livecd-iso-to-disk --reset-mbr).

In the section for partition installation method I chose custom and made sure to select the partition I reserved for Linux (format as well) and the small 512MB partition for SWAP.

In the boot menu section I renamed "other" to "Windows 7" (which came with my laptop) in order to make it clear.
I chose to "choose now" on the package install section and made sure to install both gnome and KDE desktops. I am a big fan of KDE, especially with the recent improvements and find KDE 4.4 to be nothing like earlier versions as far as stability and resources.Once the installation is complete, pretty much everything should be working from networking down to the video camera. However, there are a number of adjustments required:

Fix for skype:
If you installed a 64bit OS (which is what I did) you will need to install several packages of 32 bit before you do a full yum update, I learned that later on some strange dependencies happen due to the 64bit version being newer the the 32bit and failing to install 32bit versions. I actually re-installed at this point due to understanding that.
Run the following commands:

yum install libXv.i686*
yum install libXScrnSaver.i686*
yum install qt.i686
yum install qt-x11*.i686
Now install the Fedora 10+ RPM available from Skype (2.1 beta).

Run update!
There are quite a number of GUI little bugs that got fixed after running a full update. It will take most likely a couple hours to complete since when I did it we were talking about 500MB of updates.
To make this process faster run:
yum install yum-plugin-fastestmirror
yum update

Screen brightness control:
As reported by other people with eeepc's, the brightness does kind of act random when using the fn-brightup/brightdown. The fix for this is to apply to your kernel parameters under grub.conf the following line:
"acpi_osi=Linux acpi_backlight=vendor"
Reboot and you should have normal controls.

Sound card:
The sound card works out of the box but does have a couple bugs:
1. When plugging in headphones the sound continues to work on both the external speakers and headset. This seems to be due to the jack sense not being recognized. I found that this entry did the trick:
edit the file /etc/modprobe.d/dist-alsa.conf with your favorite editor and make sure it has this:
install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-seq
options snd-hda-intel model=auto position_fix=1
(Basically I added "position_fix=1").
Once again, reboot or reload the modules if you know how and it should be solved.
2. Microphone under skype not working.
This one was a little bit of a chalance since skype on a 64bit platform to begin with was a chalange. It did work OK with hearing audio and video conferencing even, just the microphone didn't pick up. The KDE mixer was not much help since it only showed 1 channel for capture, 1 channel for output and no special controls. I installed padevchooser:
yum install pavucontrol.
I then ran in and balanced my controls as follows:
input devices tab:
40% left
80% right.
This seemed to me optimal after lots of trial and error for skype. Still lots of background noise but it will be good enough to have some medium quality conversation.

Battery performance maximizing:
While the eeepc_laptop module does load, I did find some adjustments required to be more efficient on battery life. I am now able to get close to 8 hours of battery from my 6 cell 48W battery with the following parameters:
Wireless Internet on, 40% screen brightness, Browsing and typing/chatting with quite a few applications running. (skype, Empathy, Thunderbird, Firefox, Openoffice).
Some adjustments to the kernel params:
Start with adding these to your kernel params under /etc/grub.conf:
This will utilize power management functionality with the eeepc_laptop module (which should be loaded).
I also added the following parameters to my /etc/rc.local based on recommandeation from "powertop":
modprobe deadline-iosched
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
It could be I should have added the module under /etc/modules.d but I guess I was testing first.

Some extra control:
I installed an app called "Kill switch manager" for the KDE desktop (you can find it on google). It seems to be rather "Beta" but does offer the ability to graphically turn on/off your bluetooth or wireless.

Next, edit your services, there are many that can be disabled. I will tell you the only ones I have on, you can research and choose more if you feel you need it but for the most part I don't think you will:
bluetooth (assuming you have a 1001P with bluetooth version, there is one without too. Find out)
This should make your laptop a lean, efficient but powerful machine.

I'm guessing that thanks to the synaptics driver, the mouse pad works pretty well. I was disapointed that for me, at least, the two finger scroll option under the KDE System Settings->Keyboard & Mouse->Touchpad didn't work. Also the tap to click didn't seem to have any effect. I did a lot of playing around trying to manually add it to the X11 configuration but to no evail. The scrolling works out of the box by sliding your finger along the right side of the touchpad.
One thing I was able to at least correct is the pointer going crazy if you accedently touch it with two fingers.
My /usr/share/X11/xorg.conf.d/50-synaptics.conf looks like this:
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
# Quirks for special touchpads
# Some devices have the buttons as part of the lower edge of the touchpad.
# Pressing a button moves the cursor, causing cursor jumps and erroneous
# clicks.
# Use the synaptics area property to work around this.
Section "InputClass"
# Identifier "touchpad button overlap"
Identifier "tap-by-default"
MatchIsTouchpad "on"
# MatchTag "touchpad_button_overlap"
MatchTag "tap-by-default"
Option "AreaBottomEdge" "4000"
Option "SHMConfig" "on"
Option "ClickFinger2" "right"
Option "TapButton1" "1"
Option "RBCornerButton" "3"

Update 06/12/2010
I have solved the tap-to-click problem I was having in KDE, I simply removed from my ~homedir/.kde/share/config/kcmtouchpadrc, there must have been legacy settings there conflicting, the KDE re-creates it next login with correct settings.

Some KDE adjustments: I recommend avoiding too many plasma type widgets, some of them are quite heavy on CPU.
I also resized my task bar on the bottom to be a little smaller and chose a "Oxygen netbook" theme which seemed a little more optimized. Aside of a few large configuration menu's from firefox plugins, I have not encountered too many applications which had problems with the screen size. 

Here is a small example of my desktop:

No comments:

Post a Comment