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
    • 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 173 results

  1. 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
  2. THIS IS STILL WORK IN PROGRESS Laptop : Sony Vaio- SVE1712W1EB OSX version : 10.13 - High Sierra - SMBIOS - MacBookPro9,1 Motherboard : Intel HM76 Express DSDT FIX : Show Fan RPM's : Updated,now working with Latest Istat Menus and HWMonitor CPU : i7 - 3632QM (2.2Ghz- 3.2Ghz) : Dedicated Graphics : AMD Radeon HD 7650M 2048MB Full QE/CI and Resolution: Fix gradient issue with AMD Graphics the fast way : Fix Brightness issue + brightness fn keys: Fix sleep issue and naming issue with AMD Graphics : Integrated Graphics : Intel HD Graphics 4000 (can't be enabled in bios,no option) Touchpad and Keyboard : Wifi : AR9485 : Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller : Works out of the box Sound : Realtek ALC269 -VC1 : Battery: Works after patching : Built-in Camera : OSX version : 10.12 - Sierra - SMBIOS - MacBookPro9,1 Motherboard : Intel HM76 Express DSDT FIX : Show Fan RPM's : Updated,now working with Latest Istat Menus and HWMonitor CPU : i7 - 3632QM (2.2Ghz- 3.2Ghz) : Dedicated Graphics : AMD Radeon HD 7650M 2048MB Full QE/CI and Resolution: Fix gradient issue with AMD Graphics the fast way : Fix Brightness issue + brightness fn keys: Integrated Graphics : Intel HD Graphics 4000 (can't be enabled in bios,no option) Touchpad and Keyboard : Wifi : AR9485 : Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller : Works out of the box Sound : Realtek ALC269 -VC1 : Battery: Works after patching : Built-in Camera : OSX version : 10.11.6 - El Capitan - SMBIOS - MacBookPro9,1 Motherboard : Intel HM76 Express DSDT FIX : Show Fan RPM's : Updated,now working with Latest Istat Menus and HWMonitor CPU : i7 - 3632QM (2.2Ghz- 3.2Ghz) : Dedicated Graphics : AMD Radeon HD 7650M 2048MB Full QE/CI and Resolution: Fix gradient issue with AMD Graphics the fast way : Fix Brightness issue + brightness fn keys: Integrated Graphics : Intel HD Graphics 4000 (can't be enabled in bios,no option) Touchpad and Keyboard : Wifi : AR9485 : Ethernet : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller : Works out of the box Sound : Realtek ALC269 -VC1 : Battery: Works after patching : Built-in Camera : UPDATED : October 9. 2016.
  3. Hello everyone, I bring you today an easy installation of the latest El Capitan (10.11.5) with the CPU 5960X (16 cores) installed on ASUS X99 Deluxe U3.1 motherboard with a Nvidia GTX 908 Ti !! (Versão em Português aqui) Once installed, the following features are 100% operational: 1 x Ethernet adapter + Wlan @ 5Ghz adapter All USB3.0 ports available Nvidia 980ti working with 3 monitors and sound AppleHDA + functional HDMI CPU energy management operation from 1.2Ghz to 4.5GHz Bluetooth, AirDrop, Facetime, iMessage all workin and much faster than in 10.10.5 (Yosemite) !! Without NullCPUPowerManagement.kext the VoodooTSCSync.kext the IOPCIFamily.kext (modified) and without a modified kernel - The case of Yosemite in 5960X ... Requirements: "Install OS X El Capitan.app" downloaded and installed in the Applications folder Get the app "El Capitan HD.zip" here Access to a Mac/Hackintosh already with El Capitan installed and with SIP turned off, as described here An EMPTY SSD/hard disk on SATA/USB - If not empty, the "El Capitan HD" will format it completely !! Access to the Serial Number, ROM and MLB on a real mac Thanks: Brumbaer, stinga11, chris1111, the Clover team, onmybikedrunk, jamiethemorris, pokenguyen and many, many more ... Installation: 1 - Download the file "Comprimido.zip", which contains the Kexts, tools and EFI folder already pre-configured here and decompress on your downloads folder of your Mac/Hackintosh. Then configure the BIOS 3101 of the ASUS X99 Deluxe as per the screen snapshots stored here. 2 - Run the application "El Capitan HD.app" to install the basic configuration of El Capitan into an EMPTY SSD/hard disk: 2.1 - Enter your password at about 4% 2.2 - Wait for the end, such as: 3 - Use the "Clover Configurator.app" application to mount the EFI partition. 3.1 - "Mount EFI" 3.2 - "Check Partition" 3.3 - Search by type identifier "/dev/diskX" disk that contains the partition "Macintosh-HD" 3.4 - "Mount EFI partition/diskXs1" 4 - Install the latest CLOVER v2.3: 4.1 - Run CLOVER v2.3 application and install it on to the disk "Macintosh HD," with the following options: 4.2 - Use the "Finder" file manager to copy the files: 4.2.1 - <ZIP directory>/EFI/CLOVER/ACPI/*.* to the folder EFICLOVER/ACPI/ 4.2.2 - <ZIP directory>/EFI/CLOVER/config.plist to the folder EFI/CLOVER/ 4.2.3 - <ZIP directory>/EFI/CLOVER/kexts/10.11/FakeSMC.kext to the folder EFI/CLOVER/kexts/10.11/ 4.2.4 - <ZIP directory>/EFI/CLOVER/drivers64UEFI/OsxAptioFix2Drv-free2000.efi to the folder /EFI/CLOVER/drivers64UEFI/ 5 - Use the application "KCPM Pro.app Utility" to install the Kexts onto the "Macintosh HD" disk and then repair its file permissions and rebuild the kext Caches: AppleGraphicsControl.kext (changed already to SMBIOS 6.1) AppleIntelE1000e.kext BrcmFirmwareRepo.kext BrcmPatchRAM2.kext FakeSMC.kext X99_Injector.kext 6 - Start the PC with the new 10.11.5 installed, by selecting UEFI OS (P1:xxxxxx) 6.1 - In CLOVER boot menu, select "Boot Mac OS X from Macintost-HD" 6.2 - Setup the country and don't setup yet your AppleID 6.3 - Setup a new user 6.4 - Login and then run the application "Kext utility.app" and wait for the end of its operations: 6.5 Drag and drop the "LegacyUSBHub.kext" (for USB3.0) and "AppleHDA.kext" (changed to ALC1150) onto the window of "Kext utility" and wait for it to end its operations: 6.6 - Re-start the PC 9 - Install Nvidia Driver Web - http: //us.download.n...46.03.10f02.pkg 9.1 - Install the Nvidia CUDA - http: //www.nvidia.co....29-driver.html 9.2 - Re-start the PC 10 - To configure iMessage/FaceTime its necessary to extract various data from a real Mac: 10.1 - Check that the Ethernet network card is set to "en0" by running the "DPCIManager.app" application: 10.2 - Re-do step 3 again to mount the EFI partition 10.3 - Navigate to and follow the steps to extract (from a true Mac) the following data: Serial Number, SmUUID and Board Serial Number - used for "Clover Configurator.app" application in the "SMBIOS" section ROM & MLB identifier - used for "Clover Configurator.app" application in the "Rt Variables" section (Using the "iMessageDebug" in a terminal window) 10.4 - Re-start the PC Boa sorte, Paulo End results: Tests: Information sources: iCloud / iMessage / FaceTime - http: //www.insanelym...h/#entry2020598 http: //www.insanelym...ative-work-thru http: //www.insanelym...-capitan-10113/ http: //www.insanelym...-hotspot-patch/ http: //www.insanelym...hda-hdmi-audio/ http: //www.insanelym...da-audio/page-1 http: //www.insanelym...edstep-working/ https: //sourceforge..../Snow_or_Above/ https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
  4. Ludwig Bartholomew

    GUIDE: ASUS K501UX El Capitan

    Hey guys, I've got EL Capitan working nearly perfect on my system. I am writing this up pretty fast, so please excuse any errors lol. Specs: Core i7-6500u, 8GB RAM, GTX 950M (DISABLED), HD520 First of all, this is going to be a pretty basic guide. I've attached my clover folder with all the essential kexts along with DSDT with proper edits. What works -Sleep/Wake -Trackpad (still a little buggy, specifically with sleep/wake) -keyboard as well as backlight -Wlan -sandybridge power management native -GPU acceleration HD520 -Audio with VoodooHDA To start out with I recommend changing the Wi-Fi chipset in your laptop to a broadcom m.2 variant that is supported. Also, be sure to switch SATA Mode to AHCI in Bios. Trackpad was one of the hardest things to get working due to it being an I2C device. Getting this to work required DSDT edits. There is currently a kernel extension being developed called VoodooI2C. I've compiled the latest build of this and have included it in the download. I will upload my Clover folder for you guys to use, I have applied all the necessary DSDT patches. I have not had a whole lot of luck getting Sierra to work, but if one of you figures out a way be sure and comment to let us know how. CLOVER.7z
  5. Hi, Here a guide to install El Capitan on the Dell Latitude E6230. specs: - core I5-3320 2.6Ghz - Intel HD4000 - intel 7 series - network intel - wifi AR928x (not original wifi card) - audio IDT 92HD93 not working: - wifi/BT (need card replacement) working: - audio - built-in multi screen (hdmi) - powermanagement - brightness - hdmi port - usb - wired network - trackpad (two fingers) - battery statut Not working: - hdmi audio (should work with Voodoohda) - brightness FN keys (dsdt fn keys for dell e6410 should work) 1/ CREATE USB INSTALLER 2/ INSTALL CLOVER Add HFSPlus.efi 3/ CLOVER CONFIG FILE Copy fakeSMC.kext in: - /EFI/CLOVER/Kexts/Others - /EFI/CLOVER/Kexts/10.10 - /EFI/CLOVER/Kexts/10.11 4/ BIOS CONFIGURATION: Your Bios must be in A06 to A11 version, lower or upper bios version are not recommended. Before, plug the USB installer on a usb port. Press F12 at startup, then select Bios Configuration. Others value are normaly configured by default. 5/ INSTALLATION: You can install Mac OS X from the USB installer to the target drive, but on reboot on freshly installed system, the USB port, will not be recognised. So, you will not be able to configure your account and reach the desktop. We need to patch the DSDT from an other Mac/Hackintosh computer. 6/ DSDT PATCHES: 7/ POST INSTALLATION: Here, replug the USB installer on your Dell E6230, select the freshly installed mac os x to boot. 8/ SSDT PATCHES: 9/ OTHERS 10/ PACK FILES: 11/ TRACKPAD ISSUE: Cheers
  6. Hi guys, I need testers who have netbook with Intel Atom or Celeron Processor I want to know, whether the kernel boots or not and If not, then upload an image with Details of what point the system gets stuck with information what bootloader do you use. thx 10.11.6-IPCA.zip
  7. Hello there! I have been trying to install El Capitan 10.11.4 on my system. It is a HP 250 G2 Laptop. I have only been successful in installing on VMware using VMware unlocker and also changing the CPUID in the VMX file. After creating and installer with tutorials from Eladnava.com I was able to create an installer with Clover. But trying to boot, I keep getting: OsxAptioFixDrv: Starting overrides for \. IABootFiles\boot.efi Using reloc block: no, hibernate wake: no asked for SMC=4D535463 (MSTc) len=1 asked for SMC=4D534163 (MSAc) len=2 ++++++++++++++++++++++++++++++++++++++++++++++ And nothing else. I have even tried the OsxAptioFix2Drv but still same error but with "OsxAptioFix2Drv: Starting overrides for \. IABootFiles\boot.efi". I don't know much about boot args but I've tried nv_disable=1, cpus=1 but they don't seem to work. I attached the full Hardware info of my system in CODEBLOKS-PC.txt and CODEBLOKS-PC.HTM. Please help me with solutions.
  8. ASUS P5G41T-M LX AMD ATI Radeon HD 5450 1GB (0x68F91002) Enable S3 in bios setting Create USB El Capitan: Terminal:: sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction --> Successful making El Capitan USB --> Install Clover r3292 or latest to USB --> Select as screenshot --> Done -- Edit Config.plist with plistedit pro --> Graphics-->NVidia=False, ATI=True, Intel=False --> Copy FakeSMC to USB/EFI/CLOVER/Kext/10.11 --> Done Boot with USB and follow installation guide.-->Done Boot with USB and select El Capitan Update El Capitan to 10.11.1 --> done Install Clover to HDD and select as screenshot --> Copy FakeSMC, AtherosL1cEthernet.kext, and VoodooHDA 2.7.1 to EFI\CLOVER\Kext\10.11 --> Copy NTFS.efi to EFI\CLOVER\drivers64 -- Edit Config.plist with Clover Configuration --> ACPI > DSDT > Fixes > Fix_Display_0100=TRUE --> Devices > FakeID > ATI=0x68E01002 --> Graphics > Inject > ATI=TRUE --> Graphics > FBName > Shrike --> Reboot without USB -> Done
  9. My business is slow in updating OS's, and as a result, I'm still using Yosemite. I recently got a magic trackpad 2, only to discover it only works with El Capitan. However, I do have forcetouch capability on my macbook pro, and so i'm thinking maybe all that is missing are the drivers for the magic trackpad 2.... has anyone managed to get the magic trackpad 2 working with Yosemite? I can pair it, but it acts like a dumb mouse, just move and click, no gestures or anything. Thanks! OSX Yosemite 10.10.5 Macbook Pro Mid-2015 15-inch 2.5 GHz 16 GB RAM 512 GB SSD
  10. So I am trying to install El Capitan on my system, and I keep getting stuck at the same spot, I have looked at many guides and it seems that I always get the same output. Firstly my specs: -Asus X99-Deluxe -GTX 980 -i7-5820K - 32GB DDR4-2133 And now for show and tell! I have tried and retried the ##### method (that program from tonymacx86 that apparently isn't liked 'round these parts), and the Clover method. I just tried the RampageDev guide, and you could say I made progress, cause now what ever I do I at least get to the following point!: http://i.imgur.com/De9X4Rw.jpg I have tried using -x, nv_disable=1 (with and without InjectNVIDIA), slide=0, dart=0, and npci=0x2000 and npci=0x3000, all give me the same output (in any combination). Does anyone (especially those with similar setups) have any ideas? UPDATE: Ok, so after changing USB headers on my board and retrying the front ports, I can get past the "Still waiting for root device" message! However now I get to these points: Booting with just -v, npci=0x2000 and kext-dev-mode=1 I get this: http://imgur.com/LXunuKm.jpg and with cpus=1 added I get the following: http://imgur.com/6SuTFLN.jpg In both cases the machine restarts after a second or two.
  11. guitarsimo93

    FireWire su El Capitan

    Buon giorno ragazzi, Ho necessità di utilizzare delle porte FireWire sulla seguente configurazione: Mobo: asrock b75m-gl R2.0 Cpu: i7 2600k GPU: integrata HD3000 Bootloader: clover v2.3 r3333 In casa ho due schede FireWire che fino a Yosemite funzionavano anticamente senza bisogno di nessun kext o nessuna patch. Entrambe montano un chip FireWire della VIA siglato VT6306. La prima che ha solo la FireWire e quindi solo questo chip mi lascia avviare il computer ma non mi viene riconosciuta nessuna interfaccia FireWire. La seconda che ha quel chip per le FireWire e un secondo chip in aggiunta sempre della VIA e siglato VT6214L per delle usb aggiuntive mi fa riavviare il computer al boot. Ecco uno screen del riavvio https://www.dropbox.com/s/qh3e80gwgls616b/File%2016-02-16%2C%2018%2048%2015.jpeg?dl=0 È possibile utilizzare in qualche modo una di queste due schede sotto El Capitan? Grazie ragazzi!
  12. Salve a tutti ragazzi, vorrei installare El Capitan sul mio Asus. Potete darmi una mano per favore? Intel Core i5-6500u 4GB di Ram DDR4
  13. Hello everyone and greetings from Brazil! I've installed Mac OS X El Capitan 10.11.5 on my desktop and it's working great! Now, the only problem I'm having is that the built-in microphone on my Logitech C920 web camera is not recognized by the system. The only thing that shows up on System Preferences --> Sound is: Microphone (Pink Rear). The camera works great out of the box, but no microphone... The camera is connected to one of my USB 3.0 ports. Does anyone have any ideas on how to solve this issue? My system configuration is: Motherboard Gigabyte G41MT-S2P 8 gigabytes of RAM Video nVidia GeForce 9500 GT (1024 MBytes) Two SATA HDs Mac OS X 10.11.5 with Clover I appreciate your help and thank you very much for your time and expertise! Jay Cee
  14. Bonjour Je viens d'installer El Capitan 10.11.6 et je ne peux pas ajuster le sous-balayage sur l'écran de TV en HDMI comme indiqué ici : https://support.apple.com/fr-fr/HT202763 Internet marche Audio en HDMI avec VoodooHDA-2.8.8 marche USB 3 en facade : ne marchent pas Ma Config : Asus P8P67 Sabertooth Rev. B3 Socket : LGA 1155 CPU: Sandy Bridge 2500K Mem: 8GBs GSkill 2x4GB 0 Contrôleur NEC® USB 3.0 : IGPE : Intel HD Graphics 3000 Video Card : ASUS GTX 570 HD Sound: ALC892 Contrôleur réseau Gigabit Intel® 82579 Bios 1502 Display : TV Sony Bravia Mode d'installation : Clé USB ok clover en UEFI Clover_v2.3k_r3650 Nvidia : WebDriver-346.03.15f01 MA QUESTION : Comment puis-je ajuster l'affichage à la bonne taille en l'absence de la réglette de réglage ?
  15. Hello everybody. I need help to understand and use some patches that Pike R. Alpha has found for XCPM on his Broadwell-E cpu on X99 board. Here's the article. My knowledge is not enough to elaborate it and apply to Clover bootloader (or, I guess to the kernel itself). I think this is going to be huge. Even for Haswell-E and Ivy Bridge-E cpus. He's found some solution to have XCPM without VoodooTSCSync.kext, MSR(0xE2) unlocked BIOSes, AppleIntelCPUPowerManagement.kext, NullCPUPowerManagement.kext, FakeCPUid flag, etc... My set up (to be in a few day, components on their way) - Motherboard Asus X99-A II - CPU Intel i7 6900K Broadwell-E - RAM 64 GB DDR4 Corsair CMK32GX4M2B3000C15R Vengeance LPX - SSD nvme Samsung MZ-V5P512BW 950PRO m.2 - Video card EVGA nVidia GTX980 TI - ASUS ThunderboltEX II/Dual PCI-E card - OS X 10.11.6 El Capitan Yes, he's on Sierra DP3, but I (and many others, I might say) still am on 10.11.6 El Capitan or earlier (Yosemite). Anybody here? Thanks in advance g.
  16. Hi everyone, I run into unanticipated problem in attempt to install El Capitan on Dell Optiplex 760. I have no access to Macintosh, so I prepared El Pwn installation USB stick using Transmac. It works fine. I inserted 250GB drive initially erased and NTFS formatted In BIOS setup I specified "RAID autodetect/AHCI", Virtualization "ON" Installer loads fine from the El Pwn USB stick, does some work, and I even got to language selection, so I proceed with English But after start I get "OS X cannot be installed on your computer OS X El Capitan is already installed on this Mac Quit the Installer to restart your computer and try again" OK, the 250GB is NTFS, so I launched Disk Utility, and Erased the 250GB, formatting as El Capitan, OS X Extended (Journaled), GUID Partition Map Exited Disk Utility, then Installer, and tried again. Now after choosing booting from USB the system reported wrong configuration (?) Launched BIOS Setup - SATA Operation became "RAID On" instead of specified "RAID autodetect/AHCI", Virtualization is "OFF" (?!) Reset again to "RAID autodetect/AHCI", Virtualization "ON" Tried again to boot from USB - the same result, although Disk Utility reports that 250GB El Capitan is formatted correctly for instillation. Please help!
  17. I'm trying to upgrade to El Capitan directly from Yosemite (It's a distro but I'm trying to leave the distro environment to El Capitan, or at least find a way to fix the installer that I have downloaded to work with my laptop) and when I boot "install Mac OS X Install" it goes straight to a kernel panic right when the loading bar shows up. I appear to have issues with kexts, but I'm not sure, I have supplied an image of the panic. Please tell me how to fix this.
  18. Hello, I've got a Fujitsu Lifebook A555 with 8GB RAM, 1TB HDD, Intel i3 5th Generation processor (2.00 GHz), and Intel HD Graphics 5500. I've heard that Intel 5500 needs the DMVT to be changed, but I also heard that I could risk bricking my laptop. Will anyone please write out a guide for me to install El Capitan with Wifi and Sound working on this laptop? I would really appreciate it. I didn't understand the Broadwell part of Rehabman's new users guide. I'm not saying you guys do all the hard work and let me relax, I just want a guide specifically for my laptop (just to be safe) if you could manage writing it. (Because I don't want to end up bricking it) Thanks a lot I've got an El Capitan usb installer created using Createinstallmedia on OS X (friend's macbook) and Clover.
  19. I'm having a few relatively minor issues with my USB 2.0 ports. They function at the Clover menu, but turn off during boot. Once the OS X login screen appears there's about a ~10 second delay before they start working properly. All my USB 3.0 ports work immediately at the login screen. My other issue, and I'm not sure this is related but if I have my GMYLE usb bluetooth adapter plugged into a USB 2.0 port, I get a full USB hub reset every 10 - 15 minutes or so. When it's in a USB 3.0 port there are no hub resets. Otherwise all the USB ports seem to function correctly using PJALM's DSDT patches only.
  20. Hi everyone, I'm pretty new to hackintosh stuff but I have a pretty okay knowledge with programming. Essentially I tried installing the official version of El Capitan on my Mac Pro 3,1 running Yosemite and since then my ATI Radeon HD5000 graphics card has not been working properly. I can't fullscreen Youtube videos without serious lag and I can't run 3d graphics such as Unity3d. I think there's an issue with my kexts. Here's the output when I run kextutil on AMDSupport.kext and AMD5000Controller.kext. Can anyone point me in the right direction? mac@macs-Mac-Pro:~ $ sudo kextutil /System/Library/Extensions/AMDSupport.kext (kernel) OSMetaClass: Kext com.apple.kext.AMDSupport class ATIController is a duplicate;kext com.apple.kext.ATISupport already has a class by that name. (kernel) Kext com.apple.kext.AMDSupport start failed (result 0xdc00400a). (kernel) Kext com.apple.kext.AMDSupport failed to load (0xdc008017). (kernel) Failed to load kext com.apple.kext.AMDSupport (error 0xdc008017). Failed to load /System/Library/Extensions/AMDSupport.kext - (libkern/kext) kext (kmod) start/stop routine failed. mac@macs-Mac-Pro:~ $ sudo kextutil /System/Library/Extensions/AMD5000Controller.kext (kernel) OSMetaClass: Kext com.apple.kext.AMDSupport class ATIController is a duplicate;kext com.apple.kext.ATISupport already has a class by that name. (kernel) Kext com.apple.kext.AMDSupport start failed (result 0xdc00400a). (kernel) Kext com.apple.kext.AMDSupport failed to load (0xdc008017). (kernel) Dependency com.apple.kext.AMDSupport of kext com.apple.kext.AMD5000Controller failed to load. (kernel) Can't remove kext com.apple.kext.AMDSupport; services failed to terminate - 0xdc008018. (kernel) Kext com.apple.kext.AMD5000Controller failed to load (0xdc008015). (kernel) Failed to load kext com.apple.kext.AMD5000Controller (error 0xdc008015). Failed to load /System/Library/Extensions/AMD5000Controller.kext - (libkern/kext) dependency load failed.
  21. Hey guys, I'm new to this ans this is my first post... I have never had to post anything before, I always found the solution myself. But this time, I seriously need some help. My cousin has a Macbook Pro 2015 running El Capitan on it. So we were following step by step every single thing we saw in this youtube video : We got to the point where we had to boot from the USB. Everything was working perfectly. I had the apple logo, progress bar was going smoothly until it filled completely. And then I waited... And waited... And waited... nothing. Decided to try verbose mode. Got this : "com.apple.xpc.launchd[1] (org.ntp.sntp.117) 《Warning》: Service exited with abnormal code: 255" So... started doing what I do best.. Googling! I found SO MANY THINGS. Tried moving my kexts, tried putting some stuff in the boot args, so many things... now I'm just lost. It's an intel i5 processor, 8GB RAM, intel HD graphics, so basically all intel... Should work, no?
  22. Hi, i Have built a new PC, currently running windows 10 pro, and looking to dual boot OSX El Capitan. I have been patiently waiting to see what the state of play is regarding Skylake, and the 10 series chipset motherboards. Hardware wise it is a Skylake i5 6600K, Gigabyte GA-Z170X-UD5 TH motherboards, Apple airport native PCIe with Bluetooth 4, 32GB DDR4 2133, 2 x Samsung 850 Evo SSD, 2x Seagate 4tb Hybrid drives, and elderly maxtor HDD i use for backup purposes only. 2 x Gigabyte wind force 970 GTX 4gb. Now onto what I've found, the motherboard has been updated to F4 bios (last stable non beta at time of writing). I am trying to figure out what DSDT patches i would need to get a stable install of EL Capitan, I plan on using clover as the boot loader, and to dual boot win 10. There does not seem to be a lot of information regarding 10 series boards, and what is usually points to Asus 170 based boards. I would like to have as simple a list of required patches as possible. so i can enable them via MacIASL. I have extracted the DSDT and all 8.. yes 8 SSDT files. I want to have as "vanilla" a setup as possible. So far i have kexts to enable the Intel Ethernet i219 (mausi kext), latest FakeSMC, The USBInjectAll.kext to help enable the USB ports. I really want to get on with installing OSX onto this machine. So any pointers as to what else i will need to get a successful install done would be gratefully appreciated. I have a elderly mountain lion system running to do the editing of DSDT and build my installer from.
  23. Hello everybody, I am using El Capitan on WS Pro 11 (the same problem persists also in WS 12). I got everything installed just fine using the unlocker tool. However, I am also using a USB to serial device for work (this guy http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_UT232R-500.pdf). I have installed thee driver in OS X without problems. Now, when I am trying to pass the device through using WS11 (or WS12) I get: "USB Connection Error" The relevant part of log file is pasted below. I tried it on a macbook pro and it worked out the box, no driver necessary. I am a little baffled as to what is going on here. Any help would be greatly appreciated. Thank You! --------------------------------- 2016-03-03T09:57:54.866-05:00| vmx| I120+ A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message "The device can now safely be removed." 2016-03-03T09:57:54.866-05:00| vmx| I120+ --------------------------------------- 2016-03-03T09:57:54.882-05:00| vmx| I120: USBG: Created 1000000a04036001 2016-03-03T09:57:54.882-05:00| vmx| I120: VUsbUpdateVigorFieldsAndAutoconnect: New set of 8 USB devices 2016-03-03T09:57:54.882-05:00| vmx| I120: USB: Found device [name:Future\ Devices\ UT232R vid:0403 pid:6001 path:1/0/0 speed:full family:vendor virtPath:usb:4 instanceId:USB\\VID_0E0F&PID_0001\\FTUJHFW5 serialnum:FTUJHFW5 arbRuntimeKey:a ownerdisplay:OS\ X\ 10.10 version:2], connected to usb:1 port 2. 2016-03-03T09:57:54.882-05:00| vmx| I120: USB: Found device [name:Logitech\ USB\ Receiver vid:046d pid:c526 path:1/1/0/2 speed:full family:hid,hid-bootable instanceId:USB\\VID_046D&PID_C526\\6&2075393A&0&3 arbRuntimeKey:2 version:2] 2016-03-03T09:57:54.882-05:00| vmx| I120: USB: Found device [name:Holtek\ USB\ Keyboard vid:04d9 pid:0132 path:1/1/0/3 speed:full family:hid,hid-bootable instanceId:USB\\VID_04D9&PID_0132\\000000000008 serialnum:000000000008 arbRuntimeKey:3 version:2] 2016-03-03T09:57:54.882-05:00| vmx| I120: USB: Found device [name:Atheros\ Bluetooth\ USB\ Host\ Controller vid:0cf3 pid:e004 path:1/1/0/4 speed:full family:wireless,bluetooth instanceId:USB\\VID_0CF3&PID_E004\\ALASKA_DAY_2006 serialnum:ALASKA_DAY_2006 arbRuntimeKey:4 version:2] 2016-03-03T09:57:54.882-05:00| vmx| I120: USB: Found device [name:Apple\ Watch\ Magnetic\ Charging\ Cable vid:05ac pid:1392 path:1/2/0/4 speed:full family:hid instanceId:USB\\VID_05AC&PID_1392\\DLC507509PRG2DV4F serialnum:DLC507509PRG2DV4F arbRuntimeKey:5 version:2] 2016-03-03T09:57:54.882-05:00| vmx| I120: USB: Found device [name:Alcor\ Micro\ Mass\ Storage\ Device vid:058f pid:6362 path:1/2/0/7 speed:high family:storage instanceId:USB\\VID_058F&PID_6362\\058F63626476 serialnum:058F63626476 arbRuntimeKey:8 version:2] 2016-03-03T09:57:54.882-05:00| vmx| I120: USB: Found device [name:Texas\ Instruments\ USBtoI2C\ Solution vid:0451 pid:ca01 path:1/2/0/5/3 speed:full family:unknown,hid instanceId:USB\\VID_0451&PID_CA01\\6&17C2CCFE&0&4 arbRuntimeKey:7 version:2] 2016-03-03T09:57:54.882-05:00| vmx| I120: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth virtPath:usb:3 deviceType:virtual-bluetooth version:2], connected to usb:1 port 1. 2016-03-03T09:59:57.417-05:00| vmx| W110: USBGA: Failed to connect device 1000000a04036001, error (4) 2016-03-03T09:59:57.417-05:00| vmx| I120: Msg_Post: Warning 2016-03-03T09:59:57.417-05:00| vmx| I120: [msg.usb.connectFailedErr] The connection for the USB device "Future Devices UT232R" was unsuccessful. Driver error. 2016-03-03T09:59:57.417-05:00| vmx| I120: ---------------------------------------- 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Disconnecting device 0x1000000a04036001 2016-03-03T09:59:57.421-05:00| vmx| I120: USBG: Disconnecting 1000000a04036001, port:0 reservedPort:3AEADC0 2016-03-03T09:59:57.421-05:00| vmx| I120: USBGW: Disconnecting device: 3B6C2B0 id: 1000000a04036001 2016-03-03T09:59:57.421-05:00| vmx| I120: USBGA: device 1000000a04036001 already disconnected from host 2016-03-03T09:59:57.421-05:00| vmx| I120: VUsbUpdateVigorFieldsAndAutoconnect: New set of 8 USB devices 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Found device [name:Future\ Devices\ UT232R vid:0403 pid:6001 path:1/0/0 speed:full family:vendor instanceId:USB\\VID_0E0F&PID_0001\\FTUJHFW5 serialnum:FTUJHFW5 arbRuntimeKey:a version:2] 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Found device [name:Logitech\ USB\ Receiver vid:046d pid:c526 path:1/1/0/2 speed:full family:hid,hid-bootable instanceId:USB\\VID_046D&PID_C526\\6&2075393A&0&3 arbRuntimeKey:2 version:2] 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Found device [name:Holtek\ USB\ Keyboard vid:04d9 pid:0132 path:1/1/0/3 speed:full family:hid,hid-bootable instanceId:USB\\VID_04D9&PID_0132\\000000000008 serialnum:000000000008 arbRuntimeKey:3 version:2] 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Found device [name:Atheros\ Bluetooth\ USB\ Host\ Controller vid:0cf3 pid:e004 path:1/1/0/4 speed:full family:wireless,bluetooth instanceId:USB\\VID_0CF3&PID_E004\\ALASKA_DAY_2006 serialnum:ALASKA_DAY_2006 arbRuntimeKey:4 version:2] 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Found device [name:Apple\ Watch\ Magnetic\ Charging\ Cable vid:05ac pid:1392 path:1/2/0/4 speed:full family:hid instanceId:USB\\VID_05AC&PID_1392\\DLC507509PRG2DV4F serialnum:DLC507509PRG2DV4F arbRuntimeKey:5 version:2] 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Found device [name:Alcor\ Micro\ Mass\ Storage\ Device vid:058f pid:6362 path:1/2/0/7 speed:high family:storage instanceId:USB\\VID_058F&PID_6362\\058F63626476 serialnum:058F63626476 arbRuntimeKey:8 version:2] 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Found device [name:Texas\ Instruments\ USBtoI2C\ Solution vid:0451 pid:ca01 path:1/2/0/5/3 speed:full family:unknown,hid instanceId:USB\\VID_0451&PID_CA01\\6&17C2CCFE&0&4 arbRuntimeKey:7 version:2] 2016-03-03T09:59:57.421-05:00| vmx| I120: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth virtPath:usb:3 deviceType:virtual-bluetooth version:2], connected to usb:1 port 1. ---------------------------------
  24. Hey! :-) I really need some advice. I am not completely new to this but I admit I am far from being an expert. I tried various (about 7 or 8) How-Tos or Tutorials, read in-depth tips about partitions, UEFI, BIOS and what not ... but I am still too stupid to get this up and running! My Goal: Dual Boot OS X and Windows 10 with Clover UEFI (only) My Setup: 1x 250GB EVO 840 - Mac OS X 10.11.5 1x 120GB EVO 840 - Windows 10 GA-Z87N-Wifi, 16GB RAM, GA GeForce 760 OC, 1TB Seagate Barracuda (GPT, HFS+, Data only, disconnected), 250GB Maxtor HDD (GPT, HFS+, Data only, disconnected) Yesterday I was very close (I think): • I reformatted the EFI Partition on the OS X SSD and reinstalled the newest clover. • In OS X I reformatted the 120GB SSD to GPT with the main part formatted as FAT. • I double-checked the correct existence of the EFI partitions on the OS X SSD (disk0s1) and the Windows SSD (disk1s1). • I set my BIOS to UEFI only. • I (UEFI) booted to my Windows 10 Installer stick and installed Windows 10 on the 120GB SSD. • Windows installation finished flawlessly. • I booted once more into Windows via pressing F12 on my keyboard to see if it was working. • Then I booted into Clover ... • Now I have 4 or 5 NTFS entries, all of them left to the OS X entry, that all boot to nothing! • The last NTFS entry, the only one right to the OS X entries, started up Windows 10 correctly for two tries! I thought I did it ... well ... with the third try, booting to Windows turned into a black screen. Windows is starting up ... the circling dots appear ... then the screen turns off and it stops. When I reboot and do it again, the "Auto Repair" appears. Then again, Windows is booting to a black Screen. The next time "Auto Repair" appears again ... and so on and so on When I boot up Windows with "F12", selecting the Windows partition, everything seems to be working just fine. OS X is booting like a charme from Clover. What am I doing wrong? I work on this for over a week now and I am getting really frustrated. :-(
×