Print

[GuyHersh]

Then you can overwrite most of what Chameleon Installer did, by usind dd to copy the disk image's EFI partition over to your boot drive.

I still don't know what you mean by this, and I've been meaning to ask.  Is there a hidden EFI partition in the recoverySDcard thing you made?  If so, what are the benefits of overwriting my EFI partition with it?  I think I've tried mounting my EFI partition using commands that you provided once, but it failed saying mount_hfs was invalid or something.

Can you provide me a little more detail on this?  Thanks!  Oh, and any news on V3?

[srcnix]

Once you have your initial install running, use the opportunity to install Chameleon to the EFI partition, this should write the proper boot block. Then you can overwrite most of what Chameleon Installer did, by usind dd to copy the disk image's EFI partition over to your boot drive.
You know how to recover from the 10.5.7 update, which is the the proper way to go about it, once in safe-mode, you can install the patched kexts, and you're done.

Not sure what happened with your keyboard, maybe because you didn't have Chameleon and all the relevant drivers that are in the Extra/Extensions folder installed?

In any case, a regular USB keyboard and mouse will be able to get you out of that quandry and allow you to diagnose and fix the issue, since USB keyboards use regular Apple drivers which "just work". If the built-in keyboard would work over the internal USB interface rather than through a PS2 interface, we wouldn't even have the need for a keyboard driver.

Thanks for the information RCFA, you're a bloody legend. I'm going to be writing a howto myself with reference to all your hard work (Everything I have found through the web based on your username).

I screwed the keyboard up as the kexts in /System/Library/Extensions in the DMG you provided I imported into my own kext library using Kext Helper -- was this the wrong way to do it? Was I meant to put them in /Extra/Extensions in the root of my filesystem? If so -- that may possibly be the issue ;-).

Thanks again!

[rcfa]

Then you can overwrite most of what Chameleon Installer did, by usind dd to copy the disk image's EFI partition over to your boot drive.

I still don't know what you mean by this, and I've been meaning to ask.  Is there a hidden EFI partition in the recoverySDcard thing you made?  If so, what are the benefits of overwriting my EFI partition with it?  I think I've tried mounting my EFI partition using commands that you provided once, but it failed saying mount_hfs was invalid or something.

Can you provide me a little more detail on this?  Thanks!  Oh, and any news on V3?

The SD card images is an "entire device image", the device has two partitions, an EFI partition exactly the same size as what Mac OS X creates when you partition a reasonably large drive (large enough that OS X thinks it's a bootable drive; getting that sort of partition onto the SD card is a different issue, but I took care of that ), plus the partition that you see when you just mount that disk image.

The EFI partition isn't expressly "hidden", but the same Mac OS X mechanisms that hide the boot drive's EFI partition hide that EFI partition. I assume the OS just looks at the partition type UUID, and if it matches that which it assigns to EFI partitions, then it won't show them.

So assuming your SD card, or the SD card disk image is on /dev/disk1, then the partition you'll see mounted in the Finder is /dev/disk1s2
The EFI partition is /dev/disk1s1 in that case. So you can do (as root or sudo)

dd if=/dev/disk1s1 of=/dev/disk0s1

and as a result the entire EFI partition is over there, ready to use, incl. dsdt.aml, Extra/Extensions, Extra/Extensions.mkext, Extra/com.apple.boot.plist, smbios.plist, etc.

Come v3, you will have to edit a couple of files on that partition for fine tuning, because you will have to adjust the UUID in UUID.kext, and enter your computer's real serial number in smbios.plist

As for timing for v3: it's basically done. I tried to look into the custom hardware button support (blue Fn Keys for volume, brightness, etc. plus the four silver keys above the regular keyboard). But that will take a bit more work/research than I have time for at the moment, and the brightness keys work as is, as does the sleep and power button, and getting the rest to work isn't really essential.

So hopefully I get around to uploading v3 by the end of the weekend the latest, hopefully sooner.

[rcfa]

I screwed the keyboard up as the kexts in /System/Library/Extensions in the DMG you provided I imported into my own kext library using Kext Helper -- was this the wrong way to do it? Was I meant to put them in /Extra/Extensions in the root of my filesystem? If so -- that may possibly be the issue ;-).!

Possible. You really shouldn't need any other kext than the ones I supplied. There are tons and tons of different kexts that I tried, researched, used to fix certain issues, until I realized there are better, cleaner ways to get these things fixed.

