Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About JaBrd

  • Rank
    InsanelyMac Protégé
  1. Have you tried IGPEnbler=No npci=0x2000 ? how did you edit VoodooTSCSync.kext ?
  2. First of all, for 4930k (Ivy Bridge-E) you should only be using 10.9.2+ whose kernel supports IVBE. I've had alot of trouble trying to do a clean install using Clover but Chameleon/myHack works well. The rampagedev page has good info for Chameleon (but the only way I could get Clover to work in UEFI was to install Clover over the Chameleon install ... and into a FAT formatted EFI partition.
  3. Slytherin ::The Extreme Post-Installation Utility

    This looks like it would be very useful. Will it also incorporate myHack->myFix functionality?
  4. UEFI Clover Intall on RIVBE, 4930k, R9 270

    Using Clover 2605 Boot Args: -v -f cpus=1 npci=0x2000 PCIRootUID=1 (with or without -x) Using 10.9.1 created mediainstall When booting I get: OsxAptioFixDrv: Starting overrides for .IABootFiles\boot.efi efiboot loaded from device: ... boot file path: .IABootFiles\boot.efi ..Loading kernel cache file '\.IABootFiles\kernelcache\'... root device uuid is '...' ++++++++++++++++++++++++++++++++++++++++++++++++++++ then reboots... (note that only GPU is 610 ... r9 290 removed)
  5. UEFI Clover Intall on RIVBE, 4930k, R9 270

    I'm getting Clover to boot after replacing VBox-HFS.efi with HFSPlus.efi. Its at least starting. About a third of the way through the driver load it reboots...
  6. UEFI Clover Intall on RIVBE, 4930k, R9 270

    I have similar problem with 4930k, GA-X79-UP4 and GeForce 610. Set MOBO to UEFI.
  7. Really depends on how much storage you want. If you consider $$ / bay and want 15-24 bays (for example) then SAS with a port expander is a reasonable option in the $1400-1800 range. If you want 4 bays then USB 3.0 is more cost effective.
  8. I didn't know. When I first got my system up and running my graphics system was ridiculously slow until I ran myFix which removed several kexts that appeared to be the cause of the GUI problem. (non GUI benchmarks were fine). In any case it solved the graphics issues for me.
  9. First edit and install VoodooTscSync.kext to allow you to remove cpus=1 (i.e. don't boot with that) Also run myHack->myFix to remove some unneeded kexts that can slow down the GUI.
  10. AMD r9 270 problem

    It looks like your boot is trying to allocate an instance of a Hawaii driver -- that would be for the r9 290/290x not the 270. Assuming you are using an r9 270 you've probably edited the kexts incorrectly -- I'd guess you put the device id into the Hawaii section rather than the Pitcairn section.
  11. After the reboot use boot flags: -v -f where does it hang?
  12. R9 290x support in mavricks

    I'm not all all sure that 10.9.2 has drivers for Hawaii (r9 290x/290). My R9 290 has a device id: 0x67b11002 In AMDRadeonX4000.kext I found a device id: 0x67b01002 in the Hawaii section. This device id isn't present in AMD7000Controller.kext
  13. Install VoodooTSCSync.kext (edit plist per instructions) Use the most recent version of FakeSMC.kext (version 901 I think)
  14. I moved my old builds hard drive onto this machine. This was a dual boot OS X 10.8.5 and Windows 7. I'm in the process of installing/upgrading 10.9 onto the 10.8.5 partition using myHack. Of note this install was done entirely with the R9 290 (again in slot 2), and after I removed the 610 from the machine. The myHack boot flags that worked were: -v -f -x cpus=1 npci=0x2000 GraphicsEnabler=no PCIRootUID=1 The install seemed to hang after: ACPI_SMC_PlatformPlugin::gatherCStateOverrides - failed to set c-state demotion data: -1 I finally let the install sit there for a while and it moved on and succeeded (went on to GUI). My understanding is that QE/CE won't work with the R9 290(x) until a native driver is available. My triple boot system allows me to boot into Windows and also have two 10.9 installations available -- I can play around with clover etc without worrying that trashing my EFI will require a complete reinstall -- I can easily repair it from the other 10.9 install.
  15. I've installed an R9 290 by installing Chameleon onto the EFI partition and inserted PCIRootUID=1 and GraphicsEnabler=yes ... no QE and the graphics are a bit flakey. My Powercolor R9 290 wanted to be inserted into PCI-e slot 2 instead of 1 for some reason.