Jump to content

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

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • 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


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 161 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. 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
  3. Hi, this tutorial is about running your physical hackintosh installation in Windows. It's not about setting up a new OS X VM. As always it's very simple once you know, but it however took me a while to figure out the settings, especially using IDE in the VM and using the Clover/EFI partition or not. Luckily, it turned out we have to skip it, so we can leave Clover (or any other bootmanager) untouched. What's the point? If you have to do tasks in Windows, be it mining bitcoins, 3D-rendering, gaming or simply work with a windows-only software, you probably at the same time miss your OS X. The advantages over a simple new virtual machine running with your personal setup are many: Imagine you can use all your data, listen to your iTunes library, use your installed and configured programs and work with your settings. It also comes in handy when you messed up your installation for some reason and want to conveniently fix it. And last but not least don't forget you save the 25GB minimum space for a virtual disk what is probably not sooo insignificant since (I assume) most of us already switched to SSDs and only a few may have picked the models above 500GB because they are still pricy. tl;dr Gain advantages by hooking up your existing Hackintosh installation in a VM and work in your personal OS X environment whenever you like, even under Windows. If you have High Sierra with APFS installed it will most likely not work (yet), because Paragon and probably VMWare don't support the filesystem (yet). That being said, let's get started: 1. Preparing Instructions - do all possible reboots as required while installing - install Paragon HFS+ 11 or above (buy or know where) - install VMWare Player (free for private use) - install Unlocker from Insanelymac (free) 2. in VMWare, set up a new virtual machine - choose "I will install the operation system later" next > - choose "Apple Mac OS X" and "macOS 10.12" next > - choose "Store virtual Disk as a single file" next > and next> - choose 5GB Maximum disk size (we delete it later) and pick "Store in a single file" next > - Finish 3. in VMWare, configure your new machine - click on "Edit the virtual machine settings" - delete your new 5GB virtual Hard Disk (SATA) - click Add... on the bottom, select Hard Disk - select SATA (IDE works, too but I'd prefer SATA in 2017) (UPDATED) - pick "Use a physical disk" - select your harddisk with your OS X installation on it and pick "use individual partitions" - now do not select your UEFI partition, select the partition with your OS X: Example: My Sierra is on my PhysicalDrive 3 which I selected before. As we all know, the EFI partition is always the first partition (0), so my OS X (and probably yours, too) is on the second partition (1). So I check partition 1 and click next and finish. - if all is set and done, close VMWare. 4. check your VMWare .vmx file - replace the green parts with your data and move to "C:\Users\YourWindowsUsername\Documents\Virtual Machines\YourVM-Name\" - open yourVM-name.vmx with the Windows Editor and add the folowing lines only if they are missing: smc.version = "0" firmware = "efi" Click save. 5. VMWare optimization I choose half of my physical RAM, maxed out the graphics RAM and choose half of my physical CPU-Cores in the VM settings. 6. Finalize (UPDATED) Go to your VMWare program folder, right-click on vmplayer.exe and under Preferences > Compatibility > check the "Run as administrator" checkbox on the bottom. And that's it! Screenshots for reference. Now you have your OS X install available in Windows, too. If it asks you for updating the VMWare Tools, click yes or install them with one of the tools in the download section here on insanelymac. You can also add other Harddrives to your VM. What will not work: VMWares unity-mode in Windows - it's not supported for OS X yet. Gaming, the graphic is slow-ish but enough for coding, office, music and all basic tasks.
  4. Version


    for Chipsets : RT2770; RT2870; RT3070; RT3071;RT3072; RT3370;RT3572 ;RT3573; RT5370;5372;RT5572;MT7610;MT7612;MT7650; MT7662; ;RT8070;RT9707
  5. The is the Post-Install topic following the Ryzen Clover Installation Guide for macOS Sierra. If you have yet to install Sierra on your Ryzen machine, check out that thread for help installing. Here we can discuss post install troubleshooting such as well known issues with NVIDIA Drivers, audio interfaces, etc. Here is one workaround for audio that I am using - My audio was not working and I spent days trying to get it to work (ASUS Prime X370 Pro) to no avail. Eventually I bought this for $10 and it worked immediately with no drivers or setup: https://www.amazon.com/gp/product/B072BMG9TB/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1 One question for starters, I am using a Radeon R9 280x with no graphics injection. If I put my Ryzen build to sleep, it changes power states correctly. When Powered back on, the monitors don't turn on. I don't know if this is related to the GPU, or just an issue in general, but in any case I would appreciate any help!
  6. Here are my Specs Processor: i7-4700MQ RAM:6GB HDD : 1TB Graphics: Intel HD Graphics 4600(QE/CI Enabled) AMD Radeon M265 Audio Card :Conexant CX20757 ​Method used to patch audio: AppleHDA Patcher's generated HDAEnabler And AppleHDA Kext Audio Works Excellent... But the microphone won't work ... even if it shows up in the input section of sound preferences..... plz help Laptop is Lenovo G510 (i7 Version)
  7. Want to add a microphone to my towers front mic ports, something really small and unobtrusive multi directional and could pick up my voice anywhere in my room?
  8. Hey Guys i've tried to install Sierra on a computer that already has Yosemite on it , But when i tried to boot the installer i get this kernel panic . The reason why i'm trying to install sierra is that i have a GTX 1050 , and the Pascal web drivers are only For Sierra . Help Please . Specs : CPU : i5 3330 3 GHZ GPU : MSI Geforce GTX 1050 RAM : 8GO 1333 MHZ MB : ECS H61-H2 M6 UEFI BIOS
  9. Hello Everyone, I tried to install macOS Sierra on HP Pavilion 17 Notebook: Intel Core i5 CPU 4210U Intel HD4400 Nvidia 840M Ram 12GB DDR3 SSD 480GB I was already running El Capitan and Windows 10 dual boot using clover bootloader. I am directly downloaded macOS Sierra and open it for installation. I updated the latest clover and add FakeSMC.kext, after installation start process computer automatically rebooted, On clover boot screen i choose Boot macOS Install from Macintosh SSD. Its start installation, when process remains almost 5 minutes its suddenly rebooted and appears with a boot problem as screen shots added in attachment. Even i have Bootable clover El Capitan USB but when i select boot with UEFI USB Drive it is also not booting and showing the same error. Please i need your helps to sort it out. Thank You
  10. Hello! I finally succeeded. I have an old 80GB SATA hard disk which I use to experiment with Mac OS. I had a Mac OS X 10.11 El Capitan installation complete with Office and other applications. Using Clover 3322 in iATKOS EC installer I managed to successfully boot it from within a virtual Mac in VMWare Workstation 10 (patched to support Mac OS). The SATA disk was connected to a SATA-USB adapter and then connected to the virtual Mac as a USB disk. I downloaded Sierra, but instead of creating a USB installation medium I stupidly tried to just upgrade by running the setup. The installation didn't succeed of course but while connecting and disconnecting the USB installer and the USB disk amd forcing several resets I finally screwed the partition and could not boot either in VMWare or natively in my PC. So I reinstalled El Capitan natively and then booted within VMWare. I successfully did all the upgrades up to version 10.11.6 and then downloaded Sierra again. This time I used Pandora's Box to create the USB installer. I booted the USB installer in VMWare and I installed 10.12 Sierra. For some reason it took a couple of hours, but it finally succeeded! It even made the sound and graphics work out of the box without having to install the VMWare Tools! Thank you for creating Pandora's Box! Pity I now have to reinstall all my applications...
  11. Thestral

    Sierra su Asus X54C-NS92

    Salve, da qualche anno sono possessore di un ASUS X54C-NS92 e mi piacerebbe provare OS X, sono alle primissime armi quindi vi chiedo aiuto per eseguire questa cosa, il mio PC ha un Intel Pentium B960(so che non è nativamente compatibile ma spero che si possa fare qualcosa), 6GB di ram DDR3, come scheda wifi ho una chiavetta esterna compatibile con OS X, per il touchpad non mi interessa dal momento che è rotto fisicamente. Cosa ho a disposizione: OS X su VMWare, quindi vorrei sapere con quali settaggi fare la chiavetta (Bios legacy) e come far andare il processore. Grazie in anticipo
  12. Hi! Yesterday I downloaded Sierra and El Capitan retail and put it to my usb using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]. (I have tried transmac also, same result). I booted to my clover but unable to reach the installer. But when I use distro (niresh yosemite) I can install it. But yosemite was laggy so I want to try another. Boot flags I have tried: GraphicsEnabler=no GraphicsEnabler=yes cpus=1 /amd64 -x -F npci=0x2000 and 0x3000 My specs AMD Radeon 8180 HD Graphics @1GHz, 2GB RAM. The usb i used partitioned with GUID partition table. I tried on another laptop (amd and intel) and had the same result My verbose mode said in picture attached. After showing that it just shut down and booted again into clover. Sorry I haven't attached the photo
  13. Hi all. I'm after a bit of help with installing Sierra GM. The system this post pertains to is an EX58-UD5 with Nehalem i7 920 and Nvidia 480 GTX, all working perfectly since the snow leopard days. Updates have always been a case of clicking update and waiting, until now that is! I'm running 10.11.6, I've updated clover to r3726 (latest build from sourceforge), I've downloaded Sierra from the app store, clicked install, rebooted, selected the install media. Grey screen with beach ball/spinner. I can move the mouse, the system sleeps and wakes but just doesn't bring up the installer. So I updated fakesmc to 6.20.1410 (the latest I could find from HWsensors). Same issue This is usually what happens when fakesmc doesn't get loaded, but seeing as the install media is read only I can even load fakesmc through single user mode on the way in. I can't even run kextstat as it doesn't exist on the installer. I then created a USB with createmedia --nointeraction, looked on the USB and theres no sign of S/L/E or L/E to dump fakesmc into. So I put my working EFI folder (with updated clover and fakesmc, boots 10.11 ok) onto the USB. I also put my dsdt on there in the root and in ACPI/patched. Same issue, grey screen. I have tried booting with nv_disable=1 which results in the same grey screen with beach ball/spinner but at a reduced resolution. So what I plan to do next is to recreate the installer using the restore method and put fakesmc somewhere that is loaded by the kernel, but before I do I wanted to ask, does this sound like a fakesmc problem or something else. I can't see why clover would not be injecting fakesmc but I can't run kextstat from single user mode as it doesn't exist on the installer. Help!
  14. Hello to all, I have a problem with the installation of Os Sierra on vmware virtual machine. I see the error: "The CPU has been disabled by the guest operation system", and the O.S. doesn't start. How I can fix it?
  15. pmdcoleslaw

    Very Odd Network Behavior

    I just did a clean install of Sierra and set everything up. All is working well, but I noticed something very strange. I am dual booting a Dell OptiPlex 7010 with Windows 10 on an SSD and Sierra on a separate HDD. While in windows my network is proper. I am behind a firewall and use the firewall DNS server settings and have the proper IP scheme. However when I boot into Sierra, I get a completely different IP scheme from the router DNS server that is on the outside of the firewall. I'm connected via a single ethernet line behind the firewall, so I cannot for the life of me figure out how my hackintosh is bypassing/skipping/passing through the firewall and going to the main router for DNS. This obviously causes problems, because I can't get to anything on my network from the Sierra build. This was not an issue on El Capitan before I wiped the drive and fresh started with Sierra. Any help or insight would be much appreciated.
  16. Anyone can help me? I've got brightness full after restart/boot. I've been try to reinstall clover with emuvariableUefi-64.efi and install RC Script but its still same. I even set my Nvram to Always in Clover Prefpane. I dont know i think all asus laptop has same issue with me, Any suggestion?
  17. (Mistakenly posted in 'Installation Guides' at first) Hi, A couple of weeks back I took the plunge and upgraded my system from Yosemite (10.10.5) to Sierra 10.12.6. Reason for doing that was that I wanted to upgrade my graphics card from a GTX 960 to a GTX 1060. I followed Rampagedev's procedure and used his DMG to upgrade. I also installed the nvidia web driver 378.05.05, and I installed an Intel 750 PCIe NVME SSD, using Pikeralpha's NVME patch and included the NVME drivers from a Gigabyte Z97 board on the GA-X79-UD3, as the X79 board originally does not support NVME. So, I can boot from the Intel SSD, but it takes about 3 or random 4 kernel panics and reboots before I get to a login prompt. Once logged in everything works fine and the system is stable. I saw the same behaviour when everything was still on a SATA SSD, so I do not suspect the NVME drivers and patches to be the culprit. The KPs can happen at different stages during boot, sometimes even when I am logging in. But once logged in, everything is ok. Another thing that bothers me is USB3. I installed USBXHCI_FL1009.kext, also from the Rampagedev DMG, but the results are flaky. A USB3 USB-stick is recognised, as is my card reader, but an external (bus-powered) USB3 drive from Seagate is completely ignored when inserted. I did turn off USB3 during the upgrade, but it is switched back on now. The original install was with Mavericks, and I upgraded that too to Yosemite. I never tried a clean install as that would take a lot of work to migrate and relicense all my apps. So, in terms of system goodies: Mobo: Gigabyte GA-X79-UD3 CPU: Intel 4930k OS: Sierra 10.12.6 Nvidia web driver: 378.05.05 GPU: MSI GTX1060 3GB Boot drive: Intel 750 NVME PCIe SSD Clover: 4220 Anyone that can help to solve the kernel panics and the USB3 issue? Enclosed my complete EFI folder, IOreg, ACPI tables and kextstat.txt. Any help is appreciated. Thanks. Toms MacPro.ioreg.zip EFI.zip Send me Toms MacPro.zip
  18. Aperta la nuova sezione per macOS Sierra 10.12. http://www.insanelymac.com/forum/forum/535-sierra-1012/ Cordialmente ErmaC
  19. thiagodss

    Sem som

    Oi pessoal. Montei um PC para instalar o OSX com peças recomendadas, mas estou atualmente sem som. Já testei o som com um live cd do Xubuntu e rolou sem problemas. Tentei usar o AppleALC mas não obtive sucesso. Estou com o Sierra instalado, versão 10.12.2 Minha placa-mãe é uma Gigabyte GA-Z170X-UD5 com um Core i7-6700 e placa de vídeo GeForce GTX750Ti.
  20. Just have a couple of questions which I'm pretty sure have simple answers but I cant for the life of me figure it out 1.When I start clover I get many options. There are 3 which I don't understand, and that don't work, they are boot windows with legacy HD1 boot windows with legacy HD2 Boot windows from EFI The ones that do work are boot OS X from sierra boot microsoft efi from efi I'd like to know why those first 3 are there, and how to get rid of them. 2.I installed clover from the source forge page, clicked customize and chose install for uefi motherboards, restarted the computer, when I try to boot Sierra, I get this error "Error loading kernel cache" so I plug in my Sierra usb, clover installed on the hd starts, I chose boot Sierra from usb, that doesn't work, so what I do is go into uefi, put my usb stick first so it loads clover from the usb stick, I choose, boot OS X from Sierra (not usb) AND THAT WORKS?!?!?!?!
  21. Hi guys...been breaking my head over this. I am not totally a noob at this but from the days of El capitan I am having serious headaches. I am running Yosemite on Dell latitude E6220 with intel HD Graphics 3000 and i5-2520M. Almost everything works except the onboard wifi card. Recently I have been trying to install Sierra on this PC since there are lots of tutorials for this same PC. However my case is not a success story. I am getting an error 2 minutes into the installation that Mac OS X sierra can not be installed on my PC. Yet the specs are okay. In some post someone was advised to change the SMBios to one that Sierra supports, so I uses Macbook Pro 8.1 which should be fine but I get the same error. Please know that after finding issues booting with clover I decided to use Enoch the latest release and it boots up smoothly to the installation screen but that error is killing me. I have changed hard drives still the same thing.Someone suggested that you have to enlarge the EFI partition but my system is using chameleon so I do not think I have an EFI partition. I am not a lazy person , I have read a lot but looks like I have hit a dead end.Anyone with anything I could try is more than welcome. Cheers
  22. Hi All, Requesting for your help here. I have been able to install macOS Sierra(10.12) DP on HP Pavilion dv6-3217dx LAPTOP, however when I try to boot it through clover I am getting kernel panic. ERROR: panic (cpu 1 caller) "Local APIC error," Kindly Note the following details 1.I have created Sierra Installer through latest Pandora box 2.I have installed Sierra on external USB Drive (WD MyPassport Ultra - 2 TB) with partition size 1.5 TB for Sierra. I tried booting Sierra with the installer USB drive but again got a Kernel panic. 3. I have a working EL Capitan (10.11.5) on my laptop internal HD 4.Clover version 3577 on EL Capitan HD through which I am trying to boot Sierra. Boot flags remain the same. While EL CAPITAN is able to boot successfully, Sierra throws a KP Boot flags::: -v -f cpus=1 dart=0 slide=0 kext-dev-mode=1 rootless=0 npci=0x2000 nv_disable=1 PCIRootUID=1 USBBusFix=Yes UseKernelCache=No 5.My laptop has Insyde bios 3.5, F.10 6. I have added FakeSMC.kext(version - 6.19.1406) and USBInjectAll.kext(version - 0.5.11) in 10.12 folder under "/EFI/Clover/kexts" 7.SMBios is MacBook Pro 6,2 8.I have also attached my laptop specs taken using cpu-z and Speccy tool on windows 10 Kindly let me know if you require any more details. Thank you for your help. Regards CPU-Z 2.rtfd.zip SPECCY 2.txt config.txt dsdt.txt
  23. fantomas1

    Apple présente "macOS Sierra"

    Apple vient tout juste de dévoiler le nom de sa prochaine mise à niveau de son système d'exploitation fétiche, "macOS Sierra" et au passage, abandonne l'appellation OS X pour macOS. La Developer Preview est disponible aux développeurs dès aujourd'hui, la première bêta ouverte au public cet été (en juillet) et la version finale cet automne.
  24. Hi I'm new to the forum. I was wondering if anybody can give me a decently detailed guide on installing macOS Sierra on my Lenovo Ideapad 300-15ISK. I do know a bit about computers such as the BIOS and stuff, by I really don't know anything about Macs and how they work. Also, can I dual boot my currently installed Windows 10 alongside macOS Sierra? The specs of my laptop are below: CPU: Intel Core i5-6200U (Skylake) RAM: 2 Hyundai Electronics 4GB DDR3 sticks Motherboard: Lenovo Paris 5A8 Wireless card: Intel Wireless AC 3165 WiFi + Bluetooth chip BIOS: Lenovo D5CN28WW Graphics: Intel HD Graphics 520 Link to my laptop's support page on Lenovo's site: http://pcsupport.lenovo.com/gb/en/products/laptops-and-netbooks/300-series/300-15isk/80q7?linkTrack=Homepage%3ABody_Search+Products&searchType=4&keyWordSearch=300-15ISK%2520Laptop%2520%2528ideapad%2529%2520-%2520Type%252080Q7 Thanks.
  25. 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.