OK, sorry for the disorganized reply, I'm in a hurry, no time right now to write up something better. Anyway, below come a couple of replies I sent as answers to private messages...
In order to do the install, you need two things:
a) a customized 132-boot CD, the one that's available on the net won't work, because there are two extensions that I needed to modify for things to work.
b) Chameleon 2.0RC1 on an HFS+ formatted EFI partition, which (among other things) critically also needs to have the same two extensions that need to be on the boot-132 CD.
Otherwise, the instructsions for vanilla installs available for other EeePCs apply pretty much 100%.
Of course, I then also did some extra research to find all the various bits and pieces from a variety of sources to get the rest of the hardware and drivers to work pretty much flawlessly, with the exception of the WiFi card, which I swapped against an Apple card. As a side effect, I now also have 5Ghz-band WiFi, so that alone was worth the investment.
As for the advantages over iDeneb:
iDeneb modifies MANY things. My install modifies ALMOST NOTHING, at least not on the root file system.
The advantage is that most Apple supplied upgrades should just work (e.g. upgrading to 10.5.7 was a minimal effort, although due to the size and breadth of that particular upgrade a few minor tweaks had to be made afterwards for optimal screen resolution to work)
So the advantage is to be as close as possible to what would be on a real Mac, and KNOWING precisely which modifications are required for your hardware, rather than having a superset of all sorts of mods for all sorts of hardware, and then have to look for the needle in the haystack if something stops working.
By having a minimal set of modifications, it's much easier to track down potential problems, and it allows for better compatibility all around.
If you can provide me with some sort of place to upload things, I can put together a zip or iso image with all that's needed, plus some short instructions, which should be sufficient for you to reproduce things and maybe write up a bit more detailed instructions.
PowerManagement is something that would be nice to get fully nailed. It's not bad as it is, due to the massive battery. Some people using the VoodooPower (which I currently am not using yet), say that the fan doesn't properly adjust, which is why I stayed away from it, even though the reports that "time remaining" is properly displayed with that extension is promising. Currently the fan goes at a rate higher than what's usually the case under WinXP, but I rather have the fan go to fast than too slow...
The other thing is the VoodooHDA. I use the 0.22 version with the corresponding preference pane. That allows me to get very clean sound, because I figured out what to raise and what to set to zero.
I haven't tried the EeePC modified version of that extension, particularly since some people said something about noisy recordings (which would correspond to one of the sliders that I had to turn all the way down in the Preference Pane for the VoodooHDA.
The last thing is, that the GMA950 drivers are really a stumbling block. The ones that work are (based on?) rather old Apple drivers. I'm not sure what was patched in them, but since only these patched versions work, the corresponding plugin and bundle files (GMA950 GL, VA, etc.) need to be from 10.5.6 or older, so that's one of the issues with the 10.5.7 upgrade.
So I need to find out what was patched in these drivers, such that one can do a similar patch with newer Apple software. Unfortunately just adding the device ID string into the driver bundle did not suffice. Bummer.
Thankfully 10.5.7 fixed the CPU issues, so no more cpus=1 flag required; the CPU is now correctly recognized as "one CPU with hyperthreading", the latter can be turned on and off with CHUD's Processor preference pane.
Haven't upgraded to the latest BIOS yet, and still have some issues understanding how these .aml files interact with everything, but things are clearly getting there fast.
As for what needed to be edited: it's two of the ACPI related extensions. (I'm not able to access the machine right now since I'm installing CygWin on the XP partition and that'll take a while). The problem with these is, these are older extensions, so Mac OS X will overload them with the newer ones, and these won't work, for whatever reasons. (Maybe once I figure out this .aml file stuff or a newer firmware, this may no longer be an issue). Bottomline: I had to edit both the various Info.plist files within these extensions, AND the binary such that these extensions have a (much) higher version number than what Apple currently (and in the foreseeable future) provides. Thus the old, hacked extensions will be given preference by the kernel over the newer extensions, which the OS now considers to be older, thanks to the modified version numbers in the old extensions.
An alternative approach would be to create a modified install DVD that deletes these extensions from the DVD, but that defeats the point of a vanilla install. The point being, that it works with what you can buy at the store from Apple.
Anyway, sorry for the messy response, but I'm in a hurry, and writing a more orderly response would take more time than I have right this second
Ronald
Author
Topic: OS X Retail Installation (Read 5368 times)