What I put together is both minimal, but also addresses all issues that I'm aware of and that are known to be fixable. If you have anything that doesn't work with vanilla Mac OS X plus what's on my disk image, let me know, and I'll check it out, but you really shouldn't have to combine any "own kext library" with what's there. Basically, what you see in the provided /System/Library/Extensions folder should be added properly to your boot drive's /System/Library/Extensions folder, if necessary replacing Apple extensions with the same name.  kextHelper should do the right thing.

However, what's there only works in conjunction with the kexts that should be in the Extra/Extensions folder on your EFI partition. How to get them there, see my previous post.
Just be sure to install Chameleon onto the EFI partition BEFORE you dd my EFI partition over, otherwise the Chameleon installer will stomp over what you just put there.

v3 will also contain a readme file with a very short abstract on how to install. It's not a detailed guide, but it will give the sequence of the major steps.

[pootify]

Here's rcfa's latest retail package, version 3:

http://www.zshare.net/download/61283437c6f80315/

[primal51]

With the V3 can we install it over V2. I'm having a hard time getting V2 working without proper (step-by-step) instructions. I'm going to test V3 now and let you know how I make out.

EDIT
I've tried these steps 3 times and I can get the base install working great. 10.5.7 upgrade works fine. I run into problems when trying to do the Chameleon and kext order. I get the installs done but when I try to boot I'm stuck at a boot loop. Same issue 3 times. I'm having a hard time with the instructions provided for the order and commands on each program.

Could we have updated step by step processes for Mac Newbs? I've reviewed the V3 documents several times but my environment doesn't match (hdd and SDHC sizes are different)

[max]

A bit off topic but a quick question:  with the retail install and hyperthreading working, what is your xbench speed? 

[EGOvoruhk]

Could we have updated step by step processes for Mac Newbs?

Another vote for this. I got a little lost myself

[LonelyTV]

Could we have updated step by step processes for Mac Newbs?

Another vote for this. I got a little lost myself

I've been working on finishing up this and updating it with RCFA's newest archive. However, I've entered the last weeks of my Summer classes so I've had to put it on hold. I'll get to it ASAP. Sorry for the hold up, I should have finished it when I started it.

[primal51]

Could we have updated step by step processes for Mac Newbs?

Another vote for this. I got a little lost myself

I've been working on finishing up this and updating it with RCFA's newest archive. However, I've entered the last weeks of my Summer classes so I've had to put it on hold. I'll get to it ASAP. Sorry for the hold up, I should have finished it when I started it.

Take all the time you need, we appreciate the hard work that has already been put in. I'm a patient man and school is much more important.

[rcfa]

A bit off topic but a quick question:  with the retail install and hyperthreading working, what is your xbench speed? 

Hyperthreading may slow down a synthetic benchmark like that, while improving latency and responsiveness in system heavily multitasking. I ran each version of the test only once, so these are not averaged out to cancel naturally occurring variations due to background processes.
Also, I have a 5400rpm 500GB drive in there, which is likely quite a bit faster than the 160GB drive in the system standard, at least when it comes to sequential reads and writes. My RAM is maxed out at 2GB (anyone try a 4GB SO-DIMM yet?) Lastly, these numbers might look quite a bit different with an external, higher-res screen attached...

That said, here are the overall numbers from Xbench 1.3, Mac OS X 10.5.7, all the latest updates, incl. Safari 4.0.1, etc.:

