Jan 29 2009
Definitive Mac OS X installation guide for netbooks
There is currently a great demand for laptops which provide the user-friendliness of a Mac without the cost and weight of a MacBook or MacBook Pro, or without the cost of size of a MacBook Air.
Given that the ever-increasing varieties of Intel Atom-based netbooks are low-cost and roughly equivalent in hardware terms to the original MacBook Air, they make a tempting target to conversions to “MacBook Mini”s.
Indeed, there are a large (and also increasing) number of guides which will tell you how to get OS X running using a variety of ISO images downloaded via BitTorrent and hacked kernels which then require extensive changes to the installed system and come with copious warnings not to upgrade the OS when Software Updater prompts you to… and even then it’s common for basic functions such as sleep or USB not to work (although it has to be said that no method is entirely free from caveats).
This guide doesn’t work like that. This guide will describe how to install OS X from an original Leopard installation DVD and how to end up with an entirely unmodified system (*) which will not break when Apple issues updates.
DISCLAIMER: Please do not attempt anything you read about below without understanding what you're doing! Following these instructions will erase your hard drive before Leopard is installed, so only continue if you're happy with this and have backups. This guide is written from memory, and I haven't wiped my netbook to confirm every step - although I'm happy to receive feedback about any errors.
This guide is written with the Samsung NC10 in mind, for this is the only netbook I have available to test with. Other netbooks should also work with the same method, but I’ll post updates if I hear of any problems or improvements. This guide does not cover multi-boot systems, although it should be relatively easily achievable for anyone with a working knowledge of boot-loaders.
- What you will need:
-
- An Intel Atom-based netbook with the ability to boot from USB devices;
- A USB data stick or USB hard disc to boot from with 64Mb of free space;
- A USB DVD drive or, alternatively, a 16Gb or larger USB data stick or USB hard disc from which to install Leopard and access to a machine with a DVD drive already running OS X. 1
Some people have reported problems in getting external DVD drives to be recognised, so the current best advice is to image the Leopard DVD onto a USB hard disc, as described below, and install from this; - An OS X-supported WiFi MiniPCI-e card, an OS X-supported internal ethernet adapter, or an Apple MacBook Air USB to Ethernet adapter (or similar);2
- Access to a machine running Windows to start with (although this can be the netbook itself prior to OS X installation, or alternatively a Linux machine);
- A basic knowledge of UNIX command-lines is helpful, but not required.
1 Most (all?) netbooks do not feature an optical drive, so installing Leopard isn’t as simple as just dropping the DVD into a DVD drive… unless you happen to have one handy. If you don’t, then all is not lost – if you have access to another machine running OS X which also has a DVD drive, then you can simply insert the Leopard installation DVD and connect your removable media and launch Disk Utility. Click on the DVD icon on the left and then select the “Restore” tab. Now drag the DVD icon onto the “Source” text-box and your USB hard disc or data stick onto the “Destination” text-box and click “Restore”. Note that the Leopard DVD image is just slightly too large to fit onto an 8Gb data stick 🙁
2 This is probably the greatest hurdle to getting Leopard running on the NC10 in particular, as it is unlucky enough to have both wireless and ethernet adapters which aren’t supported as standard on OS X. If an install is attempted on a stock machine without a USB ethernet adapter, then the first stage will succeed but the user-creation stage will loop endlessly because the OS can’t find a network adapter. It is possible to avoid this by configuring a Bluetooth PAN connection, but since this doesn’t have an ethernet MAC address other problems (and lots of log messages concerning UUIDs) will result.
It is actually possible to get the stock wireless adapter running, but this is a complex process and the result is not stable, so I won’t cover it here. The ethernet adapter is currently a non-starter, with no support in OS X at all. Thus, whilst it is possible to get by with a USB network adapter, by far the best solution is to crack open the chassis and replace the standard MiniPCI-e WiFi card with a Broadcom replacement – Dell TrueMobile cards seem to be the popular choice. I opted for the 802.11BG Dell 1395 over the 802.11ABG Dell 1490 on the assumption that the lack of 802.11A networking, something I’ve never come across in the UK, might lead to some power savings. 802.11N cards also work, but check around first to ensure that there are no hardware incompatibilities with OS X.
- What you will need to download:
- This bit’s easy – you only need a single file: The installation image available from here (8.6Mb), which now includes the Windows syslinux binary, used to make your USB data stick or disc drive bootable. If you need to install from an OS other than Windows, the latest release of syslinux is available from here (but you won’t need this if you do have a Windows machine available to prepare the USB boot data stick).
- What will happen next:
- Firstly we’re going to copy the installation files, which are actually only just over 45Mb in size, to the USB data stick or hard disc. Then syslinux is run from Windows or Linux in order to make the device bootable. Booting from this device allows the Leopard installation to complete. After this, we’ll run a script which automagically performs the system changes necessary to boot without the USB device in place, and… that’s it!
- Preparing the boot device:
- If necessary, start by (re)formatting your USB data stick or disc drive as FAT32. Extract the installation image Zip file, downloaded above, and copy all of the files contained within to the root of the USB device (so that “BOOT“, “BOOT.CAT“, etc. are at the top level of the USB device – not in any subdirectory). Now open a Command Prompt and change directory to your USB device – for example, drive U:. Now run the command:
U:\syslinux -ma U:… to make the drive (U: in this example) bootable.
Note that this command shouldn’t produce any output: if anything appears on-screen, then the process has failed. This can be caused by supplying the wrong drive-letter, or by not running the command with elevated privileges on Windows Vista or Windows 7. In this latter case, “CMD” should be typed into the Start Menu search box and then the ‘CMD’ icon above should be right-clicked and “Run as administrator” should be chosen.
At the very next step, we will be reformatting the drive for use with Leopard – so now would be an excellent time to backup your Windows partition(s), or even swap out the internal hard disc (and wireless). I took the latter approach, and installed a 30Gb OCZ Core Series v2 SSD. The capacity is plenty for my needs (even with a full Xcode install, I still have almost 10Gb of space free) and has the benefits of being totally silent, having no moving parts, consuming less power, and actually performing better than the drive installed as standard!
- Installing Leopard:
- Reboot your netbook with the USB device inserted and enter the BIOS Setup (probably by pressing Escape, F2, or Delete as the machine powers on) and ensure that the following options, if available, are enabled:
- NX / XD / EDB
- HPET
… and also ensure that you change the boot order to place the USB drive before the internal disc drive. The NC10 has two USB sockets on the left and one on the right, and it simplified things greatly to place the bootable USB device in the right-hand socket with the USB DVD drive or larger-capacity USB device on the left.
Now hold your breath, cross your fingers, and allow the system to start to begin installing Leopard!
… almost. First you should see a simple text-mode boot menu where you have to press Enter to confirm booting from the DVD (image). As noted above, the most reliable installation method is currently to boot an image of the Leopard DVD from a USB hard disc (or large USB data stick).
You should now be looking at the Leopard installer’s language select screen. Please email me with details if this isn’t the case. Note that the screen will look strange at this stage, because 800×600 output is being stretched onto a 1024×600 screen.
Instead of proceeding with installation as normal, select your language and then select Disk Utility from the Utilities menu. Choose your internal drive from the list on the left, and then select the Partition tab. Define a single partition covering the entire device, but before applying hit the Options button to pull up the dialog below:
… from where the GUID Partition Table option should be selected. Now continue to select the file system to use and format the newly-created partition. Users of SSD’s should avoid the “Journalled” option (as it will needlessly generate addition wear on the device) and the “Case-sensitive” option, whilst technically correct, should be avoided if planning to run Adobe applications at any point in the future – because Adobe’s inability to consistently use either upper- or lower-case results in breakage when the file system differentiates between the two.
Now, finally, proceed through the installation as normal – being sure to deselect options, such as printer drivers, which would consume a large amount of disk space if space is at a premium such as with an SSD.
Installation should continue successfully until the very last stage when the installer tries to set the partition with the newly-installed OS as the boot volume – which will fail since this is not a real Mac. This is completely normal. Remove the installation DVD but keep the USB boot device inserted and reboot.
- Creating the EFI partition:
- The last stage of this installation method will reformat the 200Mb EFI partition, which is currently otherwise unused (but which the EFI standards say must be formatted as FAT32) as HFS+ to form an alternative boot partition for OS X. Modified override kernel extensions can then be loaded from here before the actual system extensions are seen, allowing Leopard to work transparently on foreign hardware.
You should be looking at the Leopard desktop, and have a drive icon for the bootable USB drive. In here should be a disk image named ‘MacOS Installer.dmg’: open this, and there should be a variety of items including a script named “Installer”. Run this and follow the prompts (the default answers should be sensible) in order to setup your EFI partition.
- Important Note:
-
It has just been brought to my attention that versions of the NC10 with integrated 3G modems have (slightly) different DSDTs to the non-3G models. Therefore, if you have the 3G NC10 then please do not choose to install a DSDT override when prompted by the Installer. There is now a replacement DSDT.aml for 3G editions – if you wish to install the DSDT override then either copy this in to place on your EFI partition manually, or drag it into the mounted ‘MacOS Installer.dmg’ disk-image before running the “Installer” script.
I accidentally wiped out my (real) MacBook Pro when testing the installer, but it did seem that for some reason the /Volumes/EFI/Extensions/ directory had been created, but that the contents of the Extensions directory from the installer image hadn’t been copied across. It’s worth choosing not to reboot, and double-checking that this has succeeded before restarting. It’s best to copy the files across from a Terminal session, and then run /Volumes/EFI/update.sh as root once they are in place. Again, please let me know if this works for you or not.The Version 1.1 update has now been tested on a variety of hardware, and the correct files are being created. The glitch above must have been related to accidentally running the installer on a real Mac. Don’t do it, kids 😉
If the version of Leopard installed isn’t 10.5.6, it would be worthwhile to now apply the 10.5.6 Combo update, as the extensions supplied with the Installer are the 10.5.6 versions, and may not work as expected on earlier releases.
This update can be downloaded from Apple’s Downloads site.
Eject the Installer image and the USB device, and then reboot for the final time (note that you will not see an Apple logo as the system boots from now on – this was removed from the bootloader for code-size reasons), and you should find that you have an all-singing, all-dancing, and mostly functional Leopard machine in front of you! 😀
- Where do we go from here?:
- There are still issues related to running external displays over the VGA port in non-mirrored mode which are unresolved. Audio switching from the headphone jack to the internal speakers is currently a manual job, but forthcoming drivers due soon promise to fix this. Because the touchpad is assumed to be square, the vertical sensitivity is too high, but this is also being worked on. Finally, scripts are needed to change the brightness level as this can’t be done with the function keys. And yes, the Euro key on Fn+F3 really does output “0128” instead of anything useful <sigh>.
At the time of writing, none of the SMBIOS replacement extensions work on 10.5.6, so correcting the System Profiler output is not currently possible. Finally, Intel’s EIST is currently unsupported, and extensions which enable this on other Intel processors crash the Atom. Given that the processor’s TDP is a measly 2.5W this isn’t really the big issue it would be on other more powerful systems.
Note that, after going to all of this trouble to get Leopard installed without modifying the installed copy in any way, it’s important to resist the temptation to then go and install any extensions onto the system partition itself – and ignore any instructions which direct you to do so! Any new extensions should be installed instead into the Extensions directory on the EFI partition, and the update.sh script in the root of this partition must be run after any change.
Two excellent tips from the ever-useful MacOSXHints.com are:
- Disable Safe Sleep, aka Hibernation – which doesn’t work with the current version of efi_boot, although support is already working in other bootloaders and is promised for the next release of Chameleon. Once Safe Sleep is disabled, /var/vm/sleepimage can be removed to reclaim some disk space.
- Enable remote DVD mounting allows any machine to use 10.5’s new MacBook Air feature of making remote DVD drives appear local for software installation purposes.
Apple updates should all be fine, although Snow Leopard (OS X 10.6), being 64bit (and the Atom N270 being 32bit only), is an unknown quantity. There are currently rumours of an Atom-based Mac Mini update or even an official Apple netbook, either of which could vastly improve the, already very good, hardware support for this platform.
If/when Apple to release further Mac OS updates, or when upgrading to 10.5.6 initially, it’s well worth making a (Time Machine?) backups first. I’d then advise downloading the Combo Update from Apple’s support site rather than installing the Delta update offered through Software Update. It’s well known that running “Verify Disk Permissions” can throw back warnings after installing a Delta update, whilst this doesn’t happen after applying a (more comprehensive) Combo update.
- Update:
- Version 1.1 of the installer fixes several problems, including preventing the Quiet boot plist from being given the wrong name and fixing the location of the log files which are created during the install. Anyone who has already downloaded the original release should upgrade to this version and re-run the installer if any problems were encountered previously.
* Almost 😉
25th June 2009 @ 9:51 am
Hi guys,
I’ve been away for a while, so no updates recently. Right – where were we?
Mike, I’ve not heard of this happening before, but it sounds weird. All I can imagine is that some form of corruption (or unclean mounting?) has altered the data in such a way that OS X thinks that it is an old Classic binary… or possibly that it simply can’t recognise it, and so defaults to this assumption. In any case, I’d suggest re-downloading the installer image and re-creating the boot USB key. If possible, try a different device in case the one you’ve tried up until now is somehow faulty…
Jörg, You could try here, but as-yet there’s no break-down into wireless or wired adapters. Your best bet is just to look for what other people are succeeding with. The Dell TrueMobile cards are often favoured as they are cheap and well-supported.
Matt, Yup – spot on. Those are the updates to use (after the initial install has been completed – these build on top of the extensions installed by the original Installer: they likely won’t work alone).
Mark, There are various British keymaps available which try to put the keys in the right place. The one I use leaves the bottom-left slash/pipe key unused and moves this function to the top-left key – but except for this is perfect. I think I use the keymap from here, but this site may also be useful.
I still change brightness via script from Terminal.app, because I find it the fastest method – although there are many instructions around on how to set up Quicksilver and an AppleScript program to do the same thing triggered by only a keypress – but unfortunately launching the AppleScript interpretor takes several seconds for each press. For either of these solutions, you’ll need Apple’s CHUD tools (from the Developer Tools package on the Leopard installation DVD) installed.
Just recently there are also ACPI DSDT patches which claim to make the NC10 hardware appear more like a real Mac to the OS – but I’ve encountered stability problems with each of these that I’ve tried. I have heard reports of success, though – so whether this is me doing something differently, subtle hardware variations, or insufficient testing upon the part of the reporter I don’t know…
The Trackpad preference pane is a pain – even with the fix to make it appear, it can take some prodding before it comes back. The trick seems to be to edit a plist in the Keyboard pane (IIRC) and then, as noted here erase the Preference Pane cache. I’ll check what the exact change to the plist was and post it here shortly.
Jake and Matt, this should be fine! Please try the driver update package from here.
Matt, I’ve only tried the VoodooPS2 replacement driver to fix the Trackpad vertical sensitivity, and I didn’t have much luck with it. Although it worked to begin with, I had too many instances of finding that the keyboard or trackpad dropped out on me. As with the other Voodoo drivers I think they’re doing a great job and really helping fix some tough problems – but at the same time, I think that the beta release tags are very much justified: these drivers aren’t yet ready for mainstream use.
If the source for the current PS2 driver were available (which it may be…) then a similar scaling factor could be applied.
Could you please post a link to the Touchpad driver which works for you – if this is stable then I’m sure that lots of people would really appreciate it! 🙂
26th June 2009 @ 9:33 am
Right – Trackpad PreferencePane fix:
Apply the following diff (either manually with with ‘patch -p0‘), and then execute rm ~/Library/Caches/com.apple.preferencepanes* before re-launching System Preferences. The Trackpad preference pane should then appear, giving the option to enable or disable tapping.
29th June 2009 @ 10:34 am
Finally pulled my finger out and actually working on an iPhone app. Woudl like to (occasionally) run the iphone simulator on my netbook, but can’t find anything about scaling it.
The results in google for: AppleDisplayScaleFactor “iphone simulator”
are very limited, and one of the posts says it doesn’t really work properly scaled.
Have you had any success with this?
Thanks
Marcos
30th June 2009 @ 8:18 am
Marcos, I use my NC10 for iPhone development myself – and I’ve not had to apply a scale factor to the simulator. Admittedly it doesn’t fit on the screen entirely – but you can easily fit the display at the top and the home button at the bottom, cutting off only the empty frame.
What sort of application are you working on?
1st July 2009 @ 6:21 pm
Hey Stuart,
I’ve tried searching the comments for someone with a similar problem, but I haven’t found anything. So if this has been asked/answered already, apologies in advance.
I’m performing the operation for a friend who’s a Machead, but I have exactly zero experience with installing OS X. I am however an experienced tinkerer, so I’d expected I’d at least be able to get something working. I have a Windows Vista PC with MacDrive, that can read, partition, and format Mac drives, and read Mac CD/DVD media. The problem seems to lie in ambiguity:
You mention simply putting the OS X Install DVD image on a USB drive and booting from it. Now I have two things: an OS X Install DVD, and a .dmg image of that DVD. Things I’ve tried:
Connecting a slimline external DVD drive to the NC10:
– USB stick boot with Chameleon gives me an error about boot.plist which only appears for a split second, and then gives me the option to boot from hd1,1, hd1,2, and hd1,3, the first one gives me “Windows is loading files” (and hangs), the second gives me the preinstalled XP, and the third one gives me nothing (logically, cause it’s not a bootable partition).
Connecting a different external DVD drive:
– Same thing. (I was just making sure it wasn’t due to the DVD drive not being supported by Chameleon or something)
Okay. So the physical install DVD isn’t working. This was my best bet, as I’m certain this is at least on Macs, supposed to be bootable. The vague instruction about putting the install image on a USB drive leaves me puzzled.
Do I–
Format the USB drive with an Apple partition map, make a suitably-sized partition for the OS X install image, and write the contents of the .dmg to it in raw mode (using dd):
– Chameleon tells me to “press enter to install OS X”. I do so, and am greeted with a prompt asking me to boot from 80 or 81. Selecting 80 returns me to the previous prompt asking me to press enter, and selecting 81 loads syslinux again, which loads Chameleon, which asks me to press enter. I could do this all day.
Do the same thing, but with an EFI/GUID partition map:
– Same problem as above.
Do the same thing, but with an MBR partition table:
– Same problem as with the DVD drives.
Okay, so that’s not it. I go into MacDrive and format the USB drive using an Apple partition map, and make a suitably-sized HFS+ partition. I copy the .dmg file onto it, for just in case Chameleon has some clever logic to boot from an image file residing inside a filesystem (I didn’t know what else to try at this point). I get the same looping problem, but this time with another error about boot.plist in between. I actually get time to read it, and it seems the file is missing.
It’s obvious I’m doing something wrong here, but the instructions aren’t detailed enough to push me in the right direction. Do I actually need a Mac running OS X to copy the image file and make it bootable? Or is there a way to get one of those external DVD drives working? I’m kind of at a loss what to do here.
Thanks,
Muf
2nd July 2009 @ 5:27 am
Stuart, I unzipped (bz2ed??) the 10.5.7 package but the resulting directory was locked and empty. Any chance of posting a .zip file? I seem to recall this was an issue before with the .bz2 file.
FYI – I’m reading and learning, but this stuff is tough if you’re not a guru, so thanks for you patience as I follow along!
2nd July 2009 @ 6:32 am
OK, hacked through it. Lots of permissions problems that I think I’ve fixed and now am running 10.5.7!
w00t!
2nd July 2009 @ 10:33 am
Hi Muf,
Your problem relating to the following:
1. You have to format your USB stick to HFS+ Mac OS Journaled
2. You have to use diskutility or dd to restore the disc or DMG file to the USB Stick
3. When you get the boot prompt asking you to boot 80 or 81, type 9F for DVD or I think maybe 82 or USB Stick.
If this doesn’t help, let me know and I will think of another way.
All the best
NSCXP2005
3rd July 2009 @ 2:54 am
I’m trying to dualboot XP and MacOS, using the Darwin bootloader. I installed OS X first, then XP.
When I set XP to be the only active partition:
sudo fdisk -e /dev/disk0
p, f 3, w, y, exit
Windows loads fine. After that I use the generic.ISO disc and boot back into Mac OS, copy Chamelion EFI to my desktop and do:
cd ~/Desktop/Chameleon\ EFI/source/
sudo fdisk -f boot0 -u -y /dev/rdisk0
sudo dd if=boot1h of=/dev/rdisk0s2
sudo cp boot /
sudo fdisk -e /dev/disk0
p, f 2, w, y, exit
I can now select between XP and MacOS. MacOS loads fine. XP looks like it loads fine, black-background Windows logo loads up, progress bar moves. Once it boots into the GUI, it just stalls. The background is blue and I have a Windows logo where the login box should be. Running the first set of commands setting Windows to be active without dual boot selection makes Windows work. I can’t figure out what I’m doing wrong. Can someone help me?
3rd July 2009 @ 8:28 am
Inspiring tutorial! Do you think this would work on the new Samsung N310?