By David Clack on Oct 12, 2008
The Acer Aspire One uses the new disk partitioning scheme, the diagnostic / recovery partition is mirroring the partitions Windows XP Home is installed on.
I had a plan to keep the installed Windows XP Home, adding SXDE and the Gnome 2.24 desktop.
Using the native 1024x600 resolution, testing Firefox, Evolution, gthumb, gtkpod and rhythmbox (both with IPOD support), totem and mplayer (with mpg, avi and wmv support), get the power management, screen brightness keys and volume keys working, plus the new nwam gui's (switch between ethernet and wifi automatically).
I actually did a battery run down test last week, just unplugged and let it sit, 4hrs 30 minutes later it still had power left, more on this later.
Install Try #1
So I used partition magic to remove the diagnostic / recovery partition (4Gb) and moved the Windows XP Home partitiion to the front of the disk and shrunk it to 40Gb.
Not good Windows XP does not boot anymore.
Install Try #2
Recover hard drive from recovery DVD, use partition magic just to shrink Windows XP Home partition to 40Gb (This laptop has a 160Gb HD)
Windows XP Home still boots
Download latest nightly build of OS, probably about B99, I knew I needed the Realtek driver fix.
Get all the way through an option 4 install (the Intel video chip is not allowing Xorg to run in Option 1) to the select UFS / ZFS then onto fdisk.
Fdisk says two partitions are sharing the same space and just stops. Refuses to go forward.
Install Try #3
Go back to B98 DVD, option 4 install, this time when I get to the fdisk section it does not complain at all, creates a ZFS partitiion and the install completes normally.
So now I can boot Windows XP Home or OpenSolaris B98
Video is coming up as VESA at 800x600 not 1024x600 which is the native resolution
No Realtek Ethernet
No Atheros WiFi
SDCard driver says it cannot initialized the hardware
Weird thing that I've never seen on any other machine laptop, desktop or server is the time after Hostname: os-one appears and ZFS coming up is about 4 minutes, no disk activity, no network activity, it just sites there, doing nothing, then starts correctly (still trying to debug this)
NOTE: This fdisk issue has disappeared in the full B100