Jump to content

new Mountain Lion 10.8.2 Updater - late 2012 models - Nvidia drivers


mitch_de
 Share

47 posts in this topic

Recommended Posts

http://www.macupdate...in-lion-updater

Netkas comment:

http://netkas.org/?p=1219

 

Its limited (in the .pkg distribution file) to that models:

....

function InstallationCheck(prefix) {

var models = ['iMac13,1','Macmini6,1','Macmini6,2','MacBookPro10,2',];

...

 

A bit ??? because so much non Driver parts also getting updated (most Apple Apps + Utils). 1,3GB uncompressed update!!

Diskutil for example is unique for new FLASH+HD strategie of new late 2012 models.

Unsure if you may get problems on hackintosh (if you remove that model checl code in the distribution file).

If you try please report probs / success - also how you updated (full by .pkg+ distrobution file editing or some drivers only by pacifist).

 

EDIT:

Answer why update is so huge and not only has some late 2012 updates.

It´s because the new late 2012 models shipped with special OS X 10.8.1 Version (some newer drivers as 10.8.1 / specific other content). So they need that huge update to get to 10.8.2

Info here: http://www.macminivault.com/2012mini/ MacMini opened

  • Like 1
Link to comment
Share on other sites

There is a new kext (NVIDIA) NVDAStartup.kext

It seems that it inits some gpu related stuff (injection of variables like used in chameleon / dsdt enabler variables)

 

Disassembled NVDAStartup.kext for gpu variables injection part:

Bildschirmfoto 2012-10-25 um 12.32.20.jpg

  • Like 2
Link to comment
Share on other sites

Its mainly an 10.8.2 with some newer drivers (and some newer Apps like diskutil). Also kernel is newer than 10.8.2.

I wouldn't install that without an bootable CCC clone of running system version.

Also updating only some parts (like Nvidia drivers by pacifist) maybe an risk - some frameworks may also need to be updated.

Link to comment
Share on other sites

Oke thanks.

 

How can Fusion be activated (if installed)? I understand that this proces it automatically.. but is there an option in the System Preferences or such?

If installed, does AppleACPIPlatform.kext need to be from a previous version (10.8) again?

 

I have already uninstalled the Nvidia Driver update, it seems that the new kexts are smaller than the ones that this update has.

Maybe because some stuff are moved to that startup kext?

Link to comment
Share on other sites

Ok, I haven't installed the update yet.. Anyone tried the nVidia drivers? What driver version is reported in the CUDA settings?

 

I have a SSD, but I don't mind if Apple manage the drive, because what I understand it moves apps/docs to SSD/HDD and that will reduce the life of the SSD. (Because most of them are not optimised as cash-disk)

Link to comment
Share on other sites

I installed it here without any problems. I just edited the distribution file to add my MacPro5,1 identifier.

 

The build version is 12C2034. Just had to do the usual HDA rollback and OpenCL patch. The nVidia drivers are 304.10.20f04. There's also a CUDA driver update 5.0.37. I couldn't see it on the nVidia site so I let the control panel download it and then pulled the download URL from the log.

 

Haven't seen anything visibly different.

Link to comment
Share on other sites

I installed it here without any problems. I just edited the distribution file to add my MacPro5,1 identifier.

 

The build version is 12C2034. Just had to do the usual HDA rollback and OpenCL patch. The nVidia drivers are 304.10.20f04. There's also a CUDA driver update 5.0.37. I couldn't see it on the nVidia site so I let the control panel download it and then pulled the download URL from the log.

 

Haven't seen anything visibly different.

Hmm.. the latest nVidia drivers report: 1.3.4.0 (304.00.05f02)

 

So it seems that the nVidia drivers in this update are from a newer generation.

What can be correct because the new Apple models using newer GeForce-cards.. :)

 

Do you have any performance increase? Do you had (also) freezes? (Btw. what is your card?)

Link to comment
Share on other sites

