Contribute
Register

How to build your own iMac Pro [Successful Build/Extended Guide]

Status
Not open for further replies.
Then something went wrong with the web driver patching?
I think so too... Tried to patch several times, and nothing..
 
You must continue until you succeed, sorry! It must work as described
I imagine! I will find out and post here in case anyone else encounters this silly issue. Thx
 
I think so too... Tried to patch several times, and nothing..

I had something similar happen to me. I was running the 159 drivers but couldn't take the lags and jitters. I uninstalled them and installed repacked 106 drivers. On my first attempt, my box wouldn't boot. I had to boot off of my USB drive and delete the drivers via the Terminal (see this post by Stork for how to do this).

I reran the repackage process with newly downloaded 106 drivers, reinstalled, and everything worked the second time around. Sounds like you have tried to install several times, so I'm not sure what is wrong but maybe try one more time with freshly downloaded drivers.
 
I had something similar happen to me. I was running the 159 drivers but couldn't take the lags and jitters. I uninstalled them and installed repacked 106 drivers. On my first attempt, my box wouldn't boot. I had to boot off of my USB drive and delete the drivers via the Terminal (see this post by Stork for how to do this).

I reran the repackage process with newly downloaded 106 drivers, reinstalled, and everything worked the second time around. Sounds like you have tried to install several times, so I'm not sure what is wrong but maybe try one more time with freshly downloaded drivers.

@dolgarrenan , @nnorris7 ,
the web driver always must be uninstalled by means of the uninstall option within the Nvidia Driver Manager.
 
@dolgarrenan , @nnorris7 ,
the web driver always must be uninstalled by means of the uninstall option within the Nvidia Driver Manager.
Thats what I went for, but with the outcome... I'll give a go to uninstalling everything NVDA related.
 
That your 5k screen doesn't properly work might not be exclusively the fault of the Vega

It works on the Vega on Windows, and it works on this hackintosh with smbios set to MacPro,1

SMBIOS macPro6,1 for me at present is definitely no valuable option.. in any case, your decision..
For my day to day use, I could live with it reporting to be a mac pro.
The processor is powerful enough to not need the hardware decoder.
Though, when I see the previous test about H264 encoder, thinking that I would be missing on it drives me mad :)

No idea if it is really worth to commit all efforts you are asking for... hot plug functionality is absolutely negligible in daily life..

I agree... it doesn't bother me that much, it just points that there's an issue with the vega somehow, it doesn't behave like the real vega in an imac pro.

Are you able to drive 2 standard monitors with your VEGA and SMBIOS iMacPro1,1, like @prunzi does?

What I think is happening is that with iMacPro1,1, it can only use 2 DP ports at a time, not 3.
I'm getting weird behaviours when I connect 3 cables to it (I tried with an HDMI TV as well).
Can do 2 well (without hotplug), not 3.
And DP port 2 is also behaving differently from the other.

I'll post my test results next.
 
I agree with all your reasoning.. But driving 4 cores at frequencies far beyond the stock frequency should overhead these cores tremendously, especially if one considers that you just use a H115i, isn't it? It is not a question of power consumption.

During linking time (where I can see the processor going over 4.5Ghz), the CPU temp is around 55C...

It only really heats up when all cores are in use.

Look at it this way: 4 cores at 4.7GHz aren't going to heat anywhere as much as 18 running at 4.2GHz...
Plus, I have my doubts that those 4 cores will always be the same on the die.. It all depends on when they become inactive and active again...
But you're right, I will check this using iStats and look at the temperature of each core during a compilation...

it certainly doesn't throttle , I wouldn't achieve such good compilation time otherwise.
 
  • Like
Reactions: kgp
During linking time (where I can see the processor going over 4.5Ghz), the CPU temp is around 55C...

It only really heats up when all cores are in use.

Look at it this way: 4 cores at 4.7GHz aren't going to heat anywhere as much as 18 running at 4.2GHz...
Plus, I have my doubts that those 4 cores will always be the same on the die.. It all depends on when they become inactive and active again...
But you're right, I will check this using iStats and look at the temperature of each core during a compilation...

it certainly doesn't throttle , I wouldn't achieve such good compilation time otherwise.

yep, just check the individual core temps by using iStatMenus...just to be at the save side.. :thumbup:
 
Status
Not open for further replies.
Back
Top