Lifehacker Guide with GA-EP45-UD3P Motherboard

[spincast]

I had the same issue on mine. I was able to fix it by setting the speed of the connection to 100Mbs (System Preferences > Network > Ethernet > Advanced... > Ethernet --- Select Configure: Manually and set the speed to 100baseTX.

 

Don't know why, but I can't access my gigabit switch at gigabit speed, whether manual or automatic. Maybe it's my switch (even though it works with everything else on my network)?

 

 

 

Hey guys...I'm having a big problem over here...not sure if anyone has experienced it or not:

 

My ethernet port isn't allowing me to connect anymore after months of uninterrupted use. It's telling me that I have a "self-assigned IP" in my network settings. I didn't change any settings, it just happend one day upon boot up.

 

I've tried setting up a static IP w/ no success getting my machine back online. I've tried yanking the card, and reinstalling. I've tried renewing my DHCP lease, checking my firewalls. I'm out of things that I know to get this working again.

 

Does anyone have any suggestions? I'm using this build, part for part, no changes made.

 

Thanks guys!

[max_raid]

Howdy folks.

 

I need help getting my sound working. For whatever reason, my installation is not recognizing any sound hardware. When I go into the system profiler, it says "no built in sound" and when I go into the sound control panel to change the output setting as per the Lifehacker guide, it comes up empty.

 

I've tried applying a kext file for the built in audio found on this forum, but still no luck.

 

Any ideas? If I can't get this functional, is there any pci sound card recommendations out there that will save me from pulling my hair out?

 

Thanks in advance!

[thepretender]

Howdy folks.

 

I need help getting my sound working. For whatever reason, my installation is not recognizing any sound hardware. When I go into the system profiler, it says "no built in sound" and when I go into the sound control panel to change the output setting as per the Lifehacker guide, it comes up empty.

 

I've tried applying a kext file for the built in audio found on this forum, but still no luck.

 

Any ideas? If I can't get this functional, is there any pci sound card recommendations out there that will save me from pulling my hair out?

 

Thanks in advance!

 

Tell us a little about your install how dose it vary from the lifehacker guide? Your not trying to us your GA-P35-DS3 are you? Any kext other than come in the installer, witch installer are you using? What version of OSX?

[max_raid]

Tell us a little about your install how dose it vary from the lifehacker guide? Your not trying to us your GA-P35-DS3 are you? Any kext other than come in the installer, witch installer are you using? What version of OSX?

 

The hardware is the same as the lifehacker guide. It's a GA-E45-UD3P mobo, core 2 quad, 4gb of ram, geforce 8800 gts video. I used the retail OS X installation and updated to 10.6.4 via the software installer.

 

I ran through all the steps in the Lifehacker guide which says that the sounds should be functional save for choosing the proper setting in the sound control panel. When I go into the sound control panel, however, my mac comes up with no devices listed.

 

Anything else that may be helpful in diagnosing my issue, please let me know!

 

Thanks in advance.

[konjow]

I updated my bios to 0.8 (thanks)- everything is very nice...

but cpu temp. in istat are not working any more. Im wander do you still use any additional kext for this. Id like to OC little bit if it is so cool in 0.8 but can see temps.

 

thanks for that.

[RocketLynx]

The hardware is the same as the lifehacker guide. It's a GA-E45-UD3P mobo, core 2 quad, 4gb of ram, geforce 8800 gts video. I used the retail OS X installation and updated to 10.6.4 via the software installer.

 

I ran through all the steps in the Lifehacker guide which says that the sounds should be functional save for choosing the proper setting in the sound control panel. When I go into the sound control panel, however, my mac comes up with no devices listed.

 

Anything else that may be helpful in diagnosing my issue, please let me know!

 

Thanks in advance.

 

There are two (2) downloads for that board, I know because I have the second release and it works flawlessly. One is for the original GA-EP45-UD3P and one for the GA-EP45-UD3P ver. 1.6. They differ. Did you get the correct one?

[thepretender]

The hardware is the same as the lifehacker guide. It's a GA-E45-UD3P mobo, core 2 quad, 4gb of ram, geforce 8800 gts video. I used the retail OS X installation and updated to 10.6.4 via the software installer.

 

I ran through all the steps in the Lifehacker guide which says that the sounds should be functional save for choosing the proper setting in the sound control panel. When I go into the sound control panel, however, my mac comes up with no devices listed.

 

Anything else that may be helpful in diagnosing my issue, please let me know!

 

Thanks in advance.

 

Sound is rarely a problem so it must be something simple.

 

Did the sound work before you updated the OS?

Did you find and use version 3 of stella's installer? Its best for hackintosh to use combo update instead of software, but doubt that is the cause of your sound problems.

All bios settings as per the guide with sound enabled in bios?

[960brick]

This is for anyone who has upgraded to Cartri Bios 0.8 only !

 

Install the Chameleon binaries (RC5) that came with Cartri bios 0.8 onto the EFI partition

 

 

Download this, boot.zip unzipit & place the "boot" folder on your Desktop

 

Open Terminal, Type the Following:

diskutil list

Find your target EFI partition from the list , mine was ( disk0s1)

 

 cd /Users/YOURNAME/Desktop\ boot/
newfs_hfs -v EFI /dev/rdisk0s1
mkdir /Volumes/EFI
mount_hfs /dev/disk0s1 /Volumes/EFI
./fdisk440 -f boot0 -u -y /dev/rdisk0
dd if=boot1h of=/dev/rdisk0s1
cp boot /Volumes/EFI
cp -r Extra* /Volumes/EFI/
touch /Volumes/EFI/.fseventsd/no_log
./fdisk440 -e /dev/rdisk0
f 1
w
q
umount -f /Volumes/EFI
rm -rf /Volumes/EFI

Delete the 'boot' file and 'Extra' folder from HD

 

 rm -r /boot 
rm -r /Extra

 

 

Chameleon installer from the Cartri 0.8 MacBIOS_Bootloader_v0.3lb.pkg.zip

Cartri Bios 0.8 for EP45-UD3P v1.6 only P45UD3P2.08.zip

EFI_Partition_Utility.dmg

[JTG78]

It's been close to a year since I built my machine (late September 09), so I'm wondering if the suggested Extra extensions for the LifeHacker build have changed at all. Unfortunately, I don't recall which of these were included automatically with the original or Stell's v3 installer. Personally, I'm using the following in my Extra folder:

 

ALC889A.Fix - I know this is for sound

Disabler - I don't remember what this is for

famesmc (v2.5) - This one I know is critical

IOAHCIBlockStorageInjector - Clearly deals with the hard drive, but not sure how important it is

LegacyJMB386xSATA - Same as above

NullCPUPowerManagement - disables Apple's IntelCPU power management kext - my CPU reports ~60C without it

OpenHaltRestart - I believe it helps allow the computer to properly reboot and/or sleep

SleepEnabler - Helps to allow sleep

 

Just to verify for everyone, yes, I'm running the standard Fall09 LifeHacker build (with OS X 10.6.4). The only difference is I've got 8GB Ram.

 

Basically, I'd like to know if my set of extensions is good, if I should remove something, or if I should add something.

 

On a side note, what kind of temperatures should I be getting at idle? I'm curious because I think my system is running a bit hot (CPU = [45C,38C,48C,45C] at idle) I was running 6-7C warmer before I reapplied the thermal paste - but it still seems too warm. (FYI, I've been using Hardware Monitor to read the temps.) When I maxed out the CPU for ~5 minutes earlier today it got into the mid-70s. For reference, I'm using the Arctic Cooling Freezer 7 Pro - Rev.2 cooler and Arctic MX-2 thermal paste.

 

