meina222

9 minutes ago, fabiosun said:

@meina222sleep is often a pain..but here after MMIO job was simple to have it working

often a bad sleep/wake is related to USB and mapping it on apple limit could help

For AMD i do not think is useful..but I can be wrong

 

Dummy Power management flag is there in your config flag, why?

it is a sort of null power management kext..and you should not use it

I think many AMD users want to emulate intel CPU power management ..for me this is wrong...

AMD is different and it has a great BIOS power management tool..I would trust on it

not faking intel stuff 🙂

But also here is just an opinion 🙂

 

 

DummyPowerManagement is there because it was enabled in @iGPU's initial config off which mine is based. I disabled it, and booted fine - then tried sleep, but still didn't work. Then 30 sec later my computer randomly rebooted. So maybe it's not good for my setup. Don't know. I re-enabled it now, mainly due to this reboot. Didn't have such issues prior.

@fabiosun, when you have a chance, could you share your BIOS power settings? For Gigabyte boards "wake on lan" option affects Shutdown. Wonder if something else affects sleep.

@fabiosun - when I installed I needed WEG as without it, I would get black screen - my GPU needs agpmod pikera. Will re-try w/out later tonight.

I have the NVRAM SSDT but I disabled it to find out if I can boot without any SSDT. Answer is "yes". I need NVRAM and have it enabled in my current EFI.

For Sleep it'd be great to see a good analysis - it seems a bit of a black magic if it works or not. I am yet to find a great guide for USB setup, it's a bit of a guesswork. So far @iGPU's SSDT's make sense but I keep wondering why it is done the way it's done and my Hackintool output is all over the place. I never understood what it tells me.

Update: confirmed that WEG is required for me. Without it I get black screen. I am the only one with 5700XT so far so maybe that is why.

Does anyone have a BigSur installation with sleep working? The last remaining item that triggers my OCD (of course) :). I have a feeling the fix there would be something simple - along the lines of a BIOS change or USB tweak.

@fabiosun

I did additional testing with very "barebones" EFI - no SSDT as you suggested and changing MMIO as you proposed. This is BigSur. I think maybe more kexts can be removed, I left a few in.

So your proposed MMIO works with slide=0. I think this is better to include in a common guide as mine required slide=80. But one needs to test over many boots to be 100% sure.

Sleep still does not work. Shutdown works. So sleep is definitely related more to something on my board rather than MMIO. Sharing this barebones config plist I used to boot in. Unfortunately I need NVRAM and bluetooth so I need to add back SSDT's for these to work.

config.plist.zip

@fabiosun - I just did the shut down/restart sound test. Indeed the Realtek disappeared and is not recognized when the headphones are plugged. I never noticed that since I always keep my headphones plugged in my monitor using DisplayPort which works fine on shutdown/restart.

Just tested my USB sound ports. They work (updated in my previous posts on what works and what not), but on some test sound videos it's better and on some I can perceive occasional crackling when switching from left to right. The crackling occurs on this video - only when shifting, and as my headphones are not professional quality it's hard for me to judge. I would get a special sound card or USB device if I was worried about it.

e.g. this one 

Front and back "out" only. I don't have microphone or other professional equipment

@fabiosun

System is very good now, except for sleep (and I think maybe my USB capability on ports needs to be tested carefully and optimized). I agree that MMIO should be firmware specific. There should be only a guide how to find yours and not specific addresses. I never used the Dortania ones (we went over these before and knew they were wrong).

Back to the last problematic feature - sleep. How many people have sleep working? @fabiosun - yours works, correct? Do you think it was the MMIO that made it work? It's entire possible sleep is related to something else.

12 minutes ago, Ploddles said:

@meina222

 

Sorry I didn't credit you earlier on the 'wake on lan' setting. By the time I had caught up reading all the posts, I couldn't remember or see again when skimming through who had mentioned it. Credit where credit is due, I would never have thought of that as a possible reason for the shutdown issue. Kudos to you 🙂 

No problem :). I must admit I was very excited because I have slight OCD and this shutdown bothered me a lot. But honestly, it's most important to confirm from all other boards that this option exists and works for them. In the end this hopefully can create 1 guide for all.

8 minutes ago, fabiosun said:

and i permit myself to say:

"n my experience, there seem to be many MMIO configurations that would make you system boot"

this is a not correct way to interpret DevirtualizeMMIO flag we have to use to boot on trx40

 

in big friendship Iam saying ...on a pub drinking beer 🙂

 

LOL - no problem :). Sorry, I think I am bad reader.

