[GUIDE] Retail OS X Install (10.5.8) on Gigabyte GA-EX58-UD5 (Core i7) Mobo

[everdone]

Thanks for responding!

 

I always keep the OSX drive in sata slot 0 so it boots up first, tried it with slot 1 instead and booted into it via the bios (F12) and no dice (boots, but same behavior as other slot). Using ONLY the OSX drive everything is awesome. If I attach the other two drives, it'll boot up to desktop once. From there it seems to degrade...next reboot it makes it to desktop and the reboots itself after a minute of use. Thereafter, if I reboot it makes it to the gray startup screen but then crashes before hitting the desktop. I can always make it past chameleon, thankfully.

 

is there anything in particular I could send you from the crash logs that would be of use? Most of the output is French to me. Last two lines are:

_{0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib}

_{0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib}

 

Thanks again, MAJ!

Have you tried to set this up not using Chameleon? Using Chameleon2 with bootable OSes on different drives I have found to produce some undesired results. Chameleon always favors Disk0, unfortunately MacOS can change the disk ordering from one boot to the next, ie BIOS disk 0 is not always MacOS disk0. For example at one boot MacOS could be disk0, but at the next reboot the FAT drive could be disk0. As the Chameleon bootloader runs whatever is disk0 will appear in the start screen, if you let that 'play through' without selecting a drive quite often you get a hang or some other panic.

 

Try with Darwin as the Mac bootloader and use F12 to choose the boot HD. Using Darwin you will need to use the VooDoo kernel to avoid the clock speedup problem.

[goathead]

Have you tried to set this up not using Chameleon?

 

