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 😉
Jake
15th May 2009 @ 3:24 pm
Stuart,
I know I’m fairly novice in a lot of this low level hackery, so it’s no real surprise that I’m having a tough time understanding what this EFI volume stuff is about.
When you say before the 10.5.7 upgrade, I should backup the EFI volume, how/where do I do that?
When you talk about using the AppleYukon2.kext (or other ktexts), how do I handle those?
Sorry to ask for a step down to such a basic level, but I missed that somewhere along the line.
Thanks!
Stuart
15th May 2009 @ 4:01 pm
In the first comment on this post, I wrote a script to mount your EFI partition. Save this to a file (e.g. ‘mountefi.sh’) and from Terminal.app make it executable (e.g. ‘chmod 755 mountefi.sh’). So long as you have a password set on your account (which you can alter from the ‘Users’ System Preferences pane) running this script (‘~/mountefi.sh’ from Terminall.app) will mount the EFI partition on “/Volumes/EFI”. You can then move into this directory (‘cd /Volumes/EFI/’) and backup your current 10.5.6 extensions (‘cp -r Extensions Extensions.10.5.6’), after which you’re ready to install the 10.5.7 extensions.
Having said all of this, it’s very important that you understand what you are doing rather than just copying what someone else has said by rote. The AppleYukon2 driver, for example, has to be moved from the IONetworkFamily Plugins directory to the top-level Extensions directory – and then preferably hex-edited to correct the default invalid MAC address.
Please do read around and build your understanding of the topic and of the issues involved – but if you’re not confident that you understand the procedure and how to recover in case something goes wrong, then please stay on 10.5.6 until (more) user-friendly installers are made available.
It you still want to proceed, feel free to email me and I’ll try to guide you through what needs to be done.
Larry Coltharp
15th May 2009 @ 6:18 pm
Hi Stuart…feel free to remove my last query to you if you feel it’s too long winded or not appropriate. I’m still booting 10.5.6 from the external drive. Perhaps it’s impossible to do what I imagined. Thanks again for all you’ve done and hopefully soon I’ll do the upgrade to 1-.5.7
If my cloning question is possibly doable, it’s okay to email me with whatever ideas you have. Whatever works.
Larry
Jake
17th May 2009 @ 1:55 am
Sounds like it’s probably smart to wait for the auto-upgrade 🙂
Chris
17th May 2009 @ 10:47 pm
Hours of googling still has not lead me to a proper solution for my experiements! So I’ve used these steps here to create a two partition NC10 – one for Leopard and one for Win7/Vista. I made it GUID and installed Leopard just fine. Ran the EFI updater tool and voila it’s all fancy! Now if I try to install Chameleon, it’s all crazytime! I can’t boot into Leopard without it hanging and also can’t boot the 10.5.6 installer from Chameleon. If I use the original USB disk, I can boot into my Leopard install. I tried to erase the EFI partition and reinstall the tools on this page, but the Chameleon boot still shows up.
So questions are:
1. Say I didn’t want to lose anything, how would i remove Chameleon?
2. If I wanted to use Chameleon (I tried the latest RC), how do I get it to properly install and boot up my Leopard install? Will it mess up Vista/Win7 if I install that also?
Side question 3. I”m a little unclear on what needs to be done if updating to 10.5.7. It appears as though all these drivers need to be redone, but I thought the purpose of this type of installation in this blog entry is that it DOESN’T require all this?
sebastien
18th May 2009 @ 8:10 am
Hello,
I am a bit lost at the moment because it is impossible to reach Insanely mac forum and the dedicated mysticus NC10 furum is also broken atm.
Is there other specific nc10 forum where we could have good information ?
I have installed osx with the mysticus cd, also no effi installation.
I have updated to 10.5.7 and have the chameleon 2 rc on mbr partition.
I have diseable the hibernate fonction.
When I press FN + ESC to get the computer sleep it works but I cannot get the computer to wake up even by pressin the power button.
Please can someone help me to get this fonction working ???
Thanks in advance.
sebastien
18th May 2009 @ 8:34 am
@Chris :
Answer of your question 3 is on the Stuart post #102.
Stuart
18th May 2009 @ 9:41 am
sebastien, I’m afraid that since I don’t use a Mysticus install I can’t provide much assistance with sleep issues, but have you tried using ‘pmset‘ to set ‘hibernatemode‘ to ‘0‘, as above?
Chris, given that Chameleon is a boot-loader which is written directly to the start of the disc, there is no real “uninstall” procedure – you just replace it with something else.
(There will still be the “Extras” folder – but this is ancillary and can be replaced at will)
When Windows is installed, it will automatically write two boot-loaders: One to the MBR of the system disc, and one to the header of the partition upon which it is installed. This means that after installing Windows, you will boot directly in to Windows. However, if Chameleon is then installed to the MBR, it can still chain-load the Windows loader at the start of its partition.
Therefore, if you install Windows and then reinstall Chameleon then you should be able to boot either system at will.
(Note that you’ll need to be running Windows Vista or later for EFI/GUID/GPT support. Although not significant in this instance, Windows 7 has altered the way that the boot-loader works, so that it’s no longer easily possible to use the Windows 7 boot loader (as opposed to Chameleon) as the primary boot loader on the MBR)
Chris
18th May 2009 @ 6:59 pm
It took me a while to process post #102 as I just had to follow along what it said then suddenly I understood more about how the EFI partition worked and the Extensions in there. There was a disconnect in my brain about how Stuart here completes this installation process. Once I understood (at about 3am last nite) I nearly peed my pants! 🙂
So is it fair to say that the Extensions here in the EFI are somewhat how MAc OS X manages fonts? There are multiple Font folders in OS X (System, Library, and User Library), and they go in order of loading them, some taking precedent over others.
This whole EFI shenanigans has specialized extensions to allow a plain retail install to work unmodified, but the EFI area is what gets changed to kind of redirect the hardware calls of the standard installation? (Hence, the need for the 10.5.7 Extension mods in the EFI partition.)
So the only hiccup I keep having is playing with the Chameleon 2.0 RC1 Installer. During install, I have the option of which drive I install it to. Originally, I was installing it to the Leopard partition and also check boxing format EFI partition and installing there. This lead to a non bootable system, even when booting from the USB stick. I tried only formatting the EFI and also NOT formatting the EFI, leaving all the Stuart made files there untouched. So even when booting from Stuarts USB bootloader, I learned that the Chameleon installer puts data on the Leopard partition. So if I boot from the USB stick, choose Leopard, then I still see the chameleon Apple wallpaper, and an incomplete boot. I’ve had several variations of this. So when I install Chameleon, isn’t there something to ONLY allow it to affect the EFI partition? And when I do this, doesn’t this erase all the Stuart made 10.5.7 Extensions? So I just have to put those 10.5.7 Extensions made by stuart and it WILL start booting again?
eblot
19th May 2009 @ 10:20 pm
Ok ;-( So the upgrade to 10.5.7 bricked my NC10. It keeps crashing at boot (early stage) and when I try to boot from the USB key, I get the following error message:
System config file ‘/com.apple.boot.S/Library/Preferences/SystemConfiguration/com.apple.Boot.plist’ not found
Any idea about how to recover from such an error?