Jump to content

Search the Community: Showing results for tags 'FakeSMC'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 11 results

  1. This is the guide how to make monitoring of hardware parameters (temperatures, fan speeds, voltages etc) using DSDT programming. The method invented by me with THeKiNG presence and improved by Kozlek. Prerequisites There is FakeSMC plugin named ACPImonitor in my branch or renamed to ACPISensors in kozlek's branch. They are the same. HWMonitor or other monitoring application: iStat, K-Stat-i, ... How it works. HWMonitor or other software make a request for known SMC key, for example TA0P (ambient temperature), every 1 seconds. The request catched by FakeSMC which knows that the key registered by ACPImonitor plugin. This plugin knows that the value for the key must be read from ACPI device "monitor" by method "TCRR" and make a request to AppleACPIPlatform for evaluate this method. AppleACPIPlatform interpretates AML codes written into DSDT, finds the method and calculates the value using hardware access. The value return back to ACPImonitor -> FakeSMC -> AppleSMC -> HWMonitor which shows the "temperature". The kext ACPImonitor will not work OOB. It will work only with DSDT patches for the usage. Simple example DSDT. Device (FSAM) { Name (_HID, EisaId ("APP0111")) Name (_CID, "monitor") Name (TCRK, Zero) Method (TCRR, 0, NotSerialized) { Return (TCRK) } Method (TCRW, 1, NotSerialized) { Store (Arg0, TCRK) Return (TCRK) } Method (TCPP, 1, NotSerialized) { Store (\_TZ.THM._TMP (), Local0) Return (Local0) } } You have to create new device. It must have Name (_CID, "monitor") This is the key for ACPImonitor attached to it. Then see Method (TCRR,0, NotSerialized) mentioned above. It will return a value or variable TCRK. In this demo I made a method TCRW which will fill the variable TCRK from SMC key. The I have to make correspondence ACPI_methodSMC_key in ACPImonitor.kext/info.plist I can write values to the SMC key TA1P ./SMC_util3 -kTA1P -w28 and see the value 28 appears in HWMonitor as "Ambient temperature" Value conversions must be provided in DSDT. Predefined keys ACPI SMC Name TCPU Th0H CPU heatsink TSYS TN0P Northbridge temperature TDIM Tm0P DIMM temperature TAMB TA0P Ambient TCPP TC0P CPU proximity VCPU VC0C CPU voltage VMEM VM0R DIMM voltage ACDC ACIN, ACEN Presence of AC power FAN0 - FAN9 for FAN speed FTN0 -FTN9 for FAN rotation time In the case of FAN reading we also want to assign name to them. It is also possible with the Info.plist What to monitor in real DSDT? This is individual. So why the ACPImonitor will not work OOB. See example from my notebook. looking through DSDT I found the follow region. OperationRegion (TMIF, SystemMemory, 0xFF800160, 0x20) Field (TMIF, ByteAcc, Lock, Preserve) { THS0, 8, THS1, 8, THS2, 8, Offset (0x08), FAN1, 8, Offset (0x10), TSP0, 8, TSC0, 8, TSP1, 8, TSC1, 8 } Looks like three temperatures and one FAN. As well I found ThermalZone Scope (_TZ) { ThermalZone (THM) { Method (_CRT, 0, NotSerialized) { Store (\_SB.PCI0.LPCB.WSEC.C2K (\_SB.PCI0.LPCB.WSEC.TSC0), Local0) Return (Local0) } Method (_TMP, 0, NotSerialized) { Store (\_SB.PCI0.LPCB.WSEC.C2K (\_SB.PCI0.LPCB.WSEC.THS0), Local0) Return (Local0) } _CRT - critical temperature _TMP - current temperature _SB.PCI0.LPCB.WSEC.C2K is a method to convert Celsius to Kelvin degrees. So I see that the field THS0 is really CPU temperature. Using ACPImonitor is only way to do monitoring on notebooks because no other methods works and because it usually contains ThermalZone. I know my guide is too short and hope some users shows own examples how to do ACPI monitoring. Note. This method is useful mostly for notebook where temperature and FANs control present in DSDT. For desktops there are plugins like ITE87xx, Winbond, Fintek depending on you LPC chip installed. 10.10.2017 ACPIMonitor version 1.0.3 There is a possibility to define some types and sizes for custom keys <key>keysToAdd</key> <dict> <key>TCRR</key> <string>TA0P-2</string> <key>TCRW</key> <string>TA1P-3</string> <key>MSLD</key> <string>MSLD-1</string> </dict> The number after key name means follow 0 -> "flag", len 1 1 -> "ui8 ", len 1 2 -> "ui16", len 2 3 -> "sp78", len 2 4 -> "ui32", len 4
  2. Hello I am trying to install Mac OS High Sierra on Dell Optiplex 780 (tower) desktop Specs are: Dell Optiplex 780 (tower) 4GB DDR3 Ram Core2Duo Processor ATI Radeon HD5450 512MB I have created Bootable Usb, Clover method, copied kexts, config.plist and DSDT from http://www.insanelymac.com/forum/topic/312656-guide-macos-sierra-1012-dell-optiplex-780-760-755-790-990/and http://www.insanelymac.com/forum/topic/312656-guide-macos-sierra-1012-dell-optiplex-780-760-755-790-990/page-47#entry2484626 I tried using bootflags GraphicsEnabler=Yes/No npci=0x2000 and npci=0x3000 Replaced kexts and used different versions of FakeSMC but no success. My Screen doesnot stuck at DSMOS has arrived.. After this line, 2 or 3 more lines show up very fast and then display is vanished from screen. See panics video here: https://www.facebook.com/groups/hackintosch/permalink/10156304726097446/ Please help..
  3. Where is the find FakeSMC.kext Package for yosemite 10.10. I have see my CPU,GPU and other sensor. Please Attach. Thank's.
  4. First off, this is a really cool site! I really can't wait to dive into learning about how all this works. I like the philosophy of open source, and being able to look at the code I compile. I've spent days trying to read up before posting, but it's a bit overwhelming currently. In the tutorials section, the first pinned post is really fascinating. http://www.insanelymac.com/forum/topic/280756-guide-the-all-in-one-guide-to-vanilla-os-x-including-chameleon-dsdt-for-beginners-updated-for-mavericks/ I'm wondering where to find the source code for the required software and kexts listed in the above tutorial, they mostly all seem binary apps, but I don't know quite what I'm looking at and not exactly sure as some seem a mixture of visable code and app, when I unpackage the folders. I'd like to view and dissect all the code and tools/software required to install os x, otherwise I'm not sure I'd really fully know how this is all put together. I passed on tonymacx86 for that reason, the more I learned about it, the more I realized it's all closed source, and started looking for alternatives. That's when I found this site and was amazed at all the info and brilliance. Seems like the moto of the site is for everything to be open and viewable. Is there a repository I've overlooked, or specific location containing all the source code for the utilities and software?
  5. Hi, I prepared the bootable installer USB following the instructions at the below page http://www.insanelymac.com/forum/files/file/426-el-capitan-mbr-patch When it boots from USB and then it fails with error org.hwsensors.drivers.CPUSensors - library kext org.netkas.driver.FakeSMC not compatible with requested version 1212 Cant load kext org.hwsensors.drivers.CPUSensors - failed to resolve library dependency ​I put the El capital FakeSMC in S/L/E of the USB drive yet same issue. Please help. thanks Sachin
  6. crusher

    FakeSmc.kext Yosemite 10.10

    Version 6.9.1315


    This is new FakeSMC for Yosemite 10.10
  7. Hey everyone, I tried updating FakeSMC.kext (running ######) and just replaced 3.1 with 4.2. First time it booted fine, but on the next boot it just froze at the loading screen. Turns out Lion will only boot if FakeSMC.kext is in a new location, i.e. Extra/Extensions or S/L/E. If I boot my SL drive and just move the file to the other folder Lion will boot, but not if I move the file from within Lion. What should I do? Reinstall ######?
  8. kozlek


    I want to introduce new "old" opensource fakemsc project with hardware monitoring plugins with new GUI utility - HWMonitor. Please, leave requests and issues on project's home on GitHub: https://github.com/kozlek/HWSensors Use GitHab utility or other git tool to clone repository on your computer. Project includes sources, installer and compiled binaries. If you want manually install kexts they are located in "Binaries" folder. Installer package located in "Installer" folder. Project will not be in existence without revolutional SMC emulator (fakesmc) by netkas. Special thanks to slice and user-sse2 for plugins. Big part of this project based on OpenHardwareMonitor opensource project by Michael Möller. About values modifiers in SuperIOSensors (work for all inputs, not only voltages): http://www.insanelym...dpost&p=1808223 Short description how to get gain values for different voltages (post 264): http://www.insanelym...dpost&p=1809869
  9. Hello, I'm stuck at "Waiting for DSMOS..." after (nearly) successful installation of Snow Leopard with iAtkos S3. I tried to update "FakeSMC.kext", delete "Don't Steal Mac OS.kext" or use "GraphicsEnabler=No", but can't see any "DSMOS has arrived." I am playing with the ethernet cable pluging and unpluging it for checking if the kernel isn't freezed ("Link down", "Link up"...) The system already booted but only once (I waited for about 2 hours ). Thanks for help PS : I am on an Asus P5LD2-VM with Core 2 Duo.
  10. For the most part I've had a 100% working build since 10.8.2. I've done every point update and nothing has broken until now. (Well except iMessage, but we know that's a different story) First my build - Chimera 4.1.0 Gigabyte GA-Z77X-UD5H (F14 bios) 3770K @ 4.5GHz Gigabyte GeForce GTX 670 2GB 32GB 1600MHz RAM OC to 1867MHz 256GB Samsung 840 Pro In the past I've never had an issue with all of my system stats showing up in HWMonitor or iStat Menus so long as FakeSMC Plugins are installed. My CPU has always reported at the correct frequency under HWMonitor and iStat, and my RAM showed up as the correct frequency in "About this Mac". However as soon as I updated to 10.10.3, this was no longer the case. HWmonitor and iStat show my CPU running at 3.46GHz (stock clock for the 3770K), and "About this Mac" shows my RAM as running at 0 MHz. All my other stats show up fine. At first I thought maybe my OC got wiped out somehow, so I booted into the bios and they're still there. So I booted up Windows 8.1 to double-check what frequencies it's detecting and it reports them correctly at 4.5GHz for the CPU and 1867MHz for the RAM. So I think my OC is still in tact. Although even if it was wiped out... that wouldn't explain the RAM reporting at 0 MHz. On the surface I think this is just a cosmetic issue, however my concern is that maybe it's not... maybe my CPU is running at 3.5GHz and not 4.5GHz in 10.10.3, which is quite a huge performance difference and more of a legitimate concern. However even if it is just cosmetic I'd still like to uncover the cause of this. FakeSMC and the 4 FakeSMC plugins are all loaded according to System Information, and they're all running the latest versions (1364). HWMonitor and iStat Menus are also fully updated. Booting with Chimera 4.1.0. Is anyone having similar issues? Anyone got any suggestions on where I can start to try to solve this issue? Thanks guys edit: So now I have reason to believe this isn't just a cosmetic issue. I just ran Geekbench and I'm only getting 13925 - http://browser.primatelabs.com/geekbench2/view/2552061 Previously whenever I ran Geekbench I'd get between 16500 and 17000. So I think my CPU actually is running at stock clocks... ugh
  11. Olá pessoal Uma boa configuração em uma hack pode deixa-lo muito estável e eliminar muita dor de cabeça e essa configuração começam pelo bootloader. Instalando o Chameleon Temos que ter em mente que uma versão mais atualizada do Chameleon é sempre a melhor, pois a cada atualização bugs são corrigidos e novos hardwares suportados. CPUs Haswell estava encontrando diversos problemas em versões anteriores do Chameleon, um exemplo: o busratio dos CPUs Haswell não estavam sendo ajustados pelo Chameleon, e ajustar o busratio automaticamente entre outras coisas que ficam em background é um trabalho do bootloader para um maior conforto para nós. Graças ao esforço e a agilidade dos desenvolvedores esse problema foi corrigido. Então por favor faça o download da versão mais recente do Chameleon: http://www.insanelymac.com/forum/files/download/59-chameleon-22-svn/ Você pode instalar o Chameleon de duas formas: Através dos Binários ou através do Instalador(.pkg)... Aqui eu não vou me aprofundar na instalação manual pelos binários, pois acho algo dispensável, mas quem quiser aqui tem um guia. Crédito ao c0rk007hck O app Chameleon Wizard também realiza esse tipo de instalação de forma mais confortável, o problema é saber qual arquivo de boot é o mais correto para seu CPU e ao escolher um arquivo errado, você ficará incapaz de bootar Por isso eu recomendo a instalação via Instalado(.pkg) que agiliza todo o processo automaticamente e evita muita dor de cabeça. Configurando o Chameleon Após instalar o Chameleon do jeito que você preferir... eu prefiro pkg Você já pode iniciar a configuração dele. No geral 2 arquivos principais regem a configuração do Chameleon: org.chameleon.boot.plist: arquivo de configuração que comanda o Chameleon, é nesse arquivo que você vai especificar o que o Chameleon vai ativar e como ele vai proceder antes,durante e depois do boot. Cuidado para não ativar coisas desnecessárias e bagunçar a configuração SMbios: Esse arquivo é indispensável, agiliza a interface entre a Bios e a arquitetura X86, permitindo a instrumentação de informações genéricas, tais como número serial e outras informações que apenas um Apple Computer tem. Sem uma SMbios decente não poderíamos iniciar nossos sistemas, pois o OSX procura por um número serial Apple válido antes de iniciar o sistema. Podemos criar esses dois arquivos com o app Chameleon Wizard, que nos permite cria-los de forma confortável, download do app: http://dl.dropbox.com/u/7085278/Chameleon_Installer/download.html obrigado janek202 Versões mais recentes desse app trazem novas SMbios e mais opções de configuração. Importante: Escolha uma SMbios que seja o mais próximo possivel do seu hardware, se não o gerenciamento de energia não vai funcionar... se não souber qual usar procure no google por uma SMbios compativel para você ou faça testes... Ajustes Finais Os ajustes finais são para auxiliar na configuração do Chameleon, a única kext que é obrigatoriamente necessária é a FakeSMC . Faça o download dela que vem junto com o app HWMonitor que é muito usável. Instale a kext na pasta S/L/E com ajuda do app Kext Wizard. O resto das configurações vão depender do seu hardware, tal como tipo de mobo, chipset, socket... leitura é sempre muito bom para resolver seus problemas Visão Geral Instale a versão mais recente do Chameleon Crie os 2 arquivos principais: *org.chameleon.boot.plist *SMbios Instale a FakeSMC que é a única kext obrigatória Configure o resto do seu sistema de acordo com o seu hardware. ------------------------------------------------------------------------------------------------------------------------- Bônus: Todos as possíveis opções de boot para o Chameleon: http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/ Obrigado p.H pelo link. Esse guia foi um trabalho meu, mas acima de tudo é um trabalho de todos os desenvolvedores dessas incríveis ferramentas que nos ajudam a muito tempo a tornar nossos PCs um hack. Créditos: Voodoo Project, Chameleon Team, janek202, netkas e muitos outros...