Jump to content


  • Content Count

  • Joined

  • Last visited

About shrieken213

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender

Recent Profile Visitors

3,482 profile views
  1. USB 3.0: https://www.amazon.com/Inateck-Express-Controller-Internal-Connector/dp/B00JFR2H64/ref=sr_1_3?keywords=fl1100&qid=1555849149&s=electronics&sr=1-3#customerReviews This should be natively supported since it uses Fresco Logic FL1100, the same chip used in the trash can Mac Pro. Ethernet: https://www.amazon.com/Ethernet-Realtek-Standard-Brackets-SD-PEX24041/dp/B004M18EEC/ref=sr_1_2?keywords=rtl8111&qid=1555849429&s=electronics&sr=1-2&th=1 You'll need RealtekRTL8111.kext by Mieze, available in the downloads page here at InsanelyMac.
  2. While making some final touches to an SMBIOS switch I noticed strange behavior with the CPU clocks. I'm moving from iMac14,2 to 15,1. Build is 4790K (Overclocked 4.6Ghz), Vega 56, 32GB RAM. I'm on the beta release because of a bug in 10.14.4 that doesn't spin down the Vega fans after they spin up under load. 1. Either Intel Power Gadget or power management is broken. According to IPG the clocks almost never fall below the nominal 4 Ghz. At the same time, HWSensors show that the clocks do in fact fall to the idle 800 Mhz clocks. AppleIntelInfo shows that all P- and C-states have been injected and observed by the kext. This leaves two possibilities: IPG is misreading the clocks, or there is in fact something that's artificially keeping the clocks at 4 Ghz while idle. 2. IPG utilization percentage is bugged. A ton. HWSensors also has a bug where clock speeds occasionally peak at 2^31 Hz (2147.48 THz). 3. The headless framebuffer for Intel HD 4600, 0x0b001204, gets the IGPU stuck at full clock. Only by fully enabling IGPU with 0x0300220d is IGPU stepping properly enabled. I don't know if a real iMac15,1, which uses the 0x0b001204 framebuffer natively, shows the same behavior. I'm not very certain about the IGPU since I only recently tried out the headless framebuffer, but I do know for sure that IPG properly read idle clocks in 10.13 with the same config, more or less. I'm wondering whether this is a beta thing or other people have seen the same behavior elsewhere. AppleIntelInfo.log config.plist
  3. shrieken213

    Natively supported USB 3.0 add-in cards?

    Sorry, let me clarify. I'm trying to avoid buying the overpriced "For Mac" versions of regular PCIe cards. The current Sonnet offering uses FL1100, which by judging the lack of Mac drivers (other than ones bumping up maximum available current) should be natively supported. However, even with these companies I see that some products require a third-party kext, for example SXHCD.kext for legacy Sonnet cards. So my question is whether a controller other than Intel or FL1100 exists that is natively supported by macOS.
  4. I'm in search of a new card since the one I have to give my build an extra 19-pin header has a memory leak in Windows and crashes often (works fine in macOS with GenericUSBXHCI). Might as well get something that has OOB support so I can get rid of GenericUSBXHCI, which might cause conflict with native drivers. I've looked around and peeped inside AppleXHCIPCI.kext, and the only non-Intel USB 3.0 controller that I could find it matching to was the Fresco Logic FL1100 (vendor 1b73, device 1100). That means if I get any PCIe card that uses the controller, it'll work OOB, right? Or have I missed other controllers that has native support?
  5. I've finally made the switch to the dark side and sold off my GTX 1070 for a Vega 56 It's running almost OOB on 10.14.4 since I already had WEG/Lilu installed for the IGPU and it configured everything for the Vega. However, once the fans spins up beyond 50% they don't spin down while the clocks drop to idle. This is a big issue. It's not intolerable, but it's also not Nvidia FE blower quiet since mine's an open-air card. So let's fix that since at idle the fans shouldn't even be spinning. The pinned thread gives a general outline of what needs to be done. Dig through the VBIOS ROM, find the power play info, inject it. Follow this guide to the 2:00 mark for the power play info. Once you know the offset and length of the region, you can do the rest with hex editors in macOS. The thread's pinned solutions suggest modding vanilla kexts or using injector kexts, neither of which I really like doing. Later on a SSDT DSM injection is shown to work; I'd also rather not have SSDTs where they're not needed. So let's try injecting with Clover. Unlike the IGPU entry which has a straightforward address in the PCIe tree, the Vega card is PCI0/PEG0@1/PEGP/(bridge device)/GFX0. So assuming that the card is already properly injected but fans dysfunctional, use gfxutil to find the address of GFX0: gfxutil -f GFX0 which returns: DevicePath = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) Copy and paste the power play hex data in Xcode as a data entry like above, or convert to base64 and insert it directly with a text editor. It has been injected properly. The fan now spins past 50%, up to 55%! Still doesn't spin down though...any ideas? On another note, what do the PP_FuzzyFanControl do? PP_DisablePowerContainment seems to do something with the power restrictions on the card as needed for overclocking, not sure about the fuzzy fan control.
  6. shrieken213

    AMD Radeon HD 6750M on Mojave

    No. You're in the same boat as Nvidia users right now. There simply are no drivers, no plans to make new drivers, and no hack to make the AMD card work in Mojave. Anything claiming to be a "solution" simply disable the AMD chip and run the laptop off the IGPU as you've already found out. It's an old laptop. The chip is 8 years old. You could use an upgrade.
  7. The issue has been fixed. The board's ME firmware was corrupt. Modding the BIOS to fix ME in conjunction with directly flashing the non-corrupt firmware to the ME region using FTK did the trick. Note that Windows was used for the fix. What was the issue? macOS currently expects a functioning ME device (HECI/IMEI) for Intel graphics to fully load. Because the firmware was corrupt, the kexts only loaded halfway and kextd stalled. On Windows, the ME device was "disconnected" in Device Manager. This is why even with IMEI in the IOReg, correct Clover settings and FramebufferAzul and HD5000Graphics kexts loaded in kextstat I could not get QE/CI, or even a proper graphics output. Once the firmware was restored, the ME coprocessor booted completely and the hack gets full acceleration now. For future note: should this method fail, the only option is to buy a new preflashed BIOS chip. Proceed with care. after.BMP before.BMP
  8. I've tried all the BIOS versions dating back up to 3~4 years, and all are unable to retrieve the ME version. It seems BIOS editing is the only way left.
  9. Booting from a vanilla USB installation with the same injections give the same error again, except the timeout interval is 240 seconds instead of 60. Tried adding DSDT patches for IRQ. No change. Tried deleting the DSDT and starting fresh. No change. Same goes for a fresh Clover installation with a new config. Does not change a thing. Same goes for Clover version rollbacks. Previous versions also have the same error. Also tried optimized default BIOS settings with minimal changes for booting. Same thing. Will continue exploring options to nail this down.
  10. Your config.plist is a giant mess... 1. You shouldn't need any DSDT fixes except where it is required by your mobo. In my case, I need none. 2. HECI to IMEI patch is handled by WEG. You do not need it. 3. GFX0 to IGPU patch is handled by WEG. It is redundant and you should delete it. 4. You should not need dart=0 if you disabled VT-d in the BIOS. 5. -disablegfxfirmware is only required for Kaby Lake and above IIRC. It should also not be necessary if you're using WEG. 6. Audio inject 9 isn't a thing AFAIK. It's either 1, 2 or 3. Read this. Unless you're using some other injection that I am not aware of. 7. The entire USB section does not function correctly on Z97. You do not need to enable any of them unless you're still on Z87. I cannot comment on other chipset generations. 8. Inject Intel does nothing in Mojave and may instead cause conflict with WEG. You should disable it. I have memory module information injected in the SMBIOS because the system won't read the frequency correctly (says 2000 Mhz even with XMP). This is purely cosmetic. Are you sure you know what you're doing? I could care less at who looked at your configs. If you're giving the advice, you need to understand what you're doing.
  11. Further fidgeting with the config.plist: Inject Intel does absolutely nothing in Mojave. Confirmed by removing Lilu/WEG and attempting to inject via the old Clover method. Framebuffer injection via the Properties section works as intended, but the device model appears as Intel Iris Pro, which should show "Intel HD Graphics 4600" should Inject Intel be functioning. That however does show that the properties are being read and framebuffer being recognized. This issue has also occurred in other versions as well, apparently...
  12. 1. I have my config.plist and IOReg in the OP. The "diary" you refer to is there to rule out solutions that don't work. 2. Take a read. WEG automatically injects all the properties that Inject Intel would do. If anything, you shouldn't need Inject Intel if WEG does what it's supposed to do. 3. The surprise is that disabling hardware acceleration works better than enabling? Just tried double injection. No change, doesn't work.
  13. I'm on the latest Clover release (r4895) with the latest drivers. Are you sure about Inject Intel? WEG specifically says to disable it in the readme.
  14. Hello, I'm trying to get this bugger working again as I'm ditching Nvidia and don't have a usable Mojave-compatible dGPU while I get an AMD one. It's absolutely frustrating. No matter what I do with this it won't work. It used to work perfectly fine in Yosemite and Sierra. It kept getting the busy timeout error at boot in High Sierra, so I tried updating to Mojave. No luck. I've switched from Clover auto-injection to Lilu/WEG as I heard Clover injection doesn't work with Mojave. It so far injects the IDs fine. Since it's a 4790K with native device-id 0x0412 I should theoretically only need to inject the framebuffer ID using WEG. Nope. Doesn't work at all if I use a valid framebuffer specified in the list, e.g. 0x0300220d. HDMI monitor is not detected if I use it and I can only access it via VNC. Ironically, if I use a dummy ig-platform-id (i.e. -igfxvesa) it at least spits out the unaccelerated screen on the monitor. What? IOReg and kextstat shows that the framebuffer kext is loading, and Hackintool shows that the WEG injection is working. BIOS DVMT memory is set to 64 MB, multi-monitor and VT-d off. I do have FakePCIID in /L/E for Wi-Fi, Bluetooth and Handoff (these work perfectly fine), but nothing for graphics. DSDT is vanilla except for SSDTs regarding SpeedStep, USB port injection and Wi-Fi. What the heck am I doing wrong here? Balthasar.iojones config.plist
  15. shrieken213

    Considering the jump to AMD

    I've been on a GTX 1070 (non-Ti) for the past year and a half. It's been a good card, but Nvidia and Apple haven't released a Mojave web driver for the cards, keeping the hackintosh on High Sierra. It's quite frustrating since my real MBP is on Mojave and it's causing compatibility issues, e.g. iTunes. What would be a good AMD equivalent to the 1070? The Vega 56? Also, would that work OOB in Mojave or would it need FB patches?