DarwinX Posted November 2, 2010 Share Posted November 2, 2010 Litte Offtopic:Why are the 10.5 builds much bigger (double sized) ? Thanks The 10.6.x are actually larger (2x) than the 10.5.x, no? I believe it is due to the Snow Leopard being a x64 system. Link to comment Share on other sites More sharing options...
h.M.M Posted November 2, 2010 Share Posted November 2, 2010 @The Real Deal: thanks 3.01 works great. ^^ Just a think I thought about is there any command I can use to output all this information in the Terminal? Link to comment Share on other sites More sharing options...
mitch_de Posted November 2, 2010 Share Posted November 2, 2010 The 10.6.x are actually larger (2x) than the 10.5.x, no? I believe it is due to the Snow Leopard being a x64 system. YEP, thats it. 10.6 is bigger as 10.5 .kexts (i wrote opposite by failure). 64 Bit seems to be the reason. Link to comment Share on other sites More sharing options...
The Real Deal Posted November 4, 2010 Share Posted November 4, 2010 For my information, are QPI VTT and DRAM voltages, implementable values? Link to comment Share on other sites More sharing options...
kozlek Posted November 4, 2010 Author Share Posted November 4, 2010 For my information, are QPI VTT and DRAM voltages, implementable values? Maybe, if Apple's SMC has keys for these voltages. Anyway it's possible to implement additional voltage readings. Not sure if SuperIO chips supports VTT voltages but DIMM I could see in everest. Link to comment Share on other sites More sharing options...
chuuey Posted November 5, 2010 Share Posted November 5, 2010 nice, however what if i don't really care about any monitoring, is this version more compatible with hardware etc than the original netkas 2.5 version? Is there any point using these newer versions and can i do it without the monitoring plugins? Link to comment Share on other sites More sharing options...
kozlek Posted November 5, 2010 Author Share Posted November 5, 2010 Test it and say to us is it better or not. The only difference from netkas release is various SMC key types support and plugins interface. In general I did not see any difference on how the system works. Link to comment Share on other sites More sharing options...
chuuey Posted November 5, 2010 Share Posted November 5, 2010 all right, cheers Link to comment Share on other sites More sharing options...
FKA Posted November 5, 2010 Share Posted November 5, 2010 Hi Mozodojo Thanks so much for your work! I'm not getting fan monitoring anymore with this latest build? FakeSMC: Opensource SMC device emulator by netkas © 2009 FakeSMC: Modified for plugins support by mozodojo © 2010 FakeSMC: Idea of FakeSMC plugins and code sample by usr-sse2 FakeSMC: Thanks to slice for help with hardware support code and plugins FakeSMCDevice: 16 keys added IntelThermal: CPU family 0x6, model 0x17, stepping 0x7, cores 4, threads 0 IntelThermal: CPU Tjmax 100 FakeSMC: adding key TC0D with handler, type sp78, size 2 FakeSMC: adding key TC1D with handler, type sp78, size 2 FakeSMC: adding key TC2D with handler, type sp78, size 2 FakeSMC: adding key TC3D with handler, type sp78, size 2 AppleIntelCPUPowerManagement: initialization completeVoodooMonitor: © 2009 Mojodojo, All Rights Reserved. Based on VoodooPower code by superhai. Special thanks to markswell for cpuid utilities. FireWire runtime power conservation disabled. (2) FireWire (OHCI) VendorID 1106 ID 3403 PCI now active, GUID xxxxxxxxxxxxxx; max speed s400. W836x: found Winbond W83667HG FakeSMC: adding key Th0H with handler, type sp78, size 2 FakeSMC: adding key TN0P with handler, type sp78, size 2 FakeSMC: adding key VC0C with handler, type fp2e, size 2 mbinit: done (64 MB memory set for mbuf pool) EDIT - just to confirm have corrected key for my Mac model (iMac9,1) And this is what I get from Everest: --------[ Sensor ]------------------------------------------------------------------------------------------------------ Sensor Properties: Sensor Type Winbond W83667HG (ISA 290h) GPU Sensor Type Diode (ATI-Diode) Motherboard Name Asus P5Q / P5Q3 / P5QL Series Chassis Intrusion Detected No Temperatures: Motherboard 20 °C (68 °F) CPU 38 °C (100 °F) CPU #1 / Core #1 50 °C (122 °F) CPU #1 / Core #2 49 °C (120 °F) CPU #1 / Core #3 51 °C (124 °F) CPU #1 / Core #4 52 °C (126 °F) GPU Diode (DispIO) 44 °C (111 °F) GPU Diode (MemIO) 48 °C (118 °F) GPU Diode (Shader) 50 °C (122 °F) ExcelStor Technology J9250S 29 °C (84 °F) Hitachi HDT725025VLA380 38 °C (100 °F) SAMSUNG HD321KJ 28 °C (82 °F) SAMSUNG HD322HJ 22 °C (72 °F) Cooling Fans: CPU 917 RPM Chassis #2 1854 RPM GPU 35% Voltage Values: CPU Core 1.25 V +3.3 V 3.31 V +5 V 5.02 V +12 V 12.10 V +5 V Standby 5.14 V Current Values: CPU 19.53 A Power Values: CPU 19.56 W Debug Info F FF 5C FF / 5B FF Debug Info T 20 38 43 / 00 Debug Info V 9C D8 D1 CF D1 FF 58 (03) Debug Info I C1 A513 Cheers D Link to comment Share on other sites More sharing options...
Eps Posted November 6, 2010 Share Posted November 6, 2010 It seems that my snow leopard cannot load 2010-11-06's compiled binaries. Link to comment Share on other sites More sharing options...
FKA Posted November 6, 2010 Share Posted November 6, 2010 Hi Mozodojo Thanks so much for your work! I'm not getting fan monitoring anymore with this latest build? Solved by changing W836x.kext info.plist <key>FANINLIMIT</key> <integer>0</integer> to <key>FANINLIMIT</key> <integer>4</integer> Bit odd to default it to 0 ?? Or even better: with <key>FANIN0</key> <string></string> <key>FANIN1</key> <string>Radiator FAN</string> <key>FANIN2</key> <string></string> <key>FANIN3</key> <string>Water Pump</string> <key>FANIN4</key> <string></string> <key>FANINLIMIT</key> <integer>4</integer> Very nice. Thanks a lot again Cheers D Link to comment Share on other sites More sharing options...
edgar87 Posted November 7, 2010 Share Posted November 7, 2010 I can't boot either with the latest nightly Link to comment Share on other sites More sharing options...
Carstiman Posted November 7, 2010 Share Posted November 7, 2010 It seems that my snow leopard cannot load 2010-11-06's compiled binaries. for me too. kxld[org.netkas.FakeSMC]: The following symbols are unresolved for this kext: kxld[org.netkas.FakeSMC]: __ZN10FakeSMCKey10setHandlerEP9IOService Can't load kext org.netkas.FakeSMC - link failed. Failed to load executable for kext org.netkas.FakeSMC. Kext org.netkas.FakeSMC failed to load (0xdc008016). Dependency org.netkas.FakeSMC of kext org.mozodojo.IntelThermal failed to load. Kext org.mozodojo.IntelThermal failed to load (0xdc008015). Failed to load kext org.mozodojo.IntelThermal (error 0xdc008015). Kext org.usrsse2.NVClockX - library kext org.netkas.FakeSMC not found. Can't load kext org.usrsse2.NVClockX - failed to resolve library dependencies. Kext org.usrsse2.NVClockX failed to load (0xdc00800e). Failed to load kext org.usrsse2.NVClockX (error 0xdc00800e). Kext org.mozodojo.SuperIOFamily - library kext org.netkas.FakeSMC not found. Can't load kext org.mozodojo.W836x - failed to resolve library dependencies. Kext org.mozodojo.W836x failed to load (0xdc00800e). Failed to load kext org.mozodojo.W836x (error 0xdc00800e). Couldn't alloc class "IntelThermal" Couldn't alloc class "NVClockX" Couldn't alloc class "W836x" Link to comment Share on other sites More sharing options...
FKA Posted November 7, 2010 Share Posted November 7, 2010 Same here with current SL compiled. I'm using previous build from 22-10-2010. D Link to comment Share on other sites More sharing options...
aschar1 Posted November 7, 2010 Share Posted November 7, 2010 Same here with current SL compiled.I'm using previous build from 22-10-2010. D same here - version from 22 th oct works great - the new nvclock changes doesnt load the whole {censored} - no kp same here - version from 22 th oct works great - the new nvclock changes doesnt load the whole {censored} - no kp new version posted some minutes ago with the fakesmc kext not loading fix results in kp Link to comment Share on other sites More sharing options...
Eps Posted November 7, 2010 Share Posted November 7, 2010 same here - version from 22 th oct works great - the new nvclock changes doesnt load the whole {censored} - no kp new version posted some minutes ago with the fakesmc kext not loading fix results in kp Me,too. FakeSMC results in a AppleSMC kp. Link to comment Share on other sites More sharing options...
stefano.85 Posted November 7, 2010 Share Posted November 7, 2010 for me too. kxld[org.netkas.FakeSMC]: The following symbols are unresolved for this kext: kxld[org.netkas.FakeSMC]: __ZN10FakeSMCKey10setHandlerEP9IOService Can't load kext org.netkas.FakeSMC - link failed. Failed to load executable for kext org.netkas.FakeSMC. Kext org.netkas.FakeSMC failed to load (0xdc008016). Dependency org.netkas.FakeSMC of kext org.mozodojo.IntelThermal failed to load. Kext org.mozodojo.IntelThermal failed to load (0xdc008015). Failed to load kext org.mozodojo.IntelThermal (error 0xdc008015). Kext org.usrsse2.NVClockX - library kext org.netkas.FakeSMC not found. Can't load kext org.usrsse2.NVClockX - failed to resolve library dependencies. Kext org.usrsse2.NVClockX failed to load (0xdc00800e). Failed to load kext org.usrsse2.NVClockX (error 0xdc00800e). Kext org.mozodojo.SuperIOFamily - library kext org.netkas.FakeSMC not found. Can't load kext org.mozodojo.W836x - failed to resolve library dependencies. Kext org.mozodojo.W836x failed to load (0xdc00800e). Failed to load kext org.mozodojo.W836x (error 0xdc00800e). Couldn't alloc class "IntelThermal" Couldn't alloc class "NVClockX" Couldn't alloc class "W836x" same here... and same errors while boot... 22th version works fine... Link to comment Share on other sites More sharing options...
kozlek Posted November 7, 2010 Author Share Posted November 7, 2010 Bit odd to default it to 0 ?? Value 0 means not to override default hardcoded value. I've got default values from the datasheets. If you think default value is wrong you could override it. Im not a senior developer. I don't want to make second everest. My drivers sometimes not working properly oob so you need to configure it manually. Link to comment Share on other sites More sharing options...
Zodiac Posted November 7, 2010 Share Posted November 7, 2010 iStat Menus showing wrong CPU voltage.. any clues ? Link to comment Share on other sites More sharing options...
FKA Posted November 7, 2010 Share Posted November 7, 2010 Value 0 means not to override default hardcoded value. I've got default values from the datasheets. If you think default value is wrong you could override it. Im not a senior developer. I don't want to make second everest. My drivers sometimes not working properly oob so you need to configure it manually. I knew it would be for some reason I didn't understand LOL. and I'm more than happy to have to tweak things a wee bit D Link to comment Share on other sites More sharing options...
The Real Deal Posted November 7, 2010 Share Posted November 7, 2010 iStat Menus showing wrong CPU voltage.. any clues ? I have mentioned it some days ago. We're in the same boat. Link to comment Share on other sites More sharing options...
Carstiman Posted November 7, 2010 Share Posted November 7, 2010 fake smc from 07.10. works again :censored2: seems faster to me Link to comment Share on other sites More sharing options...
ileikcaek Posted November 8, 2010 Share Posted November 8, 2010 Thank you for this. I have the kexts installed in E/E but I had to get rid of the NVClockX one as it was causing random KP's when booting. without it OS X boots a lot quicker with these kexts, a huge improvement, it no longer stalls for a while waiting for DSMOS. I have all temp/RPM sensors showing but no Voltage and obviously no GPU stuff due to the NVClockX not being present. It is more than I had before with FakeSMC 2.5 so I cannot complain, Here's to the future of this fantastic project Link to comment Share on other sites More sharing options...
kozlek Posted November 8, 2010 Author Share Posted November 8, 2010 iStat Menus showing wrong CPU voltage.. any clues ? What does it means? How do you know the voltage is right or wrong? Link to comment Share on other sites More sharing options...
MacUser2525 Posted November 8, 2010 Share Posted November 8, 2010 What does it means? How do you know the voltage is right or wrong? 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. Link to comment Share on other sites More sharing options...
Recommended Posts