I reapplied the paste, because when I transported my computer about a week and a half ago, it tipped on it's front while traveling, and the heat-sink came loose. I discovered this after my bios gave an overtemp alarm (>80C) while I was playing a CPU intensive game.

[960brick]

ALC889A.Fix - I know this is for sound

Disabler - I don't remember what this is for

famesmc (v2.5) - This one I know is critical

IOAHCIBlockStorageInjector - Clearly deals with the hard drive, but not sure how important it is

LegacyJMB386xSATA - Same as above

NullCPUPowerManagement - disables Apple's IntelCPU power management kext - my CPU reports ~60C without it

OpenHaltRestart - I believe it helps allow the computer to properly reboot and/or sleep

SleepEnabler - Helps to allow sleep

 

Delete your Extra and reinstall V3 and add VoodooPowerMini.kext (S/L/E ) to lower your temps

[bean5]

Delete your Extra and reinstall V3 and add VoodooPowerMini.kext (S/L/E ) to lower your temps

now, if i add voodoopowermini.kext will I have to remove it when there's an OS update? Also, how does one go about adding kexts?

[960brick]

how does one go about adding kexts?

 

KextHelper

[JTG78]

Delete your Extra and reinstall V3 and add VoodooPowerMini.kext (S/L/E ) to lower your temps

 

