[GUIDE]Retail Snow Leopard 10.6 on a GA EP45-UD3R

[lateralusman]

Can someone help me with my 8800GT still can't get QE/CI.

[gmacman]

Can someone help me with my 8800GT still can't get QE/CI.

 

Which way are you getting SL to recognize it? Via efi string within your com.apple.Boot.plist or using Chameleon's graphic enabler function?

[d00m42]

Can someone help me with my 8800GT still can't get QE/CI.

 

Try this com.apple.Boot.plist EFI string:

 

6c0200000100000001000000600200000d00000002010c00d041030a010000000101060000010101
060000007fff04001e00000072006f006d002d007200650076006900730069006f006e0000002e000
0006e5669646961204765466f7263652038383030204754204f70656e474c20456e67696e65205b45
46495d22000000400030002c006400650076006900630065005f00740079007000650000000b00000
0646973706c6179100000004e00560043004100500000001800000004000000000003000c00000000
000007000000000e0000006e0061006d00650000000b000000646973706c617914000000400030002
c006e0061006d0065000000120000004e5644412c446973706c61792d41100000006d006f00640065
006c0000001a0000006e5669646961204765466f72636520383830302047540e0000004e005600500
04d000000200000000100000000000000000000000000000000000000000000000000000014000000
400031002c006e0061006d0065000000120000004e5644412c446973706c61792d422000000040003
1002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616322
0000005600520041004d002c0074006f00740061006c00730069007a0065000000080000000000002
020000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e564441
2c4e564d616322000000400031002c006400650076006900630065005f00740079007000650000000
b000000646973706c61791c0000006400650076006900630065005f00740079007000650000000f00
00004e5644412c506172656e74

[gmacman]

Can someone help me with my 8800GT still can't get QE/CI.

 

 

Which way are you getting SL to recognize it? Via efi string within your com.apple.Boot.plist or using Chameleon's graphic enabler function?

 

 

I forgot to ask, but are you sure you don't have QE/CI? I've heard there are two ways to check the simplest being launching Front Row. If it launches, you're graphics card is QE/CI. The other is adding a dashboard widget. If it has that cool water droplet effect than again QE/CI is working.

 

I only mentioned two but as with everything else in hackintosh-land there are probably at least ten different ways to get your graphics card recognized and running with full acceleration (QE/CI). From what I've been able to decipher the big four are: EFI string, Chameleon's GraphicEnabler, DSDT, and Kexts.

 

Starting from the end, the old fashion method of loading up a variety of kexts (NVInject, NVKush, etc.) still seems to be used. Although due to my purist nature I highly recommend avoiding this method.

 

You can also modify your DSDT to enable your graphics card but getting my DSDT to handle ethernet and sound was so mind boggling to me I'd also recommend avoiding this method unless you really have to (or don't fear dabbling with DSDT).

 

Currently I'm using the EFI string method which you get via a variety of ways. For me I used OSXTools to get the string and then added it to the com.apple.Boot.plist. You should be able to make your own string and I'd recommend that instead of having some suggest some string that may or may not accurately define your particular graphic card.

 

However, I want to test out the Chameleon method because it seems much easier. Once I backup my current system later today I'll give it a shot. I should add that I have heard that this method will only allow using one monitor even if your card supports two. But I only use one, so I'll give it a go. The main benefit of the Chameleon method is that (supposedly) it reads the info from the card and passes the correct info to the OS.

[d00m42]

I forgot to ask, but are you sure you don't have QE/CI? I've heard there are two ways to check the simplest being launching Front Row. If it launches, you're graphics card is QE/CI. The other is adding a dashboard widget. If it has that cool water droplet effect than again QE/CI is working.

 

I only mentioned two but as with everything else in hackintosh-land there are probably at least ten different ways to get your graphics card recognized and running with full acceleration (QE/CI). From what I've been able to decipher the big four are: EFI string, Chameleon's GraphicEnabler, DSDT, and Kexts.

 

Starting from the end, the old fashion method of loading up a variety of kexts (NVInject, NVKush, etc.) still seems to be used. Although due to my purist nature I highly recommend avoiding this method.

 

You can also modify your DSDT to enable your graphics card but getting my DSDT to handle ethernet and sound was so mind boggling to me I'd also recommend avoiding this method unless you really have to (or don't fear dabbling with DSDT).

 

Currently I'm using the EFI string method which you get via a variety of ways. For me I used OSXTools to get the string and then added it to the com.apple.Boot.plist. You should be able to make your own string and I'd recommend that instead of having some suggest some string that may or may not accurately define your particular graphic card.

 

However, I want to test out the Chameleon method because it seems much easier. Once I backup my current system later today I'll give it a shot. I should add that I have heard that this method will only allow using one monitor even if your card supports two. But I only use one, so I'll give it a go. The main benefit of the Chameleon method is that (supposedly) it reads the info from the card and passes the correct info to the OS.

 