Aw crud, good call -- that could be it. I'd really hate to have to ditch Chameleon after all the time I've spent trying to get this thing up and running with Chameleon2! (That and I'd miss that crazy little lizard logo at bootup). Thanks for the idea, I'll try it after work.

 

Will dumping chameleon make my system less supportive of future OS upgrades?

[fade2nada]

hmm. i don't know why using cham2 or adding the string to boot.plist would kill the sound. in my /Extra/Stored_Kexts folder i have:

 

 HDAEnabler.kext/
  LegacyHDAController.kext/
  LegacyHDAPlatformDriver.kext/

 

just as put there by DD's script. you are going to have to watch it in verbose mode while booting to see what errors / etc. are coming out of the HDA drivers during boot. some of them might show up in console.app under console messages right after you boot up.

 

of course i am running a UD4P... it might have different sound hardware. i can't remember off the top of my head.

 

Joe, I am up and running. The sound problem originated from me using migration assistant to transfer my APPS and FILES (too lazy to re-install all my apps when they were working perfectly on previous install) I was using the user account that was transferred from the original Chamaleon install- once I used the user account that was CREATED by the retail install- the sound worked! Jumped through a few hoops with the video card and now sound but the install seems fine. Love the new "Themes" Thanks Major and Joe for your help and assistance. Greatly appreciated. This machine is an essential tool for me to showcase my creativity and get large processor intensive tasks done efficiently and quickly. Great Job! I hope Snow Leopard upgrade is seamless....

[Templeton Peck]

I think I've got a new one...

 

When I shut down, my computer just restarts! The machine appears to go through the full shut down process; the case fans and drives all turn off. Then about two seconds later, the machine starts back up again.

 

Shutting down from Windows works properly. Any ideas? I'm on F6 BIOS.

[snood]

So I have a question about installing osx using a retail disc. I have installed osx on several computers and prefer booting the retail disc and not using a distro like ideneb, ipc etc. Is this possible with the ud5 mobo? I am getting the last part of my liquid cooling system tomorrow and hopefully it will power up. If so does anyone have a premade boot123 disc?

[nabziF99]

Getting a "boot0: error" after running DD's script.

 

I have a UD5 (bios v5) with 2 SATA hard drives (on blue ports 2 and 4, nothing on the white JMicron SATA connectors); I first got up and running with iDeneb 1.4 10.5.6 on the drive on port 4; from there, I proceeded with DD's script. I followed each step: installed Chameleon 2 on the drive on port 2, set that partition as active, installed 10.5.6 DVD and then 10.5.7 combo update, kext installer and DSDT patcher; everything seemed to go well. Finally I chose option 16 to reboot, but instead of loading the new Chameleon and retail install, it just loaded the old Chameleon 1 from my iDeneb drive (and displayed that as the only available boot drive).

 

So to get the BIOS to look at the drive with the new install, I changed the Hard Disk Boot Priority setting so that the drive with the retail install was at the top, and rebooted. This time, right after "Verifying DMI Pool Data", it got stuck with the following:

 

boot0: GPT
boot0: testing
boot0: testing
boot0: error

 

I was sure I had set the new retail partition to active (step 3), but just in case, I rebooted to my iDeneb install, ran DD's script and just ran option 3 again to activate the retail partition, but it still displays the boot0 error when I set the highest Hard Disk Boot Priority to the retail partition. I also have "Hard Disk" as the First Boot Device in the same BIOS page. AHCI enabled, SMART enabled.

 

I searched and found that others have had this error, but the only suggestions given were that they had forgotten to set the target partition as active, or the BIOS is looking at the wrong drive; neither appear to be the problem in my case, unless I'm missing something.

 

Any ideas? Thanks!

[FUT1L1TY]

I searched and found that others have had this error, but the only suggestions given were that they had forgotten to set the target partition as active, or the BIOS is looking at the wrong drive; neither appear to be the problem in my case, unless I'm missing something.

 

Any ideas? Thanks!

 

Just for fun, try disconnecting all sata devices except the boot drive.

[goathead]

Aw crud, good call -- that could be it. I'd really hate to have to ditch Chameleon after all the time I've spent trying to get this thing up and running with Chameleon2! (That and I'd miss that crazy little lizard logo at bootup). Thanks for the idea, I'll try it after work.

 

Well, tried switching from Chameleon2 for the Darwin bootloader tonight and unfortunately got the exact same behavior when I attach the extra ntfs/fat32 drives: fail. It's as if the other two drives corrupt the Mac install somehow. Still, all I have to do is repair permissions and the boot cache and then it's back up...for just one session. then it always fails just before getting to the desktop on the gray apple screen. I can hear the other drives spool up just before it bites the dust, if that means anything. Maybe there's a SATA AHCI kext that can account for this behavior? Anyone with ideas, I'd appreciate it greatly!

[nabziF99]

Just for fun, try disconnecting all sata devices except the boot drive.

 

I disconnected the other hard drive and even the optical drive, leaving only the hard drive with the retail install attached. Same boot0 error. Does it sound like something hosed during the install and I should erase and try again?

[digital_dreamer]

I think I've got a new one...

 

When I shut down, my computer just restarts! The machine appears to go through the full shut down process; the case fans and drives all turn off. Then about two seconds later, the machine starts back up again.

 

Shutting down from Windows works properly. Any ideas? I'm on F6 BIOS.

I'm running F8b and don't have this issue, so try a update to F7, at least, and see how it goes. Make sure you have the OpenHaltRestart.kext installed, too.

 

So I have a question about installing osx using a retail disc. I have installed osx on several computers and prefer booting the retail disc and not using a distro like ideneb, ipc etc. Is this possible with the ud5 mobo? I am getting the last part of my liquid cooling system tomorrow and hopefully it will power up. If so does anyone have a premade boot123 disc?

I suspect you mean installing a Retail DVD without first installing a distro?

Premade ISOs are easy to come by and build (Slimbuild), but not easy to boot into.

Yes, I think that's possible. Try looking at the USB flash drive installs for some ideas. The best approach is to install a bootloader with patched kexts that will then run the OS X Installer. I'm currently looking into this and would like to make this easily done on a USB drive without requiring the user to install a distro or work from another Mac.

 

How-to Create a bootable ISO with Chameleon V2

 

regards,

MAJ

 

Well, tried switching from Chameleon2 for the Darwin bootloader tonight and unfortunately got the exact same behavior when I attach the extra ntfs/fat32 drives: fail. It's as if the other two drives corrupt the Mac install somehow. Still, all I have to do is repair permissions and the boot cache and then it's back up...for just one session. then it always fails just before getting to the desktop on the gray apple screen. I can hear the other drives spool up just before it bites the dust, if that means anything. Maybe there's a SATA AHCI kext that can account for this behavior? Anyone with ideas, I'd appreciate it greatly!

This is rather unusual, but it does sound like the bootloader is loading some erroneous information due to the WIN install.

Would you post the system.log file after the failed boot. I'd like to examine it.

 

I disconnected the other hard drive and even the optical drive, leaving only the hard drive with the retail install attached. Same boot0 error. Does it sound like something hosed during the install and I should erase and try again?

I know you said you installed the bootloader, but would you try that bootloader install, again, as that symptom indicates the BIOS has nothing to execute or run when it is looking at the right partition. I know it may sound a bit condescending, but make sure the bootloader gets installed on the right partition.

 

regards,

MAJ

[joeblough]

Joe, I am up and running. The sound problem originated from me using migration assistant to transfer my APPS and FILES (too lazy to re-install all my apps when they were working perfectly on previous install) I was using the user account that was transferred from the original Chamaleon install- once I used the user account that was CREATED by the retail install- the sound worked! Jumped through a few hoops with the video card and now sound but the install seems fine. Love the new "Themes" Thanks Major and Joe for your help and assistance. Greatly appreciated. This machine is an essential tool for me to showcase my creativity and get large processor intensive tasks done efficiently and quickly. Great Job! I hope Snow Leopard upgrade is seamless....

 

that's interesting. i did not use the migration assistant, instead i took my old boot/home disk and put it in the i7 and pointed my new account at it (new boot disk is a velociraptor, which is not big enought to contain my homedir). now i am having problems with user account preferences - i can't get the computer to remember to use a password on wake/screensaver and i noticed the other day that my color profiles are completely screwed up. if i make a new account that lives on the boot disk, the color profiles are fine and the screensaver password works fine...

[bbchucks]

I'm running F8b and don't have this issue, so try a update to F7, at least, and see how it goes. Make sure you have the OpenHaltRestart.kext installed, too.

I suspect you mean installing a Retail DVD without first installing a distro?

Premade ISOs are easy to come by and build (Slimbuild), but not easy to boot into.

Yes, I think that's possible. Try looking at the USB flash drive installs for some ideas. The best approach is to install a bootloader with patched kexts that will then run the OS X Installer. I'm currently looking into this and would like to make this easily done on a USB drive without requiring the user to install a distro or work from another Mac.

 

MAJ,

Check this new bootloader called Boothink.

 

http://www.insanelymac.com/forum/index.php...168500&st=0

 

it has a build-in cdrom driver.

Here is a demo shows usb stick boot and retail dvd install.

http://www.tudou.com/programs/view/9wyX20MjGPc/

[Templeton Peck]

I'm running F8b and don't have this issue, so try a update to F7, at least, and see how it goes. Make sure you have the OpenHaltRestart.kext installed, too

 

Thanks,

 

I updated to F7, and I got the same thing. Then I removed all my peripherals except for my Leopard drive, one video card, and a USB mouse and keyboard. Reset CMOS, and entered the settings you posted -- again, same issue. OpenHaltRestart is installed. Sleep works, restart works, but shut down behaves like restart (effectively). Weird, right?

 

UPDATE:

I tried removing OpenHaltRestart (just for the hell of it), but then the system didn't shut down fully (fans remained on).

 

Then I tried booting from an iPC disc I had downloaded prior. Since that was an installation disc, the shut down option was greyed out, so I opened up the Terimal and typed "shutdown -h now" That worked properly! So at least I know that shut down is possible. But is this command equivalent to clicking shut down from the Apple menu? To find out I booted back into my Vanilla install, and typed it into the terminal. I got the exact same problem as before. The machine shut down, and after a brief delay, started back up again!

 

So now I need to figure out why shut down works for my iPC disc, but not my vanilla install. I know that iPC uses the Voodoo kernel, so I hope that's not the answer, but I'll keep digging...

 

UPDATE 2:

I've solved the shut down issue. I changed PME Event Wakeup to [Disabled] in the BIOS. Now when I turn off the machine, it STAYS OFF!

 

The bad news is that now sleep no longer works -- more specifically, the system doesn't wake up. Enabling PME Event Wakeup makes no difference, so the problem must lie elsewhere. I'll give it another half hour --if I can't figure it out by then, I'm just going to disable sleep altogether with Insomnia.kext. I've had sleep issues on some of my REAL MACS, so for all I know, it might not even be hackintosh-related.

[nabziF99]

I know you said you installed the bootloader, but would you try that bootloader install, again, as that symptom indicates the BIOS has nothing to execute or run when it is looking at the right partition. I know it may sound a bit condescending, but make sure the bootloader gets installed on the right partition.

 

regards,

MAJ

 

I tried, but to no avail:

1. Changed Hard Disk Boot Priority to disk with the iDeneb partition (partition name is "Safetyboot"). Rebooted.

2. Launched RUN-PATCH_INSTALLER. It says "You are installing to Brickhouse (Disk0s2). Is this correct?" ("Brickhouse" is indeed the name of my retail partition, so I type y)

3. Ran step 2) Install bootloader (pre-patch). It gives option 2 as Chameleon_v2_RC1. I pressed 2. It said "Installing Chameleon_v2_RC1 on Brickhouse..." and then "Bootloader installed SUCCESSFULLY!"

4. Rebooted, changed Hard Disk Boot Priority to the disk with the Retail partition. Sure wish there were a quicker/easier way of doing that (like perhaps the Startup Disk pref).

5. Error again. boot0: GPT, testing, testing, error. So I change priority back to Safetyboot, and here I am, back in blah iDeneb land

 

So the BIOS does seem to be looking at the correct drive as you say, just not finding Chameleon 2. I tried making the Brickhouse partition active again, but no change.

 

Could iDeneb somehow be making itself active each time I reboot? The physical drive I'm installing to has Brickhouse as the first partition, and a small 32GB FAT volume (currently empty) as the second partition - could that be screwing with things? Or any other ideas?

[nabziF99]

The physical drive I'm installing to has Brickhouse as the first partition, and a small 32GB FAT volume (currently empty) as the second partition - could that be screwing with things?

 

Well the partition wasn't the problem, because I just re-partitioned the retail drive as just 1 big 1.5TB HFS+ Journaled partition, and went through the whole install process again (installed Chameleon 2, active, etc)...same thing. Ends with boot0: error.

 

I even tried plugging the drive with the retail install into SATA port 0 instead of port 2...same error.

 

With those possibilities out of the way...any other ideas?

 

(Question: I unzipped the script folder to the desktop of my iDeneb partition, and have been running it from there...the script doesn't have to be copied and launched from the target partition, or something silly like that, does it?)

[nabziF99]

Tried reinstalling again, this time, I figured I'd peek at the logs to see what on earth could be going on with the installation of the bootloader. Here is what I found:

<==================>   Install Bootloaders (pre-patch)   <==================>
Volume Brickhouse mounted and ready.
Installing Chameleon_v2_RC1...
mkdir: created directory '/Volumes/Brickhouse/Extra'
mkdir: created directory '/Volumes/Brickhouse/Extra/Stored_Kexts'
Copying bootloader files (boot0, boot1h, and boot) to Brickhouse:
2+0 records in
2+0 records out
1024 bytes transferred in 0.002095 secs (488787 bytes/sec)
chmod: 755: No such file or directory
chown: illegal option -- r
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
   chown [-fhv] [-R [-H | -L | -P]] :group file ...

#### Boot file copied to Brickhouse:
--wx--x--x@ 1 root  staff	 279168 Jun 17 19:46 boot

Copying contents of Chameleon_v2_RC1/Extra to /Volumes/Brickhouse/Extra

<==================>   Activate Drive   <==================>
Unmount of all volumes on disk0 was successful
Enter 'help' for information
fdisk: 1> Disk: /dev/disk0	geometry: -5415445/4/63 [-1364692241 sectors]
Offset: 0	Signature: 0xAA55
	 Starting	   Ending
#: id  cyl  hd sec -  cyl  hd sec [	 start -	   size]
------------------------------------------------------------------------
1: EE 1023 254  63 - 1023 254  63 [		 1 -	 409639] <Unknown ID>
2: AF 1023 254  63 - 1023 254  63 [	409640 - -1431801104] HFS+		
3: 0B 1023 254  63 - 1023 254  63 [-1431128064 -   66435072] Win95 FAT-32
4: 00	0   0   0 -	0   0   0 [		 0 -		  0] unused	  
fdisk: 1> Partition 2 marked active.
fdisk:*1> Writing MBR at offset 0.
fdisk: 1> Brickhouse partition made active!

 

The only thing that stood out were the chmod and chown errors...working as intended? Or possible cause of my boot0: error?

[JustinAiken]

Hi, I have the UD4P, which I believe has the same sound and SATA chipsets...

 

1) How do I get ACHI mode to work in XP? I can boot XP if I switch to IDE mode, but that's a pain for dual-booting!!!

 

2) I can't get sound to work... I tried putting some of the various sound files I've seen about the 889a in /S/L/E, repairing permissions, and rebuilding the cache... it shows up in system profiler now:

 

