Lifehacker Guide with GA-EP45-UD3P Motherboard

[bean5]

perfect? they're working great, absolutely, but there are still some issues, no? NIC doesn't work correctly. Temps are 10 degrees higher than what they could be. And that's just what I know of, I don't know if there's anything else. I would appreciate the temps being lower. It's getting hot where I am right now and my cpu is idling in the 50's now (when I built it a few months ago, would idle in the low 40's) It would be nice if the temp could be brought down so I could overclock it a bit.

[backinmac]

perfect? they're working great, absolutely, but there are still some issues, no? NIC doesn't work correctly. Temps are 10 degrees higher than what they could be. And that's just what I know of, I don't know if there's anything else. I would appreciate the temps being lower. It's getting hot where I am right now and my cpu is idling in the 50's now (when I built it a few months ago, would idle in the low 40's) It would be nice if the temp could be brought down so I could overclock it a bit.

Are you going by BIOS temps or temps from inside OSX? Because temp monitor says between 40-50 for me, but in BIOS I'm getting sub 30 temps.

[danyokeem]

why would your monitor display hdmi if there's no hdmi connection? (from what you said before, all it has are two dvi and an s video connection). Try the s video connection and see if you get the same problem. Also, what monitor are you using (model number)? If possible, use another monitor and see if it'll work with that. If you're using the stella installer and following the lifehacker guide, there shouldn't be an issue with kexts. Like I said, hdmi seems to be an issue and seeing your monitor display hdmi makes me think there's a connection there (like you're using a dvi to hdmi connection). I also don't see how the wireless card could cause a problem, but I wouldn't know if that could or could not cause a problem.

 

Bean,

 

I think you're right. My monitor seems to be based with HDMI and it converts it from DVI? Something weird like that... (Because I'm using a DVI from the CPU to DVI directly into the monitor. But okay. Guess it's just time to reinstall and keep 10.6.2.

[bean5]

within osx. I get the same, with low to mid 30's in bios. So, are the OSX temps just being reported within OSX as higher than what they actually are? Or are they accurately being reported?

[MacTech84]

hey bean,

 

it says hdmi only because no dvi signal is recognized. maybe the vid card somehow wasn't kexted right?

 

so i was living my life like my hackintosh was the {censored}. but once again my bubble got popped.

 

is it possible that the wireless card has caused this mess??? that sounds pretty ridiculous but who knows.

 

is keeping a time machine backup the quickest way to get back on your feet w/ a hackintosh after hiccups like these?

 

You are getting the signal disappearing because the last stage of the bootloader is to change resolution of the graphics card, i.e. graphics driver loading. Do this...

 

Boot from your USB install drive with the v3 installer on it, if that works reinstall the bootloader from the v3 installer. Remember to delete the extras folder first.

 

Why would he be? Our installs are perfect.

 

While the installs are close to perfect, I would love to see a v4 installer with an updated bootloader, but the VooDoo team has yet to release chameleon rc5

[CoHPhasor]

For anyone interested I found something very interesting, on none other, the Insanely Mac Home page. Apparently someone out there is making the HOLY GRAIL of BIOS for a string of Gigabyte boards including ours, and I think we should lend a hand. This guy is making a Custom BIOS that requires NO Bootloader, NO DSDT, and everything works including USB sleep functionality, Proper Temp read outs, and NO! NO kext's to get OS X running. If you have not guessed it, its a Custom BIOS that not only allows for Multi-Booting, but a straight Vanilla Install of OS X from the retail disk! Best part... We can still re-flash to the official Gigabyte BIOS as well. The only downside is that the BIOS is in Alpha for our Board as seen from the image below, but... Like me, being the Guinea Pig that I am, I, and hoping others will join me, want to make this a de-facto standard for our board. I am including the link to the forum for the Custom BIOS, as well as the most recent update for the BIOS he has ported. We will need to PM the developer to get the Alpha build for our boards and then we will be set. Lets get it from Alpha to RC and beyond! I have wondered about a day like this for some time and its here! Also, he is porting the BIOS from version 1.0, 1.2, & the 1.6 board, so lets help this guy out!

 

I honestly would if I ran mine that much and wasn't in school and a 45hr/wk job. :-\

 

