nvclock 0.8b5_7 (experimental) adds many new device ids and internal temperature reading fixes.
Nvclock and mapMemory binaries:  nvclock0.8b5_7_bin_universal.zip ( 184.74K ) Number of downloads: 1774
nvclock source:  nvclock0.8b5_7_darwin.zip ( 423.91K ) Number of downloads: 475

Added these devices: http://pastebin.com/ZR5RHRxU
If no i2c devices are found G92 and GT200 chips try Asus internal temp method, then G84 method, then NV50 method with correction bitshift by 2.
Attempt NV40 i2c bus unlock method on all chips.

If your card is reported as "Unknown Nvidia card" or contains "[?]" please post your device-id and card name.
If your card uses "NV50 GPU Internal Sensor" please report if your correction is too high.
If possible please report if 'sensors-detect' can find your nVidia i2c chipset from Linux if any "Internal Sensor" is used.
Also i2c may show attached to display in IOReg (as IOFramebufferI2CInterface), please report this presence if "Internal Sensor" is used.

Make sure to use the '-f' flag if your device is not recognized.

nvclock 0.8b5_6 (stable) fixes memory size and PRAMIN (BIOS info) reading!
Nvclock and mapMemory binaries:  nvclock0.8b5_6_bin_universal.zip ( 177.02K ) Number of downloads: 855
nvclock source:  nvclock0.8b5_6_darwin.zip ( 421.12K ) Number of downloads: 198

mapMemoryDriver_0.2 adds more advanced options for dumping from client.
mapMemory driver source:  mapMemoryDriver_0.2.zip ( 8.96K ) Number of downloads: 286

LOADING
Load as normal kext, mapMemoryDriverClient will verify the driver is loaded.


USING NVCLOCK
nvclock must be run with root privilege by default.
Gtk and qt3 variants build and run, but not all options may be available (ie nvcontrol extension).


ADVANCED MAPMEMORY OPTIONS
The mapMemory driver requires that requests be done by the root user, if you are sure you want to expose the mapMemory driver to any user you can edit the Info.plist "RequireRoot" property.
Modifying the "IONameMatch" property will allow the driver to attach with other devices.
mapMemoryDriverClient has advanced options like dumping memory, THIS MAY CAUSE YOUR COMPUTER TO FREEZE. You have been warned.


Special thanks to arwyn @ irc.freenode.org#macdev for patience and guidance.

Happy hacking!

This post has been edited by alphamerik: Jun 21 2010, 12:10 PM

Can't compile on 10.6 'cause it compiles i386 nvclock and tries to link x86_64/
Binary doesn't work - mapmemory finds GFX0@0, and nvclock says no nvidia cards.

Same here, dosen't work on x86_64
Can someone fix it?

I think it just needs -arch x86_64 added to the compile flags, unfortunately the configure/Makefiles ignore CFLAGS or CXXFLAGS.
Will see what I can do to make those variables work.

This post has been edited by alphamerik: Jun 11 2010, 10:21 PM

Okay a Universal build of nvcontrol binaries have been added and the source updated, configured like this:


If someone can post a Universal build of mapMemoryDriver it would be appreciated, xcode doesn't have the proper headers for 10.5.

This post has been edited by alphamerik: Jun 11 2010, 01:56 PM

you are still on 10.5?
But it still doesn't find video card. Of course, I run as root.

This post has been edited by гык-sse2: Jun 11 2010, 02:53 PM

Does it say no video card found or does it say no drivers found?
If it says that no driver is found try recompiling from source, and remove the -arch i386 flag.

Hopefully I will be upgrading to 10.6 soon.

EDIT: Also - it looks for a device name of "display", is your device name GFX?

This post has been edited by alphamerik: Jun 11 2010, 10:47 PM

It says no video card.
Memmapclient finds it OK. Property "name" of IOPCIDevice GFX0 is "display". My system is not 64 'cause of GF7300, but it runs 64-bit applications.

Memory access for x86_64 requires much more efforts then just recompilation.

Edit:
64-bit isn't such a big deal here, the only difference is in the pointer types for IOConnectMapMemory, and you can see the ifdef in the code, otherwise nvclock works with only <32-bit types from casts.

The problem is that I am using IORegistryEntryGetName which probably doesn't look at the properties for the name, it is probably more analogous to the basename of the path. Will modify it tonight to get the name from the properties dictionary instead.

This post has been edited by alphamerik: Jun 11 2010, 10:20 PM

Ok guys, I changed from using IORegistryEntryGetName to reading "IOName" from the properties.
Also a fix with x86_64 reading PRAMIN (forgot some parenthesis - 'doh).
Files up top have been updated.

The newest binary zip has x86_64 nvclock/smartdimmer with old i386 kext, yes they play nice together.

Please let me know if this fixes your detection problems.

Somebody please post a x86_64 build of mapMemoryDriver so I can lipo it with my build. Thanks.

Anyone notice their graphics fan boots with 30% manual setting?
Changing the fan to auto it stabilizes at ~ 63%, board goes from 58c to 53c, gpu 73c to 64c.
Probably a good thing to do in nvSmcMonitor startup.

This post has been edited by alphamerik: Jun 11 2010, 11:56 PM

THANKS updating binary+kext for 64 bit ("...also fixed accidental PRAMIN read on x86_64".
C2D + 8800GTX + 10.6.3 (64 Bit kernel mode) gets kextload error of
"nvclock0.8b5_3-bin/mapMemoryDriver.kext failed to load - (libkern/kext) requested architecture/executable not found; "
Perhaps i dont understand right the "64 Bit fixes"- does the kext needs to boot in 32 Bit Kernelmode ?

This post has been edited by mitchde: Jun 12 2010, 04:41 AM

It Works!!! And OCing also.
Yes, in 32bit.
Memory overclocking and underclocking gives artifacts and mouse pointer, then KP (with artifaqcts)

This post has been edited by гык-sse2: Jun 12 2010, 07:46 AM

Correct, I can't compile an x86_64 version of the kext (because I am on 10.5), but if someone posts their x86_64 build of the kext driver I can create a universal version from it.
Thanks

This post has been edited by alphamerik: Jun 12 2010, 03:08 PM

Here is the x86_64 version of the kext. Tested and working as the i386 build here.
 mapMemoryDriver.kext.zip ( 10.71K ) Number of downloads: 146

Thanks Trauma, downloads have been updated with source build fixes (minor) and universal binaries.


This post has been edited by alphamerik: Jun 12 2010, 10:41 PM

This is really great, now i can verify if the gpu throttle work or not, and the answer is : it work
I've to use a legacy AGPM.
I ve attach 2 screens, idle and in an openGL bench.



This post has been edited by real3x: Jun 12 2010, 04:47 PM

Thanks for 10.6/64 Bit kext.

nvclock -i works : only the Amount of VRAM (768 MB) is listed as 0 MB
Also using the two legacy kexts for PM (iMac5,1) for PM / GPU PM and so i now can first!!! see that it works also .



This post has been edited by mitchde: Jun 12 2010, 06:11 PM

works here too with my gtx 275 amount of memory 896 is shown as 0 and i have no fan connected to my gfx is shown as 41 rpm

Works here too bar RAM size - AGPM with iMac9,1

This post has been edited by FormerlyKnownAs: Jun 13 2010, 06:57 PM