Hyperthreading enabled:
===============
Quartz: 41.60
Quartz Extreme: 35.73 (makes you wonder why one should bother with the GMA950 driver and not just use the AppleIntelIntegratedFramebuffer that's active when you safe-boot, but one would lose some of the nice visuals that QE allows...)
Quartz GL: 34.94 (hence, no point in using the hack to turn on QuartzGL, which Apple has only there for developers to prepare for SnowLeopard anyway, and which isn't enabled by default on any Mac AFAIK)

Hyperthreading disabled:
===============
Quartz: 36.07
Quartz Extreme: 36.72
Quartz GL: 32.20

So I for my part will keep HT enabled and run without QuartzGL but with QuartzExtreme, i.e. the standard config you'll get if you don't mess with things.

[max]

Thank you, RCFA, for the xbench results.  Now I have a benchmark for a retail install.

In a previous post, you mentioned that you have hybrid GUID/MBR partition table makes your dual boot system work properly.  You also mentioned that it is not recommended for n00bs to attempt, as it is tricky process.  I found this article (http://www.mydellmini.com/forum/mac-os-x-guides/8495-dual-boot-win-7-osx-guide.html) which details the creation of GPT partition table.  What are your thoughts? 

[rcfa]

Thank you, RCFA, for the xbench results.  Now I have a benchmark for a retail install.

In a previous post, you mentioned that you have hybrid GUID/MBR partition table makes your dual boot system work properly.  You also mentioned that it is not recommended for n00bs to attempt, as it is tricky process.  I found this article (http://www.mydellmini.com/forum/mac-os-x-guides/8495-dual-boot-win-7-osx-guide.html) which details the creation of GPT partition table.  What are your thoughts? 

The GPT/MBR hybrid table is the relatively easy part, you get that by simply partitioning the drive with Disk Utility. The thing is, that XP seems not to be able to boot from any partition but the first or the fourth, so you need a tiny spacer partition between the OS X partition and the WinXP partition.
The other problem is setting the partition types, which gpt doesn't let you do easily, since it demands exclusive disk access, so I ended up writing down all the partition boundaries, and wiping and recreating the partition tables with the required partition types from scratch, using the figures written down before. This works fine, because the data in the partitions isn't affected by this (provided you make no mistake).
In short, it's not difficult, if you know how gpt and fdisk work and what they do, but it's not something that lends itself to be written up in a fool-proof how-to, particularly since I use a 500GB drive and most will likely stick with their 160GB drive, etc.

Here's what my setup looks like:

Code: [Select]

> sudo gpt -r show /dev/disk0

gpt show: /dev/disk0: Suspicious MBR at sector 0
      start       size  index  contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  842555440      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  842965080     262145      3  GPT part - 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
  843227225  133540840      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  976768065       5070         
  976773135         32         Sec GPT table
  976773167          1         Sec GPT header

> sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 60801/255/63 [976773168 sectors]
Signature: 0xAA55
         Starting       Ending
 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
*1: EE    0   0   2 -  384  75  14 [         1 -     409639] <Unknown ID>
 2: AF  385   0   1 - 1023  75  14 [    409640 -  842555440] HFS+       
 3: 82 1023  75  14 - 1023  75  14 [ 842965080 -     262145] Linux swap 
 4: 07 1023  75  14 - 1023  75  14 [ 843227225 -  133540840] HPFS/QNX/AUX



[LonelyTV]

Classes are over!! I'll work on getting this updated tomorrow.

[primal51]

Classes are over!! I'll work on getting this updated tomorrow.

Fantastic, I've been waiting for that I hope you did well with your classes

[nickca]

I tried installing retail OSX on my 1000HE using rfca's v3 kit, and it mostly worked, except for WiFi, which unfortunately makes it unusable. I have swapped the stock card for an Apple Airport Extreme, however it is the Atheros variety and not the Broadcom one. Here's what I did:
1. Booted my retail Leopard disc, I pre-ordered Leopard so the disc is the original version 10.5. Install goes fine.
2. Rebooted and did initial setup. Airport card is recognized perfectly, no problems so far.
3. Updated to 10.5.7. Rebooted in safe mode. No Airport icon in menu bar, not sure if this is because I'm in safe mode or if the 10.5.7 update kills it. Install Chameleon, EFI partition, kexts, etc.
4. Reboot with everything installed. No Airport. Console reports an error loading the Atheros kext. If I load it manually, I get an error mentioning something like "UUIDs differ for IONetworkingFamily" or something similar.

Any ideas? Is it because rfca generated his stuff with a Broadcom card installed? How can I rectify this, short of installing a Broadcom card? The Atheros card should work fine. It's a stock, Apple-branded card, and worked with no modifications in iDeneb.

[rcfa]

I tried installing retail OSX on my 1000HE using rfca's v3 kit, and it mostly worked, except for WiFi, which unfortunately makes it unusable. I have swapped the stock card for an Apple Airport Extreme, however it is the Atheros variety and not the Broadcom one. Here's what I did:
1. Booted my retail Leopard disc, I pre-ordered Leopard so the disc is the original version 10.5. Install goes fine.
2. Rebooted and did initial setup. Airport card is recognized perfectly, no problems so far.
3. Updated to 10.5.7. Rebooted in safe mode. No Airport icon in menu bar, not sure if this is because I'm in safe mode or if the 10.5.7 update kills it. Install Chameleon, EFI partition, kexts, etc.
4. Reboot with everything installed. No Airport. Console reports an error loading the Atheros kext. If I load it manually, I get an error mentioning something like "UUIDs differ for IONetworkingFamily" or something similar.

Any ideas? Is it because rfca generated his stuff with a Broadcom card installed? How can I rectify this, short of installing a Broadcom card? The Atheros card should work fine. It's a stock, Apple-branded card, and worked with no modifications in iDeneb.

Well, yes, I have a Broadcom card in my system. However, since I use the vanilla Apple WiFi drivers, if you have a truly, original Apple WiFi card that's Atheros based, it should work, too, because I didn't modify anything about these drivers. I'm somewhat mystified by your description...

A few of things you could check:
a) is the device ID reported by the card one that Apple's drivers are supposed to recognize?
b) make sure the /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist lists the interfaces in the proper order, i.e. built-in ethernet is en0 and AirPort is en1
c) did you edit the red-colored kexts and files on the EFI partition and in /System/Library/Extensions? These files need to be edited to reflect your built-in ethernet adapter's MAC address, etc. for the system to have a proper UUID assigned to itself.

Actually, I'd probably check c) first

[nickca]

A few of things you could check:
a) is the device ID reported by the card one that Apple's drivers are supposed to recognize?