I don't really keep track of benchmarks so I can't say if it's any faster. I've only had one freeze in the months that I've been using ML, and that was with the current nvidia retail drivers on 10.8.2. I launched Firefox and had an instant freeze. Reverted the drivers back to the stock 10.8.2 ones and later added a legacy AGPM kext to get my card working with it. But I don't use my hackintosh that much. There's nothing that can 100% trigger a freeze for me, but I had a freeze recently in Windows too after finally updating from driver 275.33.

 

After this update I just ran Oceanwave to test OpenCL and a couple of games (Bejeweled 3 and Modern Combat). No issues to report. My setup is in my sig.

Link to comment
Share on other sites

Would be interesting if someone which had installed that specially 10.8.2 build with Nvidia card look into the console for some output (Info/Error) of the new NVDAStartup.kext.

In his code there is some logging for console if nvidia cards (i think only non apple) isnt right "seen".

Link to comment
Share on other sites

26.10.12 17:46:43,000 kernel[0]: NVDAStartup: Official

26.10.12 17:46:43,000 kernel[0]: NVDAGF100HAL loaded and registered

with following injection:

 

 

Method (PINI, 0, NotSerialized)

{

Store (0x00B3106B, \_SB.PCI0.PEG0.GFX0.ASDI)

/*******/

}Device (GFX0)

{

Name (_ADR, Zero)

OperationRegion (SVID, PCI_Config, 0x40, 0x04)

Field (SVID, DWordAcc, NoLock, Preserve)

{

ASDI, 32

}

 

Method (_DSM, 4, NotSerialized)

{

Store (Package (0x2C)

{

"@0,can-hot-plug",

Buffer (Zero) {},

"@1,can-hot-plug",

Buffer (Zero) {},

"AAPL,aux-power-connected",

Buffer (0x04)

{

0x01, 0x00, 0x00, 0x00

},

 

"@0,compatible",

Buffer (0x0B)

{

"NVDA,NVMac"

},

 

"@0,device_type",

Buffer (0x08)

{

"display"

},

 

"@0,name",

Buffer (0x0F)

{

"NVDA,Display-A"

},

 

"@1,compatible",

Buffer (0x0B)

{

"NVDA,NVMac"

},

 

"@1,device_type",

Buffer (0x08)

{

"display"

},

 

"@1,name",

Buffer (0x0F)

{

"NVDA,Display-B"

},

 

"NVCAP",

Buffer (0x14)

{

/* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x00,

/* 0008 */ 0x3C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A,

/* 0010 */ 0x00, 0x00, 0x00, 0x00

},

 

"NVPM",

Buffer (0x1C)

{

/* 0000 */ 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,

/* 0018 */ 0x00, 0x00, 0x00, 0x00

},

 

"VRAM,totalsize",

Buffer (0x04)

{

0x00, 0x00, 0x00, 0x50

},

 

"device_type",

Buffer (0x0C)

{

"NVDA,Parent"

},

 

"NVDA,Features",

Buffer (0x04)

{

0xFF, 0x06, 0xB3, 0x00

},

 

"NVDA,gart-width",

Buffer (One)

{

0x40

},

 

"APPL,gart-width",

Buffer (One)

{

0x40

},

 

"model",

Buffer (0x10)

{

"GeForce GTX 570"

},

 

"rom-revision",

Buffer (0x0F)

{

"70.10.55.00.G0"

},

 

"AAPL,slot-name",

Buffer (0x0D)

{

"PCIe x16"

},

 

"@0,connector-type",

Buffer (0x04)

{

0x00, 0x08, 0x00, 0x00

},

 

"@1,connector-type",

Buffer (0x04)

{

0x00, 0x04, 0x00, 0x00

},

 

"hda-gfx",

Buffer (0x0A)

{

"onboard-1"

}

}, Local0)

MCDP (Arg2, RefOf (Local0))

Return (Local0)

}

}

 

Link to comment
Share on other sites

Maybe trim patch cant work if some bytes / code structures changed in the AHCIBlock... kext in this build.

Because some things changed for FUSION it can be such code changes. Normally that kext stays same between minor OS X updates.

Link to comment
Share on other sites

 Share

×
×
  • Create New...