Jump to content
5539 posts in this topic

Recommended Posts

30 minutes ago, dsynos80 said:

WEEE!!!!!!!!!!!

 

It Works!!! 

Honored to have your details also listed hahah!!! 

Thank you so much!

gpu and audio hdmi fix

DSDT.aml.zip

  • Like 1
26 minutes ago, MaLd0n said:

gpu and audio hdmi fix

DSDT.aml.zip

Works Great!!!

 

I suppose that if i choose in the future to enable iGPU and go with 19.1 SmBios i can use the same.

 

You must be an octopus man... how many hands do you have?

 

Thnx!

Screenshot 2020-03-03 at 23.25.34.png

11 minutes ago, dsynos80 said:

Works Great!!!

 

I suppose that if i choose in the future to enable iGPU and go with 19.1 SmBios i can use the same.

 

You must be an octopus man... how many hands do you have?

 

Thnx!

Screenshot 2020-03-03 at 23.25.34.png

 

@MaLd0n Is the Jedi Master of this world, Without him all my work would be for nothing. I bow to he's mighty powers and always will and am dedicated decibel of he's and what he says goes simple as. Thats enough brown nosing from me now... :hysterical:

 

  • Like 1
  • Thanks 1

So beta 4 (19E250c). I'm seeing improvement in Navi support. I had lots of issues before from the loading of macOS to drawing the sign in prompt. I would lose resolution and it would default back to 1080p. Desktop would load in native but it was jarring.

 

I still don't get a smooth transition from initial boot to sign in but it's holding the res. I was seeing random times in the last build where it would hold. Super rare.

 

Waking my display (LG UK850) is now really responsive where all prior builds would fade in the display twice. Apple/AMD has indeed been fixing the Navi cards from what I'm seeing.

 