For those here who are too paranoid,.. you can always do it on a secondary disk, and our board has TWO BIOS capability.

If the experimental BIOS causes an issue you can simply have it use the other one!

There's no real risk if you have 2 HDs and keep the old FB on your mb for backup.

[backinmac]

within osx. I get the same, with low to mid 30's in bios. So, are the OSX temps just being reported within OSX as higher than what they actually are? Or are they accurately being reported?

I don't have an extensive knowledge on any of this, just what I read. As I understand it, real Macs get their temps from an SMC device, whatever that is. Something inside I'm guessing. In order to get Mac OS X to work, every vanilla Hackintosh (maybe more, like I said not an expert) uses a kext called FakeSMC to trick the vanilla kernel to thinking it is a real Mac. Therefore, it is just "Fake" and temps are not accurate. However much of the info I just wrote is probably inaccurate, but there is one thing I am 100% sure of, temps are given from SMC, we have FakeSMC, and therefore our temps are messed up.

 

EDIT:

See post #736. Some guy had a reading of like 12,000 degrees celsius.

[CoHPhasor]

I don't have an extensive knowledge on any of this, just what I read. As I understand it, real Macs get their temps from an SMC device, whatever that is. Something inside I'm guessing. In order to get Mac OS X to work, every vanilla Hackintosh (maybe more, like I said not an expert) uses a kext called FakeSMC to trick the vanilla kernel to thinking it is a real Mac. Therefore, it is just "Fake" and temps are not accurate. However much of the info I just wrote is probably inaccurate, but there is one thing I am 100% sure of, temps are given from SMC, we have FakeSMC, and therefore our temps are messed up.

 

EDIT:

See post #736. Some guy had a reading of like 12,000 degrees celsius.

 

Right on the money.

The SMC controller in a Mac does operate the mobo sensors, as well turns on the fans even.

(That's why there are fakeSMC's for REAL macs too, to allow you to turn up and down your fans)

 

It is the lack of an SMC in our boards that brings the need of FakeSMC to parlay temp info.

There of course ARE sensors on our boards, but OSX is not programmed to listen to them,

or how to understand them.

FakeSMC is a *translator of data. (Albeit an apparently flawed one.)

I would simply surrender to the idea of not monitoring it, stop being paranoid,

or run Winblows in Paralells and use Gigabyte's software to monitor it. ;-)

[bean5]

so would you say that the temps are being reported higher than what they actually are? What would be considered safe working temps for this chip anyways? Like, what's a good idle temp to shoot for, and what's a good average for when the cpu is under load?

[scorcho]

as long as you're under 90C during full load you really have nothing to worry about. mincing between 40C and 50C means very little to the life of the equipment. well, that is unless you realistically believe you'll be using that config for the next 20 years.

[MacTech84]

so would you say that the temps are being reported higher than what they actually are? What would be considered safe working temps for this chip anyways? Like, what's a good idle temp to shoot for, and what's a good average for when the cpu is under load?

 

CoHPhasor is dead on right, from previous testing we have come across that the temps are about 10 degrees hotter then they actually are. The translation layer that the FakeSMC does is good for what it does, but its not the best for translating temps. Do not worry, one thing to keep in mind as well, the BIOS in your computer is set to automatically adjust fan speeds for your system and supersedes what the OS tells it. It will monitor your system and adjust when it needs to.

[mm67]

CoHPhasor is dead on right, from previous testing we have come across that the temps are about 10 degrees hotter then they actually are. The translation layer that the FakeSMC does is good for what it does, but its not the best for translating temps. Do not worry, one thing to keep in mind as well, the BIOS in your computer is set to automatically adjust fan speeds for your system and supersedes what the OS tells it. It will monitor your system and adjust when it needs to.

 

Core temps that iStat shows are exactly same on Windows and OS X. These are my temps from OS X idling and running Linpack stress test:

 

and this shows the same situation from Windows 7:

 

Temperature that you see in bios is from motherboards sensor and it usually is a bit cooler than core temps that are read from cpu itself,on OS X you can monitor that temperature using mark-i program, it's the one in upper left corner.

[bean5]

well, here are my temps, idling on a rather cool night.

 

 

As you can see, it shows that it's idling in the 40's.

 

 

The bios shows it in the thirties.

 

 