I would use a com.apple.Boot.plist EFI string. Try the one I gave you a few posts up.

[gmacman]

I would use a com.apple.Boot.plist EFI string.

 

I'm curious, why?

[richtig]

Is anyone using "DSDT simple editor V1.4.3"?

http://www.osx86.es/?p=610

[d00m42]

I'm curious, why?

 

I discussed this a few pages back, but basically it comes down to what you want. I like com.apple.Boot.plist EFI strings because they're just a more elegant way to solve the graphics recognition problem (as opposed to extra kext injectors).

 

DSDT editing can be done, but it's slightly harder to do, and more annoying to change if you want to swap out your graphics card for a better/different one anytime in the future.

 

Chameleon's GraphicsEnabler is a great solution, but I've heard it won't work with dual monitors (I have to verify that). Because I use dual monitors (and want easier upgrades and fewer non-standard kexts), I think com.apple.Boot.plist EFI strings are just nicer to use.

 

Is anyone using "DSDT simple editor V1.4.3"?

http://www.osx86.es/?p=610

 

I think I might have included an older version of that in my SL Pack, but I prefer to do it by hand. That tool does help, though.

[lateralusman]

Which way are you getting SL to recognize it? Via efi string within your com.apple.Boot.plist or using Chameleon's graphic enabler function?

 

EFI string. I've tried the one that EFITools gave me and another one someone with SL had.

I also tried the EFI string from my current Leopard build which is 100% stable.

 

I forgot to ask, but are you sure you don't have QE/CI? I've heard there are two ways to check the simplest being launching Front Row. If it launches, you're graphics card is QE/CI. The other is adding a dashboard widget. If it has that cool water droplet effect than again QE/CI is working.

 

I only mentioned two but as with everything else in hackintosh-land there are probably at least ten different ways to get your graphics card recognized and running with full acceleration (QE/CI). From what I've been able to decipher the big four are: EFI string, Chameleon's GraphicEnabler, DSDT, and Kexts.

 

Starting from the end, the old fashion method of loading up a variety of kexts (NVInject, NVKush, etc.) still seems to be used. Although due to my purist nature I highly recommend avoiding this method.

 

You can also modify your DSDT to enable your graphics card but getting my DSDT to handle ethernet and sound was so mind boggling to me I'd also recommend avoiding this method unless you really have to (or don't fear dabbling with DSDT).

 

Currently I'm using the EFI string method which you get via a variety of ways. For me I used OSXTools to get the string and then added it to the com.apple.Boot.plist. You should be able to make your own string and I'd recommend that instead of having some suggest some string that may or may not accurately define your particular graphic card.

 

However, I want to test out the Chameleon method because it seems much easier. Once I backup my current system later today I'll give it a shot. I should add that I have heard that this method will only allow using one monitor even if your card supports two. But I only use one, so I'll give it a go. The main benefit of the Chameleon method is that (supposedly) it reads the info from the card and passes the correct info to the OS.

 

Well how I check for QE/CI is to got to About This Mac > More Info > Graphics/Displays and seeing if it has everything enabled and my graphics card shows up.

 

I would use a com.apple.Boot.plist EFI string. Try the one I gave you a few posts up.

 

Will do I'll post back with results.

Appreciate the help.

 

EDIT: Gorram idiot....I had the extension of my com.apple.Boot as txt.

QE/CI now enabled.

 

[gmacman]

EFI string. I've tried the one that EFITools gave me and another one someone with SL had.

I also tried the EFI string from my current Leopard build which is 100% stable.

 

 

 

Well how I check for QE/CI is to got to About This Mac > More Info > Graphics/Displays and seeing if it has everything enabled and my graphics card shows up.

 

 

 

Will do I'll post back with results.

Appreciate the help.

 

EDIT: Gorram idiot....I had the extension of my com.apple.Boot as txt.

QE/CI now enabled.

 

That's amazing you were actually able to boot at all. Glad you solved the problem. But note that even if your graphics card shows up correctly within About this Mac that doesn't mean you have QE/CI acceleration.

 

I discussed this a few pages back, but basically it comes down to what you want. I like com.apple.Boot.plist EFI strings because they're just a more elegant way to solve the graphics recognition problem (as opposed to extra kext injectors).

 

DSDT editing can be done, but it's slightly harder to do, and more annoying to change if you want to swap out your graphics card for a better/different one anytime in the future.

 

Chameleon's GraphicsEnabler is a great solution, but I've heard it won't work with dual monitors (I have to verify that). Because I use dual monitors (and want easier upgrades and fewer non-standard kexts), I think com.apple.Boot.plist EFI strings are just nicer to use.

 