Also, the well is finally visible now (wasn't before starting from 10.15.x). So definitely a ton of bugs crushed on the Navi drivers :thumbsup_anim:

 

IMG_0011.thumb.jpeg.b33fdb789ca6e3c39b524f33f3b6cf5c.jpeg

 

PS: Sorry @AudioGod still no diff in performance.

Edited by Tiem
  • Thanks 1

Have done a fresh Catalina, f12 bios, and clover 5104 on my new Gigabyte 390 board - can get to login screen but USB just doesn't work so can't enter login/password.

 

Using IGFX as it'll be mostly file serving with a raid card and lots of drives.

 

Used the HD630 Z390 Pro F12d EFI 140220 EFI folder and that gets me to login screen but no further. Any suggestions where i can start? been x86-ing for 11-12 years now but this has me stumped!

 

Edit: also worth noting i get this panic and a few restarts here and there: 

panic(cpu 2 caller 0xffffff80004652fa): Kernel trap at 0xffffff7f84f1efd2, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000001dc, CR3: 0x0000000017170000, CR4: 0x00000000003626e0
RAX: 0x4a746d3640b90076, RBX: 0x0000000000000003, RCX: 0x0000000000010002, RDX: 0x0000000000000001
RSP: 0xffffff81f16cbe20, RBP: 0xffffff81f16cbea0, RSI: 0x0000000000000001, RDI: 0xffffff8034d77840
R8:  0x0000000000000001, R9:  0x0000000000000002, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0xffffff8034b0e000
RFL: 0x0000000000010202, RIP: 0xffffff7f84f1efd2, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000000000001dc, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 1

Backtrace (CPU 2), Frame : Return Address
0xffffff81f16cb880 : 0xffffff800033bb2b 
0xffffff81f16cb8d0 : 0xffffff80004734d5 
0xffffff81f16cb910 : 0xffffff8000464f4e 
0xffffff81f16cb960 : 0xffffff80002e2a40 
0xffffff81f16cb980 : 0xffffff800033b217 
0xffffff81f16cba80 : 0xffffff800033b5fb 
0xffffff81f16cbad0 : 0xffffff8000ad2aa9 
0xffffff81f16cbb40 : 0xffffff80004652fa 
0xffffff81f16cbcc0 : 0xffffff8000464ff8 
0xffffff81f16cbd10 : 0xffffff80002e2a40 
0xffffff81f16cbd30 : 0xffffff7f84f1efd2 
0xffffff81f16cbea0 : 0xffffff7f84efbf9a 
0xffffff81f16cbee0 : 0xffffff8000a4109d 
0xffffff81f16cbf30 : 0xffffff8000a3f9e2 
0xffffff81f16cbf70 : 0xffffff8000a3ef6c 
0xffffff81f16cbfa0 : 0xffffff80002e213e 
      Kernel Extensions in backtrace:
         com.apple.driver.AppleIntelCFLGraphicsFramebuffer(14.0.4)[A30AC04F-FB51-328A-8942-A2BE0CEB5C3D]@0xffffff7f84ec9000->0xffffff7f850f6fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f80d2f000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[3D78401B-5D2D-33BC-9E41-DD2164EA874D]@0xffffff7f81436000
            dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f8175d000
            dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f810c8000
            dependency: com.apple.AppleGraphicsDeviceControl(4.7.2)[2F63196D-03C6-3E49-BE5D-574F4AADED1A]@0xffffff7f81835000
            dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f816fe000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 -v 

Mac OS version:
19D76

Kernel version:
Darwin Kernel Version 19.3.0: Thu Jan  9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64
Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE
__HIB  text base: 0xffffff8000100000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 13863656522
last loaded kext at 8254357537: >AudioAUUC	1.70 (addr 0xffffff7f842a8000, size 32768)
loaded kexts:

 

Edited by smidge
7 hours ago, smidge said:

Have done a fresh Catalina, f12 bios, and clover 5104 on my new Gigabyte 390 board - can get to login screen but USB just doesn't work so can't enter login/password.

 

Using IGFX as it'll be mostly file serving with a raid card and lots of drives.

 

Used the HD630 Z390 Pro F12d EFI 140220 EFI folder and that gets me to login screen but no further. Any suggestions where i can start? been x86-ing for 11-12 years now but this has me stumped!

 

Edit: also worth noting i get this panic and a few restarts here and there: 


panic(cpu 2 caller 0xffffff80004652fa): Kernel trap at 0xffffff7f84f1efd2, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000001dc, CR3: 0x0000000017170000, CR4: 0x00000000003626e0
RAX: 0x4a746d3640b90076, RBX: 0x0000000000000003, RCX: 0x0000000000010002, RDX: 0x0000000000000001
RSP: 0xffffff81f16cbe20, RBP: 0xffffff81f16cbea0, RSI: 0x0000000000000001, RDI: 0xffffff8034d77840
R8:  0x0000000000000001, R9:  0x0000000000000002, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0xffffff8034b0e000
RFL: 0x0000000000010202, RIP: 0xffffff7f84f1efd2, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000000000001dc, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 1

Backtrace (CPU 2), Frame : Return Address
0xffffff81f16cb880 : 0xffffff800033bb2b 
0xffffff81f16cb8d0 : 0xffffff80004734d5 
0xffffff81f16cb910 : 0xffffff8000464f4e 
0xffffff81f16cb960 : 0xffffff80002e2a40 
0xffffff81f16cb980 : 0xffffff800033b217 
0xffffff81f16cba80 : 0xffffff800033b5fb 
0xffffff81f16cbad0 : 0xffffff8000ad2aa9 
0xffffff81f16cbb40 : 0xffffff80004652fa 
0xffffff81f16cbcc0 : 0xffffff8000464ff8 
0xffffff81f16cbd10 : 0xffffff80002e2a40 
0xffffff81f16cbd30 : 0xffffff7f84f1efd2 
0xffffff81f16cbea0 : 0xffffff7f84efbf9a 
0xffffff81f16cbee0 : 0xffffff8000a4109d 
0xffffff81f16cbf30 : 0xffffff8000a3f9e2 
0xffffff81f16cbf70 : 0xffffff8000a3ef6c 
0xffffff81f16cbfa0 : 0xffffff80002e213e 
      Kernel Extensions in backtrace:
         com.apple.driver.AppleIntelCFLGraphicsFramebuffer(14.0.4)[A30AC04F-FB51-328A-8942-A2BE0CEB5C3D]@0xffffff7f84ec9000->0xffffff7f850f6fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f80d2f000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[3D78401B-5D2D-33BC-9E41-DD2164EA874D]@0xffffff7f81436000
            dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f8175d000
            dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f810c8000
            dependency: com.apple.AppleGraphicsDeviceControl(4.7.2)[2F63196D-03C6-3E49-BE5D-574F4AADED1A]@0xffffff7f81835000
            dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f816fe000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 -v 

Mac OS version:
19D76

Kernel version:
Darwin Kernel Version 19.3.0: Thu Jan  9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64
Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE
__HIB  text base: 0xffffff8000100000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 13863656522
last loaded kext at 8254357537: >AudioAUUC	1.70 (addr 0xffffff7f842a8000, size 32768)
loaded kexts:

 


Hi,

a few people have been having problems with the hd630 EFI but we have retested it in the last few days and it’s working for us so I think it’s being picky from different variants of hd630 from different cpus and I’m also a bit stumped myself about it. I’m going to drop support for this EFI im afraid as it seems to have to many variables from one person to the other and as I no longer use the Z390 Pro as my daily driver anymore it’s abit difficult for me to resolve properly.

Sorry about that.

one thing we did notice is it helps any is what and how many pci lanes are in use seems to have an effect in the EFI. Also the amount of people who have problems with it compared to the amount of people it works for Straight away is tiny. It’s something like 4 out of 300 but it’s still enough to bug me..lol

Edited by AudioGod
5 minutes ago, dsynos80 said:

1.1 is rock solid for me since day 1. Not  a single crash.

 

19.1 has caused random crashes and display problems with igpu on. 

1,1 on a vega works great tbh, so should 19,1 too though but the z390 pro is a tricky board to get the igpu working properly. You can try reducing the igpu memory too 32mb and see if it helps for you.

 

Edited by AudioGod
  • Thanks 1

I’ve found that to reliably load without MemoryAllocation.efi, 32MB is ideal. I had an impossible time trying to get any memory for the kernel with 64. Even after clearing the bios and nvram, malloc errors. 32 left plenty of space.

 

Going down to 16MB might help too if you have system instability.

 

For me both 19,1 and 1,1 work just fine. Other than memory problems I’ve never had any serious issues with this build.

  • Like 1
3 minutes ago, Tiem said:

I’ve found that to reliably load without MemoryAllocation.efi, 32MB is ideal. I had an impossible time trying to get any memory for the kernel with 64. Even after clearing the bios and nvram, malloc errors. 32 left plenty of space.

 

Going down to 16MB might help too if you have system instability.

 

For me both 19,1 and 1,1 work just fine. Other than memory problems I’ve never had any serious issues with this build.

Yep your spot on there,

Its that pesky pro board.

on the Z390 Master I can jump from 19,1 too 1,1 using any of my EFIs and a quick nvram clear from the bootpicker and it’s never a problem and I’ve never had a failure to boot.

 

  • Like 1

Yeah the Pro is a train wreck. You could be booting fine for ages then one day, malloc errors. Even calculating the slide value is no guarantee. But outside of that, never had any serious problems with your EFI. Nothing like system instability or KPs :D

 

I should give 1,1 another chance see if it doesn't solve some of the little niggles like the emoji thing. I never really use Sidecar anyway so no big loss.

Edited by Tiem
24 minutes ago, Tiem said:

Yeah the Pro is a train wreck. You could be booting fine for ages then one day, malloc errors. Even calculating the slide value is no guarantee. But outside of that, never had any serious problems with your EFI. Nothing like system instability or KPs :D

 

I should give 1,1 another chance see if it doesn't solve some of the little niggles like the emoji thing. I never really use Sidecar anyway so no big loss.

Yeah please do so using the new beta because the crashing 5700xt isn’t a hack problem it’s a Mac problem so if they have sorted out the drivers in theory 1,1 should be stable now.

if you try it I look forward to hearing the results.

maybe I should slap my test drive in and update to the latest beta and go on a rocket league session for an hour cos that’s a dead cert for killing my hack under 1,1 lol

 

  • Like 1
3 minutes ago, texem said:

no crash with 1,1 profile here since 10.15.2. Now with latest beta 4 stable as usual.

 


yeah but you don’t game do you or super stress the gpu and they are the things that make 1,1 go bye bye for all of us. Me and @larabee have both tried and for sure it’s got better but it still happens. Beta 4 has Navi fixes and that’s where my hopes are resting now brother.

@texem you good sir, all ok?

  • Like 1
10 minutes ago, AudioGod said:

Beta 4 has Navi fixes and that’s where my hopes are resting now brother.

@texem you good sir, all ok?

 

yeah, still no Corona here :) 

 

