Jump to content

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

d00m42

By d00m42,
in OSx86 10.6 (Snow Leopard)

 Share

Stability  

692 members have voted

  1. 1. How stable is your Snow Leopard installation?

    • Perfect.
      266
    • Not quite there yet...
      349

2,289 posts in this topic

Recommended Posts

Squirrelf
Squirrelf
Posted
Posted
Interesting find Eliade. I have actually just been using my Win7 setup and haven't logged into OSX since you found that WOL wasn't working properly. I haven't cut power to the system though, and have also noticed instability using windows 7. Sometimes won't wake from sleep (have to hold power button) or will drop into hibernation although I've completely disabled it. I think that it's directly related to the DSDT from SL. Any advice for a kext only approach to SL?

 

*edit: we lost power last night at our place and I ended up shutting down the PC. I just woke it up preOS from work.

 

My problem just came back at the instant

last night it was fine, slept the computer for the night, woke it up, still fine, mprime still stable

now it's noon

firefox crashed,but no KP, itunes is playing music right now

checked mprime, CORE1 error after 1seconde of running it.... (actually all four coe gave an error)

 

without running mprime you wouldn't think the system was unstable, at first I was blaming it on the latest version of firefox...

 

I have NO cpui, NO voodoopowermini, NO p-states NO c-states (that's for vanialla speedstep)

 

I haven't started vmware fusion since last night, so that's not the problem either

 

so now my next suspects are:

DSDT (but this one should have been fine.... didn't do anything weird with it, I have another older dsdt, that worked very well that I was using about two weeks ago, I'll try it, they are quite different... forgot what I did, but it was working fine, )

bios F11

fakesmc v2

 

 

 

EDIT:

 

SO I now have my older dsdt, pretty much the one you would get by following the instruction in this guide (added to it are EHCI and I believe that's all I did extra on that dsdt)

 

shutting the PSU down and rebooting didn't remove the error in mprime

so I re-installed F11, started up the machine and kill it by turning off the PSU

then set all the needed setting in the bios again from optimised default, this time I'm not overclocking to be sure that it is not a factor...

rebooted and mprime works fine, not rounding error....

I'll wait a week, then I will set my overclock again, wait a week and if I still don't have the problem, I'll blame it all on the DSDT.... and compare the two dsdt to see what is the actual cause...

Link to comment
Share on other sites
elbasofolous
elbasofolous
Posted
Posted

hello,

I have followed these instructions exactly and I must say my snow leopard installation is almost perfect. I have even managed to eliminate the need for using AHCI by using the "no ahci" kext provided by netkas(http://netkas.org/?p=125) and then rebuilding the kextcache.mkext

 

this being said, I can not manage to get the onboard ethernet to connect. I patched the dsdt exactly as detailed in the instructions(trying to add the supplied code to pex4 or pex5), and adding to pex4 yields a working file that sees the ethernet and has fully working audio. At boot, it lists out the ethernet mac address and systemprefs > network sees the device in addition to firewire(also note that I get the same result from the dsdt.aml provided in this guide).

 

However, it refuses to get an IP. It just sits there with a self assigned IP

 

is there any way to fix this? it seems like ethernet should be a no brainer but for some reason its got me stumped.

 

i am using the rev 1.1 of this board, but both 1.0 and 1.1 use 8111C so i dont think it could be discrepancy with revision. I am also using bios f9, but nothing about my setup has given me issues with LAN in 10.5 so its got to be the dsdt.aml or something else specific to snow leopard

 

thanks for any help you all can provide

Link to comment
Share on other sites
d00m42
d00m42
Posted
  • Author
Posted

Anyone have an idea how I can fix the "Windows XP-hijacking-my-ethernet-from-OSX" problem? Basically, when I boot into Windows XP, ethernet works fine, but then when I boot back into OS X my ethernet card acts almost like it is turned off. I have to remember to turn off the computer, unplug it for 30 seconds or so, and then boot into OS X if I've just used Windows XP otherwise as I mentioned before I don't get internet.

 

This is getting kind of annoying, so does anyone have an idea for a fix? It's almost certainly a hardware-level problem with the ethernet card's power and Windows XP kind of hijacking the rights to turn it on and off. I would REALLY rather not have to install Vista/7, as I have a few important programs and files that I'd rather not have to totally backup and re install, because I don't currently have the time :/

Link to comment
Share on other sites
Squirrelf
Squirrelf
Posted
Posted
Anyone have an idea how I can fix the "Windows XP-hijacking-my-ethernet-from-OSX" problem? Basically, when I boot into Windows XP, ethernet works fine, but then when I boot back into OS X my ethernet card acts almost like it is turned off. I have to remember to turn off the computer, unplug it for 30 seconds or so, and then boot into OS X if I've just used Windows XP otherwise as I mentioned before I don't get internet.

 

This is getting kind of annoying, so does anyone have an idea for a fix? It's almost certainly a hardware-level problem with the ethernet card's power and Windows XP kind of hijacking the rights to turn it on and off. I would REALLY rather not have to install Vista/7, as I have a few important programs and files that I'd rather not have to totally backup and re install, because I don't currently have the time :/

 

All these problem we have that are at hardware level are either chameleon or dsdt from what I can guess

 

try removing the lan section in dsdt

I tried it without few weeks ago, I still had the bonjour fix though

and Ethernet/bonjours still worked

I re-added the lan fix afterward anyway...

 

hello,

I have followed these instructions exactly and I must say my snow leopard installation is almost perfect. I have even managed to eliminate the need for using AHCI by using the "no ahci" kext provided by netkas(http://netkas.org/?p=125) and then rebuilding the kextcache.mkext

 

this being said, I can not manage to get the onboard ethernet to connect. I patched the dsdt exactly as detailed in the instructions(trying to add the supplied code to pex4 or pex5), and adding to pex4 yields a working file that sees the ethernet and has fully working audio. At boot, it lists out the ethernet mac address and systemprefs > network sees the device in addition to firewire(also note that I get the same result from the dsdt.aml provided in this guide).

 

However, it refuses to get an IP. It just sits there with a self assigned IP

 

is there any way to fix this? it seems like ethernet should be a no brainer but for some reason its got me stumped.

 

i am using the rev 1.1 of this board, but both 1.0 and 1.1 use 8111C so i dont think it could be discrepancy with revision. I am also using bios f9, but nothing about my setup has given me issues with LAN in 10.5 so its got to be the dsdt.aml or something else specific to snow leopard

 

thanks for any help you all can provide

 

try unpluging your Power supply for like 30 seconds, and see if that fixes it

you may have to "kill" the power supply while booting (but before chameleon, like 2 seconds after booting), seems to reset more stuff

but your bios should keep your settings anyway

Link to comment
Share on other sites
d00m42
d00m42
Posted
  • Author
Posted
All these problem we have that are at hardware level are either chameleon or dsdt from what I can guess

 

try removing the lan section in dsdt

I tried it without few weeks ago, I still had the bonjour fix though

and Ethernet/bonjours still worked

I re-added the lan fix afterward anyway...

 

 

 

try unpluging your Power supply for like 30 seconds, and see if that fixes it

you may have to "kill" the power supply while booting (but before chameleon, like 2 seconds after booting), seems to reset more stuff

but your bios should keep your settings anyway

 

The LAN fix in DSDT makes my LAN work lol, I need it...

 

I haven't even had the time to set up the bonjour fix (will do soon), but I'm not sure why it would be CHAMELEON causing this when it only occurs if I reboot from Windows XP into OS X (This didn't happen with Windows 7). I would think I'd have to fix something in Windows XP.

 

I have one idea, although it might be a long shot...

 

I can tell WinXP that it DOESN'T have the rights to turn off my network card, and that might prevent this issue.

 

Also, what about the fact that I CAN'T boot into Windows XP using Chameleon? I am forced to hit F12 at boot and manually select my Windows drive.

Link to comment
Share on other sites
ripburger
ripburger
Posted
Posted

I followed the nullspot USB guide for getting my hackintosh going and it's worked out great. I have given up on the LAN as I have installed a NetGear GA-311 network card which just works. I am still looking to get sound working. I have patched my DSDT file, and tried a few different .kext files, but I'm not sure which one I should be using. I have a Realtek ALC889a audio chipset on my Gigabyte EP45-UD3R motherboard.

 

An interesting fact: I tried hooking the audio out to my speakers to the front jack of my case. And I was able to get sound that way through the pass through available on the motherboard, but never through the rear speaker jack, no matter which audio out I picked within the system preferences.

 

Any help would be greatly appreciated.

 

Added post-this-post:

 

Just found out that audio is playing via the side-output speakers (grey port), rather than the regular output port (green). Good enough for my simple two speaker setup, but I will try to modify the pin configuration to fix I guess.

Link to comment
Share on other sites
mactheworld77
mactheworld77
Posted
Posted

Just something I noticed: I use a few appleTV's at home and had the bonjour fix included in my install but was losing the appleTV's in itunes. Installed a trendnet gig card and was still losing the them. I removed bonjour fix and now got them back again. So dont use bonjour fix if you have a seperate network card installed.

Link to comment
Share on other sites
Flashe
Flashe
Posted
Posted

Hello everyboy,

 

D00m42,

I tried the procedure but to no avail bonjour.

I have installed the AppleRTL8169Ethernet.kext,in S / L / E, are what you have done ?

I have this message in the terminal :2009-09-30 12:39:01.798 sudo[187:903] _CFGetHostUUIDString: unable to determine UUID for host. Error: 35.

you can tell me what to do to successfully install "Bonjour".

 

Thanks a lot.

Link to comment
Share on other sites
aaParis
aaParis
Posted
Posted

hello,

 

i am quite a newbe, and after trying this 10 step install guide i apparently got the bios problem from a bad dsdt file maybe, because after the chameleon bootloader started, i just got the apple startupscreen, then "you need to restart your computer, then all my Bios was back to original settings,,,

 

so ! now i'm trying this step to step guide, and i am a bit worried about step 9

 

- do not know the terminology of -v -x32, possible to elaborate on this for a newbe ?

 

i am using a GA EP45-UD3P (rev 1.0) with a Q9550 & Nvidia GT9600

 

>i was planning on trying the dsdt file in your package, as this was quite difficult to grasp, and that i guess the lan chips are the same on your motherboard as i have, and sound is the same. only worry would be the Quad processor as i see you have a dual (3,8 ?? overclock ??)

 

thank you so much,

 

andreas

Link to comment
Share on other sites
aaParis
aaParis
Posted
Posted

RE:

 

used the default dsdt file, installed Leopard fine,,,

 

but on restart, choosing my freshly installed Snow drive after Chameleon boot, kernel panic,,,

 

guess this must be due to the unchanged dsdt-file ?

 

also, i have a Nvidia 9600 GT 512mo graphics card (gigabyte Silent Cell), but it wasn't listed in the EFI studio app, so i chose the 9600 GT 1024 mo in the popup menu,,, this seems also to be, euhh, wrong ?

 

>maybe the "com.apple.Boot.plist" gives the kernel panic ?

 

my exact configuration is:

GA-EP45-UD3P (rev. 1.0)

Crucial Ballistix DDR2 800 (4x2go)

Intel Q9550

Nvidia 9600 GT 512mo (fanless)

Seagate Baracuda 1TB SATA

Samsung SH-S223L/BEBE

Link to comment
Share on other sites
aaParis
aaParis
Posted
Posted

RE:RE

 

got it working,,, by changing the com.apple.Boot.plist,,,

 

but only in low resolution,,, osx only recognizes 32mo Vram,,,

 

my card is as mentionned a GT 9600 512mo,,

 

my com.apple.Boot.plist;

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

    <key>Kernel</key>

    <string>mach_kernel</string>

    <key>Kernel Flags</key>

    <string></string>

    <key>Timeout</key>

    <string>5</string>

    <key>device-properties</key>

    <string>cb0300000100000001000000bf0300001500000002010c00d041030a000000000101060000027

fff04003a000000400032002c0068007700730065006e0073006f0072002d0070006100720061006d

0073002d00760065007200730069006f006e000000080000000000000222000000400032002c00640

0650076006900630065005f0074007900700065000000120000004e5644412c6770752d64696f6465

0e0000004e00560050004d00000020000000010000000000000000000000000000000000000000000

000000000001e00000072006f006d002d007200650076006900730069006f006e0000000900000033

31373261100000004e00560043004100500000001800000004000000000003000c000000000000070

000000022000000400032002c002300730069007a0065002d00630065006c006c0073000000080000

000000000022000000400030002c006400650076006900630065005f00740079007000650000000b0

00000646973706c6179100000006d006f00640065006c0000001e0000004e5649444941204765466f

72636520393830302047542045464914000000400030002c006e0061006d0065000000120000004e5

644412c446973706c61792d4120000000400032002c0063006f006d00700061007400690062006c00

65000000160000004e5644412c73656e736f722d706172656e7414000000400031002c006e0061006

d0065000000120000004e5644412c446973706c61792d4212000000400032002c0072006500670000

0008000000000000021c0000006400650076006900630065005f00740079007000650000001000000

04e5644412c4765466f72636520000000400031002c0063006f006d00700061007400690062006c00

650000000e0000004e5644412c4e564d616326000000400032002c002300610064007200650073007

3002d00630065006c006c007300000008000000000000010e0000006e0061006d00650000000f0000

004e5644412c506172656e7422000000400031002c006400650076006900630065005f00740079007

000650000000b000000646973706c617920000000400030002c0063006f006d007000610074006900

62006c00650000000e0000004e5644412c4e564d6163220000005600520041004d002c0074006f007

40061006c00730069007a0065000000080000000000004036000000400032002c0068007700630074

0072006c002d0070006100720061006d0073002d00760065007200730069006f006e0000000800000

00000000214000000400032002c006e0061006d00650000001100000073656e736f722d706172656e

74</string>

</dict>

</plist>

 

lol, this plist must have some serious flaw,,??

 

a

Link to comment
Share on other sites
d00m42
d00m42
Posted
  • Author
Posted

As a noob, you would be quick to blame the plist. YOUR STRING most likely has the flaw, try this one:

 

cd0300000100000001000000c10300001500000002010c00d041030a000000000101060000010101
60000007fff040014000000400032002c006e0061006d00650000001100000073656e736f722d706
72656e74220000005600520041004d002c0074006f00740061006c00730069007a00650000000800
0000000002036000000400032002c00680077006300740072006c002d0070006100720061006d007
002d00760065007200730069006f006e00000008000000000000021c000000640065007600690063
065005f0074007900700065000000100000004e5644412c4765466f7263650e0000006e0061006d0
650000000f0000004e5644412c506172656e7422000000400030002c006400650076006900630065
05f00740079007000650000000b000000646973706c6179100000006d006f00640065006c0000001
0000004e5649444941204765466f726365203936303020475422000000400031002c006400650076
06900630065005f00740079007000650000000b000000646973706c617912000000400032002c007
00650067000000080000000000000222000000400032002c006400650076006900630065005f0074
07900700065000000120000004e5644412c6770752d64696f646520000000400032002c0063006f0
6d00700061007400690062006c0065000000160000004e5644412c73656e736f722d706172656e74
2000000400032002c002300730069007a0065002d00630065006c006c00730000000800000000000
0020000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644
12c4e564d616314000000400030002c006e0061006d0065000000120000004e5644412c446973706
61792d413a000000400032002c0068007700730065006e0073006f0072002d007000610072006100
d0073002d00760065007200730069006f006e000000080000000000000226000000400032002c002
006100640072006500730073002d00630065006c006c007300000008000000000000011400000040
031002c006e0061006d0065000000120000004e5644412c446973706c61792d42200000004000300
2c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61631e00
00072006f006d002d007200650076006900730069006f006e0000000900000033313732611000000
4e00560043004100500000001800000004000000000003000c00000000000007000000000e000000
e00560050004d0000002000000001000000000000000000000000000000000000000000000000000
00

 

It might or might not work, but you can easily look up how to create one that will work without having to be spoonfed information (if this one doesn't, assuming you install it right). Also, -v -x32 just means the computer will boot in verbose with the 32-bit kenrel. If you don't know what verbose or 32-bit mean, I suggest doing some reading, as it will seriously help you understand this stuff better.

 

Also, DON'T EVER install stuff to /S/L/E if you don't have to... My entire install is from /E/E, and I don't need to boot with -v -x32 anymore because I can use the 64-bit kernel (no 32-bit extensions).

 

hello,

 

i am quite a newbe, and after trying this 10 step install guide i apparently got the bios problem from a bad dsdt file maybe, because after the chameleon bootloader started, i just got the apple startupscreen, then "you need to restart your computer, then all my Bios was back to original settings,,,

 

so ! now i'm trying this step to step guide, and i am a bit worried about step 9

 

- do not know the terminology of -v -x32, possible to elaborate on this for a newbe ?

 

i am using a GA EP45-UD3P (rev 1.0) with a Q9550 & Nvidia GT9600

 

>i was planning on trying the dsdt file in your package, as this was quite difficult to grasp, and that i guess the lan chips are the same on your motherboard as i have, and sound is the same. only worry would be the Quad processor as i see you have a dual (3,8 ?? overclock ??)

 

thank you so much,

 

andreas

 

The ONLY FILE you CAN'T use in my pack is the DSDT file... I assume you haven't read any of the 60+ pages of this thread, otherwise you would probably see in many places that people fail miserably trying to use my DSDT BECAUSE THEY HAVE TO MAKE THEIR OWN!!

 

We have different motherboards, different PCI addresses for onboard components (probably), and DIFFERENT PROCESSORS! How do you expect to use my DSDT when I have an EP45-UD3R rev1.1? Please look up one of the million guides to create your own, and/or use the utilities I've included to my pack to aid you in doing so.

Link to comment
Share on other sites
aaParis
aaParis
Posted
Posted

Hello,

 

thank so much for your guide and for answering my post.

 

i did get the SL to work, and i did set my bios to 64bit from the start. But it only recognizes 32mo Vram,,

(i used Adam Pash's Lifehacker Bios guide)

 

SL does recognize the prcessor (q9550) and ram.

 

i will look up the vocabulary, guess it is the same technical expressions in french.

 

>i must have read a lot of pages, but i do not understand it very well i guess,, and i've tried 3 different install methods, and using yours, i am quite close to have osx working. i will try the new graphics card string now ! Thank you,

 

andreas

Link to comment
Share on other sites
sbl03
sbl03
Posted
Posted

I'm installing this on a UD3R, and I got all the way to the Welcome screen and past registration, but mere seconds after that, I get "You need to restart your computer". Is this a kernel panic?

 

I manage to boot onto the desktop now, but i get the same message just seconds after i boot up. (I think it has something to do with me pressing system preferences?)

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...