Tried it, but it seems to be running pretty much the same, or perhaps as much as 5-6 degrees© hotter at around 50-51C when idle. I verified the kext installed correctly by checking whether it showed up in the SystemProfiler after reboot.

 

I'd rather it was cooler, but at least it's not running at 60C like it was before when I tried running without the NullCPUPowerManagement kext.

 

I'll restate the question from the second half of my previous post though, and ask if these are the kind of temperatures I should be seeing at idle with my CPU/cooler setup?

[960brick]

Tried it, but it seems to be running pretty much the same, or perhaps as much as 5-6 degrees© hotter at around 50-51C when idle. I verified the kext installed correctly by checking whether it showed up in the SystemProfiler after reboot.

 

I'd rather it was cooler, but at least it's not running at 60C like it was before when I tried running without the NullCPUPowerManagement kext.

 

I'll restate the question from the second half of my previous post though, and ask if these are the kind of temperatures I should be seeing at idle with my CPU/cooler setup?

 

 

Hi JTG78,

 

If I remember right, I think my temps were around 44C idle and low 50s on load after voodoominipower. in bios are C states enabled?

[mm67]

Tried it, but it seems to be running pretty much the same, or perhaps as much as 5-6 degrees© hotter at around 50-51C when idle. I verified the kext installed correctly by checking whether it showed up in the SystemProfiler after reboot.

 

I'd rather it was cooler, but at least it's not running at 60C like it was before when I tried running without the NullCPUPowerManagement kext.

 

I'll restate the question from the second half of my previous post though, and ask if these are the kind of temperatures I should be seeing at idle with my CPU/cooler setup?

 

Those are the kind of temperatures you get without fully working power management. This is what you get with fully working P- and C-states:

 

Ambient temperature at the moment is 28 C and Q9550 is overclocked to 3.91 GHz

[JTG78]

Hi JTG78,

 

If I remember right, I think my temps were around 44C idle and low 50s on load after voodoominipower. in bios are C states enabled?

 