btw: with Tomb Raider i had no crashes , well it might be not super stress but i heard others still have glitches 

1 minute ago, texem said:

 

yeah, still no Corona here :) 

 

btw: with Tomb Raider i had no crashes , well it might be not super stress but i heard others still have glitches 

 

Uhh try Total War 3 Kingdoms max out everything for several hours to see how it goes. I think it depends on the power table and each brand has slightly different power delivery, that's the problem here. 

  • Like 1
3 minutes ago, larabee said:

 

Uhh try Total War 3 Kingdoms max out everything for several hours to see how it goes. I think it depends on the power table and each brand has slightly different power delivery, that's the problem here. 

 

that's what I think too, in windows under 20.2.2 you can see they have changed the power tables when your overclocking it, much less power draw for me under the latest drivers while pushing the life out of the card. 

@AudioGod, @texem I'm running the build texem shared adapted for OC 0.5.6 (tons of changes) with my own USB mapping and some edits to OC quirks. Up to date on all the efi's and kexts. I ported the same setup to Clover too. Both return pretty identical results.

 

I'm running 19,1 in headless. I never had the issues you have in 1,1 when I ran that briefly but then I didn't stress the 5700 at all. TBH I don't really game in macOS so if it's just about pushing the card too hard, I'm good there. How do you find it in Windows? I'm up to the latest drivers and the card is still pretty iffy when it's under load (J-temps ~90°). It's a lot better but will still randomly black out the screen or corrupt explorer to a crawl.

 

