Jump to content

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



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Categories

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 28 results

  1. Olá Pessoal GUIA ATUALIZADO - Foi adicionado patch XCPM para 10.10 Antes de tudo é muito bom que tenhamos uma versão atualizada do Chameleon, então por favor pegue essa versão mais atualizada bem aqui no tópico oficial: http://www.insanelymac.com/forum/files/download/59-chameleon-22-svn/ Desde 10.7.4 para os CPUs SandyBridger e IvyBridger os P e C States - que são responsáveis pelo bom funcionamento de energia - não são mais fornecidos pelo Chameleon, ou seja, somente ativar GeneratePStates e GenerateCStates não adiatam mais... Uma saída rápida é a utilização da kext NullCPUPowermanagement, mas eu não recomendo a utilização continua dessa kext, pois ela desabilita a kext AppleIntelCPUPowermanagement que é pelo gerenciamento de energia. A solução mais viável e recomendada que lhe proporcionará um gerenciamento de energia bom, é a criação de uma SSDT que irá contem todos os P-States e C-States. Passo-a-Passo Criando a SSDT Crie sua SSDT baseada no script do Pike R. Alpha Rode no terminal esses comandos curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh chmod +x ssdtPRGen.sh ./ssdtPRGen.sh Após roda-lo você precisa colocar a Frequência Máxima e o Máximo TDP do seu CPU... veja essas infos sobre seu CPU aqui: http://ark.intel.com/ Esse é um exemplo de um i7 2600 que possui 3800Mhz(3,8Ghz) de frequencia maxima e 95 de TDP sudo ./ssdtPRGen.sh 3800 95 Coloque a SSDT na pasta Extra e renomeie ssdt_pr para SSDT Obs: Alguns CPUs já são auto-detectados pelo script, simplesmente o script já detecta a frequência máxima e o TDP, então se simplesmente após rodar o primeiro comando você for avisado para salvar a SSDT na pasta Extra(não pedindo para digitar sua max frequenc. e TDP como o guia manda), não se preocupe com isso, apenas confirme, pois o script já detectou tudo e criou sua SSDT e no momento já está pedindo para salvar o arquivo. Patch na AppleIntelCPUPowermanagement Nas mobos mais antigas é necessário patchear a kext AICPUPM para possibilitar a gravação na Bios, caso contrário você receberá um Kernel Panic por não poder gravar na Bios... Faça o download do patch:AICPUPMpatch Rode no terminal cd ~/Downloads/AICPMPatch Apenas encontre e liste... sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement Depois dê patch no wrmsr para possibilitar a gravação na Bios sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement --patch Após isso é necessário atualizar o cache sudo touch /System/Library/Extensions Kernel Patch para Haswell CPU(Kernel XCPM) Desde a versão 10.8.5 um novo kernel foi implementado no OSX, ele se chamada XNU kernel(Xnu Cpu Power Management(xcpm)) Esse kernel tem o gerenciamento de energia movido para dentro dele, no passado usávamos a kext AppleIntelCPUPowermanagement para o controle do gerenciamento de energia e algumas Bios eram travadas, ou seja, não era permitido gravar informações nela, por isso foi criado o patch para a kext AICPUPM para solucionar esse problema(veja acima como patchear a kext AICPUPM Mas com o gerenciamento movido para dentro do kernel(XNU kernel)a kext AICPUPM não é mais carregada e por isso o mesmo erro que estávamos tendo no passado com a kext AICPUPM(Kernel Panic)estamos tendo agora com o XNU kernel em alguns modelos de CPU haswell(principalmente modelos portáteis, alguns modelos Desktop não precisam de patch) Para solucionar esse problema é necessário aplicar um patch no kernel. Para 10.10 você precisa abrir o terminal e digitar: cd /Volumes/Nome do seu HDD/System/Library/Kernels/ Note que em 10.10 o diretório do kernel foi alterado. Copie esse código perl, isso é para a versão 10.10, coloque linha por linha sudo perl -pi -e 's|\xe2\x00\x00\x00\x02\x00\x00\x00|\x00\x00\x00\x00\x02\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x4c\x00\x00\x00|\x00\x00\x00\x00\x4c\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x90\x01\x00\x00|\x00\x00\x00\x00\x90\x01\x00\x00|g' kernel Para 10.9.x e 10.8.5 você precisa rodar esse comando no terminal: cd /Volumes/Nome do seu HDD/ Agora, copie esse código perl se você usa as versão 10.9.x sudo perl -pi -e 's|\x74\x6c(\x48\x83\xc7\x28\x90\x8b\x05..\x5e\x00\x85\x47\xdc)\x74\x54(\x8b\x4f\xd8\x45\x85\xc0\x74\x08\x44\x39\xc1\x44\x89\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x99(\x5d\xc3)\x90{7}|\x74\x73${1}\x74\x5b${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x92${5}|g' mach_kernel ou esse outro código perl se você usa a versão 10.8.5 sudo perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g' mach_kernel Por último atualize o cache sudo touch /System/Library/Extensions Pronto! Kernel patcheado e o XCPM está trabalhando perfeitamente em seu CPU haswell OBS1: XCPM só trabalha nos CPUs Ivy Bridger e Haswell, sendo que, os CPUs Ivy Bridger utilizam por padrão o gerenciamento de energia dado pela kext AICPUPM, para usar o gerenciamento de energia dado pelo kernel XCPM é necessário ativar essa flag(Chameleon)/argumento(Clover): -xcpm Os CPUs Haswell utilizam o gerenciamento XCPM por padrão e não mudam. O gerenciamento XCPM não suporta os CPUs Sandy Bridger, então quem usa SB pode ficar tranquilo acerca disso. OBS2: Mesmo patcheando o kernel XCPM, você irá precisar patchear a kext AICPUPM, caso a sua BIOS seja trancada para gravação. OBS3: Caso você não tenha nenhum problema com KP, não é necessário patchear o kernel, mas, em alguns casos, patchear o kernel ajudou em adicionar alguns states de energia. OBS4: O Clover bootloader já tem o patch embutido, você só precisa editar o config.plist para habilitar o patch <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> </dict> Então, se você habilitar isso no Clover não é necessario patchear o kernel, porque o Clover irá fazer isso para você Ajustes finais Para fazer com que o Chameleon reconheça a sua SSDT, habilite DropSSDT no org.chameleon <key>DropSSDT</key> <string>Yes</string> Não instale a NullCPUPM e não habilite P e C States no org.chameleon... Não se esqueçam de futuramente criar uma DSDT para auxiliar no gerenciamento de energia OBS: Para quem está com dificuldades com gerenciamento de energia... dê uma olhada para ver se as kexts: X86PlatformPlugin, ACPI_SMC_PlatformPlugin, AppleLPC estão carregadas, rode kextstat no terminal para ver... Boa sorte para todos que tentarem este guia, eu somente juntei tudo em um único tutorial para facilitar a compreensão sobre gerenciamento de energia em Sandy e Ivy Bridger, mas todos os créditos vão para os respectivos donos das ferramentas maravilhosas que possibilitam o gerenciamento de energia em nossas CPUs Créditos: Pike R. Alpha flAked RevoGirl ReHabMan: http://www.insanelymac.com/forum/topic/302376-guide-patching-the-kernel-for-haswell-cpus-xcpm-early-reboot/
  2. phillmont22900

    Generating DSDT to use on Hackintosh

    Howdy everyone! This guide is perfect for you guys that are going to install Hackintosh (in this guide, I would say "Mac") on a PC/notebook that is not really popular and difficult to find out the right DSDT for your PC. Requirements: - Windows 7 or later installed on your PC directly, by "directly" I mean full-install, not VM. - Mac (of course). - MaciASL or DSDT Editor or EvOSx86's DSDTFixer (may preferable). - AIDA64 for Windows. (I would suggest AIDA64 Extreme) Note: AIDA64 is currently on version 4. Look out for version 3, because ACPI Tools has been removed on version 4 and later. The steps: 1. Get to Windows. Run AIDA64. 2. Right-click the AIDA64's status bar and click on "ACPI Tools". 3. Another new window will be opened. Now click "Save DSDT". Note: If you want to save SSDT, XSDT, or other, you may want to click "Save Table" and choose. 4. New file will be saved onto your computer. It should be "acpi_dsdt.bin". 5. Rename the new file to "DSDT.aml". 6. Boot up to your Mac. 7. Open DSDT.aml using MaciASL (or what you use). 8. Click "Compile" and look for errors. There should not be any errors. 9. If there is no errors, continue and save the DSDT. If you want to add some code, add it up and Compile again. 10. Once your DSDT.aml is saved without errors, copy it to "/Extra" and reboot. 11. Congratulations! Your Mac should now boot using the right DSDT. Troubleshooting If you get Kernel Panics on reboot, simply use DSDT=NULL boot flags on the bootloader and boot up. Once Mac boots up without DSDT, check the problems using MaciASL (or what you use). Good luck!
  3. Version 20150515

    1,926 downloads

    Intel ACPI tools. The NEW version 20150515 compiled by me from original sources. Use iasl compiler with your DSDTSE or another editor. To update your DSDTSE, simply right click on DSDTSE --> Show contents, drag'n'drop iasl into --> Contents --> Resources. Another editors have mostly the same way. Or another way by Terminal: drag iasl on Terminal window (bash), (press Return (Enter) to see all keys) -> write some keys, drag Aml/Dsl file to compile/decompile. This way you can more deeply configure/clean your DSDT during compile (especially with -w3 key), find more warnings and junk code, empty / uninitialized methods. Have a nice day good compilings! For MaciASL simply drag iasl to Contents --> MacOS and rename it to iasl5 (or iasl51 for MaciASL 1.3 b262+ builds) Major tools and utilities: iASL - ACPI Source Language Compiler, ACPI Table Compiler, and AML Disassembler AcpiExec - Load ACPI tables and execute control methods from user space AcpiDump - Obtain system ACPI tables and save in ASCII hex format AcpiXtract - Extract binary ACPI tables from an ASCII acpidump AcpiHelp - Help utility for ASL operators, AML opcodes, and ACPI Predefined Names Miscellaneous utilities: AcpiNames - Example utility that loads and displays the ACPI namespace AcpiSrc - Convert ACPICA code to Linux format AcpiBin - Miscellaneous manipulation of binary ACPI tables Intel ACPI тулзы версии 20150515 скомпилированы мною из оригинальных сырцов. Для использования с ДСДТ редактором. Инсталим сюда: Открываем правой кнопкой по "любимому" редактору --> показать содержимое пакета --> Contents --> Resources --> перетаскиваем драг-н-дропом на эту папку файл iasl, на замену соглашаемся. Имеем свежий компайлер. Для MaciASL перетаскиваем в подпапку Contents --> MacOS и даем ему имя iasl5 (или iasl51 для современных билдов MaciASL 1.3 b262+ ) ACPISpec ver. 6.0 / ACPI Спецификации 6.0 ACPI Spec ver. 5.1 / ACPI спецификации версии 5.1 ACPISPec ver. 5.1 Errata A / ACPI спецификации 5.1 Исправления А Attension / Внимание :: Simple replacement of iasl compiler (iasl --> iasl5) in MacIASL leads to an empty window Summary, the bottom line shows correctly the number of errors / warnings / remarks, but the screen remains blank and errors addresses hard to find. This is the MacIASL's bug, not the compiler's. Простая замена компайлера iasl (iasl --> iasl5) в MacIASL ведет к пустому выхлопу окна Summary, то есть количество ошибок / предупреждений / ремарок в нижней строке показывает корректно, но окно остается пустым и адреса ошибок найти сложно. Это баг самого MacIASL, а не компилятора. IMPORTANT / ВАЖНО : To have a correctly disassembled DSL file w/o unexpected errors, you need to use the Terminal to decompile AML binaries. If you have a modern platform and more than 1 SSDT in your ACPI, you need to decompile all of them correctly. To decompile only DSDT.aml use -e key (to decompile in legacy ASL code mode you have to add -dl key instead of -d ) : Чтобы получить корректно дизассемблированный DSL файл без непредвиденных ошибок декомпиляции, нужно использовать терминал для декомпиляции бинарников. Если вы владеете современной платформой и среди ACPI таблиц присутствует более 1 SSDT, необходимо их корректно декомпилировать. Чтобы декомпилировать только DSDT, используйте ключ -e: (для распаковки в легаси код ASL вместо ключа -d надо использовать новый ключ -dl ) : New ASL+ decompile: / Декомпайл ASL+: iasl -e SSDT*.aml -d DSDT.aml iasl -e /@full_path@/SSDT*.aml -d /@full_path@/DSDT.aml iasl -da /@full_path@/SSDT*.aml /@full_path@/DSDT.aml Legacy ASL decompile / Декомпайл ASL легаси: iasl -e SSDT*.aml -dl DSDT.aml iasl -e /@full_path@/SSDT*.aml -dl /@full_path@/DSDT.aml iasl -da -dl /@full_path@/SSDT*.aml /@full_path@/DSDT.aml To decompile all DSDT & SSDTs use -da key: Чтобы декомпилировать все DSDT и SSDT таблицы, используйте ключ -da: iasl -da DSDT.aml SSDT*.aml iasl -da /@full_path@/DSDT.aml /@full_path@/SSDT*.aml Also add reference file ref.txt with unresolved External Methods and Argument count for each. Use -fe key: Также можно добавить дополнительный реф.файл ref.txt c перечислением все еще нераспознанных методов и количество Аргументов для каждого. Используйте ключ -fe: External (MDBG, MethodObj, 1) // <<<--- Unresolved Method with designated Arguments count iasl -fe /@full_path@/ref.txt -e /@full_path@/SSDT*.aml -d /@full_path@/DSDT.aml iasl -fe /@full_path@/ref.txt -e /@full_path@/SSDT*.aml -dl /@full_path@/DSDT.aml iasl -fe /@full_path@/ref.txt -da -dl /@full_path@/SSDT*.aml /@full_path@/DSDT.aml And more: if you need to decompile your custom DSDT with your patches, you need to use all of the SSDTs this time too. В дополнение: если вы решили декомпилировать свою кастомную DSDT с примененными патчами, в этом случае также требуется использовать терминал и включить в декомпиляцию все SSDT таблицы. Changelog 20150410:
  4. Happy New Year all! I am attempting to install Sierra 10.12.6 on a rather odd computer, a Microsoft Surface Studio. It is essentially a laptop with a 4.5K screen strapped on. I have the install done, but the internal (or external? I don't know how it is connected) display and the video card are not matching up once I enable the Web drivers. I've attached two sets of files: one without Web drivers being enabled, and a second with Web drivers. Also attached are the dumped ACPI files in origin, as well as the EDID information from Windows with and without the monitor driver being installed, IOregs, complete Clover folders, and various other items. Let me know if you need something else. Without web drivers enabled the built-in display works, but of course has no acceleration. It allows me to select between two valid resolutions (full 4.5K and 2.25K). With web drivers enabled, I get a black screen (NvidiaFixup, plus manual editing of AGDP already done). I can remote in and I see the card as not recognized, and no valid display. I've flailed about a bit and manually added some device properties, EDID, as well as NVCAP, loaded a different ROM, but all have met with no success. Anyone have any ideas on what to try?
  5. Hello everybody, My machine is a HP Pavilion P6230it with the addition of a TP-LINK TG-3468 LAN interface, and I'm running OS X 10.9.3. I'm approaching DSDT and SSDT editing in order to get as many features as possible to work natively without the need of patched kexts of sort. As of my understandment of the practice its two goals are: 1 - To update the code so that it matches the latest iASL compiler syntax and standars. 2 - To modify the names and specifications of listed devices to match the names that the system natively expects to find. Still I can't find an exhaustive list of global or common modifications, providing explanations so that I understand what I'm turning into what and why. For example, I'm trying to get the devices to match those contained into the iMac11,1, which seems to me close enough to my machine. In a previous attempt to edit AGPM.kext to set better fitting thresholds I found that the graphic device is listed as GFX0: Which leads me into thinking that's the name given by Apple to graphic devices at least in this Mac. In my current DSDT the graphic device is also listed as GFX0, does this mean I should leave it as it is for the OS to find it? Am I getting this right? Thanks in advance.
  6. Hi, This is my first time trying to patch a DSDT, and while I like to learn by doing, I want to be safe this time so I would need a bit of help Currently I have sleep problems when I close the notebook I end up with a black screen so I need to reboot. From what little I know/read this is related to the C-states, and since the notebook is new I would like to get the P-states and SSDT patches so to prolong the notebook lifetime. Details on how to properly identify and edit the DSDT in general (Audio,IGPU,P-states,C-states,HPET, etc) is welcome too, so I won't bother you much next time Thanks in advance. /Edit: Added ioreg dsdt.dsl.zip
  7. I have successfully install Mavericks on this laptop but not able to install Battery Manager, Touchpad (NX Pad tried VoodooPS2 kext) and generate correct SSDT. Need experts' help to correct DSDT and SSDT. DarwinDump, SSDT and DSDT using attached http://121ware.com/lavie/x/ i7-3537u (Intel default 2.0Ghz but Mac regconized as 2.5Ghz) HD4000 Wifi (To be replaced 9285) OS Mavericks.
  8. I'm trying to disable my discrete graphics card and the consensus seems to be that it should be disabled through an SSDT, not necessarily in the DSDT itself. So I extracted my DSDT and SSDT's using Ubuntu, added the .aml extension and using maciASL I can't find the area the area that I need to turn off. All of my knowledge I have on this comes from the guides and forum posts I go over, I don't have any prior experience with DSDT's. Here is the most precise guide I can find on the subject, and it specifically states that it's for Radeon cards. Here's the issue: it says to look for \_SB.PCI0.PEG0.PEGP function. I don't have this function anywhere in my SSDT's; most of them look like they're for the processor. I do, however, have SB.PCI0/PEG0/PEGP in my DSDT but it's in subdirectories and not all on one line. I also can't find the _OFF or _ON methods that it states that it would have neither anywhere in my DSDT or in any of my SSDT's. I think that PEGP is definitely something to look at, but there doesn't seem to be anything there that I would need to go forward. Does anyone have any suggestions? I'm using Clover on Yosemite 10.10.5. This is an HP DV6t 6100 i7 + HD3000. My DSDT has already been modified a few times to get brightness, battery, etc.
  9. second ,as you can see, there all lots of kernel: AppleUSBInterface: family specific matching fails. errors in the log sorry for my poor English,but can anyone help with that? I would very appreciate that! Best wishes!!
  10. lilit

    HD4600 SSDT Injection

    Hi there, I am in the process of getting a Haswell hackintosh running. Currently, both 10.8.4 (with 10.8.5 kernel) and 10.9 DP boot, but I have trouble getting integrated graphics to work. While I don't expect it to work in 10.8.4, it should be possible with 10.9. As far as my progress goes, I have extracted the DSDT and 7 SSDTs, recompiled (and fixed) them and Chameleon finds and loads them. And that's exactly where the problem kicks in: even though Chameleon says it loaded the SSDTs, it seemingly did not. How do I know: I modified SSDT-3, which contains the graphics device, but none of the changes appear in ioreg. My first solution was to start merging SSDT-3 with the base DSDT. While it was quite some work, my modifications to the graphics device (which I could do in the DSDT) now show up in ioreg correctly. Consequently, I would now proceed merging the other 6 SSDTs into the DSDT as well. On the other hand, I doubt that this is the proper way to go (let alone error prone). There must be some way to get the SSDTs to be used. As for the boot settings, I only used DropSSDT=Yes .. to my understanding this will drop the firmware SSDTs so my own can be loaded. But I also tried without this and got the same result. Is there a way to get more precise debugging output from Chameleon? Or should I try alternatives like RevoBoot or Clover? Best, lilit PS: On second thought, merging the SSDTs also has its benefit: you can catch and fix more errors. In my case, the SSDT had an external int value declared, which simply did not exist. Instead, it should have been a method taking two arguments. With SSDTs, this stuff remains hidden.
  11. Hello folks! GUIDE UPDATED - Added support for 10.10 XCPM kernel First of all it is very good that we have an updated version of Chameleon, so please take this most updated version right here in the official thread: http://www.insanelym...ameleon-22-svn/ Since 10.7.4 for CPUs and SandyBridger IvyBridger P and C States - that are responsible for the proper functioning of energy - are no longer provided by Chameleon, in others words, only activate GeneratePStates and GenerateCStates doesn't work any more. A quick exit is to use the kext NullCPUPowermanagement, but I don't recommend continued use of this kext because it disables AppleIntelCPUPowermanagement kext which is responsible for power management The most viable and recommended solution that will give to you a good power management is the creation of a SSDT which will contain all P-States and C-States. Step-by-Step Creating the SSDT Create your SSDT based on the script Pike R. Alpha Run these commands in terminal curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh chmod +x ssdtPRGen.sh ./ssdtPRGen.sh After you run it you need to put the Maximum Frequency and Maximum TDP of your CPU ... see these information about your CPU in here: http://ark.intel.com/ This is an example of one i7 2600 that has 3800MHz(3.8 Ghz) of maximum frequency and 95 of TDP sudo ./ssdtPRGen.sh 3800 95 Place the SSDT in Extra folder and rename ssdt_pr for SSDT Note: Some CPUs are auto-detected by the script, the script just now detects the maximum frequency and TDP, so if simply after running the first command you are prompted to save the SSDT in Extra folder(not asking to enter your max frequenc. and TDP as the guide teach),don't worry about it, just to confirm, because the script already detected everything and created the SSDT and the time is already asking to save the file. Patch AppleIntelCPUPowermanagement In older mobos is necessary to patch the kext AICPUPM to enable recording in Bios, otherwise you will get a kernel panic because it can't write to the Bios ... Download the patch: AICPUPMpatch Run in terminal cd ~/Downloads/AICPMPatch Just find and list ... sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement Then give patch in wrmsr to enable recording in Bios sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement --patch After that you need to update the cache sudo touch /System/Library/Extensions Kernel Patch for Haswell CPU(Kernel XCPM) Since version 10.8.5 a new kernel was implemented on OSX, he called XNU kernel(XNU CPU Power Management(xcpm)). This kernel has the power management moved down into it, in past we used AppleIntelCPUPowermanagement kext to control power management and some Bios were lockeds, in others words, were not allowed to write information on it, so the patch was created for kext AICPUPM to solve this problem (see above how to patch the kext AICPUPM). But with the power management moved down into the kernel(XNU kernel) AICPUPM the kext isn't loaded and so the same mistake that we were having in the past with AICPUPM kext(Kernel Panic)are having now with the XNU kernel in some models CPU haswell(mainly in portable models, some Desktop models doesn't need patch) To solve this problem it is necessary to patch the kernel. For 10.10 you need Open the terminal and type: cd /Volumes/Name of your HDD/System/Library/Kernels/ Note that in 10.10 kernel directory was changed. Copy this perl code is for 10.10 version, put line by line sudo perl -pi -e 's|\xe2\x00\x00\x00\x02\x00\x00\x00|\x00\x00\x00\x00\x02\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x4c\x00\x00\x00|\x00\x00\x00\x00\x4c\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x90\x01\x00\x00|\x00\x00\x00\x00\x90\x01\x00\x00|g' kernel For 10.9.x and 10.8.5 you need run this command in terminal: cd /Volumes/Name of your HDD/ Now copy this perl code if you use version 10.9.x sudo perl -pi -e 's|\x74\x6c(\x48\x83\xc7\x28\x90\x8b\x05..\x5e\x00\x85\x47\xdc)\x74\x54(\x8b\x4f\xd8\x45\x85\xc0\x74\x08\x44\x39\xc1\x44\x89\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x99(\x5d\xc3)\x90{7}|\x74\x73${1}\x74\x5b${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x92${5}|g' mach_kernel or that other perl code if you use version 10.8.5 sudo perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g' mach_kernel Finally update the cache sudo touch /System/Library/Extensions Ready! XCPM patched kernel and is working perfectly on your CPU haswell Note1: XCPM only works in Ivy Bridge and Haswell CPUs, and the CPUs Ivy Bridger use by default the power management given by AICPUPM kext, to use the power management provided by the kernel XCPM you must enable this flag(Chameleon)/argument(Clover): -xcpm Haswell CPUs use XCPM management by default and doesn't change.The management XCPM not support CPUs Sandy Bridger, so who uses SB can stay quiet about it. Note2: Even Patching the kernel XCPM, you will need to patch the kext AICPUPM if your BIOS is locked for writing. Note3: If you have no problem with KP, it isn't necessary to patch the kernel, but in some cases, helped to patch the kernel to add some energy states. Note4: Clover bootloader already has this patched built-in, you just need edit config.plist to enableir it <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> </dict> So, if you enable it in Clover isn't necessary patch kernel, because Clover will make this for you Final adjustments To make the Chameleon recognize your SSDT, enable DropSSDT in org.chameleon <key>DropSSDT</key> <string>Yes</string> Don't install the NullCPUPM and don't enable P and C States in org.chameleon ... Don't forget to create a DSDT in future to help the power management Note: For those who are having difficulty with power management ... take a look to see if the kexts: X86PlatformPlugin, ACPI_SMC_PlatformPlugin, AppleLPC are loaded, type kextstat the terminal to see ... Good luck to all who try this guide, I just put it all together in a single tutorial to facilitate the understanding of power management in Sandy and Ivy Bridger, but all credits go to the respective owners of the wonderful tools that enable power management in our CPUs Credit: Pike R. Alpha flaked RevoGirl ReHabMan: http://www.insanelymac.com/forum/topic/302376-guide-patching-the-kernel-for-haswell-cpus-xcpm-early-reboot/
  12. marcosviniciusf17

    Editando erros na SSDT. Ajudem por favor

    Extrai a DSDT E SSDT conforme a guide que usa iasl pelo Ubuntu. Gerei os arquivos .dsl e corrigi os que encontrei solução, porem as SSDTs 0,2 e 3 apresentam erros que não consigo corrigir. Se puderem me ajudar. Agradeço muito. Entre eles estão: Scope (\_SB.PCI0) <<<<<<< Existing object has invalid type for Scope operator (\_SB.PCI0 [untyped]) Code 6117 (Se repete 3 vezes nos arquivos) -------- Package (0x06) <<<<<<< { <<<<<<< 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000, 0x80000000 } Syntax error, unexpected parseop_package Syntax error, unexpected "{" Code 6126 Se repete 8 vezes entre os arquivos) ---------
  13. Hola a tod@s: Hace tiempo que estoy ocioso en el tema hack y con la excusa que empezó el 2018 apelo a uds para solventar algunas dudas en el tema SSDT. Sin ser experto en el tema, descalabro, destripo, pongo a prueba y abuso de mi DSDT sin problemas hasta hoy. Pero… si hablamos de SSDT es otra cosa, me supera. De hecho uso Generate State y Cstate de Clover para no tener ningún SSDT en la carpeta Patched. Para los usb3 uso USB_Series8_Injector.kext modificado para mi placa. http://www.insanelymac.com/forum/topic/308325-guide-1011-full-speed-usb-series-89-keeping-vanilla-sle/page-1 Sin embargo me interesaría hacer un SSDT-UIAC especifico para tal fin. Mi problema viene que cuando intento usarlo en Patched mi equipo no se da por aludido y no hace nada (no corrige nada) Mis dudas: CLOVER 1)¿Podría algún alma caritativa explicarme muy detalladamente que es eso de Sorter Order y como se usa y cuando debo usarlo y cuando no? (A ver si ahí puede estar mi fallo) SSDT 2) Si uso un SSDT como en este caso el SSDT-UIAC ¿debo poner alguna linea especifica en mi DSDT para que se relacione con dicho SSDT? ¿Cuando hay que poner ese tipo de menciones y porque? Creo que para empezar está bien. Luego según entienda/comprenda las respuestas seguiré preguntando. Muchísimas gracias desde ya. Perdonen si no saludé a nadie por Navidad o Año Nuevo pero estoy muy molesto con el gordo Papa Noes pues he descubierto que es un feminista rabioso: DSDT uzmi.zip
  14. Hi all, Thanks to some of the wonderful guides here, I've gotten most of my machine working. One of the things that aren't working is the WiFi module on my motherboard. If I disable the module in the BIOS, everything goes smoothly, but if I enable it, this appears: http://imgur.com/ylYix1I Additional Information: Motherboard: Rampage IV Black Edition CPU: i7-4930k GPU: R9 290X Operating System: OS X Yosemite Beta 3 installed with Clover I've installed the following kexts: AppleIntelE1000e FakeSMC GenericUSBXHCI VoodooTSCSync I've also installed the two SSDT's from rampagedev which are related to my motherboard and my CPU, removing or adding the SSDT's don't appear to affect the panic: SSDT.aml for my Rampage IV Black Edition with AMD Graphics: https://www.dropbox.com/s/p78osq4j5l668gb/SSDT.aml?dl=0 SSDT-1.aml for my 4930k stock CPU: https://www.dropbox.com/s/wjg4ika9prakmey/SSDT-1.aml?dl=0 Please tell me if I can provide more information to help you help me!
  15. hola... Instale en mi Sony vaio vpcf131fm osx yosemite, en medio de haber tenido problemas en el proceso de arranque, al final pude resolverlo, sin embargo tengo problemas con las gráficas y creo también con las conexiones usb del portátil. El portátil tiene integradas una tarjeta de vídeo Nvidia geforce 310m de 512 mb, el problemas es que estoy trabajando como si no tuviera tarjeta y no he logrado encontrar algún kexts que sea compatible con esta tarjeta. Con las conexiones de Internet la verdad no estoy claro, ya que uso un módem que es compatible con cualquier S.O y este es capas de funcionar en linux, windows y mac, sin usar algún tipo de driver o kext para su funcionamiento, pero si tengo problemas con el wifi, porque a como les dije no se que tipo de kext instalar ya que he investigado y no hallo uno que me pueda ayudar con esto. Otro inconveniente que me tiene un poco dudoso, es el asunto de los DSDT y los SSDT, he buscado información acerca de como compilar o de como arreglar eso en mi portátil y la mayor cantidad de información esta totalmente en ingles y la que logro encontrar tiene algunos (5 años) de antigüedad por lo que no me confió para poder trabajarla. Si alguien sabe información acerca de como resolver problemas en mi vaio, se lo agradecería mucho Una información extra es que actualice a la versión 10.0.1 y el sistema arranco igual que recién lo instale. Especificaciones SONY VAIO VPCF131FM CPU intel core i5 480m 2.67 GHz Video Nvidia Geforce 310 southbridge PM55 Network ethernet PCI-E Marvell yukon 88e8057 Network Intel centrino advanced-N 6250 AGN Sonido Realtek ALC275 Por si se necesita mas detalles les adjunto un informe de AIDA64 sobre mi hardware y también el DSDT y el SSDT, aunque sobre este ultimo no estoy seguro, ya que al sacarlo con AIDA me salían varias opciones de este, el que les envió es el ultimo de los que me salio. De antemano, les agradezco. acpi_dsdt.rar acpi_ssdt.rar reporte de hardware.txt
  16. Hey Guys, I use the AMD platform of the computer, but I installed El-Capitan encountered a lot of problems, for example, I cannot use the USB interface, so I have been unable to install the 10.10 version of the above, I have no choice, but to help, hope that the moderator will not delete my post, here is my DSDT and SSDT. Hope it will help me revise modification, makes it possible to use USB on the 10.11, thank you (I know, English is not my these are Baidu Translate with grammatical errors, please excuse) I do not speak English very well, I know that my posts are likely to be deleted at any time, I just want someone to help me modify, my mouse can not be used in El-Capitan! DSDT and SSDT.zip
  17. Version 20150930

    745 downloads

    The NEW version of MaciASL 1.3 b265 / Новая версия MaciASL 1.3 b265 Intel ACPI tools. The NEW version 20150930 compiled by me from original sources. Use iasl compiler with your MaciASL, DSDTSE or another editor (or Terminal). To update your DSDTSE, simply right click on DSDTSE --> Show contents, drag'n'drop iasl into --> Contents --> Resources. Another editors have mostly the same way. For MaciASL simply drag iasl to Contents --> MacOS and rename it to iasl5 (or iasl51 for MaciASL 1.3 b262+ builds) Intel ACPI тулзы. Новая версия 20150930 их скомпилирована мною из оригинальных сырцов. Для использования с ДСДТ редактором MaciASL, DSDTSE или другим (или Терминалом). Инсталим сюда: Открываем правой кнопкой по "любимому" редактору --> показать содержимое пакета --> Contents --> Resources --> перетаскиваем драг-н-дропом на эту папку файл iasl, на замену соглашаемся. Имеем свежий компайлер. Для MaciASL перетаскиваем в подпапку Contents --> MacOS и даем ему имя iasl5 (или iasl51 для современных билдов MaciASL 1.3 b262+ ) Major tools and utilities: iASL - ACPI Source Language Compiler, ACPI Table Compiler, and AML Disassembler AcpiExec - Load ACPI tables and execute control methods from user space AcpiDump - Obtain system ACPI tables and save in ASCII hex format AcpiXtract - Extract binary ACPI tables from an ASCII acpidump AcpiHelp - Help utility for ASL operators, AML opcodes, and ACPI Predefined Names Miscellaneous utilities: AcpiNames - Example utility that loads and displays the ACPI namespace AcpiSrc - Convert ACPICA code to Linux format AcpiBin - Miscellaneous manipulation of binary ACPI tables iASL HELP: ACPISpec ver. 6.0 / ACPI Спецификации 6.0 ACPI Spec ver. 5.1 / ACPI спецификации версии 5.1 ACPISPec ver. 5.1 Errata A / ACPI спецификации 5.1 Исправления А Attension / Внимание :: =========================== Simple replacement of iasl compiler (iasl --> iasl5) in MacIASL leads to an empty Summary window, the bottom line shows correctly number of the errors / warnings / remarks, but the screen remains blank and errors addresses hard to find. This is the MacIASL's bug, not the compiler's. Простая замена компайлера iasl (iasl --> iasl5) в MacIASL ведет к пустому выхлопу окна Summary, то есть количество ошибок / предупреждений / ремарок в нижней строке показывает корректно, но окно остается пустым и адреса ошибок найти сложно. Это баг самого MacIASL, а не компилятора. =========================== IMPORTANT / ВАЖНО : =========================== To have a correctly disassembled DSL file w/o unexpected errors, you need to use the Terminal to decompile AML binaries. If you have a modern platform and more than 1 SSDT in your ACPI, you need to decompile all of them correctly. To decompile only DSDT.aml use -e key (to decompile in legacy ASL code mode you have to add -dl key instead of -d ) : Чтобы получить корректно дизассемблированный DSL файл без непредвиденных ошибок декомпиляции, нужно использовать терминал для декомпиляции бинарников. Если вы владеете современной платформой и среди ACPI таблиц присутствует более 1 SSDT, необходимо их корректно декомпилировать. Чтобы декомпилировать только DSDT, используйте ключ -e: (для распаковки в легаси код ASL вместо ключа -d надо использовать новый ключ -dl ) : New ASL+ decompile: / Декомпайл ASL+: iasl -e SSDT*.aml -d DSDT.aml iasl -e /@full_path@/SSDT*.aml -d /@full_path@/DSDT.aml iasl -da /@full_path@/SSDT*.aml /@full_path@/DSDT.aml Legacy ASL decompile / Декомпайл ASL легаси: iasl -e SSDT*.aml -dl DSDT.aml iasl -e /@full_path@/SSDT*.aml -dl /@full_path@/DSDT.aml iasl -da -dl /@full_path@/SSDT*.aml /@full_path@/DSDT.aml =============================== To decompile all DSDT & SSDTs use -da key / Чтобы декомпилировать все DSDT и SSDT таблицы, используйте ключ -da: iasl -da DSDT.aml SSDT*.aml iasl -da /@full_path@/DSDT.aml /@full_path@/SSDT*.aml Also add reference file ref.txt with unresolved External Methods and Argument count for each. Use -fe key: Также можно добавить дополнительный реф.файл ref.txt c перечислением все еще нераспознанных методов и количество Аргументов для каждого. Используйте ключ -fe: =============================== External (MDBG, MethodObj, 1) // <<<--- Unresolved Method with allocated Arguments count (text file ref.txt) iasl -fe /@full_path@/ref.txt -e /@full_path@/SSDT*.aml -d /@full_path@/DSDT.aml iasl -fe /@full_path@/ref.txt -e /@full_path@/SSDT*.aml -dl /@full_path@/DSDT.aml iasl -fe /@full_path@/ref.txt -da -dl /@full_path@/SSDT*.aml /@full_path@/DSDT.aml =============================== The command in the Terminal should be like this (with full paths of the files): Команда в Терминале будет выглядеть так (с полными путями к файлам): 0:~ steve$ /Volumes/2\ UNIT\ 2T/MAC\ OS\ X\ \&\ HACK/ACPI/iASL_MAC/acpica-unix-20150619/iasl_20150619_64/iasl -fe /Volumes/Y/Users/stevebondaryan/Desktop/N551JM/origin/ref.txt -e /Volumes/Y/Users/stevebondaryan/Desktop/N551JM/origin/SSDT*.aml -dl /Volumes/Y/Users/stevebondaryan/Desktop/N551JM/origin/DSDT.aml After pressing the Return key you should see something like this. It means that all of SSDTs were attached correctly to parsing (but in this example there were not all Externals resolved). После нажатия клавиши Return вы увидите что-то наподобие этого. Это означает, что все ССДТ таблицы были прикреплены к парсингу (но в этом примере не были распознаны все External методы). Here is an example how disassembler parses the Externals. / Вот пример, как дизассемблер парсит External методы. And here you are a correctly disassembled Method ADBG, which refering to External Method MDBG with 1 Arg count Вот пример корректно дизассемблированного метода ADBG, который ссылается на External метод MDBG c 1 Аргументом. But without ref.txt parsing will be incorrect and compiler will return an error, like this: Но без подключенного ref.txt файла парсинг кода пройдет неправильно и компилятор вернет ошибку компиляции: Here is an original SSDT with MDBG method, which was lost. / Вот SSDT таблица с методом MDBG, которая была утеряна: =================== And more: if you need to decompile your custom DSDT with your patches and if it still has many External Methods, you need to use all of the SSDTs this time too. If you deleted all of the Externals and those dependencies in the code, then no need to decompile with SSDTs and refs. В дополнение: если вы решили декомпилировать свою кастомную DSDT с примененными патчами и в таблице все еще имеются в большом количестве External методы, в этом случае также требуется использовать терминал и включить в декомпиляцию все SSDT таблицы. Если вы удалили все External методы со всеми зависимостями в коде, тогда не требуется использовать при декомпиляции SSDT таблицы и реф.файлы. =================== Changelog 20150930:
  18. Yosemite has been installed, and ran OK. CPU is: E3-1230v2(http://ark.intel.com/products/65732/Intel-Xeon-Processor-E3-1230V2-8M-Cache-3_30-GHz) motherboard is: GA-B75m-D3V GPU is: R9 290 non-X (insert ID into AMD kext, and working fine) boot loader is: Clover r2976. SMBIOS is: iMac13,1 And, I have tried: 1. only use config.list drop tables: SSDT Cpu0Ist, DMAR, SSDT CpuPm Drop OEM: Checked Generate P States: Checked Generate C States: Checked Plugin Type: 0 EnableC2/C4/C6: Checked Min Multiplier: 16 C3 Latency: 205 this option, my CPU can get: x16(1.58GHz) and x29(2.87GHz) 2. use config.list and SSDT.aml drop tables: SSDT Cpu0Ist, DMAR, SSDT CpuPm only Drop OEM: Checked leave others null and use ssdtPRGen.sh(download from GitHub, I think it should be latest version) to generate ssdt.aml and copy to /Volumes/EFI/EFI/CLOVER/ACPI/patched from my desktop and rename ssdt.aml to SSDT.aml this option, my CPU only can get x8(796Mhz). 3. use config.list and SSDT.aml (2) drop tables: SSDT Cpu0Ist, DMAR, SSDT CpuPm only Drop OEM: Checked leave others null use Hackintosh Vietnam Tool.pkg -> Clover-> Config -> SSDT -> Custom the result same as option 2.
  19. yashshah

    HP Envy m6-n015dx

    Hello, and I'd like to thank everyone in advance for their time and efforts. It seems that every time I attempt to create a patch for the DSDT on MaciASL, I end up with the following error no matter how many times I remove the lines/save it/duplicate it, the problem persists even after things appear to be saving and working. As a result, I'm unable to tell if my patches are saving too. I have attached my DSDT and SSDT files. I am currently using Piker-Alpha's SSDT Gen Script, but in the zip file labeled "Linux Extracted ACPI Tables," I have included the original SSDT files, if it helps in any way. The DSDT, I believe is the same. Current DSDT/SSDT: Archive.zip Ubuntu Extracted DSDT/SSDT: Linux Extracted ACPI Tables.zip The hackintosh has the following specs: 2.6GHz 4th generation Intel Core i5-4210M Processor Intel HD graphics 4600 with up to 1792MB total graphics memory Realtek ALC290 8GB Ram 750GB Hard Drive HP Motherboard w Insyde Bios
  20. I am trying to enable low power states in my laptop cpu using ssdtPRgen script. I got 17 p-states in IOregexplorer and no igpu states. only 9 p-states working and cpu rarely idles. am I doing something wrong or should I use this instead? CPU Ratio Info: ------------------------------------ CPU Low Frequency Mode.............: 400 MHz CPU Maximum non-Turbo Frequency....: 2000 MHz CPU Maximum Turbo Frequency........: 2000 MHz IGPU Info: ------------------------------------ IGPU Current Frequency.............: 0 MHz IGPU Minimum Frequency.............: 300 MHz IGPU Maximum Non-Turbo Frequency...: 300 MHz IGPU Maximum Turbo Frequency.......: 900 MHz IGPU Maximum limit.................: No Limit CPU P-States [ (5) 19 20 ] iGPU P-States [ ] CPU P-States [ (5) 14 19 20 ] iGPU P-States [ ] CPU P-States [ (5) 14 16 19 20 ] iGPU P-States [ ] CPU P-States [ (5) 12 14 16 19 20 ] iGPU P-States [ ] CPU P-States [ (5) 12 13 14 16 19 20 ] iGPU P-States [ ] CPU P-States [ (5) 12 13 14 16 18 19 20 ] iGPU P-States [ ] CPU P-States [ (5) 10 12 13 14 16 18 19 20 ] iGPU P-States [ ] edit1:this cpu always spends time at 400~500 Mhz at idle in linux. ioreg.zip CLOVER.zip
  21. uzmi

    ACPI Warning

    Hola: Una consulta acerca de sudo dmesg, en mi equipo tengo estos warning: ¿Se pueden quitar? ¿Como? Uso un dsdt personalizado y un ssdt-1 para la parte grafica Adjunto los archivos pertinentes. Muchas gracias. SSDT-1.zip dmesg.rtf
  22. Hi everyone I'm a new comer for OSx86, in the stage of modify DSDT & SSDT for monthes. Unfortunately, I've been tried four times experiences about modified - copied to EFI - Black - U disk Clover booted and recovered EFI - remodified - ... I REALLY don't know where the mistake I made, dispointed and ALMOST GIVEUP. I try to modified all the error and warning in DSDT, although someone tell me to ignore the warning, its nothing matter. maybe my motherboard is special? my PC as the signature, the MB is an infrequent one, Gigabyte H110tn-e, a thin ITX MB with H110 chipset ( 1xHDMI 1xDP 4xUSB 3.0 1xLAN 1xMIC 1xAudio output, needs external power adepter ) Anyone can help me to solve this problem ? My original DSDT and SSDT from aida 64 is attached, sincerely appreciated! Original DSDT.zip
  23. Hello!!!I have a problem via my CPU Power Management P-State i7 3770k. Which Mac definition for my CPU Mac board id. I have a MacPro6,1 but don't work I have a one P-state 8..... I create my SSDT via this link. Thanks in advance!!!!
  24. newapple4g

    Help with patching DSDT

    First I try to disassemble Dsdt and Ssdt located at Clover\ACPI\Origin ,but iasl gives error. Then I try Dsdt created from linux but dissembled dsdt have errors that I can't fix. Please help me ? origin.zip Linux ACPI Tables.zip
  25. Kynyo

    i5 4570 SSDT

    Hello everyone! Could someone help me with a SSDT for i5 4570? System from signature! Thanks in advance.
×