Carstiman Posted November 8, 2010 Share Posted November 8, 2010 could you please add this key TA0P with handler, type sp78, size 2 into W836x.kext ? it is the heatsink of Winbond W83627DHG / Asus P5K. Th0H with handler, type sp78, size 2 is ambient. i played around but i don´t know how to add it into the info.plist. thx in advance Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578593 Share on other sites More sharing options...
kozlek Posted November 8, 2010 Author Share Posted November 8, 2010 I can tell mine is wrong because it never changes and the voltage it shows (1.23v) is higher than the highest set by both my BIOS and in my DSDT.aml which is 1.196 after the vdroop of my board and this latter voltage is the highest I see when I open the Voodoo Monitor. Even if it was picking up the default VID of my chip then it is still wrong as that is 1.2125. What you see in iStat is a near real value. It must be different from what you set in BIOS or DSDT. This is how your speedstep working... Seems not working. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578599 Share on other sites More sharing options...
MacUser2525 Posted November 8, 2010 Share Posted November 8, 2010 What you see in iStat is a near real value. It must be different from what you set in BIOS or DSDT. This is how your speedstep working... Seems not working. My speed stepping works I can see it in the Voodoo monitor it steps through all my p-states and even pops up with the one c-state I have on occasion that is how I know that part of it works as well. So I am not really sure what you mean there all I know is no matter what the voltage is always 1.23v even when I watch it jumping back and forth in the Voodoo monitor between the various states it never changes in iStat. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578605 Share on other sites More sharing options...
kozlek Posted November 8, 2010 Author Share Posted November 8, 2010 VoodooMonitor doesn't shows real voltage but requested by the CPU. Request doesn't means motherboard will provide it. Like mine - after overclocking if I leave CPU voltage on AUTO in BIOS I get frozen 1.29 Vcore. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578607 Share on other sites More sharing options...
MacUser2525 Posted November 8, 2010 Share Posted November 8, 2010 VoodooMonitor doesn't shows real voltage but requested by the CPU. Request doesn't means motherboard will provide it. Like mine - after overclocking if I leave CPU voltage on AUTO in BIOS I get frozen 1.29 Vcore. I am no expert at this but I know if I have nothing in my DSDT.aml that requests lower voltages through the p/c-states being defined my CPU is a full 10-12C higher just like when I run it at full 100% load ie. no speed stepping at all being used, so I have to tend to think that it is actually getting the lower voltages/speeds that are requested and shown in the monitor also without the p/c-states being defined the monitor shows my highest voltage and speed that is there when its defined which I think supports my assertion that its working. Now you could be onto something with the AUTO though I only over clock to the highest the board will go with no screwing around with the voltages and I do believe that it is set to AUTO will have to check next time I reboot and get back to you on this one. Thanks for the work I do appreciate the effort you have put into it. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578617 Share on other sites More sharing options...
FKA Posted November 8, 2010 Share Posted November 8, 2010 Same here - I am overclocked but voltages in BIOS are set to AUTO. Must admit I hadn't payed much attention to the CPU volts in istats! Please note my CPU volts in istats does change! D Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578654 Share on other sites More sharing options...
kozlek Posted November 8, 2010 Author Share Posted November 8, 2010 Same here - I am overclocked but voltages in BIOS are set to AUTO. Must admit I hadn't payed much attention to the CPU volts in istats! Please note my CPU volts in istats does change! D It's not surprising. It must be deviations on all readings in real world. But still with this tool you could see what's going on. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578658 Share on other sites More sharing options...
mm67 Posted November 8, 2010 Share Posted November 8, 2010 I am no expert at this but I know if I have nothing in my DSDT.aml that requests lower voltages through the p/c-states being defined my CPU is a full 10-12C higher just like when I run it at full 100% load ie. no speed stepping at all being used, so I have to tend to think that it is actually getting the lower voltages/speeds that are requested and shown in the monitor also without the p/c-states being defined the monitor shows my highest voltage and speed that is there when its defined which I think supports my assertion that its working. Now you could be onto something with the AUTO though I only over clock to the highest the board will go with no screwing around with the voltages and I do believe that it is set to AUTO will have to check next time I reboot and get back to you on this one. Thanks for the work I do appreciate the effort you have put into it. On my Gigabyte boards C -states only work when Cpu voltage is set to Normal or Auto in bios. With Auto option FSB has to be at stock value. Same thing happens with my Asus P5Q Deluxe board, my MSI P43 doesn't care about Cpu voltage, C - states always work. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578678 Share on other sites More sharing options...
Pietruszka Posted November 8, 2010 Share Posted November 8, 2010 Stock voltage is normal if you overclock there is DVID (dynamic VID) function (in BIOS) that can help to overclock and keep cpu cool --> dynamic voltage mobo must support this function...not all mobos got it Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1578939 Share on other sites More sharing options...
THe KiNG Posted November 10, 2010 Share Posted November 10, 2010 Who waiting for radeon and acpimonitor, be patient, I am planing to port all available plugins soon. Cool! Can't wait for ACPIMonitor. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1579900 Share on other sites More sharing options...
bigfranco03 Posted November 11, 2010 Share Posted November 11, 2010 Solved by changing W836x.kext info.plist <key>FANINLIMIT</key> <integer>0</integer> to <key>FANINLIMIT</key> <integer>4</integer> Thank you!! That's exactly what I needed! How did you figure out which fan was which? Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1580800 Share on other sites More sharing options...
kalel83 Posted November 11, 2010 Share Posted November 11, 2010 works here Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1580887 Share on other sites More sharing options...
FKA Posted November 11, 2010 Share Posted November 11, 2010 How did you figure out which fan was which? trial and error. D Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1580955 Share on other sites More sharing options...
xavinoiz Posted November 11, 2010 Share Posted November 11, 2010 Hello and thank u vry much for the efforts. Im having some problems reading temps of my Q6600, its showing rly low temperatures, far from what it should be. I've changed the TjMax to 90 cause it was auto setting to 100, but no go. Also tested older istat versions but all read the same temps. Does anyone got any ideas? Thx Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581073 Share on other sites More sharing options...
FKA Posted November 11, 2010 Share Posted November 11, 2010 Hello and thank u vry much for the efforts. Im having some problems reading temps of my Q6600, its showing rly low temperatures, far from what it should be. I've changed the TjMax to 90 cause it was auto setting to 100, but no go. Also tested older istat versions but all read the same temps. Does anyone got any ideas? Thx What temps are you showing here? CPU, HDD, GPU ? D Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581128 Share on other sites More sharing options...
xavinoiz Posted November 11, 2010 Share Posted November 11, 2010 What temps are you showing here? CPU, HDD, GPU ? D Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581194 Share on other sites More sharing options...
kozlek Posted November 11, 2010 Author Share Posted November 11, 2010 Hello and thank u vry much for the efforts. Im having some problems reading temps of my Q6600, its showing rly low temperatures, far from what it should be. I've changed the TjMax to 90 cause it was auto setting to 100, but no go. Also tested older istat versions but all read the same temps. Does anyone got any ideas? Thx I need info about your CPU: model, family etc. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581273 Share on other sites More sharing options...
xavinoiz Posted November 11, 2010 Share Posted November 11, 2010 I need info about your CPU: model, family etc. Hi mozodojo its an Intel Core 2 Quad Q6600, G0 stepping (SLACR). Thx in advance. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581315 Share on other sites More sharing options...
CooSee Posted November 11, 2010 Share Posted November 11, 2010 @ Mozodojo i used your kext before, but after ' MaLd0n's ' great DSDT modifications i'll get problems with the kexts ! with the FakeSMC V. 405 from ProjectOSX ! everything worked, except NvidiaTemps ! Nov 10 02:42:55 localhost kernel[0]: FakeSMC: Opensource SMC device emulator by netkas © 2009Nov 10 02:42:55 localhost kernel[0]: FakeSMC: Modified for plugins support by mozodojo © 2010 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: Idea of FakeSMC plugins and code sample by usr-sse2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: Thanks to slice for help with hardware support code and plugins Nov 10 02:42:55 localhost kernel[0]: FakeSMCDevice: 16 keys added Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key TC0D with handler, type sp78, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key TC1D with handler, type sp78, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key TC2D with handler, type sp78, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key TC3D with handler, type sp78, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key TN0P with handler, type sp78, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key TA0P with handler, type sp78, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key Th0H with handler, type sp78, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key VC0C with handler, type fp2e, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key F0Ac with handler, type fpe2, size 2 Nov 10 02:42:55 localhost kernel[0]: FakeSMC: adding key F1Ac with handler, type fpe2, size 2 is this ( please look at the attachment ) a KextUtility Problem or your kexts, no offence ? CooSee ' Ya CooSeeS_Prob_After_Modified_DSDT.rtf Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581347 Share on other sites More sharing options...
MacKonsti Posted November 11, 2010 Share Posted November 11, 2010 Hello guys, updated to 10.6.5 without major problems, it's just that now I get a warning in NVClockX before it actually detects the graphics card. Is it the packaging in Extensions.mkext or is it the kext itself? Mozodojo, any idea? Nov 12 00:14:42 localhost kernel[0]: FakeSMC: Opensource SMC device emulator by netkas © 2009 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: Modified for plugins support by mozodojo © 2010 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: Idea of FakeSMC plugins and code sample by usr-sse2 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: Thanks to slice for help with hardware support code and plugins Nov 12 00:14:42 localhost kernel[0]: FakeSMCDevice: 16 keys added Nov 12 00:14:42 localhost kernel[0]: IntelThermal: CPU family 0x6, model 0x17, stepping 0xa, cores 4, threads 0 Nov 12 00:14:42 localhost kernel[0]: IntelThermal: CPU Tjmax 100 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key TC0D with handler, type sp78, size 2 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key TC1D with handler, type sp78, size 2 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key TC2D with handler, type sp78, size 2 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key TC3D with handler, type sp78, size 2 Nov 12 00:14:42 localhost kernel[0]: NVClockX: [Warning] no nVidia graphics adapters found Nov 12 00:14:42 localhost kernel[0]: NVClockX: [Error] Nov 12 00:14:42 localhost kernel[0]: IT87x: found ITE IT8718F Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key TN0P with handler, type sp78, size 2 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key TA0P with handler, type sp78, size 2 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key Th0H with handler, type sp78, size 2 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key VC0C with handler, type fp2e, size 2 Nov 12 00:14:42 localhost kernel[0]: FakeSMC: adding key F0Ac with handler, type fpe2, size 2 Nov 12 00:14:42 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete Nov 12 00:14:42 localhost kernel[0]: Not loading kext com.apple.driver.AppleHDAController - not found and kextd not available in early boot. Nov 12 00:14:42 localhost kernel[0]: NVClockX: [Warning] no nVidia graphics adapters found Nov 12 00:14:42 localhost kernel[0]: NVClockX: [Error] Nov 12 00:14:42 localhost kernel[0]: Not loading kext com.apple.iokit.AppleYukon2 - not found and kextd not available in early boot. Nov 12 00:14:42 localhost kernel[0]: NVClockX: Vendor ID: 10de, Device ID: 6e4 Nov 12 00:14:42 localhost kernel[0]: NVClockX: Architecture: 80000 Nov 12 00:14:42 localhost kernel[0]: NVClockX: G98 [GeForce 8400 GS] Nov 12 00:14:42 localhost kernel[0]: NVClockX: Memory mapped successfully Thanks in advance. Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581381 Share on other sites More sharing options...
darylz Posted November 12, 2010 Share Posted November 12, 2010 Mighty Kind If some1 here could look at the dsdt i have made for myself,for the Lg x130,running Snow Leopard 10.6.5,its rare that some1 else has the same net book,i tried and have done all modifications myself by learning and checking around this site and else Any Help HIGHLY APPRECIATED, Thanking U Lg X130 Snow Leo DSDT Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581553 Share on other sites More sharing options...
sparkythewondersquid Posted November 12, 2010 Share Posted November 12, 2010 I get the same readings with or with out these but it doesnt hurt Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1581820 Share on other sites More sharing options...
norman25 Posted November 13, 2010 Share Posted November 13, 2010 thankyou guys working in my asus f3sv hdd, proc and gfx temp Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1582353 Share on other sites More sharing options...
doabit Posted November 13, 2010 Share Posted November 13, 2010 Hi ,i use the last version and still get the errors: Nov 13 15:58:03 localhost kernel[0]: NVClockX: Vendor ID: 10de, Device ID: a34 Nov 13 15:58:03 localhost kernel[0]: NVClockX: Architecture: 800000 Nov 13 15:58:03 localhost kernel[0]: NVClockX: GT216 [GeForce GT 240M] Nov 13 15:58:03 localhost kernel[0]: NVClockX: Memory mapped successfully Nov 13 15:58:03 localhost kernel[0]: Error reading BIOS My notebook is Asus N61 with GT240M. Does anybody know what's the wrong ? Thank you ! Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1582464 Share on other sites More sharing options...
CooSee Posted November 13, 2010 Share Posted November 13, 2010 @ Mozodojo i used your kext before, but after ' MaLd0n's ' great DSDT modifications i'll get problems with the kexts ! with the FakeSMC V. 405 from ProjectOSX ! everything worked, except NvidiaTemps ! is this ( please look at the attachment ) a KextUtility Problem or your kexts, no offence ? CooSee ' Ya please forget what i mention before, it was a ' KextUtility ' Problem ! now, using your current kexts, but there's a little problem with ' NVClockX.kext ', please look at the attachment. i've never get Nvidia temps, whatever Version i use, yours or any other ! THX CooSee ' Ya CooSeeS_Kernel.log.rtf Link to comment https://www.insanelymac.com/forum/topic/234452-hwsensors-project/page/9/#findComment-1582867 Share on other sites More sharing options...
Recommended Posts