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 and SSDT
    • 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

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 175 results

  1. 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.
  2. Run Vanilla OS X El Capitan, Sierra, or High Sierra in VMware Workstation 12 on a Windows Host I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host. The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh. There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there…. I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program. Requirements Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack 1. On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder. 2. Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg 3. Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes…. 4. Open OS X terminal, then run the following commands to execute the script: cd downloads chmod +x CECI.tool ./CECI.tool 5. At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later. Update: @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362. Install and Patch VMware Workstation 12 on your PC 1. Download and install VMWare Workstation Player 12 or later 2. Download and extract Unlocker 2.0.7 or later to your USB stick… 3. Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt. Create an El Capitan Virtual Machine 1. Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”. Choose “I will install the operating system later” at the How will you install screen…. 2. Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version. By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder. 3. Under Specify Disk Capacity, you can leave the default 40GB or set a larger value. I personally store the virtual disk as a single file. Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12. 4. Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier. 5. To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file). The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad). 6. For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine. 7. Finally click “Play virtual machine” Installation of El Capitan Installation should be relatively straight forward, just following the prompts of the OS X installer: 1. Select language, agree to legal terms 2. Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended. I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan. 3. Quit DU and choose Macintosh HD to install El Capitan on. 4. After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot… 5. At the welcome screen, choose your country and keyboard layout. You can skip transfer information, location services and logging in with your Apple ID if you wish… 6. Create a User Account and select your Time Zone. You can skip sending diagnostics and usage data to Apple…. 7. Finally, you will arrive at the El Capitan Desktop. You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”. This will allow you to install VMware Tools…. 8. After rebooting, the VM can now be resized or run at full screen resolution. Audio and network/internet should also work OOB. SMBIOS Customization and iMessage Vars To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS - eg for an iMac 11,3 SMBIOS, you can enter the following lines.... smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation. The critical variables for iMessage/Facetime activation are MLB & ROM. By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk. If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0").... efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to "<=>?@A". Vanilla Mavericks and Yosemite The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite . Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware. With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie To create a Mavericks ISO on your desktop cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5... Enjoy Update for Sierra 10.12 The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13. Update for High Sierra 10.13 See post#30 & post#41 which describes how to build "Install macOS High Sierra.app" on the fly from installer files downloaded beforehand in /SharedSupport folder. CECI.zip CYI.tool.zip CMI.tool.zip
  3. 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
  4. 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
  5. Version v2.5

    33,147 downloads

    A Minimal and Super Fast Kext Installer and Repair Permissions for Mac OS This app is written in Swift Description : Drag one or several Kexts,Bundle,Plugin,PPP on the application (not a folder) Double Tap on "Drop your kext here" to select several Kexts,Bundle,Plugin,PPP on the application manually Change destination as desired (LE or SLE) Backup is created at Desktop Option to save log Choose auto-mode , when automode is not selected you have to press Install button after dragging files Use Drag-Drop or manually browse (click on drop section) files to select New option : Right click on kext , select open with EasyKextPro and rest will be automatically, you don't need to open app New option : Drag kext to EasykextPro icon and rest will be automatically , you don't need to open app Note : for Mac OS 10.12 and greatersudo spctl --master-disable for EL Capitan and Sierra disable SIP or use 0x03 For Yosemite use kext-dev-mode=1 Restart is required after installation
  6. Atasher

    Help! ASUS K501UX

    Hey guys, I am fairly new to the scene and recently successfuly installed El Capitan 10.11 on the Asus K501UX The specs are: Core i7-6500u, 8GB RAM, GTX 950M (DISABLED), HD520 Everything seems to be in good working order thanks to Ludwig Bartholomew for guiding me and helping me through the process. But, I keep recieving a Kernel Panic everytime I have the VoodooI2C kext installed for the trackpad to function. If I remove it everything works fine except for the trackpad which is the issue. Note: I also removed all of the LPSS kext files from the S/L/E to no avail. Any help would be greatly appreciated. Thanks in advance.
  7. Hey guys, This is a tutorial on how to fix (or at least try to fix) the second stage boot, when you're having these issues: missing logo and loading bar being displayed on the bottom left corner of the screen. Might or might not work for other issues. So proceed with caution. This is an issue that I experienced starting with early stages of development in Yosemite. Still continued in El Capitan. So this thread is primarily for these two versions of Mac OS X. Not sure it will work on earlier versions, cause I never tried it. So far it worked in Yosemite, El Capitan and Sierra. Please, note that I did not test this on all video cards. So it might or might not work, depending on that. Don't take this as a final solution for everything. Also, I'm pretty sure this won't work with iGPUs. So I would strongly suggest to look around for solutions if that's your case. This tutorial is not for multiple display setups! Please, don't use it for that! Especially not in iGPU + dedicated GPU combos. Known issue: if you're using the auto-login feature, try to disable it and use the regular login screen. Otherwise you won't get the second stage boot (confirmed as fixed in Sierra). This tutorial would have not been possible without the help and insight of: Pike R. Alpha cecekpawon Mirone Riley Freeman So all the credit goes to them. I just put this together based on my successes and failures. Succesfully tested with: NVidia cards: GeForce 210 GT 640 GTX 650 GTX 660 GTX 670 Superclocked+ 4GB - works partially (ok for 1080p, with CSM disabled, but no second stage in higher resolutions) GTX 750 Ti - works partially (ok for 1080p, but no Apple logo for second stage in higher resolutions) GTX 760 GTX 780 GTX 960 GTX 970 - works partially (ok for 1080p, and 1440p with CSM disabled, but no second stage in higher resolutions) ATI cards: Sapphire Toxic R9 270X Might work on other graphic cards, as well. But these are the ones that worked so far. Please, share if you got good results with another video card. Also, the same thing can be achieved by modding your DSDT. Unfortunately this thread does not make the object of that method, nor am I able to help you with that, since I really have no idea how to mod a DSDT, so far. Also, to be honest, this method seems a bit easier. Nonetheless, try this at your own risk! I'm not responsible for any damage that you might cause to your computer/components etc. Also, please, note that this tutorial is not perfect. I'm doing my best to make it as easy to understand as possible. Also, I'm opened to suggestions and I'm doing my best to improve this in the future. Still, it's not perfect. So keep that in mind. Suggestions are appreciated though. Please, note that, if you've got a video card with GOP UEFI Bios, you most likely don't need this tutorial in the first place. All you need is to disable CSM in BIOS (motherboard dependent). Note that, by doing this, only GPT drives will be loaded. So if you've got Windows installed on another drive, for example, you won't be able to select it anymore, if it's installed in "legacy" mode. With that being said, let's get to work. Prerequisites: Mandatory: a computer running Mac OS X Yosemite or newer Clover bootloader (changes are gonna be saved to the config.plist file) IORegistryExplorer v 2.1 (attached) gfxutil (attached) gfx_hex (attached) - script credit to cecekpawon Optional: Sublime Text Editor Clover Configurator a Windows PC for reading the graphic card's VBios version. So far, I couldn't find a way to do it from OS X. But if you know how to do it, please, share. I'll update this accordingly. An alternative (though not really the same thing) is this. an USB installer might come in handy, so keep one close by. Extra: If you want to try the modded Bootx64.efi (rev 3279), thanks to cecekpawon, featuring an option to easily enable/disable string injection in Clover (in case you're stuck outside your OS, and don't have a USB drive or something else to boot from), click here to get it. Please, note that this revision might not work with newer versions of OS X/macOS. You will need to replace the one in your EFI/EFI/CLOVER folder. If you want to revert to the previous one, you can either reinstall Clover, or make a backup of your current one before replacing it. I would recommend creating a single folder with all the necessary files and tools and putting it on your Desktop, just to have all the needed things in one place. Note: If you use a custom SSDT/DSDT, I would try first without it, and using Clover's patches instead, so that you minimize the risk for failure due to custom DSDTs. I don't use a custom DSDT, didn't test in collaboration with a custom DSDT, so I don't know if it will work. If you wanna try it this way, I would love to know your results. What to do: Step 1 (establishing the port): Open up your IOreg file (or just open IORegistryExplorer if you don't want to save it as a separate file), and search for "display". You should see something like this: Now, depending on your card, you might have more or less ports. The important thing is to note the one that has the AppleDisplay attached to it. In this example, the second port (B@1) is the one in use. So that's the one we need to set as default. Please, note that they start at 0, so first port is A@0, the second one is B@1 and so on so forth. Step 2 (extracting device-properties.hex): Open up a terminal window, navigate to the desktop folder you're using, and do this (make sure gfxutil is present into that folder): ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;' > "device-properties.hex" && ./gfxutil -s -n -i hex -o xml "device-properties.hex" "device-properties.xml" This will extract two new files into that folder: device-properties.hex and device-properties.xml Step 3 (modding the device-properties.xml): Open up the xml file using any text editor (I'm gonna use Sublime here) and ADD the number of ports you need for your card (the same number of ports, with the same name as in the IOreg) and the rest of the information, as described in the example below (use the attached xml as reference): Don't forget that the first port is port 0! In this example, we're using an MSi GTX 650 OC with 2GB of RAM, which has 3 ports, and we want to set as default port #2 (B@1). Attached you can find my device-properties.xml file, if you wanna use it as reference. The first section will set port B@1 as default. Change this according to your case. <!-- Primary display --> <key>@1,AAPL,boot-display</key> <string>0x00000001</string> Whereas on the bottom you can see regular values. Here we can set the amount of VRAM, the name of the card and the VBios version. <key>VRAM,totalMB</key> <string>0x00000800</string> // for 2048 MB or 2 GB of RAM <key>device_type</key> <string>NVDA,Parent</string> <key>model</key> <string>MSi GeForce GTX 650</string> // Name of your card <key>rom-revision</key> <string>80.07.35.00.04</string> //VBIOS version In my experience, these values are rather cosmetic than anything else. For an accurate version of your VBios, you can use either the Nvidia driver on Windows, or any hardware information software like GPU-Z, aida64 or nvflash. Here's a little table with hex values for different amounts of RAM. If you need other values than the ones specified in this table, please, ask. Also, if you spot a mistake, let me know so I can correct it. Amount of memory Hex value 128 MB 0x00000080 256 MB 0x00000100 512 MB 0x00000200 1024 MB (1 GB) 0x00000400 2048 MB (2 GB) 0x00000800 3072 MB (3 GB) 0x00000C00 4096 MB (4 GB) 0x00001000 5120 MB (5 GB) 0x00001400 6144 MB (6 GB) 0x00001800 7168 MB (7 GB) 0x00001C00 8192 MB (8 GB) 0x00002000 9216 MB (9 GB) 0x00002400 10240 MB (10 GB) 0x00002800 11264 MB (11 GB) 0x00002C00 12288 MB (12 GB) 0x00003000 13312 MB (13 GB) 0x00003400 14336 MB (14 GB) 0x00003800 15360 MB (15 GB) 0x00003C00 16384 MB (16 GB) 0x00004000 Once we're done modding, we're gonna save the changes and convert the xml file back into hex, using this command: ./gfxutil -i xml -o hex device-properties.xml device-properties.hex Step 4 (reading the modded hex): Unpack gfx_hex (attached) file into your working directory and double click to run it. It should output the content of your modded hex into a terminal window, and it should look something like this: Select and copy that code. After that, open up Clover Configurator and paste that hex code in Devices -> Properties section (see below) and check the box for Inject. You can also add this manually into the config.plist file, if that's more of your thing. Step 5 (setting up final arrangements): We're almost done. But, if your experience is the same as mine, at this point you only got the loading bar back centered. Which, of course is a step forward. But we're not quite there yet. So, to add the logo as well, we will check the boxes for Patch VBios and Inject EDID in Clover Configurator (Graphics section). You can inject your own EDID if you have one. Though, in my experience, Clover does a really good job in adding the correct one itself. So you don't really need to add a custom EDID. Just to use Clover's InjectEDID feature. Also, in my experience, you don't need CsmVideoDrv.efi for this to work. And I've got pretty similar results with and without it. So, if you have issues with it, you can try without it, and vice-versa. When it's all done, save the changes to your config. Now, I would highly recommend you to make a backup of your current config.plist from EFI/EFI/Clover/config.plist anywhere you want. You might need it later. When that's done too, replace the config.plist in your Clover folder with the one you just modded, and restart. Keep your fingers crossed (toes too). And hope for the best. If everything ok, you should have a pretty close to perfect second stage boot. If not, you might have nothing or an unbootable system. To fix this, boot from your USB installer, or use boot flag nv_disable=1 (for Nvidia cards), upon booting, and revert the changes. Or, if you already know where is the problem, fix that and restart. That's it. Please, let me know if it worked for you. gfx_hex.zip IORegistryExplorer.app.zip gfxutil.zip device-properties.xml
  8. 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!
  9. This thread is a walkthrough on how to install El Capitan. These are fully detailed instructions to make it easier for newbs. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW. THANKS I wanna start off by thanking the following guys whose efforts inspired me to proceed in making this guide: stinga11 for his implementation of the FakeCPUID hack, rehabman for his kexts, ammulder for his Skylake Starter Guide, chris1111 and DwarfVador for their configuration setup ideas, Slice for Clover, toleda for his audio solution and vit9696 for his audio solution, and shout outs to Pike for the IOAPIC Fix and assisting me with applying his ssdtPRGen.sh script SSDT generation method. • MY SPECS: 1. Intel Pentium Processor G4500 2. ASUS Z170M-PLUS Micro ATX Motherboard 3. Mushkin Enhanced ECO2 512GB SSD 4. Corsair Vengeance LPX 16GB (2x8GB) DDR4 5. HGST Travelstar 7K1000 1TB 2.5" 7200RPM HDD 6. Seagate Barracuda 3TB 3.5" 7200RPM HDD ST3000DM001 7. LEPA AquaChanger 240 Liquid CPU Cooler 8. Corsair Carbide 88R Mid-Tower Case 9. LG Electronics 14x SATA Blu-ray Rewriter 10. PNY GTX 960 XLR8 4GB 11. EVGA SuperNOVA 750 G1 750W PSU • WHAT YOU WILL NEED: 1. Mac OS X 10.11 El Capitan [from Mac App Store] 2. A computer running an Intel Processor 3. Access to OS X on VMWare (for Windows), Mac, or Hackintosh 4. A supported graphics card 5. Clover v2.3k r3354 and up 6. A USB flash drive at least 8 GB 7. Update your system with the latest BIOS • STEP 1: BIOS SETTINGS 1. Start off by entering the BIOS and accessing Advanced Mode. Go to Exit to select 'Load Optimized Defaults'. 2. Go to Boot and disable 'Fast Boot' and go to CSM (Compatibility Support Module) to enable 'Launch CSM'. 3. Back out to Boot and scroll down to Secure Boot and access Key Management to disable 'Secure Boot State'. In order to do so you must clear any installed keys [delete each keys]. a. Access Secure Boot again and set OS Type to 'Other OS'. 4. Scroll down to Hard Drive BBS Priorities to set boot sequence of the available hard disks. 5. Go to Advanced → System Agent (SA) Configuration and disable 'VT-d'. 6. Scroll down to access Graphics Configuration and set 'Primary Display' to PCIE and disable 'iGPU Multi-Monitor'. 7. Back out to Advanced and scroll down to access APM Configuration → 'ErP Ready' and disable it [equates to "S3 only, Suspend to Ram"]; the rest of the options should be disabled by default. 8. Go to Advanced → CPU Configuration and disable 'Intel Virtualization Technology'. 9. Scroll down to CPU Power Management Configuration to disable 'CFG lock'. 10. Go to Advanced → Onboard Devices Configuration and turn off 'Serial Port Configuration' and 'Parallel Port Configuration'. 11. Go to Advanced → USB Configuration and enable 'XHCI Hand-off'. 12. [Optional] Go to Ai Tweaker → Scroll down to 'DRAM Frequency' and set it to the specified frequency of your memory. 13. [Optional] Go to Tool → ASUS Overclocking Profile to save your BIOS settings profile [to a USB stick]. 14. Go to Exit, 'Save Changes & Reset'. • STEP 2: CREATING A BOOTABLE USB TO INSTALL OF EL CAPITAN 10.11 1. Clover and the OS X installer are placed on separate partitions on the USB stick. This guide will use 'diskutil list' in Terminal instead of Disk Utility to format the USB with GPT partitioning for Clover UEFI support. 2. You must determine its disk identifier before you can partition the USB. Plug the USB stick into a Mac (or Hackintosh), run Terminal and type 'diskutil list'. The following screenshot will serve as a reference: As you can see the the USB stick’s identifier is /dev/disk2. 3. Type the following entry into Terminal to format the USB stick (two partitions, via GPT): diskutil partitionDisk /dev/disk2 1 GPT HFS+J "OS X" R During the process the following occurred: /dev/disk2 GPT partitioning initiated by default EFI was automatically created remainder "OS X", HFS+J is partitioned 4. It resulted in the following screenshot: Close Terminal 5. We need to download and install the latest version of Clover (here) on the USB stick. a. Run the pkg, "Change Install Location" by selecting "OS X" (partition name) as the target of the install. Use the following settings below: Make sure that it shows "Installation Complete." NOTE: When installing to HDD select "Install RC scripts on target volume" and/or "Install all RC scripts on all other boot volumes" and "Install Clover Preference Pane". 6. You must copy your kexts to the EFI/ Clover folder. You can use EFI Mounter v3 when necessary to mount the EFI partition, just use "diskutil list" first to ensure you chose the right one for the USB stick. a. Remove EFI/CLOVER/kexts/10.6, 10.7, 10.8, 10.9, 10.10, leaving just '10.11' and 'Other'. b. Copy the required kexts FakeSMC.kext, NullCPUPowerManagement 1.0.0d2, VoodooPS2Controller.kext, and your ethernet kext (Intel I219-V) IntelMausiEthernet-V2.1.0d5 or AppleIntelE1000e 3.3.1 to the following directory: /EFI/CLOVER/KEXTS/10.11. NOTE: If you are having trouble getting Ethernet to work you can also try copying IONetworkingFamily.kext from S/L/E to /EFI/CLOVER/KEXTS/10.11 with your networking kext. 7. We must apply the following mandatory patches: a. IOAPIC Fix. Without this fix most things such as USB, SATA, ethernet, many PCI devices, sound devices, etc will not work. ○ Use a text editor or a plist editor like PlistEdit Pro to modify your config.plist manually. Add this <dict> entry to EFI/CLOVER/config.plist in the KextsToPatch array: <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>Skylake APIC fix, discovered by Pike R. Alpha</string> <key>Find</key> <data> wegQD7bw </data> <key>Name</key> <string>AppleAPIC</string> <key>Replace</key> <data> vhcAAACQ </data> </dict> </array> b. FakeCPUID patch. Since the Pentium is not supported in 10.11, the following CPUID will convert it into an Ivy Bridge CPU. Add this <dict> entry to the config.plist: <key>KernelAndKextPatches</key> <dict> <key>FakeCPUID</key> <string>0x0306A0</string> <key>KextsToPatch</key> </dict> or [Lynnfield] <key>KernelAndKextPatches</key> <dict> <key>FakeCPUID</key> <string>0x0106E0</string> <key>KextsToPatch</key> </dict> c. USB patch. It is required to raise the port limit in order to boot the USB installer. Otherwise garbled text with the message "Still waiting for root device" and a circle with a slash in the middle will appear onscreen. This process involves installing USBInjectAll.kext as well. Add this <dict> entry to the config.plist: <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>change 15 port limit to 30 in AppleUSBXHCIPCI</string> <key>Find</key> <data> g72M/v//EA== </data> <key>Name</key> <string>AppleUSBXHCIPCI</string> <key>Replace</key> <data> g72M/v//Hw== </data> </dict> </array> Be sure to copy USBInjectAll.kext to /EFI/CLOVER/KEXTS/10.11. d. SMBIOS. With the config file still opened in your text/plist editor, scroll down to SMBIOS section to add the following SMBIOS system definition: <key>SMBIOS</key> <dict> <key>Manufacturer</key> <string>Apple Inc.</string> <key>ProductName</key> <string>MacPro3,1</string> <key>Trust</key> <false/> </dict> NOTE: Macmini6,2, iMac13,2 and iMac13,1 support speedstep. You can also do this using Clover Configurator: In the SMBIOS section, click the magic wand to select a SMBIOS relevant to your hardware (e.g. iMac14,2) – and close the screen and File/Save. e. GUI. Here you indicate the theme you want to use that you installed by entering the title in the string. I chose to use "random" as shown below: <key>GUI</key> <dict> <key>Mouse</key> <dict> <key>DoubleClick</key> <integer>500</integer> <key>Enabled</key> <true/> <key>Mirror</key> <false/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <true/> <key>Theme</key> <string>random</string> </dict> f. Boot Flag. NVIDIA graphics cards especially 'Maxwell' currently lack support natively in OS X. To correct this problem in order to boot the installer it requires "nv_disable=1". In addition to that, it is necessary to use "-v" to monitor if any problems arise. Add this <dict> entry to the config.plist: <key>Boot</key> <dict> <key>Arguments</key> <string>-v nv_disable=1</string> </dict> g. SIP. Apple has implemented 'rootless' security or System Integrity Protection (SIP) (reference sources 1, 2, & 3) in 10.11 which restricts users from modifying system folders/files, and as a result it locks down system folders and files against hacks and root attacks, making the system safer. However, SIP must be disabled in order to install anything (i.e., kexts) into protected system folders. Add this <dict> entry to the config.plist: <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x3</string> </dict> h. Audio Fix. This Skylake board comes with a Realtek ALC887 audio chip. Realtek onboard audio device has been changed in ACPI to 'HDAS'. In order to use toleda's CloverALC (discussed further in this guide), you must add the following patch in the config.plist: <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Patches</key> <array> <dict> <key>Comment</key> <string>Rename HDAS to HDEF</string> <key>Find</key> <data> SERBUw== </data> <key>Replace</key> <data> SERFRg== </data> </dict> </array> 8. Preparing OS X partition. Download OS X v10.11.0 (15A284) El Capitan [Mac App Store]; "Install OS X El Capitan" will be in /Applications. a. Right-click "Install OS X El Capitan" → Show Package Contents → Contents → ShareSupport → Double click to mount "InstallESD.dmg". b. Once "OS X Install ESD" appears, use ShowHiddenFiles to show hidden files. c. Now you will see an image called "BaseSystem.dmg" appear. Mount it by right-clicking and opening it with DiskImageMounter... d. Open Disk Utility. Select and highlight the volume "OS X Base System", click "Restore" at the top-right, drag the volume into "Source" field, and drag the USB [OS X] partition (you already created) to the "Destination" field where you will restore the image: click the "Restore" button then "Erase"... e. After the process is complete, you'll now have (2) "OS X Base System" present in Finder. Eject the image "BaseSystem.dmg" and close Disk Utility. f. On the remaining volume "OS X Base System" (USB stick), go to System/Installation and delete Packages symlink. g. Open "OS X Install ESD" in a new Finder window, and copy the Packages folder to System/Installation folder inside "OS X Base System". h. Copy BaseSystem.chunklist, BaseSystem.dmg, AppleDiagnostics.chunklist, and AppleDiagnostics.dmg from "OS X Install ESD" and copy it to the volume root. i. Create a new folder named "Kernels" in System/Library on the USB stick. Use Pacifist v.3.2.17+ to extract "kernel" from "OS X Install ESD/Packages/Essential.pkg [/system/Library/Kernels/kernel]" and place "kernel" into System/Library/Kernels/ location. Or download the vanilla version here. j. Delete following kexts from System/Library/Extensions/: AppleIntelCPUPowerManagement.kext and AppleIntelCPUPowerManagementClient.kext. k. Use ShowHiddenFiles to hide the hidden files, and quit the application. l. With the USB installer ready, remember before restarting system to change boot priority of USB stick to first to install El Capitan on the hard disk of choice. m. Once installer is finished, it will automatically restart the system. n. Now reboot from the USB installer and select the drive where you installed El Capitan at the boot menu screen and use boot flag nv_disable=1 to log in. • STEP 3: Mac OS X 10.11 Post-Installation 1. As the system is loading, you'll be prompted to the Mac OS X Welcome screen. a. Select your country then click "right arrow" to go to the next screen. b. Select "My computer does not connect to the Internet." c. Select "Don’t transfer any information now." d. Do not "Enable Location Services on this Mac" e. Agree to "Terms and Conditions." f. Enter your name, password, and hint and Continue. g. Confirm "Diagnostics & Usage" h. Wait a moment for the OS X desktop to load. i. When prompted to back up any disk with Time Machine, click on the "Don't Use" button. • STEP 4: Mac OS X 10.11 Post-Installation (Continued) 1. Mount the EFI partition of the USB stick with EFI Mounter v3 and copy the 'EFI' folder to the EFI partition of El Capitan boot disk. 2. Install Clover v2.3k on the El Capitan install HDD partition you plan to boot from. In addition to the settings configured earlier, select "Install RC scripts on target volume" and "Install Clover Preference Pane" when installing to the HDD. Installing RC scripts enables nvram variables required for iCloud and other services. It processes logs that are located in /Library/Logs/CloverEFI. You can also type bdmesg > Desktop/boot.txt in Terminal to get them manually. 3. Edit the config.plist from your boot disk in EFI/CLOVER/ by adding the following <dict> entries: a. Change boot flag to "nvda_drv=1" without "-v" <key>Boot</key> <dict> <key>Arguments</key> <string>nv_drv=1</string> </dict> NOTE: Ensure you have updated to the latest version FakeSMC kext. If your 'hack' happens to instant reboot loop randomly like mine did, to fix it I added cpus=1 in the boot arguments in Clover config.plist. Boot arguments: nvda_drv=1 cpus=1 SMBIOS: iMac14,2 system definition Situations may vary when accessing 10.11 with GTX 960 Video output should be connected through HDMI b. Hide UEFI partitions. To hide internal UEFI (i.e., "Boot Windows from Recovery", "Boot Windows from EFI") you have to use Scan/Legacy=false: <key>GUI</key> <dict> <key>Scan</key> <dict> <key>Legacy</key> <false/> </dict> c. Designate name of boot menu entries (Renaming Mac/Windows). In the Clover bootloader menu you will notice all EFI Windows partitions labeled "Boot Microsoft EFI boot menu from EFI [or SYSTEM]". The Windows partition is called EFI but there's also a Mac partition called EFI which is hidden by default in the Clover boot menu so it's a nonfactor. The volume names are what Clover shows by default. In order to change what the Clover boot menu shows your volume name to be you will have to specify its details under GUI/Custom/Entries section in your config.plist. There are 3 <key> tags necessary to edit in this section: Volume, FullTitle, and Type. You can refer to my personal settings below for help. E.g., in my config.plist, my OS X volume is called "ELCAP" because that's what I named the partition I installed OS X on. It can also be seen as a bootloader screen entry as "Boot Mac OS X from XXXXXXXX" where XXXXXXXX is the volume name. "FullTitle" is the name you want the entry to say, i.e.: OS X 10.11 El Capitan. "Type" is where you indicate what type of OS it is, i.e.: OSX (or Windows). Tags such as "Hidden" and "Disabled" are self-explanatory, while the "NoCaches" tag designates whether you want to boot without caches. NOTE: Adding "InjectKexts" causes infinite loading on the Apple logo screen. NOTE: Although you’re able to indicate if the "VolumeType" you are using is Internal, External, Optical or FireWire, I have found through tests that after adding the "VolumeType" tag for the OS X volume in the config.plist followed by restarting my system, it would initiate a constant reboot loop, making my system incapable POSTing and requiring a CMOS reset to fix: YOU HAVE BEEN WARNED. <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Volume</key> <string>EFI</string> <key>FullTitle</key> <string>Windows 10</string> <key>Hidden</key> <false/> <key>Disabled</key> <false/> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Volume</key> <string>ELCAP</string> <key>FullTitle</key> <string>OS X 10.11 El Capitan</string> <key>Hidden</key> <false/> <key>Disabled</key> <false/> <key>InjectKexts</key> <false/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSX</string> <key>VolumeType</key> <string>Internal</string> </dict> </array> </dict> d. Remove Recovery partition. Deleting and merging a partition with 'diskutil' from the command line is the most precise method to remove the partition since it targets the recovery disk directly and merges it with the full El Capitan partition. ○ Launch the Terminal and type the following into the command line: diskutil list ○ This will print out your drives partition scheme and look something like this: ○ Look for "Recovery HD" and see which identifier it is uses. In this screenshot it’s disk2s3. ○ To remove that partition we use the following command (you can also use the volume name): diskutil eraseVolume HFS+ Blank /dev/disk2s3 ○ The partition will be erased. You’ll now have a blank partition sitting around, so you’ll want to merge that with your other El Capitan partition: diskutil mergePartitions HFS+ ELCAP disk2s2 disk2s3 ○ This will merge the two partitions, with disk2s2 absorbing the space from disk2s3 and expanding, it causes data loss so don’t expect this to preserve anything. 4. 10.11.0 breaks compatibility with native graphics kexts so you will not be able to boot without nv_disable=1 flag. a. Download and install NVIDIA Web Driver 346.03.02f02 to enable NVIDIA Graphics Cards because they won't work OOB without them. NOTE: Remember to go to the NVIDIA Driver Manager menu bar at the top, change the settings to use Web drivers. Changes will take effect after restart. 5. Reboot without the USB installer and choose the El Capitan boot disk. 6. Download CUDA 7.5.20 drivers (increases GPU computing performance) needed for 10.11.0 support and install. 7. [OPTION 1] Install AppleALC to enable native audio by injecting the layout id supported for ALC887 through dynamic patching without modifying any kexts. Audio will no longer be affected after each OS X update and SIP can remain enabled. More details here. NOTE: AppleHDA must be native, original and unpatched. a. Mount EFI partition and add the following entry under Devices/Audio in the config.plist to inject working layout id 11 (or 13 or 1). <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <integer>11</integer> </dict> b. Download the latest version of AppleALC and copy it to CLOVER/kexts/10.11 or CLOVER/kexts/Other. NOTE: Rebuild kext cache if you have removed a modded AppleHDA to replace it with a native one by using Kext Utility or 'force rebuild cache' in Terminal: sudo –s sudo touch /System/Library/Extensions 8. [OPTION 2] Install the following patch associated with Realtek ALC887 AppleHDA Audio (by Toleda): a. Mount EFI partition, verify "Disable SIP" entry CsrActiveConfig=0x3 is in config.plist. b. Download audio_cloverALC-110.command.zip and extract "audio_cloverALC-110_v1.0q10.command". c. No edits made to any native AppleHDA.kext file, 2-4 files added to Resources folder. NOTE: There may be noticeable pops before starting playback which is caused by OS X putting the audio codec to sleep. Disable AFGLowPowerState in config.plist with following <dict> entry: <key>Devices</key> <dict> <key>Audio</key> </dict> <key>AFGLowPowerState</key> <false/> </dict> If popping is still exists after using the method above, try using antipop. NOTE: There may be noticeable distortion after around 2 minutes of audio playback. Update to the latest version of Clover (or downgrade to ver. 3354) and add UseARTFrequency=false entry in the config.plist: <key>CPU</key> <dict> <key>UseARTFrequency</key> <false/> </dict> <key>Devices</key> <dict> 9. Create a DSDT??? (More to come later) 10. [OPTION 1] Create a SSDT (Secondary System Description Table) to configure the maximum clock speed. a. Download Pike's ssdtPRGen.sh script which should auto-copy into your home directory, 'Volumes/Users/<username>' folder. Open Terminal and type the following: curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/Beta/ssdtPRGen.sh b. Next, set the execute/search bits: chmod +x ~/ssdtPRGen.sh c. Run ssdtPRGen.sh script for first time without any arguments and let it download all the data that you need: ./ssdtPRGen.sh d. The Skylake.cfg with Pentium information should have already downloaded. e. Once finished you will have the ssdt.aml on the ~/library/ssdtPRGen/. Move it to /EFI/CLOVER/ACPI/patched. NOTE: If you come across issues try the following: ○ Use Terminal to ensure Skylake.cfg is in the 'Data' folder by typing: open ~/library/ssdtPRGen/Data ○ You can remove any previously generated and downloaded script file by typing: sudo rm -R ~/Library/ssdtPRGen ○ You can rerun another freshly downloaded ssdtPRGen.sh script with your processor type: ./ssdtPRGen.sh ○ For additional help see also: ./ssdtPRGen.sh -help 11. [OPTION 2] Create a SSDT (Secondary System Description Table) to configure the maximum clock speed. a. Download the Pike’s script v14.1 (modified for i-core processors) and put it on your desktop. Use it only for the PC it is running from. The script reads some information specific about your CPU and its number of cores. b. Open Terminal and type "sudo" then leave a space and drag the script file into the Terminal window then leave a space and type in the Turbo Speed (Maximum Turbo Frequency) for your processor and then press enter. e.g., Intel Pentium G4500 type code: sudo /Users/"YourUsername"/Desktop/ssdtPRGen.sh -TURBO 3500 Type your password when prompted and press Enter. c. Ignore the following "Error: Unknown processor model ..." since the CPU is unsupported. d. A decompiled file called SSDT.aml will generate in a hidden folder "tmp". Type "open /tmp" (no quotations) to reveal its location. e. Mount EFI using EFI Mounter v3 and place SSDT.aml into /Volumes/EFI/EFI/CLOVER/ACPI/patched/ 12. Installing the following kexts/widget is optional. Mount the EFI partition to copy the kexts into the /EFI/CLOVER/KEXTS/10.11 folder. Install the widget using Launchpad → Dashboard: ○ HWSensors 6.19.1406 Binaries (with FakeSMC): Helps you monitor CPU, memory, disks, network, temperatures, fans, load/uptime, and processes. ○ Install iStat Pro 4.92 r2, a highly configurable widget that lets you monitor every aspect of your Mac including CPU, memory, disks, network, battery, temperatures, fans, load & uptime and processes. • STEP 5: Updating to 10.11.4 1. Download and install OS X El Capitan 10.11.4 Combo Update. 2. After restarting, booting from the El Capitan partition presents the following error: OsxAptioFixDrv: Error - requested memory exceeds our allocated relocation block a. This is caused by the lack of support for the OsxAptioFixDrv-64 in 10.11.4 which is intended to fix memory map issues on most UEFI systems, mainly in AMI BIOS. b. Plug the USB installer into another Mac (or Hackintosh) and reinstall the latest version of Clover (here) on the USB stick. Be sure to select the checkbox OsxAptioFix2Drv-64 instead of OsxAptioFixDrv-64. c. Once it completes, mount EFI of the USB stick using EFI Mounter v3 and remove OsxAptioFixDrv-64.efi from /EFI/CLOVER/drivers64UEFI/. 3. Reboot using the USB installer and choose the El Capitan install drive. Mount EFI of the El Capitan partition and remove OsxAptioFixDrv-64.efi and copy OsxAptioFix2Drv-64.efi from the USB stick to /EFI/CLOVER/drivers64UEFI/. 4. Reinstall audio by patching AppleHDA with audio_cloverALC-110.command.zip [for OPTION 2]. 5. Accept the popup window that prompts you to download and install the latest the NVIDIA Web Driver 346.03.06f01 to proceed. Download CUDA 7.5.26 drivers needed for 10.11.4 support from NVIDIA and install and reboot. • STEP 6: Updating to 10.11.5 1. Download and install OS X El Capitan 10.11.5 Combo Update. 2. After restarting, accept the popup window that prompts you to download and install the latest the NVIDIA Web Driver 346.03.10f01 to proceed. 3. Download CUDA 7.5.29 drivers needed for 10.11.5 support from NVIDIA and install and reboot. 4. Reinstall audio by patching AppleHDA with audio_cloverALC-110.command.zip [for OPTION 2]. • STEP 7: Updating to 10.11.6 1. Download and install OS X El Capitan 10.11.6 Combo Update. 2. After restarting, accept the popup window that prompts you to download and install the latest NVIDIA Web Driver 346.03.15f01 / NVIDIA Web Driver 346.03.15f02 to proceed. 3. Download CUDA 7.5.30 drivers needed for 10.11.6 support from NVIDIA and install and reboot. 4. Reinstall audio by patching AppleHDA with audio_cloverALC-110.command.zip [for OPTION 2]. config-WORKING for G4500 boot.plist.zip EFI-Mounter-v3.zip ssdtPRGen.sh-master.zip
  10. 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,
  11. Apple changed something in the CoreWlan.framework and the trick with airportd from Snow Leopard doesn't work now. I wrote a simple menubar app like the Apple's WiFi menu. This menubar app uses AirPort.framework from Snow Leopard instead of CoreWlan.framework and Apple80211.framework from El Capitan. Here is my step-by-step guide how to make Wi-Fi work: Put your working IO80211Family.kext from Snow Leopard into /System/Library/Extensions. Disable airportd: sudo -i (enter root password) cd /System/Library/LaunchDaemons/ launchtl unload com.apple.airportd.plist mv com.apple.airportd.plist com.apple.airportd.plist-disabled Put AirPort.framework into /System/Library/PrivateFrameworks/ Rebuild kext cache. Repair permissions. Reboot There is also a console version of the menubar app with some advanced options like iwconfig from linux. For example you can set a different locale code to get more channels, change power save mode or manually set transmission rate. Credits: Jonathan Levin - http://newosxbook.com/articles/11208ellpA-II.html Comex - https://gist.github.com/comex/0c19c1b3fa569f549947 Files.zip Version 2.0 (Requires Airport.framework from the Files.zip above): Aerodrome v2.zip Here is a build with default Apple82011.framework. Use it if you have OOB wlan and want to change locale code etc. aerodrome-apple80211.zip
  12. 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!
  13. 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.
  14. 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.
  15. 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.
  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. So I boot OS X El Capitan from my Clover USB Drive, and instead of being presented with the option to Install, it gives me the option to reinstall. Odd if I do say so myself. OS X has never touched any of the drives in my PC, save for InstallESD.dmg, so it shouldn't be telling me to REinstall it. Anyway, I tried to use that option and it gives me a message saying that it will now connect to Apple's Servers for something, then it presents the error in the title ("Could not find information for this mac, contact apple care") Any thoughts?
  18. Ho trovato questa scheda mini PCi-e adatta a notebook che fa sia wifi che bluetooth con driver per MacOS. Chipset : Qualcomm Atheros AR9285 + AR3011 Qualcuno la conosce? Funziona sia il wifi che il bluetooth? è possibile collegare il mouse al bluetooth? http://www.ebay.it/itm/111624555780?_trksid=p2060353.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT Grazie Aggiornamento : con due kext da trovare on line ( lo posterò anche qui ), funziona alla grande: sia il Wi-Fi ( riconosciuta come airport ) che il Bluetooth !
  19. 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.
  20. 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 ?
  21. Update (4/25/16): With the guidance of Slice, I was able to reset the flags on my EFI(disk0s1) partition. Now Clover installer/updater correctly mounts and updates the bootloader in the EFI partition. 1. I dowloaded the most current gparted (v2016) and there is now a new flag called ESP in addition to the boot flag on the disk0s1 EFI partition. 2. Apparently, the older gparted (v2009-2010) I was using wasn't showing me all the flags on the partition. 3. I double checked the technical specs for OSX EFI partitions and there is supposed to be those two flags (boot and ESP) when using gparted to view the drive. 4. I turned both flags off and then rewrote them both back by turning them back on within gparted for the EFI partition (disk0s1). That seemed to do the trick. There may have been some data corruption on the boot sector area. 5. The most current version of clover installer/updater v3438 was able to now mount my EFI partition and update the bootloader correctly. The other possibility is that there was a slight change to the clover installer that resolved my drive mounting issue within the clover installer package. Either way, I am relieved.--------------------- I have been having issues with Clover (most current and slightly older versions) not wanting to install to my hidden EFI partition on my SSD OSX installation drive (disk0s1). I didn't have this issue when i was running Yosemite. Clover updated as it should to my hidden EFI partition and I used UEFI boot without problem. I decided to update my system to El Capitan doing a clean install. I wiped my SSD using Disk Utility. I first errased the drive, reformatted to a new partition (GUID HFS) and created my UEFI USB El Capitan loader. I installed El Capitan to the SSD without issue. After installation, both the EFI and the OSX partition where created properly along with the recovery partition. I rebooted using the UEFI USB and configured OSX after the welcome screen. I then tried to run the latest version of Clover for the UEFI installation and it failed as it couldn't open the EFI hidden partition and install the kexts and Clover. It basically failed to mount the EFI partition and install to the EFI partition. I even mounted the EFI partition on disk0s1 where my OSX install was on my SSD and it didnt create any files or folders in the partition. I did create an EFI folder with everything in my root OSX partition instead (very odd). I double and triple checked that i selected UEFI as I always do and that the drive was indeed the OSX SSD installation drive. I manually mounted disk0s1 EFI partition and it had nothing from clover in it. I wiped the EFI partition and tried again without success. I reloaded my GA-Z97MX Gaming5 firmware v6 again and it still failed to load clover into the EFI partition. It did create a EFI folder in my root directory for OSX with all the correct files but i couldn't boot to it using UEFI (YES- i was selecting UEFI from the menu, i have done this successfully on Mavericks and Yosemite many times before) If I move the folder and files from the root EFI folder to the EFI partition, I can boot OSX using UEFI I used gparted to reformat the SSD and try to do another fresh install of OSX again thinking that Disk Utility didn't get rid of all the old bootloader info. Clover couldn't mount the hidden EFI partition on disk0s1. I could do it manually though. I manually mounted the EFI boot partition for my SSD and moved all the clover/mulitbeast files over there. I was able to again boot UEFI SSD El Capitan. When I try to update clover, it doesn't open the hidden EFI partition or update the files in it. It does, however, create an EFi folder in my OSX root with the new Clover bootloader files there. ------------------------------------------------ Original post: Background facts: I have done this successfully many times with both Mavericks and Yosemite in the past using the Clover UEFI booloader 1. I clicked uefi 2. The hidden EFI partition exists on my SSD (disk0s1) OSX install 3. I tried reformatting the drive using gparted and Disk Utility as was outlined in the guides 4. I tried erasing just the EFI partition and changing the file structure 5. I reloaded my GA-Z97MX Gaming5 v6 firmware 6. I did check off the box for loading Clover as uefi 7. I told Clover to install into the ssd OS X drive (I doubled and triple checked this) 8. I booted everything using Uefi from both my F12 option and BIOS option - I don't Legacy boot 9. I tried the most recent versions of Clover. I also tried an older version of Clover for curiosity. ---------------------- Nothing I do can seem to get Clover to load to the hidden EFI partition on my SSD OSX install (disk0s1) Does anyone have an idea what I need to fix to get Clover to recognize, mount, open, and install to my EFI partition on my SSD (disk0s1)?
  22. 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. ---------------------------------
  23. 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
  24. 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
  25. 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. :-(
×