"Intel High Definition Audio:

 

Device ID: 0x1458A102

Audio ID: 12

Available Devices:

"

 

But not in the sound pane!

[L3B3R]

Core i7 Theme

 

Click here:

Hac Pro Theme

 

I made a Core i7 Hac Pro theme for anyone who is interested. This package includes an "about this mac" graphic, boot picture, and Chameleon 2 theme. The "about this mac" graphic has already been incorporated into digital_dreamer's script v3.7 and I finally had time to finish everything else. I give permission for DD to include this package into the next update.

 

I am sorry but I do not have time to support this package. Please view the "read_me" that it contains.

 

The screenshots are not that great, but you get the idea.

 

[digital_dreamer]

Tried reinstalling again, this time, I figured I'd peek at the logs to see what on earth could be going on with the installation of the bootloader. Here is what I found:

<==================>   Install Bootloaders (pre-patch)   <==================>
Volume Brickhouse mounted and ready.
Installing Chameleon_v2_RC1...
mkdir: created directory '/Volumes/Brickhouse/Extra'
mkdir: created directory '/Volumes/Brickhouse/Extra/Stored_Kexts'
Copying bootloader files (boot0, boot1h, and boot) to Brickhouse:
2+0 records in
2+0 records out
1024 bytes transferred in 0.002095 secs (488787 bytes/sec)
chmod: 755: No such file or directory
chown: illegal option -- r
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
   chown [-fhv] [-R [-H | -L | -P]] :group file ...