Good point. I only use one monitor and find Chameleon's way one less thing I have to do. Interestingly though, I did try to connect a second monitor and it did work. But I have a card that is actually used in one of the MacBook models so perhaps it's more stable with OS X.

[lateralusman]

That's amazing you were actually able to boot at all. Glad you solved the problem. But note that even if your graphics card shows up correctly within About this Mac that doesn't mean you have QE/CI acceleration.

 

That's never been so in my experience. But anyway, Front Row does load up. Expose and min/max windows all smooth.

[lateralusman]

Hmmm Installed 10.6.1 update no problems. But kernel panic after installing 10.6.2 after restart.

 

EDIT: Looks like sleepenabler is the culprit. Others seem to have the problem.

 

EDIT 2: I'm now using the kexts from d00m42's SL Pack v5.0b. It works! I'm in 10.6.2 now.

I'll see how it goes from here.

[d00m42]

That's never been so in my experience. But anyway, Front Row does load up. Expose and min/max windows all smooth.

 

Easiest way to check QE/CI is to open up dashboard and add a new widget. If you get the cool ripple effect, then it's working.

 

Hmmm Installed 10.6.1 update no problems. But kernel panic after installing 10.6.2 after restart.

 

EDIT: Looks like sleepenabler is the culprit. Others seem to have the problem.

 

EDIT 2: I'm now using the kexts from d00m42's SL Pack v5.0b. It works! I'm in 10.6.2 now.

I'll see how it goes from here.

 

Yep, always make sure before you run an update that all your kexts are up to date. Glad to hear it's running smoothly so far. Keep me posted!

[d00m42]

That's amazing you were actually able to boot at all. Glad you solved the problem. But note that even if your graphics card shows up correctly within About this Mac that doesn't mean you have QE/CI acceleration.

 

 

 

Good point. I only use one monitor and find Chameleon's way one less thing I have to do. Interestingly though, I did try to connect a second monitor and it did work. But I have a card that is actually used in one of the MacBook models so perhaps it's more stable with OS X.

 

Yeah, I have an eVGA 9800 GTX+ which works nicely with an EFI string, but I'm not sure if it's close enough to the cards in Macs right now to use GraphicsEnabler perfectly (especially with 2 monitors).

[jamse]

How did it break your install? Make sure you do NOT have old SleepEnabler.kext installed when you update or it will kernel panic the whole way home and back.

 

Has anyone had any luck getting their hard drives to show up as internal? I thought the IOAHCIBlockStorageInjector.kext was supposed to do that but its not. Read about tricking drivers via the DSDT here on the forum but it talks about lspci command which is not even a valid command. Had got bootcamp to work but it won't let me work on the hard drives because they are listed as external.

 

alright i tried finding that sleepenabler.kext and it wasnt in there, its basically bricking me out of using snow leopard, and then gives this greyed out screen telling me to reboot and what not.

[d00m42]

alright i tried finding that sleepenabler.kext and it wasnt in there, its basically bricking me out of using snow leopard, and then gives this greyed out screen telling me to reboot and what not.

 

If you updated to 10.6.2 without making sure to switch it out, it's almost certainly the problem.

 

Look in /S/L/E and /E/E using Single User Mode (boot with -s).

[sw170]

Hi All

 

Just want to share my latest achievements:

 

for Snow Leopard 10.6.2 + Chameleon RC4 :

 

here is my dsdt (+Audio LegacyHDA) Im using now (C1C2C4 States, SpeedStep, Sleep, shutdown, usbfix, etc.. working) - cool1

 

here you have dsdt +LegacyHDA with basic CPU info that I believe should work with all GA-EP45-UD3R boards (no CStates and SpeedStep) - basic2

 

and last: dsdt, basic CPU info with Audio - green Jack Only but no extra kexts needed - green3

 

in all packs I included new OrangeiconFix.kext (thanks to THEKING)

 