Overclocked to 3.33ghz in OSX it's in the 50's. Granted, it's rather cool at the moment where I am so the temps are about 5 degrees lower than what I would expect.

 

In windows 7, this is what I get, top not OC, bottom OC to 3.33ghz

 

 

 

 

So, does that sound about right? I'm not using the stock heatsink/fan. I got that arctic freezer cooler whatever it's called. I'm pretty sure I put it on right (not too much thermal paste) however I think I may have sunken in the cpu casing (is that bad?). What's the general concensus? Will I be alright if I overclock it to 3.33ghz and have istats reporting that the temps are in the 50's-60's while idle?

[mm67]

well, here are my temps, idling on a rather cool night. As you can see, it shows that it's idling in the 40's. The bios will probably show it in the thirties. If I overclock it to 3.33ghz, it'll be in the 50's. So, does that sound about right? I'm not using the stock heatsink/fan. I got that arctic freezer cooler whatever it's called. I'm pretty sure I put it on right (not too much thermal paste) however I think I may have sunken in the cpu casing (is that bad?). What's the general concensus? Will I be alright if I overclock it to 3.33ghz and have istats reporting that the temps are in the 50's-60's?

 

Those idling temps do seem to be quite high but full load temps are more important, get Linpack and let it run run for 10 times with max problem size. If your temps stay below 75 you should be ok. But be careful, nothing else will make your cpu run as hot as Linpack.

[bean5]

where do I get this linpack?

[mm67]

where do I get this linpack?

 

Here : http://software.intel.com/en-us/articles/i...npack-download/

[bean5]

I don't understand how to use this...

 

I get this:

 

*****-Mac-Pro:~ ****$ /Users/****/Downloads/linpack_10.2.4/benchmarks/linpack/runme64 ; exit;

This is a SAMPLE run script. Change it to reflect the correct number

of CPUs/threads, problem input files, etc..

Sat Apr 3 04:06:52 PDT 2010

/Users/****/Downloads/linpack_10.2.4/benchmarks/linpack/runme64: line 11: ./linpack_cd64.app: No such file or directory

Done: Sat Apr 3 04:06:52 PDT 2010

logout

 

[Process completed]

[mm67]

I don't understand how to use this...

 

I get this:

 

*****-Mac-Pro:~ ****$ /Users/****/Downloads/linpack_10.2.4/benchmarks/linpack/runme64 ; exit;

This is a SAMPLE run script. Change it to reflect the correct number

of CPUs/threads, problem input files, etc..

Sat Apr 3 04:06:52 PDT 2010

/Users/****/Downloads/linpack_10.2.4/benchmarks/linpack/runme64: line 11: ./linpack_cd64.app: No such file or directory

Done: Sat Apr 3 04:06:52 PDT 2010

logout

 

[Process completed]

 

Open Terminal, go to folder where you extracted Linpack to and run ./runme64. Like this:

[backinmac]

I don't understand how to use this...

 

I get this:

 

*****-Mac-Pro:~ ****$ /Users/****/Downloads/linpack_10.2.4/benchmarks/linpack/runme64 ; exit;

This is a SAMPLE run script. Change it to reflect the correct number

of CPUs/threads, problem input files, etc..

Sat Apr 3 04:06:52 PDT 2010

/Users/****/Downloads/linpack_10.2.4/benchmarks/linpack/runme64: line 11: ./linpack_cd64.app: No such file or directory

Done: Sat Apr 3 04:06:52 PDT 2010

logout

 

[Process completed]

Yes, I get the same thing when clicking on the Runme. But if you click on the file called like LinpackCD_64 or something along those lines, you get a message saying that the classic environment is no longer supported. Do we need OS 9 or OS 9 drivers to run this? Bean, I think you should try Prime95 instead. It's pretty much the standard for testing your overclock settings. Google is your friend.

 

EDIT: I forgot, you need a Winblows installation for that.

[mm67]

Yes, I get the same thing when clicking on the Runme. But if you click on the file called like LinpackCD_64 or something along those lines, you get a message saying that the classic environment is no longer supported. Do we need OS 9 or OS 9 drivers to run this? Bean, I think you should try Prime95 instead. It's pretty much the standard for testing your overclock settings. Google is your friend.

 

