Jump to content

Search the Community: Showing results for tags 'el capitan'.



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
    • OSx86 Installation
    • Post-Installation
    • DSDT
    • Hardware Components and Drivers
    • Complete 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

Categories

  • OSx86
  • Apple News

Found 372 results

  1. Hi guys. Sometimes I am a complete noob, so I deleted two kexts from S/L/E and now my Asus Q200E laptop with OS X El Capitan boot hangs on kernel panic. I still can enter go through Clover to reach Recovery Mode and use Terminal, so I've put the two kexts on a USB pendrive and after some struggle I've managed to succefully copy them using Terminal, but the boot is still stuck on kernel panic. As I remember, these are the commands I've typed: mount -rw cp -a /Volumes/usb-stick/name.kext /Volumes/my-osx-drive/System/Library/Extensions Is there anything else I should do? Is anything wrong? Should I type some command else? For instance, should I type something to fix permissions and rebuild cache? Thanks a lot!
  2. specs: Intel® Core™ i5-2450M CPU @ 2.50GHz Lenovo base board 4gbsingle channel ram intel hd 3000 Wi-Fi 802.11b/g/n Wi-Fi Model Atheros AR9285 Wireless Bluetooth Bluetooth 2.1+EDR Finally installed el captain successfully i tried many ways but was unable to install a working bootloader or any kexts Could someone help and tell me how to install a bootloader which is easy and good And how to install the basic kexts like audio wifi keyboard and trackpad
  3. Hi insanelymac, I'm using a Dell All in one Inspiron 5348. It has a Pentium dual core G3240 Haswell clocked at 3.07 ghz in Mac. I've successfully booted and installed Mac Os X el capitan on an external hdd using a fake cpuid (0x0306E0) its ivybride. But my problem is the drivers. The only thing I could remotely do is wifi. I've installed the kexts for my wifi card. What I need is to install intel hd graphics (desktop) kexts and audio drivers (alc668) I've tried doing every method. Except for Ddst because I don't understand it whatsoever.Also found this thing called xcpm and was wondering if I can just spoof the graphics ids or something like that. Hopefully you guys can help me and thanks!
  4. Boa noite, estou com dificuldades para atualizar o clover. Eu abro o clover configurator, baixo a ultima versão, instalo e reinicio porém ele nunca sai da versão 4200, sendo que quando eu abro o clover instalado na preferencias do sistema ele me mostra que estou na versão 4200 mostra que tem um atualização disponível mas quando clico para atualizar ele fala que está na ultima versão
  5. Hello guys, Greetings from Brazil! I am running Mac OS X El Capitan 10.11.6 on my hackintosh and I am getting kernel panic at start and / or restart. It's random. Sometimes it happens and sometimes it doesn't. My hackintosh is as described below: Mac OS X El Capitan 10.11.6 from AppStore Motherboard Gigabyte G41MT-S2P F3 Intel Core 2 Duo 8 Gigabytes of RAM Video GeForce 9500GT 1 Gigabyte 2 SATA HD Samsung 500 Gigabytes each NEC uPD720200 USB 3.0 Host Controller Any suggestions? Thank you very much. I really appreciate your time and help! Best regards,
  6. EFI_Clover for VMware

    Version r4385

    755 downloads

    Clover r4385 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation. Tested with unlocked Workstation 12.5 running OSX 10.9 -->10.13 guest in Windows X64 host. Installation 1. Download and unzip "EFI_Clover_r4385 for VMware.zip". Mount Clover-v2.4k-4385-X64.iso by double clicking on it. 2. Mount your VM's EFI System Partition eg in terminal diskutil mount disk0s1 3. Copy EFI folder from step 1 into the EFI partition 4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file 5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu. Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
  7. Hello, I was initially running a Hackintosh that I built and set up using TonyMac as a guide, but at the time I didn’t realize that TonyMac was closed-source. So now I have an Intel chip PC ( Intel Core i7-4770K Quad-Core Desktop Processor 3.5 GHZ 8 MB Cache ) with a Gigabyte motherboard GA-Z87MX-D3H. I would like to build a fresh Hackintosh setup using InsanelyMac as the guide, but I was wondering if there would be issues with my hardware and I was wondering where the best guide on InsanelyMac exists to do that.. I want to install OS X.11 El Capitan, but I notice that my Gigabyte motherboard ( GA-Z87MX-D3H ) has not been listed as a potential component for hardware compatibility for that OS: http://wiki.osx86project.org/wiki/index.php/HCL_10.11.6 It is important that I install El Cap because certain software that I use is not compatible with newer OS’es. I notice that this site doesn’t endorse TonyMac, yet it gives a link on the Installation Guide page ( http://wiki.osx86project.org/wiki/index.php/Installation_Guides ) to the “Always up to date guide to building a Hackintosh” on Lifehacker ( http://lifehacker.com/the-always-up-to-date-guide-to-building-a-hackintosh-o-5841604 ) which is a link that explains the TonyMac method of installation. And also there isn’t any information supplied about installing OS X11 on the initial link in this paragraph even though a header exists on the page for it. Where would the best information be for setting up an OS X11 installation which does’t use TonyMac? Should I just follow the instructions for a previous version of OS X and hope for the best? Am I better off giving my motherboard the priority or the OS version the priority when it comes to finding and choosing the instructions to follow since instructions don’t seem to exist for using both of them together? This OS X.11 El Capitan forum that I’m posting on now doesn’t have any info about my motherboard — http://www.insanelymac.com/forum/forum/503-osx86-1011-el-capitan/ … But the top pinned link on the forum seems to have important information but it doesn’t give enough background information for me to be able to make use of it.. http://www.insanelymac.com/forum/topic/306777-guide-usb-fix-el-capitan-1011/ .. But posts in other forums do exist which talk about my specific motherboard, including this post in Italian which explains how to install the previous OS X.10 on my motherboard.. https://translate.google.com/translate?hl=en&sl=it&tl=en&u=http%3A%2F%2Fwww.insanelymac.com%2Fforum%2Ftopic%2F306828-guida-installazione-mac-os-x-101x-clover-usb%2F .. Is the above Italian link the best one I can follow to install OS X.11 even though it is for OS X.10? In other words, where would be the best “InsanelyMac” introductory information be about creating a Hackintosh installer which uses Clover and not TonyMac for my motherboard? Thanks for your help!
  8. The hardware specs: GPU: EVGA GtX970 4GB SC+ ACX2.0 GDDR5 Motherboard: Gigabyte Z97X-UD5H-BK CPU: Intel Core i7-4790K RAM: Crucial Ballistix Tactical 16GB DDR3 1600Mhz CPU Cooler: Hyper 212x Cooler Master Intel Storage: Samsung 850 EVO 500GB PSU: Corsair RMX Series RM650x 650W UEFI/BIOS settings - Most important. Vt-d - Disabled XHCI Mode - Auto XHCI Hand-Off - Enabled EHCI Hand-Off - Enabled SATA Mode - AHCI OS Type - Other CSM Support - Never For Install: Create a Penboot of OS X El Capitan 10.11.0, and install Clover in UEFI mode. The process of install is the usual. For install OS X and boot I used these boot-args: -v nv_disable=1 Post-Install: After entering in OS X, I've installed Clover in UEFI mode and upgrade OS X for 10.11.5 version using a Combo Update. Keeping the boot-args. Now you can download and install the last version of Nvidia Web Drivers, using NVIDIA Web Driver Updater.app After that, change the boot args: nvda_drv=1 About USB 3.0 recognition and speed. I have the proper USB 3.0 recognition and speed, using only these methods. DSDT patches. EHC1 to EH01 EHC2 to EH02 XHC was not necessary change it, this device comes with this way (name) natively. I used the @Pjalm patches (Intel 9) and (USB Power). And I used the RehabMan's kexts: FakePCIID + FakePCIID_XHCIMux What works: SpeedStep and Power Management - Ok QE/CI - Ok USB - Ok and in full speed Trim for SSD - Ok Audio - (ALC1150) Ok - I use AppleALC for this HDMI video and audio - Not tested, 'cause are used DVI instead. Ethernet Port - Ok Sleep - Ok Big thanks to: PJALM and RehabMan - for DSDT patches, and kexts. Mieze - For Ethernet kext vit9696 - for audio stuffs Micky1979 and fantomas1 - for Web Drivers updater tool Piker R. Alpha - for SSDT script Clover guys - for Clover obviously
  9. I know this is kind of broad, but if I build a workstation that's well supported on High Sierra now, how likely is it to still work well with the next major OSx release next fall? If you had to guess, what % chance do I have of encountering major issues when trying to update next fall? The kinds of issues that would seriously interfere with my day to day work of photo and video editing? For example, kext/kernel panics (is that even a thing still?) or major pieces of hardware suddenly not being supported, and so on... Has migrating your Hackintosh to the latest release has gotten easier in recent years? So for those of you who have been making builds for a while, is going from Sierra to High Sierra causing you fewer problems than Mavericks --> Yosemite for example or Yosemite --> El Capitan etc? Sorry if this is a bit broad and ignorant, but I've been away from the forums for quite a while and just trying to get a sense of how "stable" and "future-proof" Hackintoshes are these days - compared to Apple's own desktops ... I'm OK not updating incrementally ie v13.1 to v13.2 if I need to, but I'm worried about having to start completely from scratch with each new main version.
  10. Introduction With Whatevergreen.kext we already have a workaround for the AMD GPU wakeup issue which first arose with the release of El Capitan, but as a workaround is just a second class solution for a problem I decided to trace back the reason for the issue to it's origin and this post is the result of my research. As I used a R9 270X to do my research, which is the only AMD GPU I have, my patch has only been verified to work properly with this chip but according to the information sources I used, I have no reason to believe it won't work on other AMD GPU's too. In case there is still some uncertainty left in a particular point, I will mention this explicitly. Materials Used The Linux kernel sources of the Radeon driver in order to get a better understanding of the GPU's internals: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/radeon?h=next-20171013 A copy of the ACPI 6.0 specs in order to find out how to dump the chip's control register space. A disassembler, e.g. objdump in Terminal or the trial version of Hopper Disassembler. What I Did As it's been a well known fact that wakeup with AMD GPUs still works with El Capitan and Sierra provided you select the IGPU as primary GPU enabled CSM and use Legacy VBIOS of the AMD GPU in BIOS setup. I was wondering what is different with UEFI VBIOS and decided to I create dumps of the GPU's control register space while using Legacy VBIOS with CSM enabled and while using UEFI VBIOS with CSM disabled in order to find out. Comparing the register space contents it became obvious where the root of the problem lies and how it can be fixed with a DSDT patch. Technical Background Using Legacy VBIOS only the primary GPU is initialized by the VBIOS, i.e. only the IGPU is initialized while the AMD GPU is left untouched. When OS X boots up the framebuffer controller kext will find the AMD GPU in vanilla state, initialize it properly and wakeup will work as expected. That's also the reason why you have to blind boot in this configuration. Using UEFI VBIOS the AMD GPU will be initialized too, provided it has a display connected to one of it's ports. You'll see the BIOS splash screen and will be able to access the BIOS settings but unfortunately macOS's framebuffer controller kext will notice that the GPU has already been initialized and skips the basic setup so that the configuration made by the VBIOS will be used and this is the point where things start to go wrong because this configuration seems to be broken causing wakeup to fail. First of all you have to locate the AMD GPU in your DSDT. In my case it can be found at _SB.PCI0.PEG0.PEGP but it needs to be renamed to GFX0 for AppleGraphicsDevicePolicy.kext (AGDP) to work properly. This can be done manually or using a Clover patch (this is what I did) and I assume that this problem has been already solved before. The reason why I mention it explicitly here, is that you should be aware of it and don't get confused when your AMD GPU has a different name in the DSDT than in IORegistry. Second, we need to get access to the GPU's control register space. According to the Linux sources, PCI Base Address Register 2 (BAR2) is used to address the control register space on Radeon HD5000, HD6000 and HD7000 GPUs. It's a 64bit base address register but newer GPUs (BONAIRE and above, i.e. Radeon HD8000 and HD9xxx) are different as the use BAR5 instead of BAR2. Unlike BAR2, BAR5 is a 32bit base address register. On my R9 270X (PITCAIRN) BAR5 is zero so that I decided to use this as an indication to use BAR2 but I must confess that I haven't checked if it works for all supported GPUs too. In case my patch doesn't work for you, be aware that this might be a pitfall! The Radeon driver's source code tells us that the first display controller engine's registers can be found starting at offset 0x6800. It also tells us a lot about the meaning of the register contents. Using Legacy VBIOS my R9 270X's display controller engine's registers are still at their default values when macOS boots: 00006800 01 00 00 00 08 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006820 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | With UEFI VBIOS the display controller engine's registers look quite different. Using the Linux driver sources you can easily make sense out of these values and will discover that I've got a 4K display connected to my R9 270X which is configured to it's native resolution using 32 bits per pixel. 00006800 01 00 00 00 0a 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 0f 00 00 f4 00 00 00 |................| 00006820 f4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 0f 00 00 70 08 00 00 00 00 00 00 |........p.......| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | The rest was just a little bit of laborious work and trial and error, comparing register contents, understanding their meanings and see what happens when you reset these registers to their default values. If you try to play around with your GPU's control registers a little bit more, be prepared to get a garbled screen for a few seconds. After all I've managed to create a DSDT patch which fixes the wrong registers while preserving screen output during boot and, most important, solves the wakeup issue. The Patch Putting things together I created a DSDT patch to fix the incorrectly initialized registers. With this patch applied, I now have working wakeup with my R9 270X under Sierra (10.12.6) using UEFI VBIOS with CSM disabled in UEFI setup. No kext patches or additional kexts are needed anymore for sleep/wake to work properly with my R9 270X anymore. I can see the BIOS splash screen on my display and can access UEFI setup but the best of all is that there hasn't been a single wakeup issue since I applied this patch. Device (PEGP) { Name (_ADR, Zero) // _ADR: Address OperationRegion (PCIB, PCI_Config, Zero, 0x0100) Field (PCIB, AnyAcc, NoLock, Preserve) { Offset (0x10), BAR0, 32, BAR1, 32, BAR2, 64, BAR4, 32, BAR5, 32 } Method (_INI, 0, NotSerialized) // _INI: Initialize { If (LEqual (BAR5, Zero)) { Store (BAR2, Local0) } Else { Store (BAR5, Local0) } OperationRegion (GREG, SystemMemory, And (Local0, 0xFFFFFFFFFFFFFFF0), 0x8000) Field (GREG, AnyAcc, NoLock, Preserve) { Offset (0x6800), GENA, 32, GCTL, 32, LTBC, 32, Offset (0x6810), PSBL, 32, SSBL, 32, PTCH, 32, PSBH, 32, SSBH, 32, Offset (0x6848), FCTL, 32, Offset (0x6EF8), MUMD, 32 } Store (Zero, FCTL) Store (Zero, PSBH) Store (Zero, SSBH) Store (Zero, LTBC) Store (One, GENA) Store (Zero, MUMD) } } In case you have in-detail questions or need AML code for debugging (code to dump BARs or to dump the GPUs control register space) please let me know. I'm willing to share all my information in order support further research. Below you can find the register dumps I created attached to this post. FAQ Do I still have to select the IGPU as the primary display? No. Although I haven't tried this on my own, user chh1 confirmed that this is no longer required when using the patch (please see http://www.insanelymac.com/forum/topic/328549-tracing-back-the-amd-gpu-wakeup-issue-to-its-origin/?do=findComment&comment=2519884). Nevertheless I still recommend to select the IGPU as primary as there is absolutely no reason not to do so, in particular as the IGPU will be unusable for multimedia acceleration on Haswell based systems when it's not the primary one (IGPU's dev id is different when it's not the primary one). ​When I boot into macOS I always end up with a black screen. Does your patch solve this problem too? No, it doesn't. This patch solves the wakeup issue, nothin more and nothing less. The black screen after boot is either the result of a connector problem (please create a connector patch for your graphics card using the well-known methods) or the result of a problem with AGPM as certain system definitions (in particular recent iMacs) select special configurations for graphics power management. In order to achieve proper operation of AGPM it is crucial that your GPUs have correct names in the DSDT matching those listed in the AGPM configuration for the system definition (IGPU for the Intel GPU and GFX0 for the AMD GPU on iMac15,1, iMac17,1 and iMac18,x). You may patch your DSDT manually or use a Clover DSDT-patch to fix the device names. Credits vit9696 for developing Whatevergreen.kext and pointing me to the right direction. RehabMan for developing ACPIDebug.kext The Linux Radeon driver kernel developers for providing me with the background information I needed. Legacy.bin.zip UEFI.bin.zip
  11. Buon giorno a tutti ragazzi, Vorrei aggiungere una scheda di rete ethernet gigabit su pcie alla build server che potete leggere in firma sulla quale ho installato El Capitan. Ho trovato questa su amazon che monta un chipset realtek RTL8111G, qualcuno sa dirmi se può andare bene o crea problemi di qualche tipo? https://www.amazon.i...bit pci express Oppure, dato che mi farebbero comodo anche delle usb in più, ho trovato la sorella gemella lan + usb3.0. Il chipset lan è lo stesso di quella sopra, quello delle usb3.0 è VL806, potrebbero funzionare sia le usb che la lan con questa? https://www.amazon.i...bit pci express Grazie in anticipo del vostro aiuto!
  12. I have installed El Capitan on my y510p laptop using Clover. followed this thread Actually everything worked quite well. The time when everything ready, even keep switch windows and mac os also no problem. Then eventually I going back to my windows 10 and did my stuff. In the next day, when I want to boot into Mac OS, then problem come (WHAT? the last boot was just perfect! Why so sudden?) I couldn't boot into my Mac OS. It gave me infinite spinning ball after logging in. OK, fine, I reformatted it. I reinstalled everything and even EFI partition. Everythings worked well again. Then I used back my windows 10 and did my stuff. The next day, SAME THING HAPPENED. I reinstalled everything again. This time I reinstalled both my windows 10 and Mac OS. Wow, Worked well. Then the next day, stucking at apple logo. Above are my reformat processes. Now I'm going to explain my debugging about this. I tried to boot in verbose mode, safe mode. I tried to use disk utility to repair my disk. What I got is "disk could not verified" DiskWarrior expensive, so I used MacDrive 10, tried to repair the disk. Couldn't repair and get "internal result 8". So what should I do, it could not even stand over one night. Is my windows break Mac OS partition? EFI breaks Mac OS partition? Clover break Mac os partition? Hardware problem? but my windows works perfectly. PLEASE help me.
  13. Please Help!

    Hello all! I have been working with this for at least 2 weeks and can't seem to get my El Capitan installer to work. I have looked through so many forums and can't seem to get my El Capitan installer started. It keeps going to a white screen. Here is my config.plist that can show everything that I have tried to get it to work. I really need someone to explain to me what is missing or what needs to be taken away. Thanks in advance! MB: MSI m55h-e33 Mainboard Graphics: Intel integrated h55 CPU: Intel i3 550 3.2 Ghz processor - Clarksdale cpuid RAM: 8gb
  14. So, when i try to boot from chameleon,macOS 10.11.5 boots fine, but when i try to boot with Clover i get stuck on a "_" (not +++++++++++++++) I'm using pikeralpha's boot.efi because without it i get this: My hardware: CPU: AMD Athlon x3 440 Motherboard: MSI 760GM-P23
  15. Hi! I'm about to laying hands into a IBM System X3100 M4 entry-level server, to employ it as audio workstation. The specs of this particular machine are: Processor: Xeon E3-1220v2 Memory: 4 GB (1600 MHz) Video controller: Matrox MGA G200eR2 Memory 16 MB (shared) HDD Hot-swap HDD controllers SAS/SATA Channels 1 Connector int. 2 Connector ext. 0 RAID: M1015 Controller LAN: Intel 82546EB I know I will not go to any place with the G200eR2, so I need a graphics card anyways. I want to know if there could have some problems with this setup, apart of that. Thanks for any help!
  16. Hi I've managed to install OSX El Capitan on my Dell XPS 8000 using lots of tutorials and forums on here so I really appreciate the effort everyone has put into making this resource available. 3 main issues with my hackintosh 1.Audio does not work - I've been recommended to try the ALC887 (non legacy or legacy??) audio driver using the recommended post installer - I guess I have to disable SMC to get this to work. 2. SATA dvd rw and SATA hdd do not appear once in OSX. I need to add an AHCIPort Injector.kext with possible ICH8 dev id to the clover boot loader? but which one? 3. Is the icloud/facetime/appstore/update download for Sierra log in thing an issue on hackintosh? Everytime I set a generated config.plst file with created details from my system it breaks the clover bootloader so I have given up. I'm happy to assist how I managed to get my Dell XPS 8000 to work as far as I have if anyone needs a hand doing so. Thanks in advanced. S
  17. http://www.insanelymac.com/forum/files/file/31-vmware-tools-for-os-x-darwiniso/ Please tell me, what is the difference between the 8.5.6 and 8.5.5 versions of the VMWare tools for OS X ? Probably by mistake, the changelog for 8.5.6 and 8.5.5 is the same. What is a real changelog between them?
  18. Hello, I just installed el Capitan on my computer with the utility and I wanted to update Clover (like I did when i had Yosemite) to make the sound work in HDMI, fix shutdown issue and the inability to close my DVD player. But now OS X can't boot anymore... This is a screenshot of what i get when i try to boot on OS X : http://i.imgur.com/DREikGb.jpg Before that, i installed network card driver from here : http://www.osx86.net/files/file/1892-atheros-ar8121ar8113ar8114/ and sound card driver from here : http://www.insanelymac.com/forum/topic/161430-realtek-alc1200-ich10-working-kext-on-yosemite-1010-from-106/ Can someone help me please? Thanking you in advance. This is my configuration : Motherboard : ASUSTeK Computer INC. P5Q-PRO CPU : Intel Core 2 Duo CPU E8400 @ 3.00GHz dual-core 64 bits RAM : 6,00 Go DDR2 (2x2 Go + 2x1 Go) GPU : AMD Radeon HD 6570 Network card : Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller Reader/Writer CD-ROM/DVD ASUS DRW-1814BLT ATA Device
  19. Olá a todos! Segue um breve tutorial de como instalei o El Capitan na placa GA‐X58A‐UD3R, e vídeo NVIDA GeForce GTX 650 2GB. Especificações da máquina: Placa mãe: Gigabyte GA‐X58A‐UD3R Chipset: Intel® X58 Express Chipset Processador: Intel Core i7-3820 3.2 GHz // LGA2011 Memória: Corsair (5x 2GB = 10GB) 2000MHz DDR3 Rede: Realtek RTL8111E chip (10/100/1000 Mbit) Áudio: Realtek ALC889 codec Vídeo: NVIDIA GeForce GTX 650 2GB Teclado: Apple Aluminium Mouse: Microsoft HD para Sistema: SSD 120GB Kingston 1 - Criando o PenBoot Você precisará de um Pendrive com pelo menos 8GB; Baixe o Flash Drive Maker: Download Siga passo a passo em vídeo criado pelo autor: Assistir Feito isso, pule para a próxima etapa. 2 - Instalando o Clover no pendrive Baixe o Bootloader Clover mais recente: Download Instale ele normalmente, não esquecendo de na última etapa selecionar o Pendrive no disco de destino. Agora abra o pendrive e procure a pasta EFI, baixe esta pasta clover: CLOVER.zip e substitua a do pendrive por esta. Inicie a máquina pelo pendrive e instale o El Capitan. 3 - Pós-Instalação Inicie o sistema usando o Boot do Pendrive. Instale o Clover novamente em seu HD: Selecione o botão CUSTOMIZE Certifique se a opção Install for UEFI booting only está marcado e instale. Agora baixe o Clover Configurator clicando aqui http://mackie100projects.altervista.org/download-clover-configurator . Procure a aba Mount EFI; Agora monte a partição EFI do seu HD, basta clicar no botão Mount Partition; Abra a partição e dentro da Pasta EFI, substitua a pasta CLOVER pela pasta que deixei mais acima para download. Feito! -----------/-//----------- VÍDEO: 100% ÁUDIO: 100% [Graças a MaLd0n] PROCESSADOR: 100% REDE: 100% USB 3.0: 100% HIBERNAÇÃO: 100% SHUTDOWN E RESTART: 100% Créditos ao MaLd0n pelas dicas em outro sistema, mas que me ajudou muito para esta instalação. Valeu! Espero ter ajudado.
  20. Hi guys, I have a HP Probook 4540s with an i5 3380M CPU, 8gb RAM and a 250GB SSD. I have booted to the installer and installed El Capitan to the SSD but after a restart I boot once again via the USB but this time hoping to boot my fresh install from the SSD but it is not there. The UEFI clover boot loader is only showing my USB boot stick and not the SSD with the install of El Capitan on. The SSD was erased and formatted, journaled and GUID. I have made hack's before but never had this issue after installing OS X Any ideas on this please ?
  21. CPU | Intel core i7 6700 3.4Ghz Mobo | Gigabyte H170-D3hp Ram | Corsair Vengeance 16GB (2x8GB) 2133Mhz GPU | Galax GTX970 4GB SSD | Samsung 850 Evo 500GB PSU | Thermaltake 600w OS | 10.11.6 I initially thought this issue was a blown port and while it still could be hardware I've noticed something very odd. Two days ago I was using a USB 3.0 portable drive doing some colour grading in Da Vinci resolve. Quite suddenly, the mouse stopped working and then a couple of seconds later the system reset itself. I have no idea what happened but when the system rebooted a message popped up and for a tense few seconds I was worried the drive was ruined. The message said something like 'drive connected to mac but does not have power' or something along those lines but specifically indicating that I should plug the device in to a port that has power. This was the same port the drive was plugged in to when the reset happened and so I unplugged it and moved it to the port above and it worked. I was curious about the issue today and didn't have any critical work to do so I had a test with another bus powered drive that also previously worked fine. This one also had not encountered any dodginess like the sudden system reset either. I plugged it in to the port that I knew had caused issue and received the same message. I plugged it in to the port immediately adjacent and also received the same message. The thing is the drive is spinning so it *is* receiving power and the fact that it's giving me that message suggested to me that is registering on at least some level with OSx. Anyone know what I should do?
  22. I changed i3-530 to xeon x3460. First i change cpu section with cpu section of i7-860. During loading the signal on the monitor vanishes (black screen). Then i maked cpu section from linux SSDTs - same problem. I try boot with imac and macpro smbios. There are no errors in logs. Boot fine only with nv_disable=1 in low resolution. I think problem with GPU section in DSDT. How can i fix it without installing clover? MB: ASUS P7P55D-LE (bios version - 2101) GPU: GTS250 (plugged by VGA, only VGA) 10.11.6 + chameleon (Enoch-rev.2773) dsdt_i3.aml.zip dsdt_x3460.aml.zip
  23. Hey guys, I am receiving 9 errors no warnings or remarks and I can't figure out what the issue is. Can someone please help? DSDT: https://ufile.io/f5d01
  24. I have a working Niresh Yosemite 10.10.5 install on my PC with Clover UEFI as the bootloader. I'd like to update it to El Capitan if possible. I've tried to do it through the Install El Capitan update app as I heard that it works as long as you have Clover. The program worked fine but when I try to boot into the Installer through Clover, I get the black Apple screen (without loading bar) followed by a black screen with a circle and a slash through it. I booted in verbose and got a message saying something about it not being able to boot. Any suggestions or other ways to upgrade to El Capitan? Build: i7 3770 EVGA GTX 760 SC Acer Aspire MC605 OEM Motherboard 500GB HDD 8GB RAM
×