#### Boot file copied to Brickhouse:
--wx--x--x@ 1 root  staff	 279168 Jun 17 19:46 boot

Copying contents of Chameleon_v2_RC1/Extra to /Volumes/Brickhouse/Extra

<==================>   Activate Drive   <==================>
Unmount of all volumes on disk0 was successful
Enter 'help' for information
fdisk: 1> Disk: /dev/disk0	geometry: -5415445/4/63 [-1364692241 sectors]
Offset: 0	Signature: 0xAA55
	 Starting	   Ending
#: id  cyl  hd sec -  cyl  hd sec [	 start -	   size]
------------------------------------------------------------------------
1: EE 1023 254  63 - 1023 254  63 [		 1 -	 409639] <Unknown ID>
2: AF 1023 254  63 - 1023 254  63 [	409640 - -1431801104] HFS+		
3: 0B 1023 254  63 - 1023 254  63 [-1431128064 -   66435072] Win95 FAT-32
4: 00	0   0   0 -	0   0   0 [		 0 -		  0] unused	  
fdisk: 1> Partition 2 marked active.
fdisk:*1> Writing MBR at offset 0.
fdisk: 1> Brickhouse partition made active!

 

The only thing that stood out were the chmod and chown errors...working as intended? Or possible cause of my boot0: error?

