[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[Budge]

Well, I've tried following the instructions, but something seems to be wrong.

 

Twice now, I've booted my Hackintosh disk and I get the following message during POST:

 

Verifying DMI pool data........

boot0: GPT

boot0: testing

boot0: testing

boot0: error_

 

So I've been thinking about what I may have done wrong. I ran back through the process a third time and realized that I have made the ASSUMPTION that choosing the EFI install is necessary if I want to use the PC_EFI bootloader. If that's not the case, then maybe the Extra install would be easier and I could still use the PC_EFI bootloader? From what I read, the EFI install method is less susceptible to update issues, so I would prefer that type. Is this why I'm getting the error.

 

So to recap, I have my target HDD attached to my Leopard iMac with an external USB enclosure. I'm partitioning the target drive in Disk Utility to a GUID partition. I run the patch installer, choose my new partition, select EFI install, load the PC-EFI bootloader, set target partition as active, and install Retail DVD. After that, I try to run the Kext/Kernel Installer, but I get the following text in yellow:

 

The Chameleon bootloader does not appear to have been installed.

(There is no /Extra directory on Hackintosh - EFI)

 

Then it's just the main patch installer menu. I didn't notice this on the first two go arounds. I got the boot error when I tried to boot from the hard drive in my Hackintosh machine.

 

After this latest attempt at running the Kext/Kernel Installer, I tried to use Option 8 to View EFI Partition and got:

 

chown: /Volumes/EFI: No such file or directory

chmod: /Volumes/EFI: No such file or directory

 

EFI partition does not appear to be a valid HFS-formated partition.

 

So what am I doing wrong?

[knightprozac]

Budge:

 

Read the first post made by DD thoroughly (maybe a few times if you don't fully understand after reading once).

[LocusOfControl]

Well, I've tried following the instructions, but something seems to be wrong.

 

Twice now, I've booted my Hackintosh disk and I get the following message during POST:

 

Verifying DMI pool data........

boot0: GPT

boot0: testing

boot0: testing

boot0: error_

 

So I've been thinking about what I may have done wrong. I ran back through the process a third time and realized that I have made the ASSUMPTION that choosing the EFI install is necessary if I want to use the PC_EFI bootloader. If that's not the case, then maybe the Extra install would be easier and I could still use the PC_EFI bootloader? From what I read, the EFI install method is less susceptible to update issues, so I would prefer that type. Is this why I'm getting the error.

 

So to recap, I have my target HDD attached to my Leopard iMac with an external USB enclosure. I'm partitioning the target drive in Disk Utility to a GUID partition. I run the patch installer, choose my new partition, select EFI install, load the PC-EFI bootloader, set target partition as active, and install Retail DVD. After that, I try to run the Kext/Kernel Installer, but I get the following text in yellow:

 

The Chameleon bootloader does not appear to have been installed.

(There is no /Extra directory on Hackintosh - EFI)

 

Then it's just the main patch installer menu. I didn't notice this on the first two go arounds. I got the boot error when I tried to boot from the hard drive in my Hackintosh machine.

 

After this latest attempt at running the Kext/Kernel Installer, I tried to use Option 8 to View EFI Partition and got:

 

chown: /Volumes/EFI: No such file or directory

chmod: /Volumes/EFI: No such file or directory

 

EFI partition does not appear to be a valid HFS-formated partition.

 

So what am I doing wrong?

 

/Volumes/EFI doesn't exist by default, you need to create it manually if you want to look what's inside there

 

eg cd /Volumes

mkdir EFI

 

You can't normally see EFI/Extra etc, you need to manually create a mount point eg /Volumes/EFI, then mount

the EFI/Extra partition on top of it. Confusingly 'convention' is to name the mount point directory EFI the same as

the partition

 

if you do diskutil list in a terminal window you can see something like this

 

note make sure you pick the correct EFI partition if you have more than one OS X drive

 

in this case there is only one

 

mount_hfs /dev/disk1s1 /Volumes/EFI

 

bash-3.2# [color="#FF0000"]cd /volumes
[/color]bash-3.2# ls
.DS_Store	ATI_092308	SnowLeopard	Untitled
bash-3.2# [color="#FF0000"]diskutil list[/color]
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:     FDisk_partition_scheme                        *500.1 GB   disk0
  1:               Windows_NTFS                         500.1 GB   disk0s1
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *1.0 TB     disk1
[color="#FF0000"]   1:                        EFI                         209.7 MB   disk1s1[/color]
  2:                  Apple_HFS SnowLeopard             999.9 GB   disk1s2
/dev/disk2
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:                            ATI_092308             *2.6 GB     disk2
bash-3.2# !mkd
[color="#FF0000"]mkdir EFI[/color]
bash-3.2# !moun
[color="#FF0000"]mount_hfs /dev/disk1s1 /Volumes/EFI[/color]
bash-3.2# cd EFi
bash-3.2# ls -l
total 3744
-rwxr-xr-x@  1 xxxxxxxxxx  admin   15364  1 Jan 11:45 .DS_Store
drwxr-xr-x@  3 xxxxxxxxxx  admin     102  6 Sep 15:50 .Trashes
-rwxr-xr-x   1 root         admin       0  6 Sep 15:36 .com.apple.timemachine.supported
drwxr-xr-x   3 root         admin     102 30 Dec 15:50 .fseventsd
drwxr-xr-x  27 root         wheel     918  1 Jan 11:58 Extra
[color="#FF0000"]-rwxr-xr-x@  1 root         wheel  321408 30 Dec 15:03 boot[/color]
-rwxr-xr-x@  1 root         wheel  307968 30 Sep 10:56 boot-pcefi10.3
-rwxr-xr-x@  1 root         wheel  313440 13 Oct 22:18 boot-pcefi10.4
-rwxr-xr-x@  1 root         wheel  314016 25 Oct 14:35 boot-pcefi10.5
-rwxr-xr-x@  1 root         wheel  309344 30 Sep 10:49 boot-rc3
-rwxr-xr-x@  1 root         admin  321408 30 Dec 16:46 boot-rc4hacked
bash-3.2# cd Extra
bash-3.2# ls -l
total 608
-rwxr-xr-x   1 root  wheel   4064  7 Sep 14:33 BootHelp.txt
-rw-r--r--   1 root  wheel  18423 20 Dec 01:34 DSDT.amal.powerehci
-rwxr-xr-x   1 root  wheel  16356 30 Dec 12:13 DSDT.aml.HPETDRive
-rwxr-xr-x   1 root  wheel  16642 30 Dec 00:20 DSDT.aml.RTC
-rwxr-xr-x   1 root  wheel  10808  1 Jan 11:58 DSDT.aml.SAFE
-rwxr-xr-x   1 root  wheel  18187 18 Dec 01:01 DSDT.aml.d00d
-rwxr-xr-x   1 root  wheel  19259 29 Nov 15:09 DSDT.aml.lastWorking
-rwxr-xr-x   1 root  wheel  18187 29 Nov 15:09 DSDT.aml.power
-rwxr-xr-x   1 root  wheel  16761 29 Dec 11:20 DSDT.aml.satadelta
-rw-r--r--   1 root  wheel  18242 21 Dec 00:01 DSDT.aml.usb
[color="#FF0000"]drwxr-xr-x   3 root  wheel    102 31 Dec 12:18 Extensions[/color]
drwxr-xr-x   7 root  wheel    238 29 Oct 23:56 Sessions
drwxr-xr-x  16 root  wheel    544 10 Sep 22:12 Themes
[color="#FF0000"]-rwxr-xr-x@  1 root  wheel    789 30 Dec 16:45 com.apple.boot.plist[/color]
-rwxr-xr-x@  1 root  wheel    713 30 Dec 16:14 com.apple.boot.plist.edited
-rwxr-xr-x@  1 root  wheel    628 30 Dec 16:15 com.apple.boot.plist.pcefi10.5
-rwxr-xr-x@  1 root  wheel    672  5 Dec 14:20 com.apple.boot.plist.saved
[color="#FF0000"]-rwxr-xr-x   1 root  wheel  10808  1 Jan 11:57 dsdt.aml[/color]
-rwxr-xr-x   1 root  wheel  13602 31 Dec 12:17 dsdt.aml.LPCBfixed10c
-rw-r--r--   1 root  wheel  14386 30 Dec 14:40 dsdt.aml.cuts
-rw-r--r--   1 root  wheel  18082 28 Dec 22:12 dsdt.aml.kdawgwithOHR
-rw-r--r--   1 root  wheel  13602 31 Dec 01:33 dsdt.aml.lcpb
-rwxr-xr-x   1 root  wheel  10808 31 Dec 23:09 dsdt.aml.noJmicron
-rwxr-xr-x   1 root  wheel  18052 24 Dec 21:41 dsdt.aml.usb.kdawgedit
[color="#FF0000"]-rwxr-xr-x@  1 root  wheel   1748 30 Dec 16:41 smbios.plist[/color]
bash-3.2# [color="#FF0000"]cd /[/color]
bash-3.2# !umo
[color="#FF0000"]umount /Volumes/EFI[/color]
bash-3.2# 

 

I have highlighted the key parts and commands

 

When you finish editing it you should unmount it before you log out ie umount /Volumes/EFI

 

You should have either /Extra or /Volumes/EFI/Extra with content in it

 

My bootloader is installed in the EFI partition, but other people choose /Extra, if I had done that then the contents of

my ../Extra would be similar to what you would see in /Extra, ie you have a choice of two locations for your bootloader

 

 

By the way, you can run the chameleon rc2 installer by hand from your Leopard partition making the SL one

your target. Having done that successfully change the boot file to either RC3, RC4 boot or PCEFI 10.5 boot

 

The boot file will be in your root partition or /Volumes/EFI depending on your install

[myhobby]

I'm stuck.......................................

 

See my HW list below. Just upgraded my BIOS to this version, hoping it would solve my boot problem. It feels like these samsung hard disks are imcompatible... Spend DAYS on fora to find out why this is a problem, but no luck

 

I'm constantly stuck with Boot0 errors, where everybody used whatever tool and successfully installed SL.

 

Weird thing is..... I've SL running on a similar Samsung model, but I want to start all over....

 

Anyone familiar with similar problems and what was the solution ?

 

Kind regards

 

 

P.S I don't have any other problems with installing once it boots from the Hard drive

[zoro2]

Is is Critical that I either find a way to reboot into my old RAID set up or figure where the encrypted dmg file with my passwords stores it's key. New year and bills are past due . I know, my own stupidity for forgetting the password and using it daily on a system that remembered it. Really stupid of me, I think we can all agree on that.

 

And, I need to get it right again as soon as possible. In Leopard, when you store a value in a keychain, as in encrypting a dmg file, where exactly is this stored? I tried swapping in some keychainn files and no luick so far. What about the keychainsettings.nib file? THis contains files within it si I suppose it is actually a folder, anyway ...

 

Please, and thanks much as always.

 

ADDED: There was a discussion on the old Leopard instal thread where it was discussed how to get the disk ID of a smaller non raided drive and boot to that non raided drive which then handed off to the RAID drive.

 

I cannot find that discussion on the old thread. If anyone knows this info and/or where I may find it, I would be most grateful. If I could just return to my old RAID drive and system files, I Could open my passwords db once again, and store it that way - NEVER again!!!

[bossent20]

That's because during the install your system is in generic VESA mode and not relying on GPU drivers. The VESA mode is supported by all modern graphics cards and only provides basic features that can be provided by all cards.

Once you have installed the drivers and have rebooted, then you are relying on all the GPU's proprietary features. Whether this is successful or not depends on how complete your install process was. For nVidia cards, this requires EFI strings or some other sort of injector.

 

 

----------

 

thanks but what do i use then for my gtx 275. i am also pretty sure it is the nvidia drivers causing this panic.

 

do you know what i can do to make this work. what kext should i use to drag into the EXTRA folder

 

thanks

 

PS - does it only install from the extra folder prior to installing 10.6 or if after the install is done but then i ghet the KP, is it okay to then put the correct kext into the EXTRA folder on the USB, boot form there and see if the OS loads up, or does it have to be done beforehand?

 

simply put - can i update the EXTRA folder for booting into the OS?

 

thanks again

[gamala]

Thanks for the guide!

 

Just installed successfully Snow Leopard 10.6 to my system: Asrock X58 Deluxe, i7 920, Nvidia GTX 260, SATA DVD-drive.

 

I installed first Kalyway 10.5.2 to harddrive dedicated to OS X (divided to 2 partitions). Bios settings: all ACPI options off, number of cpus 1. Kalyway was installed with default settings, no adjustments were needed. Kalyway worked after installation ok but GTX 260 was not recognized so the display resolution was limited to 1024x768.

 

After that I followed this guide to install SL. I used EFI-boot installer. I used Snow Leopard 10.6 universal iso to install snow leopard (installation program on the disk). Then I finalized installation following the steps of this guide.

 

Snow Leopard booted successfully immediately after installation and graphics (1920x1200), audio and networking are working without any problems.

[Cindori]

Thanks a lot, VirusX.

 

I can't believe how authentic this is. Back in the summer I had so many kernel panics and random glitches, but man, NONE this time around! Well, besides chameleon not going to 1920 x 1080 and surround sound, but that's minor.

 

you can change chameleon resolution, edit the plist of your theme (/Extra/Themes/Yourcurrenttheme)

[Formal]

OK been playing with DD's script for a few days but got just one or two minor probs that it would be great to sort.

 

I am using an GB-EX58-UD3R board and by using PC EFI-10.5 with the normal DSDT load I get a fully operational system apart from no audio and no sleep.

 

I have tried a LOT of audio kexts but don't seem to be getting anywhere!

 

The soundset is realtek ACL888.

 

I also haven't upgrade to 10.6.2 yet, should I get the system fully up and running once kexts sorted and then move onto updating?

 

Thanks a bunch DD, it has made it very easy to get OS X running

[AppleIIGuy]

OK been playing with DD's script for a few days but got just one or two minor probs that it would be great to sort.

 

I am using an GB-EX58-UD3R board and by using PC EFI-10.5 with the normal DSDT load I get a fully operational system apart from no audio and no sleep.

 

I have tried a LOT of audio kexts but don't seem to be getting anywhere!

 

The soundset is realtek ACL888.

 

I also haven't upgrade to 10.6.2 yet, should I get the system fully up and running once kexts sorted and then move onto updating?

 

Thanks a bunch DD, it has made it very easy to get OS X running

 

Use VoodooHDA to get stereo sound only.

[defecta]

hey all. I pretty much got my 10.6.2 install almost perfect but I still have a few little issues. I was hoping I could find out if anyone else was having them too.

 

I am getting frequent DVD drive seeking/polling sounds coming from my DVD drive. It sounds like its checking for a disc in the drive and the intervals vary from lest than minute and anywhere up to 5 or more.

 

 

I also haven't been able to resolve the Bonjour/AFP issue with my system satisfactorily as Sonotone's fix from another thread seems to stop working for me after a few hours.

 

Has anyone else had these issues or better yet fixed them? I haven't been able to find an answer searching here.

 

Thx.

[abalamut]

Hello, everybody, I have a little question.

I have done everything as described above - everything is fine, but I have network problem.

I setup network & everything is work good, internet speed is ok - but when i try to connect to server near me (in my local subnet) it takes really long time before login window comes up. Already tried change network interface order - did not work for me. BTW - when i try reach my local server i use comm + K, then IP address (no DNS) - so I think it cant be DNS problem. Also I disable IP6. It seams problem in my system or just miss-configuration something

ping to this server works fast, traceroute -n - fast too, but without "-n" - takes long time (about 10 sec)

 

Any suggestion ?

[Formal]

Use VoodooHDA to get stereo sound only.

 

Hmmm I tried that and nothing, I do need something confirmed, when I load in new kexts should I be taking out old ones? If this is so what is the procedure? I have literally used this guide note for note, so with the standard DSDT install with DD's script what should I do to add voodoo?

thanks for the tip

[Josvdp]

As I am back from my holiday, I tried installing from scratch. But this time with even more problems. I would really appreciate any help, since I'm oblivious at what to do. This is what I did:

 

Setup:

• Intel Core i7
  
• Gigabyte GA-EX58-UD5
  
• Gygabyte GeForce GTS 250 1GB
  
• Samsung F3 1TB
  
• Samsung F3 500GB
  
• Single display for now (but later I want to use the second display I have (VGA)
  

 

Preparation:

• Use OSX SL install on my 1TB disk.
  
• Format the 500GB disk as Mac OS Extended Journaled (and GUID Partition table) named "OSX"
  

 

Installation:

1. Started RUN-PATCH_INSTALLER and entered password.
   
2. Selected "OSX" (which I just formatted) as target volume.
   
3. Selected /Extra as install type (#1)
   
4. Ran the entire install sequence (#1)
   ---- 1. Chameleon 2.0 RC3
   ---- 2. Make partition active (I wasn't sure about this, because I think that now I might have 2 active partitions, how do I deactivate my other partitions?)
   ---- 3. Ran the Mac OSX Install off the Retail SL DVD ISO with the following customizations:
   -------- 1. Disabled most of the languages
   ---- 4. Prior to installing the kexts, deleted ATY_init.kext from the Kexts_10.6/_Graphics folder to make sure that this wasn't installed.
   ---- 5. Installed all the other default kexts
   -------- 1. Which were: AppleIntelPIIXATA, IOAHCIBlockStorageInjector, JMicronATA, HDAEnabler, LegacyHDA, RealtekR1000SL, facesmc, NullCPUPowerManagement, OpenHaltReastart, PlatformUUID.
   -------- 2. All in the Extra folder
   -------- 3. Normal cache build (#N)
   ------------- 1. "Kext installer has completed with boot caches updated! PlatformUUID.kext updated with newly generated UUID"
   ---- 6. Ran the DSDT patcher.
   ---- 7. Turned off Spotlight.
   
5. Reboot
   ---- -v arch=i386
   ---- buildcache
   ---- reboot
   
6. Modified plists (#9):
   ---- Add EFI string for my Graphics card
   -------- Boot plist, #A, #29 (Device properties), #2 (Nvidia), #27 (GTS 250), #2 (1024MB)
   ---- Update boot cache
   

 

Problems:

• No Ethernet, In the boot log:
  ---- AppleRTL8169Ethernet: Unknown hardware version ID (280000000)
  ---- AppleRTL8169Ethernet: Unknown hardware version ID (280000000)
  ---- AppleRTL8169Ethernet: probeHardware() failed
  ---- AppleRTL8169Ethernet: probeHardware() failed
  
• No sleep
  ---- CPU Fan speeds up, no wake up
  

 

Tried 64bit

• At bootloader: -v arch=x86_64
  
• Same problems as in 32bit-mode.
  

 

I can provide boot logs if needed. Does anybody know what I should do? Are the kexts in the wrong folders maybe? They should all work in Extra, especially in 64bit, right? They were in Exta, as was defaulted in the script.

[everdone]

Problems:

• No Ethernet, In the boot log:
  ---- AppleRTL8169Ethernet: Unknown hardware version ID (280000000)
  ---- AppleRTL8169Ethernet: Unknown hardware version ID (280000000)
  ---- AppleRTL8169Ethernet: probeHardware() failed
  ---- AppleRTL8169Ethernet: probeHardware() failed
  
• No sleep
  ---- CPU Fan speeds up, no wake up
  

 

Tried 64bit

• At bootloader: -v arch=x86_64
  
• Same problems as in 32bit-mode.
  

 

I can provide boot logs if needed. Does anybody know what I should do? Are the kexts in the wrong folders maybe? They should all work in Extra, especially in 64bit, right? They were in Exta, as was defaulted in the script.

 

Rerun DDs installer, select your drive, then Kext Install option. Toggle the Realtek kext to System, rebuild cache (N) then restart.

 

If you want 32 bit operation type arch=i386 at boot. If you want 64 bit no flag is required. (you can use -v boot flag in either case).

[AppleIIGuy]

Hmmm I tried that and nothing, I do need something confirmed, when I load in new kexts should I be taking out old ones? If this is so what is the procedure? I have literally used this guide note for note, so with the standard DSDT install with DD's script what should I do to add voodoo?

thanks for the tip

 

remove the audio kexts files from /X58_Mobo_Patch_Installer/Kexts_10.6/_Audio and put the voodoo kext there then run dd's script then run option 5 and then type in the nuber for the voodoo hda kext to put it in the /S/L/E then rebuild caches

[seanmcgpa]

So my current 100% stable system is up and running, and it really rocks.

 

Gigabyte GA-EX58-UD5 with F9m bios

dood's DSDT.aml and various hacks

Xeon W3520 @ 4ghz (1.35 volts)

Prolimatech Megahalems rev B

Corsair TR3X6G1600C8 6 GB DDR3 @ 1600

Intel X-25M G2 160GB SSD boot drive with Snow Leopard (64 bit)

4x 2TB drives in Raid-0

Geforce 8800 GTX 768megs

COOLER MASTER HAF 932

BFG Tech EX-1200 PS

HP LP3065 30" Monitor

 

 

CPU is idling at 26-28 degrees, even at 4ghz (however, the room the computer is in is pretty chilly). Load temps around 50 degrees. I have thought about trying to up the ghz, but I'm 100% stable (Mprime 64 bit for MacOSX x 24 hours, no KP).

 

My regrets - I didn't buy 12 GB of memory. Anyone have reliable 12 GB kits that work at 1600?

I want to upgrade my video card, but am unsure what is worth the costs / hassle ration. The 8800 GTX was so painless, and runs Wow at 60 fps in 2560x1600x32 with everything maxed.

My cpu voltage seems a little high. Is 1.35 too high for the W3520?

 

A special and huge shout out / hugs / pickle tickles to Digital Dreamer (MAJ) and dood for all their hard work.

[defecta]

My regrets - I didn't buy 12 GB of memory. Anyone have reliable 12 GB kits that work at 1600?

 

I work in a PC store and we sell a lot of high end/game systems. Steer clear of the OCZ 12GB kit on this mobo unless you want to shell out for a RAM cooler also. These OCZ kits arent stable at 1600Mhz unless you use a RAM cooler in my experience. The Corsair 12GB kits have been the best with the UD5 I have found, plus its a LOT easier to get the Corsair RAM working as it has XMP and the OCZ does not.

 

I hope this helps.

[Josvdp]

Rerun DDs installer, select your drive, then Kext Install option. Toggle the Realtek kext to System, rebuild cache (N) then restart.

 

If you want 32 bit operation type arch=i386 at boot. If you want 64 bit no flag is required. (you can use -v boot flag in either case).

Thank you everdone for your quick response! I did know that some kexts just won't run in Extra, but I have screwed up a lot in the past so I didn't dare to make the change. Also, I thought that for a vanilla setup (64-bit) all kexts should be in Extra, since this was pointed out in the start post of DD. But, I did move the kext and it seems to be working perfectly in both 32- and 64-bit, so thanks for that!

 

Now, about the 64-bit boot mode. I did have to put in the flag "arch=x86_64" in the bootloader. As DD also stated in his starting post, the bootloader boots in 32-bit by default. Changing this is rather easy though and is done by running DD's script with the option "edit plists".

 

The system is all up and running now, but I'm missing one important feature: sleep. This was my biggest problem a few weeks ago when I first tried. The problem then was my dual screen setup. With both displays, the Mac just wouldn't wake up from sleep. As for now, it doesn't even GO into sleep. I have a feeling this is just because I simply didn't install the sleepenabler.kext yet. But I don't understand why it was deleted from DD's default install? What is the best way to enable sleep?

 

Included new SleepEnabler.kext for SL 10.6.2. Note that this is NOT compatible with 10.6.1 and earlier. Because this one has issues with the earlier SL version and the earlier version of SL has issues with the new kext, I'm leaving them both out of the default install. They are both in the repository.

 

From DD's startpost. Sorry, I read it late but it's there. I'm going to try and install the sleepenabler kext, see how that goes. Fingers crossed!

[Formal]

OK no audio, I give up (I am running Pro Tools anyway so its not the end of the world!) Sleep under 10.6 is fine (thanks)

 

I just have to battle with the 10.6.2 update now, any tips anyone?

 

cheers

[Josvdp]

I just have to battle with the 10.6.2 update now, any tips anyone?

Just don't forget to change your kext to the 10.6.2 compatible one.

 

----------------------------

 

I have been fiddling around some more, with both good and bad effects. I could use some additional help, since I'm stuck.

 

After my previous posts (about my installation) I fixed the networking issue by toggling the Realtek kext to System. After that I did the following steps:

 

Post-installation

1. Installed combo update to 10.6.2
   
2. Restarted (as installation wanted), SL shut down but no reboot (black screen).
   
3. Reset button, booted normally.
   
4. Installed software updates (iTunes, Safari, Remote Desktop client, Java, AirPort Client)
   
5. Updated bios to F9m
   
6. Modified Processor info
   ---- Wouldn't shut down (Screen said something about: "still alive with 2/8 children. In HopeFullyExitLasts phase of shutdown")
   
7. Installed sleepenabler.kext
   ---- 1. Copied the sleepenabler.kext from the scriptfolder/Kexts_10.6/Misc_Patches/_repository/Sleepenabler for 10.6.2 to Extra/Stored_Kexts
   ---- 2. Updated boot caches
   ---- 3. Reboot
   
8. Tried sleep: works in 32-bit with both single display and dual display!
   
9. Booted in 64-bit, graphics not detected, limited graphics mode. Mmh, weird?
   ---- Reboot to 32-bit again (with flag arch=i386 at bootloader prompt), graphics still not working properly, what happened? It seems that it ignores my EFI String in the boot plist. Is it somehow using the plist in System?
   

 

A couple of questions from me:

 

1. How come this sudden change of graphics was triggered by booting in 64-bit? Everything was working perfectly, before that!
   
2. Where can I find the bootlog?
   
3. How do I see which boot plist OSX is using? I've read that it's possible that the install uses the one in /System, but I can't find it there and I can't edit it with DD's script either.
   
4. So if I find that plist in system, how do I edit it?
   

[CruiSAr]

1. How do I see which boot plist OSX is using? I've read that it's possible that the install uses the one in /System, but I can't find it there and I can't edit it with DD's script either.
   
2. So if I find that plist in system, how do I edit it?
   

I know for certain my system uses the bootPlist in Library/Preferences/Systemconfiguration.

 

When you find it, copy it to your desktop, then replace the one in L/P/SC with the one from your Extra folder that is assuming you already have your efi strings present in the bootPlist in your Extra folder

[iCore]

After my previous posts (about my installation) I fixed the networking issue by toggling the Realtek kext to System. After that I did the following steps:

 

Post-installation

[*] Installed combo update to 10.6.2

(...)

[*] Installed software updates (iTunes, Safari, Remote Desktop client, Java, AirPort Client)

[*] Updated bios to F9m

(...)

[*] Installed sleepenabler.kext

---- 1. Copied the sleepenabler.kext from the scriptfolder/Kexts_10.6/Misc_Patches/_repository/Sleepenabler for 10.6.2 to Extra/Stored_Kexts

---- 2. Updated boot caches

---- 3. Reboot

[*] Tried sleep: works in 32-bit with both single display and dual display!

 

I have done a similar installation (using DD script), but sleep does not work perfectly.

System goes to sleep and awake "normally" but after a wake up I get a Kernel Panic:

- When I try to launch an old power pc application (Epson Scan Utility v2.77 for my Perfection Photo 2580 scanner)

- or randomly immediately after wake up.

 

The only difference I can see from your configuration is the bios version (I am running the F8 bios revision)

 

Any idea from where my problem can come from ? (I really miss the sleep feature...)

Could the Bios be the source of the problem ? I am not really a fan of beta versions of bios, and I would prefer to wait the final F9 release.

Thanks

 

 

PS: Here is some softwares/hardware I am using that uses some additional drivers and could be the cause of the problem

- Parallels Desktop v4

- Little Snitch v2.2

- Epson Perfection Photo 2580 scanner

- Brother HL2030 laser printer

- Wacom Graphire pen tablet

- Contour Design Shuttle Xpress (jog/shuttle controller for final cut)

- Bluetooth dongle Cellink BTA3000

- Dual display (DVI + Vga) on a single Nvidia 9500 GT 512Mb DDR2 video card through home made EFI string (using NVFlash and NVCAPMaker)

[LocusOfControl]

Just don't forget to change your kext to the 10.6.2 compatible one.

 

----------------------------

 

I have been fiddling around some more, with both good and bad effects. I could use some additional help, since I'm stuck.

 

After my previous posts (about my installation) I fixed the networking issue by toggling the Realtek kext to System. After that I did the following steps:

 

Post-installation

1. Installed combo update to 10.6.2
   
2. Restarted (as installation wanted), SL shut down but no reboot (black screen).
   
3. Reset button, booted normally.
   
4. Installed software updates (iTunes, Safari, Remote Desktop client, Java, AirPort Client)
   
5. Updated bios to F9m
   
6. Modified Processor info
   ---- Wouldn't shut down (Screen said something about: "still alive with 2/8 children. In HopeFullyExitLasts phase of shutdown")
   
7. Installed sleepenabler.kext
   ---- 1. Copied the sleepenabler.kext from the scriptfolder/Kexts_10.6/Misc_Patches/_repository/Sleepenabler for 10.6.2 to Extra/Stored_Kexts
   ---- 2. Updated boot caches
   ---- 3. Reboot
   
8. Tried sleep: works in 32-bit with both single display and dual display!
   
9. Booted in 64-bit, graphics not detected, limited graphics mode. Mmh, weird?
   ---- Reboot to 32-bit again (with flag arch=i386 at bootloader prompt), graphics still not working properly, what happened? It seems that it ignores my EFI String in the boot plist. Is it somehow using the plist in System?
   

 

A couple of questions from me:

 

1. How come this sudden change of graphics was triggered by booting in 64-bit? Everything was working perfectly, before that!
   
2. Where can I find the bootlog?
   
3. How do I see which boot plist OSX is using? I've read that it's possible that the install uses the one in /System, but I can't find it there and I can't edit it with DD's script either.
   
4. So if I find that plist in system, how do I edit it?
   

 

Have you tried putting boot.plist in Extra ? This is where it should be, the other two are apple versions which you

want to override, remember to set permissions to 755 and owner 0:0

 

You don't need a script to edit it, it's just a text based file. try vi from terminal, or the plist editor

(ie right click on the file, open with Property List Editor)

 

ATY_Init and some other graphics kexts are 32 bit only and won't work in 64 bit mode, I use the inbuilt graphics

support of PCEFI boot file etc which is 64 bit, up to you though

 

I don't use EFI strings in boot.plist so can help with that

 

All the logs you need are in /var/log eg kernel.log

[Formal]

Just don't forget to change your kext to the 10.6.2 compatible one.

 

I take it you mean just the sleepenabler.kext? if thats the case should I take it out of the extras folder before doing the update and then run the script again afterwards adding the new one?

 

is running the update from software update OK?

cheers