EDIT: I forgot, you need a Winblows installation for that.

 

There is Prime95 for OS X also, you can get it here : http://mersenneforum.org/gimps/Prime95-MacOSX-2511.zip

Runs exactly the same tests as Windows version but no gui, you have to use Terminal like with Linpack

[mosslack]

You are getting the signal disappearing because the last stage of the bootloader is to change resolution of the graphics card, i.e. graphics driver loading. Do this...

 

Boot from your USB install drive with the v3 installer on it, if that works reinstall the bootloader from the v3 installer. Remember to delete the extras folder first.

 

 

 

While the installs are close to perfect, I would love to see a v4 installer with an updated bootloader, but the VooDoo team has yet to release chameleon rc5

 

 

I have a similar issue, I have mine setup with dual video cards and after a long, long search I finally found the correct DSDT to allow this to work in 10.6.x. It worked fine under 10.6.2, but with the update I get blue screens. Switching off the monitors and back on, I get blue screens on the 2 monitors hooked up via VGA, but the other one which is hooked up via DVI shows snow, which I assume means no signal.

 

If I boot up in safe mode, I can get past the blue screens and a semi-normal desktop display. Only the DVI display comes up in the correct resolution, the others have their resolutions lowered and the arrangement is out of order. Reseting the order and resolutions and then rebooting just makes it come up blue screens again.

 

BTW, I'm using Stel's v3 installer package with modified DSDT for my dual video card setup.

[backinmac]

I have a similar issue, I have mine setup with dual video cards and after a long, long search I finally found the correct DSDT to allow this to work in 10.6.x. It worked fine under 10.6.2, but with the update I get blue screens. Switching off the monitors and back on, I get blue screens on the 2 monitors hooked up via VGA, but the other one which is hooked up via DVI shows snow, which I assume means no signal.

 

If I boot up in safe mode, I can get past the blue screens and a semi-normal desktop display. Only the DVI display comes up in the correct resolution, the others have their resolutions lowered and the arrangement is out of order. Reseting the order and resolutions and then rebooting just makes it come up blue screens again.

 

BTW, I'm using Stel's v3 installer package with modified DSDT for my dual video card setup.

Could we get more details on your setup?

[MacTech84]

Core temps that iStat shows are exactly same on Windows and OS X. These are my temps from OS X idling and running Linpack stress test:

 

and this shows the same situation from Windows 7:

 

Temperature that you see in bios is from motherboards sensor and it usually is a bit cooler than core temps that are read from cpu itself,on OS X you can monitor that temperature using mark-i program, it's the one in upper left corner.

 

 

well, here are my temps, idling on a rather cool night.

 

As you can see, it shows that it's idling in the 40's.

 

The bios shows it in the thirties.

 

Overclocked to 3.33ghz in OSX it's in the 50's. Granted, it's rather cool at the moment where I am so the temps are about 5 degrees lower than what I would expect.

 

In windows 7, this is what I get, top not OC, bottom OC to 3.33ghz

 

So, does that sound about right? I'm not using the stock heatsink/fan. I got that arctic freezer cooler whatever it's called. I'm pretty sure I put it on right (not too much thermal paste) however I think I may have sunken in the cpu casing (is that bad?). What's the general concensus? Will I be alright if I overclock it to 3.33ghz and have istats reporting that the temps are in the 50's-60's while idle?

 

Are you using the OS X Bootloader to select the Windows drive upon boot? If so... guess what... That supersedes the Windows Bootloader and its translation of hardware to software. You get the same temps thanks to our bootloader. Let me put it this way, if you smell burning silicon you have a problem, if you do not, then you are all set and have nothing to worry about.

[bean5]

I use the bootloader and I get a 10 degree difference...lemme try doing it before the bootloader to see what happens.

[mm67]

Are you using the OS X Bootloader to select the Windows drive upon boot? If so... guess what... That supersedes the Windows Bootloader and its translation of hardware to software. You get the same temps thanks to our bootloader. Let me put it this way, if you smell burning silicon you have a problem, if you do not, then you are all set and have nothing to worry about.

 

Are you seriously trying to claim that using Chameleon has something to do with how Windows reads cpu temperatures ??? Maybe you should run some tests with and without Chameleon and you will very quickly see that those things have nothing to do with each other.