nabziF99,

Thank you for that log. That was revealing. I found the problem and will upload an update shortly (tonight).

My apologies for the trouble.

 

kind regards,

MAJ

[goathead]

This is rather unusual, but it does sound like the bootloader is loading some erroneous information due to the WIN install.

Would you post the system.log file after the failed boot. I'd like to examine it.

 

regards,

MAJ

 

Hey MAJ! Thanks for taking a look at this!

Already I can see some unholy things going down in this log (I was looking at the wrong logs it seems) Looks like it's setting my ram at the wrong speed (1600 rather than 1333), sets me as a MacPro3,1 (??). You'll see I threw in an extra jmicron.kext to try to fix things (blindly & in vain) -- I'm attaching the last most important bits as it seemed to repeat itself.

 

systemlog.txt

 

Thanks again!

d.

[goathead]

Hi, I have the UD4P, which I believe has the same sound and SATA chipsets...

 

2) I can't get sound to work...

 

Hey Justin,

 

I'm not near my computer currently but I have the same board as you and just recently got the sound working. Couple things that might help you out:

-Make sure and remove any extra audio kexts you've added manually to S/L/E (such as ALCInject I believe...sorry, not near the computer right now)

-You will need a patched AppleHDA.kext for the ALC889a (search and you shall find, they're everywhere--there's also an HDA patcher that allows you to patch your own)

-LAST THING you'll need is the audio kexts from the ex58-ud5 kext pack in this thread. The ones you want are marked orange I believe and they are outside of the ALC889a folder

 