Yes, it's reported as a genuine Airport card in my iDeneb install, and upon reboot after the initial install of OSX (i.e. before updating to 10.5.7).

b) make sure the /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist lists the interfaces in the proper order, i.e. built-in ethernet is en0 and AirPort is en1

Yes, they're in that order.

c) did you edit the red-colored kexts and files on the EFI partition and in /System/Library/Extensions? These files need to be edited to reflect your built-in ethernet adapter's MAC address, etc. for the system to have a proper UUID assigned to itself.

I don't see anything red colored in the System/Library/Extensions folder on the SD card, and the only red colored files I see on the EFI partition are UUID.kext and smbios.plist, which I did edit as per the instructions. Is there something else I'm supposed to edit besides those?

[rcfa]

Well, that's all I can think of, really.
(I wrote the other e-mail from memory, so I couldn't see if I ended up having the UUID.kext on the EFI partition or in /System/Library/Extensions/ hence the reference to red-colored files there, which you can ignore)

SystemProfiler sees the card? If so, as what is it reported?

What BIOS version and settings do you have?

Did you try a repair permissions? Did you try deleting /System/Library/Extensions.mkext ?
Did you install all post 10.5.7 update that Apple has out (which includes, IIRC some AirPort related updates)?

Did you try booting with the -f option?
Did you try deleting the boot chache?

Really just guessing here, because it sounds like you did the right things, and more to the point, WiFi drivers are something that I never messed with (even the setting of the UUID affects the ethernet, not the WiFi)

[EGOvoruhk]

Classes are over!! I'll work on getting this updated tomorrow.

Sweet!

I was wondering if you've seen this yet: http://www.insanelymac.com/forum/index.php?showtopic=168500

I was messing around with it while I waited for your quide. I actually installed it to an SD card, and put the Extension.mkext from the V3 pack on it, and it boots great, just like the Boot-132 CD I was using. I even partitioned the card, so I had the bootloader and restored a retail 10.5.6 image onto it, so I can do a fresh install from the SD slot without needing to hook up an external drive

Question though, what kexts are actually needed for the 1000HE to work perfectly? I opened the Extension.mkext, and I found tons and tons of kexts. Usually it's only half a dozen

[rcfa]

Classes are over!! I'll work on getting this updated tomorrow.

Sweet!

I was wondering if you've seen this yet: http://www.insanelymac.com/forum/index.php?showtopic=168500

I was messing around with it while I waited for your quide. I actually installed it to an SD card, and put the Extension.mkext from the V3 pack on it, and it boots great, just like the Boot-132 CD I was using. I even partitioned the card, so I had the bootloader and restored a retail 10.5.6 image onto it, so I can do a fresh install from the SD slot without needing to hook up an external drive

Question though, what kexts are actually needed for the 1000HE to work perfectly? I opened the Extension.mkext, and I found tons and tons of kexts. Usually it's only half a dozen

Just about all of them

Usually people just throw the extensions in that are are different, but if you build the mkext you get all sorts of errors about missing dependencies.
I included all the kexts that are required to satisfy the dependencies, such that the mkext builds cleanly.
This should speed up the boot process and make things a bit more predictable, although some of the bootprocess still seems like voodoo (pun intended).

You can see exactly what's in the Extensions.mkext by looking at the Extra/Extensions folder on the EFI partition, the Extensions.mkext is built straight from that, so you can delete it or rebuild it as you please without affecting the bootability of the system.

Colored kext files are required/modified/etc. (see color legend in the docu), the plain kexts are in there to satisfy dependencies, and can/must be replaced as a new version of the OS is released (e.g. 10.5.

[nickca]

rfca: I finally got it to work. I don't know why I even thought to try this, but I looked at IO80211Family.kext and IONetworkingFamily.kext on the EFI partition, and they were much older versions than I had in /System/Library/Extensions. They must have been conflicting, because I deleted them from the EFI partition, replaced them with the versions from /System/Library/Extensions, and rebuilt Extensions.mkext on the EFI partition (as detailed at the end of the EEE1000HEMods.rtf document). Lo and behold, I rebooted, and my Airport card worked!  Awesome! I don't know why I would have to do this with the Atheros variety and you wouldn't with the Broadcom, but it fixed everything. Thanks a lot for all your work/help!

If I get time, I'll try to write a little guide with more detailed info on updating to 10.5.7, installing Chameleon, the EFI partition, the kexts, etc. I probably had to reinstall 5 or 6 times before I finally got it right, and I'm pretty knowledgeable about OSX.

[rcfa]

rfca: I finally got it to work. I don't know why I even thought to try this, but I looked at IO80211Family.kext and IONetworkingFamily.kext on the EFI partition, and they were much older versions than I had in /System/Library/Extensions. They must have been conflicting, because I deleted them from the EFI partition, replaced them with the versions from /System/Library/Extensions, and rebuilt Extensions.mkext on the EFI partition (as detailed at the end of the EEE1000HEMods.rtf document). Lo and behold, I rebooted, and my Airport card worked!  Awesome! I don't know why I would have to do this with the Atheros variety and you wouldn't with the Broadcom, but it fixed everything. Thanks a lot for all your work/help!

Sweet. Problem solved. I was seriously scratching my head for a while, because it didn't make sense.
Likely, some sort of AirPort update only updated the Atheros drivers, and not the Broadcom drivers, and hence there's no conflict with one, but the other. I guess I'll have to check if all the dependencies are still current (or simply replace all the non-colored extensions on the EFI partition with their /System/Library/Extensions/ versions before I start having similar issues...
Maybe I should add this to the instructions for future reference, that this is a step that needs to be considered after OS updates....

If I get time, I'll try to write a little guide with more detailed info on updating to 10.5.7, installing Chameleon, the EFI partition, the kexts, etc. I probably had to reinstall 5 or 6 times before I finally got it right, and I'm pretty knowledgeable about OSX.

Great, surely will help others.

All that's missing from 1000HE bliss at this point are some updated drivers for sound, hibernation, and figuring out why I occasionally after 28h+ non-sleep-uptime I get a kernel panic somewhere in the window server.
Actually, the last item is the only true show-stopper, lack of hibernation is an important missing feature, but a Chameleon update will likely fix that, and the rest are just minor inconveniences, but don't really impede any functionality. So we're getting close.

The next hurdle will be SnowLeopard...
...and hopefull we'll see laptop versions of the N330, and NetBooks that can take 8GB RAM (or at least 4GB)
like e.g. http://www.ionbased.com/2009/06/first-ion-netbook-with-atom-n330-announced/
or http://www.ionbased.com/2009/06/asrock-multibook-g22-is-clone-of-dospara-dual-core-netbook/

[nickca]

Now I'm getting frequent sound-related kernel panics. Sometimes it will panic while playing a sound, and opening the input preferences (from "Sound" in System Preferences, not the VoodooHDA prefpane) will panic it almost immediately. Also, occasionally when playing a sound, the system will freeze momentarily halfway though playing it, then unfreeze and play the rest of the sound. I've tried replacing the VoodooHDA.kext that come with the install .dmg with the latest version from voodooprojects.org and the older version on Google Code, and I get kernel panics with all of them. I saw another guy earlier in the thread was also getting audio-related kernel panics, were you able to fix them at all? I used this same version of VoodooHDA under iDeneb, and never got a single audio-related kernel panic.

[nickca]

Now I'm getting frequent sound-related kernel panics.

I just tried booting with "cpus=1" (no other flags), and this seems to fix the kernel panics. I can go to the input preferences in Sound and record with Audacity, when trying to do either before would instantly cause a kernel panic. I'll keep my fingers crossed, but this seems to have fixed the issue.