I bought a new ASUS Eee PC 1005PEB in March of 2010. Below are some notes I'm taking while install linux on it. At this time only Fedora 13 Alpha is out but notes should apply mostly for final Fedora 13 as well.
I've also made some updates based on behaviour after upgrading to Fedora 14.
Windows seems to prefer to place some system files (page file, hibernate file, and system restore files) above the half way point on a drive and defrag can not move them around. Since I want to give half or more to Linux and other OS's, I used the following steps to move the files.
how to do this. To use the USB drive, you may need to change the boot priority in BIOS settings menu. Also, I think you can hit Escape and then TAB key during boot sequence and the BIOS will request which device to boot from.
After installing, it doesn't include all the applications that the more standard DVD install would give. You can get the default set of applications by running following command line once logged in.
UPDATE: 2010/10/15 - When ACPI detects Windows 2009 query, it disables older ACPI interfaces and switches to WMI which is a standard defined by Microsoft. There is a eeepc-wmi driver in Fedora 14 that works with default acpi_osi values for most hotkeys and backlight. But this driver doesn't let you control SHE as described below. I have submitted patches upstream to eeepc-wmi to re-enable cpufv/SHE interface and some missing hotkeys and will be in kernel 2.6.37.
*Volume keys only work after adding
For Fn-F4 (resolution), I do not have any need for smaller resolutions but I would like to use a higher resolution for apps that just don't work well with 1024x600. xrandr supports an --scale option that will allow going higher; although rather ugly. I make use of Keyboard Shortcuts and run the following script to toggle between 1024x600 and 1024x768 resolutions. Save the following to a file and "chmod 755 restoggle.sh".
UPDATE: 2010/10/15 - On Fedora 14, Fn-F2, F5, F6, F10, F11, and F12 all work as you would expect now. Fn-F3, F4, F7, and F9 have a regression but I have submitted patches upstream to re-enable these in new eeepc-wmi module.
UPDATE: 2010/11/05 - There is some hope in getting Fn-F3 working. It seems that F22 is currently being used as indication in Gnome (gnome-settings-daemon) to toggle touchpad. To get this working, you would need to recompile your linux kernel and edit eeepc-laptop/eeepc-wmi and change reference of KEY_F13 to KEY_F22. I'm attempting to work with upstream to get this working out of the box.
UPDATE: 2011/01/02 - FIgured out how to fix Fn-F3 without patching the kernel by using udev to remap them. Recent updates to Fedora have changed F22 for touchpad toggle to F21 instead. If you have old software, change below text to f22. Add following two lines to your /lib/udev/rules.d/95-keymap.rules towards area were a "ASUS*" already exists and reboot. I've submit it as patch to udev team so hopefully it will show up in a future udev update.
I noticed using that Mouse preferences that the 2 finger options were greyed out. Using the gpointing-device-settings application, I also noticed that 2 and 3 finger support was not working. Digging deeper, I noticed in dmesg output that it lists its capabilities as 0xd04731. Digging in the kernel and in Synaptics documents I see that means the hardware says it can report finger widths but not multi-touch. The windows drivers seems to be using the width of fingers to determine when 1, 2, or 3 finger gestures are being done.
The xf86-input-synaptics driver does have an xorg.conf value that can be used to emulate 2 finger multi-touch. It is EmulateTwoFingerMinW since it needs to be based on W value. I've not tried it yet.
Another major issue with the netbook is related to its size. When you put your finger on the button to click, its very easy for that to also register as touching the lowest row of touchpad (they can sense things even when your not touching the pad). If your other hand is moving the mouse cursor at same time, you can get unwanted mouse jumps once that other hand is lifted off the mouse pad.
Googling the issue turns up a few common complaints on this but no clean solutions yet.
UPDATE: 09/07/2010 - Good progress made with touchpad. As of this commit to linux kernel, the syaptics driver will now correctly inform userspace when hardware supports finger width reporting. As of this commit, xf86-input-synaptics defaults to enabling 2-finger emulation on hardware that supports finger width reporting. This reduces enabling 2-finger scrolling mode to single xinput. I've also submitted this patch that stops most cursor jumps related to multi-touch.
xf86-input-synaptics-1.3.0 and Fedora 14 contains all mentioned updates.
I've submitted this patch to config GUI gnome-mouse-properties to un-grey option for enabling 2-finger scrolling on hardware that supports 2-finger emulation but I've heard no response. In mean time, you'll need to use X config files or xinput to enable 2-finger scrolling mode or I've read you can bypass the Gnome GUI by executing:
See my projects page to download and install the system service.
Windows 7 automatically detects when you plug in head phones and gives you a pop-up window asking if you want to switch audio to head phones. When you unplug them, Windows automatically restores to built in speakers (no pop-up). I would hope this is possible under Linux as well.
TODO: I noticed browsing /usr/include/linux/input.h that a switch event exists called SW_HEADPHONE_INSERT. I've no idea if its ALSA or ACPI or what that would generate it. It would be nice if that event could be sent upon insertion and we monitor for it and then can do similar to Windows 7. Who knows; maybe Gnome already does the right thing if just we sent that event.
To always have NTFS parition mounted on bootup, add the following line to your /etc/fstab file:
Also, create this directory:
To make sure file permissions are correctly translated to something Windows understands, run the following command while NTFS partition is not mounted. Follow the prompts and inform it of linux users and groups for your main users under Windows.
Once thats done, you need to move the files created over to Windows partition.
My hopes are I can do things like share a single Dropbox directory on Windows partition and have it sync correctly regardless of which OS I'm running.