I believe so. (If I recall, it's C1E in the bios - which allows the clock multiplier to be adjusted on the fly.) In bios, my CPU temp registers at 44C, meaning in MacOS with VoodoPowerMini, I'm running about 6C hotter.

 

I'm certainly not getting the temperatures mm67 is getting - it makes me wonder what kind of cooling setup he has.

 

It also makes me worry about whether or not the thermal paste was applied properly to my heatsink.

 

On a side note, what program is mm67 using to register temperatures? I use HardwareMonitor, but it isn't able to register the any of my fans.

[mm67]

I believe so. (If I recall, it's C1E in the bios - which allows the clock multiplier to be adjusted on the fly.) In bios, my CPU temp registers at 44C, meaning in MacOS with VoodoPowerMini, I'm running about 6C hotter.

 

I'm certainly not getting the temperatures mm67 is getting - it makes me wonder what kind of cooling setup he has.

 

It also makes me worry about whether or not the thermal paste was applied properly to my heatsink.

 

On a side note, what program is mm67 using to register temperatures? I use HardwareMonitor, but it isn't able to register the any of my fans.

 

I have Prolimatech Megahalems as cooler and the program I was using is iStat menus. But to see all rpm readings etc you need to be using new version of FakeSmc.kext which you can find here: http://www.projectosx.com/forum/index.php?showtopic=1206. Just remember that is still pretty much at beta stage.

 

Setting C1E option in bios won't help if you are running a normal Gigabyte bios, with Cartri bios it might work, you'd have to ask those who use it. Using normal bios your only chance for perfectly working power management is patching your dsdt. Using VoodooPowerMini etc will give you P-states but it is C-states that are more important for temperatures while idling. Working C-states usually drop temps 5-15 degrees depending on your cooling system.

[JTG78]

I have Prolimatech Megahalems as cooler and the program I was using is iStat menus. But to see all rpm readings etc you need to be using new version of FakeSmc.kext which you can find here: http://www.projectosx.com/forum/index.php?showtopic=1206. Just remember that is still pretty much at beta stage.

 

Setting C1E option in bios won't help if you are running a normal Gigabyte bios, with Cartri bios it might work, you'd have to ask those who use it. Using normal bios your only chance for perfectly working power management is patching your dsdt. Using VoodooPowerMini etc will give you P-states but it is C-states that are more important for temperatures while idling. Working C-states usually drop temps 5-15 degrees depending on your cooling system.

 

So what you're saying is that having C-states enabled in bios doesn't matter unless my dsdt is properly patched? (Unfortunately, I don't know whether Stell's v3 dsdt is. I assume it isn't.) Anyone know where I can find the info around here to patch my dsdt with the proper C-states? (I'd search, but the search function is these forums is not too helpful a lot of times - and I'm sure there are others who'd be interested. That and I'm likly to find more information than I'd know what to do with.)

 

I've thought about using the Catri bios, but I'm still a little leery and may wait until it's a bit further along (i.e. step 5 or 6 - alpha running or released).

 

From what I read though, you're getting your temperatures with your cooler, the stock Stell v3 setup, and the modified fakeSmc. Or have you made other modifications to your setup?

[mm67]

So what you're saying is that having C-states enabled in bios doesn't matter unless my dsdt is properly patched? (Unfortunately, I don't know whether Stell's v3 dsdt is. I assume it isn't.) Anyone know where I can find the info around here to patch my dsdt with the proper C-states? (I'd search, but the search function is these forums is not too helpful a lot of times - and I'm sure there are others who'd be interested. That and I'm likly to find more information than I'd know what to do with.)

 

I've thought about using the Catri bios, but I'm still a little leery and may wait until it's a bit further along (i.e. step 5 or 6 - alpha running or released).

 

From what I read though, you're getting your temperatures with your cooler, the stock Stell v3 setup, and the modified fakeSmc. Or have you made other modifications to your setup?

 

I'm not using Stell's setup and temperatures come mostly from patched dsdt file, of course good cooler also helps but using stock speeds like you it doesn't really matter much. The thread to read is Vanilla speedstepping thread, don't get scared about the length of it. Almost all you really need to know is written in first post. Thread is here: http://www.insanelymac.com/forum/index.php?showtopic=181631

 

Gigabyte default C-states and P-states from bios don't work, you have to define them manually in dsdt.

[bean5]

I'll restate the question from the second half of my previous post though, and ask if these are the kind of temperatures I should be seeing at idle with my CPU/cooler setup?

I have the same cooler (that freezer 7 whatever it's called) but I have the q9650 OC'd to 3.33ghz. Running stock v3 stella, no modifications. I get the same temps you're reporting. This morning I was running at 51c idle. I was running hotter before yesterday, though, in the 60's because I had my rig stuffed with HDDs. I removed a few, cleaned out all the dust and it dropped my temps back down to the high 40's low 50's (I noticed that the heaksink for the freezer cooler built up dust right behind the fan making a wall of dust that didn't allow the fan to blow air over the heatsink...might want to clean that). In windows 7, the computer reports running at about 10 degrees lower (high 30's low 40's).

 

So, if I install this voodoo kext thing, will I have to remove it before I do a system update? say when 10.6.5 comes out?

 

Also, like I said, I'm running stock stella v3...are there any changes I should make to the kexts he provides? Like recent updates? I know there are some kexts you have to remove before doing updates, so if there are any that don't need to be removed when that time comes that I should update, I would appreciate it if someone could help me out.

[mm67]

I have the same cooler (that freezer 7 whatever it's called) but I have the q9650 OC'd to 3.33ghz. Running stock v3 stella, no modifications. I get the same temps you're reporting. This morning I was running at 51c idle. I was running hotter before yesterday, though, in the 60's because I had my rig stuffed with HDDs. I removed a few, cleaned out all the dust and it dropped my temps back down to the high 40's low 50's (I noticed that the heaksink for the freezer cooler built up dust right behind the fan making a wall of dust...might want to clean that). In windows 7, the computer reports running at about 10 degrees lower (high 30's low 40's).

 

So, if I install this voodoo kext thing, will I have to remove it before I do a system update? say when 10.6.5 comes out?

 

Also, like I said, I'm running stock stella v3...are there any changes I should make to the kexts he provides? Like recent updates? I know there are some kexts you have to remove before doing updates, so if there are any that don't need to be removed when that time comes that I should update, I would appreciate it if someone could help me out.

 

Probably you won't have to, none of the previous 10.6 updates have required that.

[JTG78]

I have the same cooler (that freezer 7 whatever it's called) but I have the q9650 OC'd to 3.33ghz. Running stock v3 stella, no modifications. I get the same temps you're reporting. This morning I was running at 51c idle. I was running hotter before yesterday, though, in the 60's because I had my rig stuffed with HDDs. I removed a few, cleaned out all the dust and it dropped my temps back down to the high 40's low 50's (I noticed that the heaksink for the freezer cooler built up dust right behind the fan making a wall of dust that didn't allow the fan to blow air over the heatsink...might want to clean that). In windows 7, the computer reports running at about 10 degrees lower (high 30's low 40's).

 

So, if I install this voodoo kext thing, will I have to remove it before I do a system update? say when 10.6.5 comes out?

 

Also, like I said, I'm running stock stella v3...are there any changes I should make to the kexts he provides? Like recent updates? I know there are some kexts you have to remove before doing updates, so if there are any that don't need to be removed when that time comes that I should update, I would appreciate it if someone could help me out.

 

One thing I've noticed while running the VoodooPowerMini kext is that while my system runs hotter while idling, it seems to run cooler under maximum load. Where before I ran it up to 76C under full load, now it stays around 69-70C.

 

Currently, I'm contemplating whether I want to go back to my previous kext loadout, just with the NullCPUPowerManagement kext removed. I prefer it since I have the Extra/Entensions folder to work with, and I can update kexts as needed. This isn't really an option with the mkext file Stell's installation offers.

 

FYI, I checked using MKextTool's mkext decompiler and found that Stell included the following kexts in his V3 package:

 

Disabler

fakesmc

IOAHCIBlockStorageInjector

LegacyATI4800Controller

LegacyHDA

LegacyJMB36xSata

OpenHaltRestart

 

This is pretty similar to my earlier list with the exception that the LegacyHDA kext replaced my ALC889A.Fix kext, and I have no need of the ATI4800 kext. From what I recall, if you use NullCPUPowerManagment, you should also use SleepEnabler - which I did as well. SleepEnabler is the only kext in the group I've used that has needed to be removed(or updated) before an update.

 

Edit: I've found that when modifying my kext load-out in either Extra/Extensions or System/Library/Extension that it's a good idea to run KextUtility (most recent version as far as I know is 2.4.2). It repairs permissions and rebuilds the mkexts, which doesn't always occur if you simply place the kext into the folder.

 

There's also a program called KextHelper (version 0.7) that may make it unnecessary to use KextUtility, but I haven't used it.

[JTG78]

I'm not using Stell's setup and temperatures come mostly from patched dsdt file, of course good cooler also helps but using stock speeds like you it doesn't really matter much. The thread to read is Vanilla speedstepping thread, don't get scared about the length of it. Almost all you really need to know is written in first post. Thread is here: http://www.insanelymac.com/forum/index.php?showtopic=181631

 

Gigabyte default C-states and P-states from bios don't work, you have to define them manually in dsdt.

 

I've managed to find my p-states using pstatechanger, unfortunately, I'm running into a roadblock when it comes to AppleLPC. I'm simply unable to find the ISA device - mostly because I couldn't get lspci tools working. I tried installing it from OS86 tools, but after rebooting I couldn't get it to work from the command line. Unfortunately, the instructions are a bit lacking. (Not to mention the trouble in finding where to get lspci tools in the first place.)

 

I'm taking a break from this for a few days. Frankly, I'm shuddering to think of the trouble I'll have to go through to get c-states working. Until I'm able to get the LPC information I'm back to running with the power management disabled since my computer runs cooler (at idle anyway) in this state. Since I think it was put on too thickly, I'll probably try replacing my thermal paste first to see if that improves the CPU temps.

 

I was also considering a getting a better CPU cooler, but since the ones I looked at required me to remove my motherboard to install a mounting/support bracket thing on the back, I think I'll hold off on that. I really don't want to have to deal with removing and reinstalling the motherboard.

[960brick]

I've managed to find my p-states using pstatechanger, unfortunately, I'm running into a roadblock when it comes to AppleLPC. I'm simply unable to find the ISA device

 

 

You guys who haven't already switched to Cartri bios, are missing out!

 

Don't waste your time with Lifehacker v3 , enjoy lower Temps, working p-states without voodoopowermini ! and dont need to deal with DSDT, smbios.plist, com.apple.Boot.plist & Extensions.mkext anymore.

[MacWannaBe]

You guys who haven't already switched to Cartri bios, are missing out!

 

Don't waste your time with Lifehacker v3 , enjoy lower Temps, working p-states without voodoopowermini ! and dont need to deal with DSDT, smbios.plist, com.apple.Boot.plist & Extensions.mkext anymore.

 

 

Agreed. the Cartri BIOS has my Hack running better than ever. With V3, sleep only worked if I set it (timed sleep did not work) and my temps were higher.

 

Now, all of is working fine.

 

-ED