I'm at least gonna try 1,1 for you regardless. If it can fix my emoji delay that's great. I'll toss Cinebench at mine for a while and see what happens :ph34r: But beta 4 is legit a big leap forward for the Navi chips.

 

2 minutes ago, Tiem said:

@AudioGod, @texem I'm running the build texem shared adapted for OC 0.5.6 (tons of changes) with my own USB mapping and some edits to OC quirks. Up to date on all the efi's and kexts. I ported the same setup to Clover too. Both return pretty identical results.

 

I'm running 19,1 in headless. I never had the issues you have in 1,1 when I ran that briefly but then I didn't stress the 5700 at all. TBH I don't really game in macOS so if it's just about pushing the card too hard, I'm good there. How do you find it in Windows? I'm up to the latest drivers and the card is still pretty iffy when it's under load (J-temps ~90°). It's a lot better but will still randomly black out the screen or corrupt explorer to a crawl.

 

I'm at least gonna try 1,1 for you regardless. If it can fix my emoji delay that's great. I'll toss Cinebench at mine for a while and see what happens :ph34r: But beta 4 is legit a big leap forward for the Navi chips.

 

not cinibench that's cpu not gpu stress and won't make a difference, your be stable. you need to run a semi complex game for a while or stress the hell out of the gpu with some hefty rendering for a prolonged amount of time or anything like that should do it.

 

have you tried reseating and pasting the heatsink for the gpu cos my nitro ran a fair bit cooler when I was using it?

yeah sorry, not Cinebench, not sure what I was thinking. Heaven.

 

The card is all stock. I could do the washer trick and apply some quality TP. Just haven't gotten around to it. This will be a good test of stock. If I can get the system to crash, maybe I'll try getting better cooling and test again.

 

Can you shoot me a copy of 1,1 on rails? The one using SSDT-EC-USBX.aml. Have you updated to OC 0.5.6? If not I can shoot you a copy of my 19,1

8 minutes ago, texem said:

(if not already known) : metal benchmark for caty  https://www.basemark.com/benchmarks/basemark-gpu/

 

no super stress , just another test

 

 

Nice one, that's one to add to the test collection :thumbsup_anim:

 

7 minutes ago, Tiem said:

yeah sorry, not Cinebench, not sure what I was thinking. Heaven.

 

The card is all stock. I could do the washer trick and apply some quality TP. Just haven't gotten around to it. This will be a good test of stock. If I can get the system to crash, maybe I'll try getting better cooling and test again.

 

Can you shoot me a copy of 1,1 on rails? The one using SSDT-EC-USBX.aml. Have you updated to OC 0.5.6? If not I can shoot you a copy of my 19,1

 

ah ha, stock as in reference card?

if so then that's what im using now but have it under water and its the best 5700xt of the bunch I think but 100% take off the cooler and scrape off that rubbish between the die and cooler plate and get some thermal grizzly or what ever you like to use on there and put it back together and yes do the washer mod to it..

if you have any knocking around, the Ek washers that comes with there pumps or rads are spot on perfect to use for the mod. 

 

Ive got it for the master and I updated the thread with all new EFIs of all variants last night.

Got everything ready to do the same on here just waiting on feedback before I post. no OC dsdt free for the pro just yet under 19,1 but that's about to go under test too.

I haven't got a copy of the pro 1,1 EFI around me at the second, Ask mr Texem for that one :)

Edited by AudioGod
×
×
  • Create New...