Jump to content

FFForever

Members
  • Content Count

    29
  • Joined

  • Last visited

About FFForever

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,321 profile views
  1. FFForever

    AMD R9 270 issues

    Thanks for the information. I haven't had a chance to get back to high sierra before now. Is this still the suggested tutorial? I know it's missing the padding around the code construction string. http://www.insanelymac.com/forum/topic/303186-how-to-modification-of-amd-fb-clover-injection/ My system loads Futomaki (4 connectors) by default on my system without any issues with full acceleration. Decoded connectors: DP 12 04 01 01 HDMI 22 04 02 02 DVII 10 00 03 06 DVII 00 10 04 06 DVID 11 02 05 05 Should I drop the DVID? Full bios decoded PCI ID: 1002:6811 01 [DP] Connector Object Id [19] which is [DISPLAY_PORT] encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector at index 0 Type [@offset 43574]: DisplayPort (10) Encoder [@offset 43578]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 43684]: 0x90, OSX senseid: 0x1 12 04 01 01 02 [HDMI-A] Connector Object Id [12] which is [HDMI_TYPE_A] encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true Connector at index 1 Type [@offset 43584]: HDMI-A (11) Encoder [@offset 43588]: INTERNAL_UNIPHY2 (0x21) i2cid [@offset 43711]: 0x91, OSX senseid: 0x2 22 04 02 02 03 [DVI-I] Connector Object Id [2] which is [DVI_I] encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector at index 2 Type [@offset 43594]: DVI-I (2) Encoder [@offset 43598]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 43748]: 0x95, OSX senseid: 0x6 10 00 03 06 04 [DVI-I] Connector Object Id [2] which is [DVI_I] encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false Connector at index 3 Type [@offset 43604]: DVI-I (2) Encoder [@offset 43608]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 43748]: 0x95, OSX senseid: 0x6 00 10 04 06 05 [DVI-D] Connector Object Id [4] which is [DVI_D] encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Connector at index 4 Type [@offset 43614]: DVI-D (3) Encoder [@offset 43618]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 43775]: 0x94, OSX senseid: 0x5 11 02 05 05
  2. FFForever

    AMD R9 270 issues

    Hey yo, Firstly, thanks for taking the time to even stop by this thread . I decided to take the plunge and try 10.13 to see how it's coming along. Unfortunately it's not going so well at the moment. Information about my setup: - Build: 10.13 Beta (17A291m) - CPU: i5-4440 - Internal GPU: Intel HD Graphics 4600 - Graphics card: R9 270 (non x) with a fake pci id of 0x86001002 - Monitor a: connected via HDMI on the intel card - Monitor b: connected via DVI to the R9 - Monitor c: connected via DVI to Display Port active converter - Clover revision: 4097 In Sierra the only thing required to get my r9 working was setting my fake pci id to 0x68001002, and enabling inject AMD. I'm using the intel graphics as a helper card to get sleep/wake working in Sierra. I'm not really sure what I should try doing to fix this in High Sierra. I've included my clover configuration in case you guys can spot any issues. Things I've tried: - Adding my device id directly into AMDRadeonX4000.kext & AMD7000Controller.kext, disabling the fake pci id. - Patching a 4 and 5 connector frame buffer (Ebi and Futomaki) with my relevant configuration. See this previous thread I created including the patched connectors (http://www.insanelymac.com/forum/topic/313473-asus-r9-270-directcu-ii-frame-buffer-patching/). I did add the 0 padding around my custom connector pin layout. Patched connector strings: 4 connectors 000400000403000000010000 000000001204010100000000 000800000002000000010000 000000002205020200000000 000200000402000000010000 000000001000030600000000 000200000402000000010000 000000001102050500000000 5 connectors 000400000403000000010000000000001204010100000000 000800000002000000010000000000002205020200000000 000200000402000000010000000000001000030600000000 000200000402000000010000000000000010040600000000 040000001402000000010000000000001102050500000000
  3. FFForever

    New Driver for Realtek RTL8111

    Thanks for the prompt response. I found the issue and it was related to my ssdt. After fixing that the problem went away.
  4. FFForever

    New Driver for Realtek RTL8111

    Good afternoon Mieze, After leaving my system unattended / in sleep mode for an extended period of time I came back to a kernel panic. Is there any known issues with Sierra? panic(cpu 0 caller 0xffffff80004011bd): Kernel trap at 0xffffff7f838951a2, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff81ec657000, CR3: 0x0000000009b62000, CR4: 0x00000000001627e0 RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0xffffff81ec657000, RDX: 0xffffff81c2469088 RSP: 0xffffff81ed40be40, RBP: 0xffffff81ed40be50, RSI: 0x0000000000000000, RDI: 0xffffff81a1b97000 R8: 0x00000591bb32903c, R9: 0xffffff80296b6d98, R10: 0x0000000000000000, R11: 0xffffff8000a8a810 R12: 0x00000591ba46549d, R13: 0x000000008df5a1c1, R14: 0xffffff81a1b97000, R15: 0xffffff81a1b972a0 RFL: 0x0000000000010246, RIP: 0xffffff7f838951a2, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff81ec657000, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffff81ed40bad0 : 0xffffff80002ec3ec 0xffffff81ed40bb50 : 0xffffff80004011bd 0xffffff81ed40bd30 : 0xffffff800029d543 0xffffff81ed40bd50 : 0xffffff7f838951a2 0xffffff81ed40be50 : 0xffffff7f83896e39 0xffffff81ed40be70 : 0xffffff7f838967ea 0xffffff81ed40bea0 : 0xffffff7f8389609f 0xffffff81ed40bee0 : 0xffffff80008bcfaf 0xffffff81ed40bf30 : 0xffffff80008bb811 0xffffff81ed40bf80 : 0xffffff80008badf6 0xffffff81ed40bfb0 : 0xffffff800029a8f7 Kernel Extensions in backtrace: com.insanelymac.RealtekRTL8111(2.2.1)[8BA5E6A6-5DCA-3102-B71B-CE613147F452]@0xffffff7f83835000->0xffffff7f8389bfff dependency: com.apple.iokit.IONetworkingFamily(3.2)[6326DB88-5330-3F0C-91F6-D478AB5E7503]@0xffffff7f812fd000 dependency: com.apple.iokit.IOPCIFamily(2.9)[C6E3195E-A0D7-3B71-B5F4-9EE9E182D4FC]@0xffffff7f80b32000
  5. Success! You rock MaLd0n! I upgraded clover again, and it's still working so that's good. If I use the generated SSDT file it'll break again. Do you think dumping the patched SSDT clover generates would work? Is there a way to decide how often it'll step? I've noticed that while Windows will maintain 0.8 ghz for a bit, OS X will continuously jump between different frequencies even when idle.
  6. Hmm it still doesn't appear to be stepping correctly. Should I try clearing the nvram? I checked the power widget in Windows (and recorded a log) to verify speed stepping is working correctly / there's no MSR lock. PwrData csv: https://mega.nz/#!IchWTYKB!K-bDnOC0UjIUEjR04PLy-vp2JEY71EZgYOy1zidSB1Y
  7. I downgraded to revision 4049 per your recommendation, and copied your configuration back in. The speed stepping sill appears to be the same unfortunately.
  8. Thanks again for all of your help last night . The new config doesn't seem to change the speedstepping. Even with idle loads I'm still seeing the same frequencies for the most part.
  9. FFForever

    Black screen with flashing white bar

    He's referring to compressing EFI\Clover. and attaching it for him to view.
  10. Looks like it's still favoring the high frequency. I've attached ~/library/ssdtprgen's content, the ACPI folder contains the original ssdt/acpi, and the patched dsdt. It was complaining that they didn't exist so I copied them in, and ran it again. Should I ignore the error, and run it again with the files deleted? ssdtPRGen: https://mega.nz/#!EM5FWIpT!mxugJtnLgR8pNwcGZyF4CFXMaIjg_Z5rvKYS2eJN_Qk
  11. ioreg: https://mega.nz/#!xUxHVDaT!G3mHO3-sE8zHz3dZ1NmWMOjarLipUAxYFDXCb4mC-W0 Does this look like it's stepping correctly? Even with a 90%+ idle system it's still hovering around the max frequency with minor drops.
  12. Ah. I was using hwmonitor as a way to test speedsteping / monitor temperatures. Do you have a recommendation on something else to use? I noticed in my verbose boot output I have ACPI errors relating GPX0 with a note on AE_NOT_FOUND. I tried searching console for ACPI, and found nothing. Is there a log file I can check to get the exact error?
  13. Wow! I am floored by how much of a change a proper DSDT / clover configuration can make. I can't test HDMI audio out unfortunately so I can't comment on if that's working or not. The audio is working just fine without the hda enabler loading. The only issue I have left to fix on my system is the graphics not waking from boot, but that's a known AMD issue from the looks of it on <= 10.11. Thanks a lot for taking a look at my setup MaLd0n! Edit: Looking at hwmonitor from rehabman / fakesmc it looks like only drive temps and ssd life remaining is showing. It use to include fan speeds, temps, etc. This could be due to my ssdt changes from earlier. Should I try adding the other ssdt-# files into my patched folder (after fixing any errors of course)?
  14. Hey hey, Mind lending me a hand with my DSDT / checking it over? Changes made to the DSDT: - Injected layout-id (probably incorrectly as I still need the HDAEnabler) - Fixed codepaths not returning a value by appending return (Zero) - Removed random Arg0 after a return statement causing an unexpected end of file - Fixed possible timeout error by changing 0x0FFF to 0xFFFF - Removed unused locals - Removed 20+ lines of Zero repeated The SSDT.aml is the output from the latest version of ssdtPRGen.sh. System: Dell Inspiron 3847 Graphics card: r9 270 CPU: i5-4440 Memory: 8gb SSD: 1x Samsung Pro HDD: 1x WD Black 3tib Lan: RTL8168G / 8111G via Realtek8111.kext Audio: ALC662v2 via AppleALC.kext Links: System specs (for reference): https://downloads.dell.com/manuals/all-products/esuprt_desktop/esuprt_inspiron_desktop/inspiron-3847-desktop_reference%20guide_en-us.pdf IOReg: https://mega.nz/#!lNpiUYJB!XlaNWUyYgacLCsbSKMfBQLebihFHYbexzl9PchV2kvs App output: https://mega.nz/#!xdoXkSqb!HXgXo1M13QuhppHfZs5eBPODlM0UHzRYMzl_Z2U0-4g Clover: https://mega.nz/#!5RQwlLZI!8_HBy9jqLCh7RJPr_wF3yErUgVQ97yrqI-3jjWII7Y0
×