Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 11/18/2019 in all areas

  1. 2 points
    Slice

    OpenCore Discussion

    Choose iMac13,2 instead of MacPro5,1
  2. 1 point
    Allan

    [Guia] DSDT/SSDT - Conhecimentos Gerais

    Introdução. A ACPI (Advanced Configuration and Power Interface) define um grande número de tabelas que fornecem a interface entre um sistema operacional compatível com ACPI e firmware do sistema. Estes permitem descrição do hardware do sistema, de forma independente da plataforma em ACPI Machine Language (AML). O DSDT (Descrição de Tabela do Sistema Diferenciado) é a tabela principal na parte ACPI do BIOS de um computador, define a maioria dos principais dispositivos do sistema. O SSDT (Secondary System Description Table) tem a mesma estrutura com DSDT, mas é geralmente menor e define alguns dispositivos específicos. Por padrão, os bootloaders vão ter todas as tabelas OEM do BIOS/UEFI e transferi-lo para sistemas operacionais. Por que temos de corrigir o DSDT/SSDT do hackintosh? Ao contrário do Windows ou Linux, o OS X tem uma implementação ACPI incompletas que suporta apenas um subconjunto de DSDT apenas em modelos de Mac. Já nos Hackintosh, alguns dispositivos não estão definidos como compatível com OS X, sendo assim não vão funcionar corretamente. Objetivo Corrigindo o DSDT permite ao usuário melhor uso do seu hardware. Muitos bootloaders permitem que o usuário substitua a tabela OEM no BIOS/UEFI por tabelas definidas nos arquivos .aml Seção 1. Como extrair? Se você não usa DSDT, use essas maneiras pra extrair. No OS X. Se usa Chameleon, digite essa flag antes do boot: DSDT=null Pode usar esse comando no Terminal: perl -e 'open(CMD, "ioreg -lw0 \| grep DSDT|") or die; while(<CMD>) { chomp; if($_ =~ /\"DSDT\.?\d?\"=<([^>]*)>/) { $buff = $1; open(PIP, "|xxd -r -p > dsdt.aml") or die; print PIP "$1"; } }' Ou usar o app DSDT Editor, um app leve e facil de usar. Vá no menu File - Extract DSDT Dai vai aparecer a tabela disponível para edição no painel principal. Clover Na tela inicial do Clover, aperte F4, depois inicie o OS X, todas as tebelas ACPI estarão dentro de /EFI/Clover/ACPI/origin/ No Windows Como não existe mais Everest, baixe o Aida64 (pode ser Trial mesmo) Veja as prints. Depois de salvar, copie o arquivo para um Pendrive, cole na Mesa do OS X, e renomeie para DSDT.aml. No Linux (Ubuntu) Crie um Penboot (LiveCD) e abra o Terminal, e use esse codigo: cd ~/Desktop sudo cat /sys/firmware/acpi/tables/DSDT > DSDT.aml Caso não funcione, use esse: cd ~/Desktop sudo cat /proc/acpi/dsdt > DSDT.aml Seção 2 Adicionando o DSDT/SSDT no bootloader Depois de editar e compilar, salve o arquivo .dsl para .aml, a partir dai vamos colocar este arquivo para ser carregado pelo bootloader: Chameleon: /Extra Clover: /EFI/Clover/ACPI/patched Note: Se você tem mais de um SSDT e deseja que seja carregado, renomeie os adicionais como: SSDT.aml, SSDT-1.aml, SSDT-2.aml, … etc. O bootloader carrega a DSDT do sistema a partir do primeiro inicio. Para carregar a SSDT, você precisa adicionar estas flag nos seguinte bootloaders. DropSSDT=True (Chameleon) ou Drop OEM SSDT=True (Clover) Seção 3 Como editar e o que usar. Existem varios editores de DSDT, vou destacar alguns. O app mais usado é o DSDT Editor, um app leve e facil de usar. Há também o DSDTSE, esse já ensina a como fazer, não vem com muitos patchs prontos, é muito bom pra quem quer aprender na marra. Mas existe também o MaciASL que é bem mais completo, e também muito fácil de usar. Quando aberto pela primeira vez, ele de forma automática já extrai a DSDT que se chama Pre-Edited DSDT. Quando terminar as alterações, somente salve o arquivo, no menu File - Save As… [Nota] O MaciASL pode ser inserido alguns repositórios de patchs, poupa tempo em vez de baixar patch por patch. (Vou falar mais abaixo). Seção 4 Verificar erros/warnings. Para ver isso, com o DSDT Editor, vá em IASL - Compile. No MaciASL no icone Compile. Corrigir erros/warnings. Vou citar aqui os erros/wangins mais comuns e como resolver. 1 - Warning ResourceTag larger than Field (Tag: 64 bits, Field: 32 bits) Mude disso: CreateDWordField (BUF0, \_SB.PCI0._Y0F._LEN, MSLN) Para: CreateQWordField (BUF0, \_SB.PCI0._Y0F._LEN, MSLN) 2 - Warning Result is not used, possible operator timeout will be missed De Acquire (MUT0, 0x0FFF) Para Acquire (MUT0, 0xFFFF) 3 - Warning Not all control paths return a value (_HID) Warning Reserved method must return a value (Integer/String required for _HID) De: Method (_HID, 0, NotSerialized) { If (TCMF) {} Else { Return (0x310CD041) } } Para: Method (_HID, 0, NotSerialized) { If (TCMF) { Return (Zero) } Else { Return (0x310CD041) } } 4 - Error Object is not accessible from this scope (_T_0) Exclua o ultimo “_” (Ex: _T_0 para T_0) 5 - Error Object does not exist (_VPC) Exclua todos os “_” (Ex: Store (Local0, _VPC) Return (_VPC) Para Store (Local0, VPC) Return (VPC) Seção 5 Patchs Talvez se assustou um pouco com a maneira que deve ser corrigido os warnings/erros, mas para facilitar o trabalho, existem varios patchs que fazem o trabalho pra você. Há varios patchs uteis que você pode encontrar no Olarila: Patches E vários packs para as diversas motherboards: Patches by Motherboard Esses podem ser usados tanto no DSDT Editor como no MaciASL. Há uns benefícios pra quem usa o MaciASL, que como comentado tem a possibilidade de adicionar repositórios de patchs, veja: Os mais usados. Toleda RehabMan PJALM Como adicionar: (Créditos da imagem Pjalm) Seção 6 Como aplicar os patchs? DSDT Editor Dai você caminha até sua pasta com seus patchs. Escolhe o patch para sua situação e aplique. MaciASL Legenda: Clique no icone Patch, (1) depois escolha qual patch vai usar, (2) e aplique o mesmo. Veja que existe a opção “Open” onde você vai navegar até sua pasta de patchs. [Nota] Todo o patch deve ser um documento .txt, para criar o seu, use o TextWrangler, abra, copie e cole, e salve. Salvando o DSDT/SSDT Caso precise salvar o DSDT/SSDT, mas tem erros presentes que não foram compilados, faça assim: Clique em File > Save As..> File Format: Disassembled ASL File Notará que se tentar salvar no modo padrão "ACPI Machine Language Binary", o MaciASL não vai permitir isto. Esse recurso é legal pois, caso já tenha partes já editadas, e não quer começar tudo denovo, então poderá continuar o trabalho em outra hora. Bonus: Tenho uns amigos que tem videos muito funcionais para quem tem alguma duvida de como aplicar patchs e quer aprender sobre DSDT. 1 - AppleAbreast (Bruxo) Hackintosh - DSDT erro external (\TNOT) HDMI INTEL HD3000 HACKINTOSH AUDIO FUNCIONAL mov 2 - Fábio Qliskra (fabio_qliskra) Manobra no Device HDEF Aplicando o HPET Possible operator timeout is ignored Ainda estou adicionando coisas novas. Conselhos e dicas ou duvidas, por favor comentem abaixo. Creditos: Fabio Qlistra, pokenguyen, oldnapalm, e outros...
  3. 1 point
    This project is dedicated to the memory of Mausi, the cat I loved more than anybody else. A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports: 5 Series 82578LM 82578LC 82578DM 82578DC 6 and 7 Series 82579LM 82579V 8 and 9 Series I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0) I219LM I219V 200 Series (since V2.3.0d0) I219LM I219V 300 Series (since V2.4.0d0) I219LM I219V Key Features of the Driver Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2. Current Status The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and newer versions of macOS. Known Issues There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer. FAQ Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5. Installation Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface. Help - I'm getting kernel panics! Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches. As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches: Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again. Troubleshooting Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me. Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000. In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog Version 2.5.0 (2019-10-15) Reworked interrupt throttling code and added new configuration parameters. Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8 Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
  4. 1 point
    vector sigma

    Clover.app testing

    Sorry for the inconvenience, but you just give me a good new as mount finally works for you. This is the code: if (disk != nil) { // get the mount point or mount it var mounted : Bool = false if let mp = getMountPoint(from: disk!) { mounted = true saveNVRAM(nvram: nvram, volume: mp) return } if !mounted { log("mount begin for \(disk!)..") var mountattempts : Int = 0 repeat { mount(disk: disk!, at: nil) { (result) in mountattempts+=1 sleep(1) if result == true { var attempts = 0 repeat { sleep(1) attempts+=1 if let mp = getMountPoint(from: disk!) { mounted = true mountattempts = 5 saveNVRAM(nvram: nvram, volume: mp) sleep(1) umount(disk: disk!, force: true) break } } while (getMountPoint(from: disk!) == nil || attempts > 10) } } } while mountattempts < 5 There are two loops, one for mount and one to wait for the mount point to appear. This is easy to fix by force to break the first loop as soon the volume is mounted. Now I have no time but I will within 4 hours. P.S. as far I can see mount succeded at first attempt, and maybe there's no need for a loop.
  5. 1 point
    Pavo

    [Pre-Release] macOS Catalina 10.15.2

    1. My GPU has never needed WEG because I use my AGPMInjector to inject the correct GPUPM settings. 2. As stated previously it all relies on the SMBIOS + GPU combination. 3. See picture below
  6. 1 point
    Matgen84

    OpenCore Discussion

    Keep cool The EFI structure is already in the Docs, I know. OC Builder is also compiling all necessary efi and kexts, all in one. I don't use it. Let users choosing by themself, is also a good idea @Andres ZeroCross Right.
  7. 1 point
    Matgen84

    OpenCore Discussion

    It's exactly what I says to @nmano Despite of that OC Builder is useful for those how need complete EFI structure. Right.
  8. 1 point
    Pavo

    AGPM Injector kext generator app!!

    Found a HUGE bug in the the app on version 2.7.7, if you generated a injector kext using this version please update to the latest (2.7.8) and re-generate your injector kext.
  9. 1 point

    Version v1

    1,370 downloads

    Kexts from 10.9.1 required to get this card working. Either install them using kext utility or boot up your installer go to terminal and type following: rm -rf /Volumes/NAMEOFYOURDRIVE/System/Library/Extensions/IOPCIFamily.kext rm -rf /Volumes/NAMEOFYOURDRIVE/System/Library/Extensions/AppleACPIPlatform.kext - NAMEOFYOURVOLUME == name of the volume you installed osx onto. cp /PATHTOWHEREYOUEXTRACTEDTHEM/IOPCIFamily.kext (!!not IOPCIFamily.kext/ must be without / !!) /Volumes/NAMEOFYOURDRIVE/System/Library/Extensions/ cp /PATHTOWHEREYOUEXTRACTEDTHEM/AppleACPIPlatform.kext (!!not AppleACPIPlatform.kext/ must be without / !!) /Volumes/NAMEOFYOURDRIVE/System/Library/Extensions/ - PATHTOWHEREYOUEXTRACTEDTHEM == path to the kext files. chown wheel:root /Volume/NAMEOFYOURDRIVE/System/Library/Extensions chmod 775 /Volume/NAMEOFYOURDRIVE/System/Library/Extensions sorry for fool proof instructions but there is always one guy who just doesnt get it
  10. 0 points
    Ok, I'll go back to csm disabled and I'll see how to fix windows, it's odd as I was sure the usb I created to install Windows was gpt, I guess I {censored}ed up something during the install? Anyway, before putting your EFI folder in my ssd I have to install clover in it (creating an EFI partition). When installing clover, it asks me to choose the drivers (maybe that's not important as I will overwrite those with yours), but what about rc scripts? Should I let it install them or not? Also, what do you mean by "my new details"? Thank you for your help
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×