Goodluck! (I'm still trying to accomplish a dual boot with ACHI -- I get crashes whenever attaching other drives in ahci...grrr)

 

d.

[digital_dreamer]

UPDATE: 6/18/2009

• Script version 3.8 is released.
  
• Fixed a serious file permissions bug affecting the bootloader.
  
• Added ability to copy kernels with .voodoo or other extensions. The "mach_kernel" suffix must be maintained, however, for proper script operation.
  
• Added ability to restore original kernel and system.kext.
  
• Added ability to unpack and examine contents of current mkext file.
  
• When installing a kernel and matching System.kext, the System.kext will install into S/L/E by default.
  
• Fixed a bug so that the System.kext in the _For_System folder will be preserved when that kext is removed from Script's Kernels folder.
  
• Added the new Voodoo2 alpha3 9.7.0 kernel.
  

regards,

MAJ

[beboy]

You mean "3.2Ghz Unknown"? (wording transposed.)

Is it OCed to 3.2? What bootloader are you using?

When you attempt to change name, are you working on the correct hard drive?

Yeah i guess it's "3.2Ghz Unknown", my OS is in french so I translated "3.2ghz inconnu". When i switch my system to english language and restart, the About box still shows "3.2ghz inconnu" in french...

My i7 920 is not overclocked, still at 2.66ghz, and i use the chameleon 2.0 bootloader.

That's weird because when i use your script (v3.7) to change the Processor info, it already says : "Your current Processor info is: 2.66 GHz Intel® Core™ i7 920 CPU"...

And yes I'm working on the correct drive.

Maybe i should boot on a other OS X partition before running the script (i have an iPC 10.5.6 backup partition) ?

 

Thanks for your help DD

[Templeton Peck]

UPDATE: 6/18/2009

• Script version 3.8 is released.
  
• Fixed a serious file permissions bug affecting the bootloader.
  
• Added ability to copy kernels with .voodoo or other extensions. The "mach_kernel" suffix must be maintained, however, for proper script operation.
  
• Added ability to restore original kernel and system.kext.
  
• Added ability to unpack and examine contents of current mkext file.
  
• When installing a kernel and matching System.kext, the System.kext will install into S/L/E by default.
  
• Fixed a bug so that the System.kext in the _For_System folder will be preserved when that kext is removed from Script's Kernels folder.
  
• Added the new Voodoo2 alpha3 9.7.0 kernel.
  

regards,

MAJ

Sounds wonderful. Thanks for your hard work!

 

One thing I forgot to mention earlier is that when I first tried to run your script without a password, it didn't accept <no password> as a password. While bad practice in general, I figured it would make troubleshooting easier (Of course I used a password on my target install). Anyway, I ended up setting a password and running the script again, and all went well. But I just thought I'd let you know...

 

Again, thanks for your hard work.

 

Yeah i guess it's "3.2Ghz Unknown", my OS is in french so I translated "3.2ghz inconnu". When i switch my system to english language and restart, the About box still shows "3.2ghz inconnu" in french...

My i7 920 is not overclocked, still at 2.66ghz, and i use the chameleon 2.0 bootloader.

Mine looks like that too, whether at stock speeds or overclocked. It didn't bother me, so I left it alone. One thing I did notice, though, is that DD's CPU-X info looks a lot more accurate than mine (and presumably yours). I think this could have something to do with the different chip steppings.

 

That's weird because when i use your script (v3.7) to change the Processor info, it already says : "Your current Processor info is: 2.66 GHz Intel® Core™ i7 920 CPU"...

I think "2.66 GHz Intel® Core™ i7 920 CPU" is the name that's hard-coded into the chip, whereas "About This Mac" actually tries to calculate the speed (incorrectly, in our case).

[ingalz]

Solved!

 

Run Parallels with vanilla kernel and no KP. I also had KP problems with sustained network load.

 

I found a method that solves this problem and uses the vanilla kernel.

 

Step 1: Follow the steps to the EFI partition install method

Step 2: Install to newly prepared EFI partition disk using digital dreamer method with the following exceptions:

2.a. do not select a bootloader

2.b. use retail install disk (when installation is finished, do not hit continue rather)

2.c. download and install the osx combo update 10.5.7 (select appropriate target disk to install)

2.d. continue the remaining steps (some won't run, that is OK, you can install kexts after bootup using kext helper or osx86 tools).

Step 3: Boot right up into 10.5.7. Install the kexts from DD. Use your favorite graphics installer method.

Step 4: Parallels away. Also, system is now stable under heavy net load!

 

Cheers