Mork vom Ork Posted July 30, 2017 Share Posted July 30, 2017 got one dump question: does the ".dSYM"-files also have to be placed in "EFI/CLOVER/kexts/Other"-folder - or just the kext files themselve? Link to comment Share on other sites More sharing options...
TheRacerMaster Posted July 30, 2017 Share Posted July 30, 2017 You only need the kext, the dSYM is for the debugging symbols (which are stripped in the release target). 3 Link to comment Share on other sites More sharing options...
Mork vom Ork Posted July 30, 2017 Share Posted July 30, 2017 @TheRacerMaster: thanx. 1 Link to comment Share on other sites More sharing options...
Picasso Posted July 31, 2017 Share Posted July 31, 2017 I tried this kext with amd R9 390x and not change. Could work in this powerfull cards? Thanks. Link to comment Share on other sites More sharing options...
griven Posted July 31, 2017 Share Posted July 31, 2017 For me it does work well to some point (Sleep works and it wakes without BlackScreen) but my Card isn´t detected correctly. I use a Sapphire R9-270X (Vendor: 1002, Device: 6810, SubVendor: 174B, SubDevice: E271) which is detected as R9-370X by WhatEverGreen and is using the generic ATY,AMD,RadeonFramebuffer (before WhatEverGreen I used DSDT Inject and Futomaki as Framebuffer). For some Reason I am not able to get HDMI Audio to work (it worked before). DCPI Manager shows me a Pitcarin/Cape Verde HDMI Audio Device (Vendor: 1002, Device: AAB0, SubVendor: 174B, Subdevice: E271) and the GFX0 and HDAU Device in my DSDT are configured like that: Device (GFX0) { Name (_ADR, Zero) // _ADR: Address Name (_SUN, One) // _SUN: Slot User Number Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x18) { "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "device-id", Buffer (0x04) { 0xB0, 0xAA, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Device (HDAU) { Name (_ADR, One) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x08) { "layout-id", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-2" } }) } } What may possibly be wrong? Link to comment Share on other sites More sharing options...
Cyberdevs Posted July 31, 2017 Share Posted July 31, 2017 @griven Do you use the 1.0.1 release or the 1.0.0? Link to comment Share on other sites More sharing options...
griven Posted July 31, 2017 Share Posted July 31, 2017 I use the latest 1.0.1 Link to comment Share on other sites More sharing options...
vandroiy2012 Posted July 31, 2017 Share Posted July 31, 2017 For me it does work well to some point (Sleep works and it wakes without BlackScreen) but my Card isn´t detected correctly. I use a Sapphire R9-270X (Vendor: 1002, Device: 6810, SubVendor: 174B, SubDevice: E271) which is detected as R9-370X by WhatEverGreen and is using the generic ATY,AMD,RadeonFramebuffer (before WhatEverGreen I used DSDT Inject and Futomaki as Framebuffer). For some Reason I am not able to get HDMI Audio to work (it worked before). DCPI Manager shows me a Pitcarin/Cape Verde HDMI Audio Device (Vendor: 1002, Device: AAB0, SubVendor: 174B, Subdevice: E271) Added your card subvendor and subdevice with correct name. WhateverGreen.kext.zip As for AMD,RadeonFramebuffer and HDMI - read the FAQ... 5 Link to comment Share on other sites More sharing options...
Gigamaxx Posted July 31, 2017 Share Posted July 31, 2017 Thank you very much for this long awaited fix, this is great! I have had great success with it for Intel systems with my i3 7350k and pentium G3258 it works well, I even have it on my Ryzen setup. However, with Ryzen I can only get it to work on Sierra 12.5, if I use Sierra 12.6 public release it goes to black screen after boot. I tried many Framebuffer combinations but it still leads to black screen in Sierra 12.6 for Ryzen CPUs, if I use a helper card it shows the Radeon Pro 480/575 so I know it's loading somewhat but it's not fixing black screen after boot. The card accelerates at boot and system is active, just no screen output. It may be a kernel compatibility issue but it would be nice to have it in sierra 12.6 since it has many native fixes for Polaris and fury cards which work better overall than Nvidia cards for Ryzen systems. You only need the kext, the dSYM is for the debugging symbols (which are stripped in the release target). I noticed when I opened the .Sym first it ran in terminal "debugging"? When I load the kexts in S/LExtensions first and then open the .sym it doesn't debug, or appear to but it then does a restart. 1 Link to comment Share on other sites More sharing options...
carlo_67 Posted July 31, 2017 Share Posted July 31, 2017 Added your card subvendor and subdevice with correct name. WhateverGreen.kext.zip As for AMD,RadeonFramebuffer and HDMI - read the FAQ... Perfect R9 270x Sapphire dual x 1 Link to comment Share on other sites More sharing options...
verleihnix Posted August 2, 2017 Share Posted August 2, 2017 AirportBrcmFixup Is it possible to add "AirPortBrcm4360 - fcvo" patch? Link to comment Share on other sites More sharing options...
lvs1974 Posted August 2, 2017 Share Posted August 2, 2017 AirportBrcmFixup Is it possible to add "AirPortBrcm4360 - fcvo" patch? Do you mean the following one? Kext: AirPortBrcm4360 Find: 81F952AA00007529 Replace: 81F952AA00006690 You can try DEBUG version of AirportBrcmFixup_1.0.1.kext.zip And string -brcmfxdbg into boot-args and reboot. After reboot type in terminal: log show --predicate 'process == "kernel" AND eventMessage CONTAINS "BRCMFX"' --style syslog --source And put output here. 1 Link to comment Share on other sites More sharing options...
verleihnix Posted August 2, 2017 Share Posted August 2, 2017 Do you mean the following one? Kext: AirPortBrcm4360 Find: 81F952AA00007529 Replace: 81F952AA00006690 You can try DEBUG version of AirportBrcmFixup_1.0.1.kext.zip And string -brcmfxdbg into boot-args and reboot. After reboot type in terminal: log show --predicate 'process == "kernel" AND eventMessage CONTAINS "BRCMFX"' --style syslog --source And put output here. Yes, initialize the fvco (frequency voltage controlled oscillator) log is empty Link to comment Share on other sites More sharing options...
lvs1974 Posted August 2, 2017 Share Posted August 2, 2017 Yes, initialize the fvco (frequency voltage controlled oscillator) log is empty Did you check installed Lilu version? It should be 1.1.6 or higher. Type in terminal: kextstat | grep -i airp kextstat | grep -i lilu And put output here. 1 Link to comment Share on other sites More sharing options...
verleihnix Posted August 2, 2017 Share Posted August 2, 2017 Did you check installed Lilu version? It should be 1.1.6 or higher. Type in terminal: kextstat | grep -i airp kextstat | grep -i lilu And put output here. kextstat | grep -i airp 63 0 0xffffff7f81de3000 0x7bd000 0x7bd000 com.apple.driver.AirPort.Brcm4360 (1150.12.1a1) BB3626FA-A579-348F-AF69-3249DAC7949D <62 61 60 52 12 7 6 5 4 3 1> kextstat | grep -i lilu 17 2 0xffffff7f80e76000 0x37000 0x37000 as.vit9696.Lilu (1.1.6) 261A5E4B-4824-3834-89C1-290B74C6FEEC <7 5 4 3 2 1> Link to comment Share on other sites More sharing options...
lvs1974 Posted August 2, 2017 Share Posted August 2, 2017 kextstat | grep -i airp 63 0 0xffffff7f81de3000 0x7bd000 0x7bd000 com.apple.driver.AirPort.Brcm4360 (1150.12.1a1) BB3626FA-A579-348F-AF69-3249DAC7949D <62 61 60 52 12 7 6 5 4 3 1> kextstat | grep -i lilu 17 2 0xffffff7f80e76000 0x37000 0x37000 as.vit9696.Lilu (1.1.6) 261A5E4B-4824-3834-89C1-290B74C6FEEC <7 5 4 3 2 1> It should be so: kextstat | grep -i airp 27 0 0xffffff7f83447000 0x8000 0x8000 as.lvs1974.AirportBrcmFixup (1.0.1) 4FB3F52B-5B9C-31D8-B160-EA217E9AC826 <25 12 7 5 4 3 2 1> 71 0 0xffffff7f81d5e000 0x836000 0x836000 com.apple.driver.AirPort.Brcm4360 (1150.12.1a1) BB3626FA-A579-348F-AF69-3249DAC7949D <70 69 59 58 12 7 6 5 4 3 1> AirportBrcmFixup is not loaded. 1 Link to comment Share on other sites More sharing options...
verleihnix Posted August 2, 2017 Share Posted August 2, 2017 I put the kext in /Library/Extensions. could that be the reason? Link to comment Share on other sites More sharing options...
vit9696 Posted August 2, 2017 Author Share Posted August 2, 2017 Of course it is the reason. Lilu and friends must go to bootloader kexts unless you use https://github.com/PMheart/LiluFriend. 3 Link to comment Share on other sites More sharing options...
truemac Posted August 3, 2017 Share Posted August 3, 2017 hi I get this warning on boot log how I can fix it>? kernel: (AMDFramebuffer) WARNING: Setting ACCELERATOR RENDER WSAA state without flip. Screen corruption is possible! kernel: (AMDSupport) WARNING: Setting ACCELERATOR RENDER WSAA state without flip. Screen corruption is possible! thx in advance Link to comment Share on other sites More sharing options...
lovan6 Posted August 4, 2017 Share Posted August 4, 2017 I have clean install Sierra 10.12.6 with Saphire HD7870 and its working OOB. Never had to configure IP config list yet so it's untouched. The problem right now is black screen upon waking from sleep. Never use IGPU as the second card and just leave on most of the time. I figure out that someday this will be fixed. So to solve this problem I need to install the latest Lilu kext to /EFI/Clover/kext/10.12. But what about whatevergreen how to install? I notice it's not a kext but something like a plug in. I need to try both but a simple guide and explanation will suffice. Thanks Link to comment Share on other sites More sharing options...
LostVector Posted August 5, 2017 Share Posted August 5, 2017 I have clean install Sierra 10.12.6 with Saphire HD7870 and its working OOB. Never had to configure IP config list yet so it's untouched. The problem right now is black screen upon waking from sleep. Never use IGPU as the second card and just leave on most of the time. I figure out that someday this will be fixed. So to solve this problem I need to install the latest Lilu kext to /EFI/Clover/kext/10.12. But what about whatevergreen how to install? I notice it's not a kext but something like a plug in. I need to try both but a simple guide and explanation will suffice. Thanks Copy WhateverGreen.kext to /EFI/Clover/kext/other. Reboot. That's all. 1 Link to comment Share on other sites More sharing options...
jalavoui Posted August 5, 2017 Share Posted August 5, 2017 where is the WhateverGreen.xcodeproj ? the logs show entries that i can't find in source code e.g. (kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo found 4 connectors") AMDCIHardwaregetFrameBufferBaseAddress AMDGraphicsAcceleratorpopulateAccelConfig are all this patches available in github ? Link to comment Share on other sites More sharing options...
vandroiy2012 Posted August 5, 2017 Share Posted August 5, 2017 where is the WhateverGreen.xcodeproj ? the logs show entries that i can't find in source code (e.g. "(kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo found 4 connectors") https://github.com/vit9696/WhateverGreen/blob/master/Manual/FAQ.en.md Link to comment Share on other sites More sharing options...
MacNB Posted August 5, 2017 Share Posted August 5, 2017 where is the WhateverGreen.xcodeproj ? the logs show entries that i can't find in source code e.g. (kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo found 4 connectors") AMDCIHardwaregetFrameBufferBaseAddress AMDGraphicsAcceleratorpopulateAccelConfig are all this patches available in github ? Whatevergreen is not fully open source I believe...it's only partly open. The part that finds the AMD card type and names it is open ... that's what available on git. The actual core source I cannot find either. Link to comment Share on other sites More sharing options...
MattsCreative Posted August 5, 2017 Share Posted August 5, 2017 1.0.3 breaks DP on 290x Link to comment Share on other sites More sharing options...
Recommended Posts