if you need Jmicron.kext (BIOS jmicron IDE mode only!-don't need that if you use AHCI mode) use one from d00m42 pack or download it here

 

for restart fix thanks to Duvel and thiagomorales for compiling it with Rekursor fix, download it here

 

Big Big Thanks to MM67 for all his work and sharing it !!

 

And finally want to say thanks to all people actively involved in "creating" InsanelyMac

salut!

 

happy New 2010!

s

[gmacman]

Been running with the 64 bit kernal (actually a mistake, I originally forgot to add the force 32 bit stuff in my com.apple.Boot.plist). So I've been booting in 64 bit from the beginning and just never realized it. But it get's stranger.

 

I also have not yet added the bonjour fix and mistakenly tried to print something via our network printer (via bonjour) and it worked!

 

Not sure how that happened.

 

Has anyone else experienced this?

[d00m42]

Been running with the 64 bit kernal (actually a mistake, I originally forgot to add the force 32 bit stuff in my com.apple.Boot.plist). So I've been booting in 64 bit from the beginning and just never realized it. But it get's stranger.

 

I also have not yet added the bonjour fix and mistakenly tried to print something via our network printer (via bonjour) and it worked!

 

Not sure how that happened.

 

Has anyone else experienced this?

 

Are all Bonjour features working with no modifications? Check iTunes playlist sharing and computer networking.

[gmacman]

Are all Bonjour features working with no modifications? Check iTunes playlist sharing and computer networking.

 

 

It appears so. I've run Bonjour Browser which shows all working services and everything from my AppleTVs to my MacBook, the other Hackintosh, my wife's MacBook, the shared iTunes library (from the other Hackintosh) all seem to be there.

 

I've been able to file transfer to both real Macs and the other Hackintosh and even do screen sharing.

 

Not sure why this is happening.

[d00m42]

It appears so. I've run Bonjour Browser which shows all working services and everything from my AppleTVs to my MacBook, the other Hackintosh, my wife's MacBook, the shared iTunes library (from the other Hackintosh) all seem to be there.

 

I've been able to file transfer to both real Macs and the other Hackintosh and even do screen sharing.

 

Not sure why this is happening.

 

Wow.. I'm going to have to look into that, it could be pretty valuable.

[gmacman]

Wow.. I'm going to have to look into that, it could be pretty valuable.

 

The only thing that I can think of that is significantly different with two my systems is that (if you check out the signature) I do not use onboard LAN and instead use a nic card from netgear. I made this move many moons ago when first installing Leopard after hearing that this particular card was very OS X friendly.

[d00m42]

The only thing that I can think of that is significantly different with two my systems is that (if you check out the signature) I do not use onboard LAN and instead use a nic card from netgear. I made this move many moons ago when first installing Leopard after hearing that this particular card was very OS X friendly.

 

Are you still using a DSDT that IS patched for the onboard LAN?

[gmacman]

Are you still using a DSDT that IS patched for the onboard LAN?

 

Here are all my specs because this thing is kinda of interesting that it worked.

 

First off what's in E/E:

 

fakesmc.kext

IOAHCIBlockStorageInjector.kext (looking into removing this)

LegacyACPI_SMC_PP.kext (looking into removing this)

LegacyAGPM.Kext (looking into removing this)

LegacyHDA.Kext

OpenHaltRestart.kext

PlatformUUID.kext (Currently running Chameleon RC3, due to some things I've read about RC4 and the UUID thing, I will not move there at this time. I know there is a mod to the boot file made by Rekursor (I think?) but I would rather wait until that is made a part of RC5 before I switch)

 

DSDT was modified for ONLY the following:

Audio per your guide "How to patch DSDT with LAN and HDEF functions"

Onboard LAN is Disabled in the BIOS

 

What does this mean?

From all this I deduce that IF you avoid onboard LAN and use a pci nic card it will work out of the box without any modifications. My file transfer rates are identical to my real Mac. I am able to use Bonjour and do not appear to have any network issues.

 

Side note: I recently went back to the efi string method for my graphics card after I noticed some odd graphic behavior while playing a game.

 

I must also point out that I DO NOT do windows. My house is pure OS X from my 4 year old's (very) old iBook to our two MacBooks, AppleTVs, and of course the two Hackintoshes. My Hacks were built from the ground up to only run OS X. I say this only to mention that if someone wishes to use another OS on the same box, I'm not sure if the separate nic card is a viable option.

[OSX86tester]

I discussed this a few pages back, but basically it comes down to what you want. I like com.apple.Boot.plist EFI strings because they're just a more elegant way to solve the graphics recognition problem (as opposed to extra kext injectors).

 

DSDT editing can be done, but it's slightly harder to do, and more annoying to change if you want to swap out your graphics card for a better/different one anytime in the future.

 

Chameleon's GraphicsEnabler is a great solution, but I've heard it won't work with dual monitors (I have to verify that). Because I use dual monitors (and want easier upgrades and fewer non-standard kexts), I think com.apple.Boot.plist EFI strings are just nicer to use.

 

 

 

I think I might have included an older version of that in my SL Pack, but I prefer to do it by hand. That tool does help, though.

 

which page exactly do you talk about the com.apple.Boot.plist EFI because I need to do this myself and have installed or re-installed osx 4 times already. Each time Im pretty much screwing up the boot loader. So the things I will never try (The new chameleon) (myhack installer) That ruined my graphics. I just want my 8600 GTS 256 to freakin work Ugh!! So im willin got try the graphics enabler if thats what it takes but I want to make sure im doing this s%^&t correctly or else its another farking format again.