DevirtualizeMMIO is not well explained. It seems to be a way to free certain regions of memory so the kernel can load but this is a very crude explanation. There are many ways to allocate and free memory (I should know that because I actually develop in C++ for a living so I think I do understand overall the concept of virtual memory - and in particular why "devirtualizing" frees memory - because you don't need additional space to store virtual lookup tables).

However, the explanations on the methods are not very clear. 

Do you believe above MMIO change addresses SLEEP specifically?

Sorry I think I misread your post. I now realize you propose these changes for "my MMIO". My bad. I don't know how good the guide is.

Let me try this change. But maybe then I need to set slide=0?

@fabiosun - commenting on your MMIO

In my experience, there seem to be many MMIO configurations that would make you system boot. And perhaps many that would make your shutdown and NVRAM work. The goal is to find the optimal one where you disable the least amount of memory ranges and enable the rest. For me that combo was (from bottom to top), 2 ON, 2 OFF, ALL rest ON. You can check in my config and log.

This worked great for NVRAM and shutdown, but it was too tight without a slide and would sometimes not boot. More often it would not work on hot reboots, and more often it would work in cold starts. Not sure why. So I calculated slide=80 using the Dortania guide. Turns out OC log already hints what the right slide should be.

I am not eager to recommend this method, as I myself do not understand it well. But it is consistent with Dortania (and @iGPUs guide).

1 minute ago, fabiosun said:

@meina222I think also no one of those four are mandatory to boot..but I repeat myself every user have to try what it is better for him

 

With MSI creator, Asrock Creator, MSI Pro 4g no need to boot of any ssdt

then, maybe some are useful for NVRAM , for thunderbolt and some renaming..

but I would stay more simple..

 

I must admit I have not tried to boot without 1-4. I do notice they are being strongly recommended by @iGPU and also Dortania has similar recommendations so I choose to include them.

1 minute ago, fabiosun said:

all your ssdt I see are mandatory to boot your system?

 

No - only the ones numbered 1-4. I think 5 (system bus) could be added but not essential.

The non-numbered ones are my own (lots of them with generous help from @iGPU and they do various things specific to my setup).

config.plist.zip

@fabiosun - here it is. Thank you!

I am curious to hear about shutdown from other people not on Gigabyte boards. So far for myself and @Ploddles, turning OFF "wake up on LAN" option in BIOS fixes shutdown. I think a "good" MMIO is a pre-requisite for that though so MMIO comes 1st.

7 minutes ago, fabiosun said:

I think you should try the exact schema I propose because it is working without any ssd or particular config options

obviously with your conversion MMIO number

 

@fabiosun - would love to try. Do you mind sharing again - I think I have lost or missed this post as right now there is a lot of activity!

Sleep is the only thing not working right now. Edited above to include that. Display sleeps and can wake up, PC stays ON. My USB's still need work I think, I will try to play with that using plugging in devices and  IOReg and set types correctly. But Sleep is the least important right now for me.

@fabiosun

Attached is my OC debug log. GB Designare TRX40. So far working:

1. NVRAM

2. Stable boot (slide=80 + MMIO as indicated in the log). For me slide=80 is important as otherwise boot would sometimes not work.

3. Shutdown (posted how to fix it last night, @Ploddles confirmed it works, perhaps he saw my post or found it himself)

4. Bluetooth and wireless

5. HDMI sound through Lenovo P32u-10 (Display Port)

If not plugged on startup:

5. Rear output sound (onboard Realtek USB)

6. Front output sound (onboard Realtek USB)

Not working:

1. Sleep (only monitor turns off and sleeps properly and then can come back after input from user)

2. If output plugged on startup Realtek USB disappears. Not a problem with DisplayPort.

No tested yet:

USB sound. I use  HDMI Navi as it works perfectly for me, will retest Realtek.

I will only post EFI if someone specifically asks me, and would happily do so! I think we just wanted to respect the rules of not having too many EFIs floating around and maybe confusing people.

opencore-2020-08-30-130759.txt.zip

@fabiosun - I probably wasn't clear enough. I had 2 problems - 1) Start up (especially after reboot) would not always work - OC would fail in same way as if MMIO was not devirtualised. But sometimes it worked - it was non-deterministic (for me at least). As MMIO succeeded using cold reboot when doing the test described in Dortania, I figured it must be the slide as the slide is related to KASLR which is randomized. Now slide=80 fixes that issue for me. No more non-determinism. 2) Shutdown (or rather reboot after it). This was partly related to MMIO, and then partly related to what I describe next:

@iGPU, @Driftwood. I fixed shutdown. It works now, no problem. I turned off "Wake up on LAN" in my BIOS power settings. Now this puppy goes to full power down without an issue. Maybe all boards have this setting. I remembered I wanted to try that but didn't get a chance as my Catalina bare metal got corrupted so forgot. Until now. Hope it works for you too.

p.s. forgot to try sleep. Signing off, will try it tomorrow.

6 minutes ago, fabiosun said:

I believe that more or less our motherboards have the same problems and behaviors

analyzing the logs of some of them I saw that the number of pages contained in the mmio groups are identical ..

obviously I don't know if the contents of the same

But the scheme I tested on my MSI also works on the asrock creator and it certainly worked also on MSI creator

in the various tests you are doing it is very simple to do this test with a basic EFI

now i am trying to mix this with Efi proposed by @iGPU because i assume that with his EFI is it possible to do a fresh installation of big sur os

this is the latest goal for me to reach

for now i can do a fresh install with old Osx but not with the newer one

You won't believe it, but I had the most twisted "successful" installation ever.

I 1st started with @iGPU's EFI, but would get freezes at 3-4 min in. I would try to erase all my partitions for clean install. But erasing a partition doesn't mean the files in it are deleted! So when the installer froze it did it AFTER it re-created the partitions but BEFORE it overwrite the install target disk EFI, so my old Catalina EFI survived! And because of an obscure option I used in the Catalina config.plist (enable bootstrap) on next reboot OC autoselected that without me realizing (as if someone changes the default boot option in BIOS), so I actually succeeded installing it using the 0.6.0 OC Catalina EFI and not the 0.6.1 by iGPU. Don't ask me how! I keep that EFI still though - still not sure if I re-try the install, if it will work or not with 0.6.1.

Meaning that if MMIO is bad it won't boot (as opposed to boot sometimes). If MMIO boots sometimes but then randomly fails, one needs to look at slide. In my case leaving slide to default was causing these reboot failures, which look very similar to if MMIO is not devirtualised in the log. For me right value is slide=80. Now I get consistent boots.

Geekbench 5 loves bare metal and Big Sur 😎 - I think this is the highest I've seen and almost matches Linux! New OC fixes single core scores:

https://browser.geekbench.com/v5/cpu/3482941

Cinebench is unchanged at 21K same as VM

Geekbench Metal is also 75K same as VM.

I am amazed still at how good VM is given the stability and predictability I get from it.

@iGPU, @Driftwood - the MMIO was fine. In my case I needed to provide a slide=80, which I calculated using memmap. I think before it was a matter of luck as I succeeded sometimes and failed sometimes and the appearance of success on cold boot might have to do with the memory being reset, or just pure bias based on small samples where in fact it was always random.

OC log itself tells you actually the slide range and mine turns out to be the lower end of it.

04:892 00:001 OCABC: Only 176/256 slide values are usable!

104:893 00:001 OCABC: Valid slides - 80-255

I independently verified that 80 is indeed the least address under 256 in my memmap that is available (the derived from the Dortania formula address matching 79.5 which needs to be rounded to 80). Now my warm reboots work fine.
 

I now have only the shutdown problem (and maybe sleep haven't tried it), which everyone else faces.

@iGPU - I downloaded the EFI. you can delete it.

After every reboot  get this 

Yes, it does after disabling the AX200 with an SSDT as per @iGPU's post half a page above this.

The 2 big issues I have:

1. Not able to boot in after a shutdown or a restart (peculiar as I have not seen anyone else report this)

2. Shutdown itself still doesn't work but is close as we need to identify what causes the system to spring back to life after the click off.

@tsongz - the Dortania guide is discussed earlier in this topic. The MMIO address section of it is not accurate as it does not apply to many motherboards/configurations. I would rather follow @iGPU's posts and try to start from his EFI's.

Some further observations on Big Sur:

• NVRAM works! Kudos, @iGPU

• Shutdown clicks and turns off and immediately re-boots back up. Still unresolved even after USB remap (which I think needs more work as my port types are not 100% correct)

• Whenever I reboot or shutdown (which turns into a reboot after the power off click), I cannot boot back in. Most of the time if not always. Stop is early on in the same manner as if my MMIO's are incorrect. But then when I power cycle the PC, I can boot back in without a problem. This is very weird and is the most serious issue so far.

@iGPU, My attempt to define my ports (and remove that PRT5 that is the AX200 BT as you showed me earlier) is attached.

Unlike Catalina, this one doesn't seem to work though. It's the last of my SSDT's. Attaching EFI, IOReg. Could you please help with checking if anything is off?

EFI.zip BSiMacProIOReg.zip

Edit: Digging thru my OC log I see this:

09:224 00:001 OC: Failed to find ACPI SSDT-TRX40-DESIGNARE-XHC

That's weird - file was there (forgot to add .aml but I don't think that matters if name matches).

Update: BT fixed. I erased and reapplied the SSDT and changed its name to have .aml (latter wasn't the issue I think but better for consistency). Must have had some subtle typo.

I still do get occasional failures to boot as if my MMIO is not correct but it is non-deterministic.