X299 Big Sur Support

[rustEswan]

Sounds good Btw I think GPRW disables wake from usb devices. Not a deal breaker for some people but it's nice to just press a button on the bt keyboard to wake up

If you really wanted you could edit your GPU-DISABLE SSDT and device properties to have the name of the RTX card and fix the slot number. See my Rampage VI Extreme Encore EFI for an example

shinoki7/ASUS-X299-Hackintosh

Contribute to shinoki7/ASUS-X299-Hackintosh development by creating an account on GitHub.

github.com

Interesting, I was running

pmset -g log | grep -e "Sleep.*due to" -e "Wake.*due to"

to check the reason it wasn't sleeping and noticed that is was receiving what looked like wake from USB (or LAN) calls even though that was disabled in BIOS.
I was seeing this over and over again until I applied the GPRW patch.

2021-04-24 17:26:24 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to XHCI GBE1/Network Using AC (Charge:0%) 45 secs

It would be handy to just hit the keyboard though - perhaps I'll investigate further.

I did have Device properties set to disable the GPU at first, and while that worked it did cause some Apps to crash, like MacCPUID or Intel Power Gadget. SSDT seems to work better though. I like the idea to add the cosmetic bits back to device properties, will check that out now

 

[djlild7hina]

@djlild7hina, any idea what could be causing KP from my post? I am using 11.2.3.
I believe it is somehow connected to 10gbe or USB, but I don't really know how to read KP report.

Any good reason to upgrade to newer beta with X299 SAGE 10G and dual Radeon VII...? Also, is is possible to "upgrade" beta to final without doing clean install?

I'm not sure what could be causing it, you could try signing up for the public beta to install 11.3 RC (public release might be this week tho). But yes, updates have been very smooth but make a backup just in case.

You could try using Sonnet 10G drivers (requires Ubuntu EEPROM flashing) but I'm not sure if it'll be different. Proceed at your own risk!

GitHub - shinoki7/ASUS-X299-Hackintosh

Contribute to shinoki7/ASUS-X299-Hackintosh development by creating an account on GitHub.

github.com

Do you have another NIC you can try? does the same issue happen with a clean install?

 

[djlild7hina]

Interesting, I was running

pmset -g log | grep -e "Sleep.*due to" -e "Wake.*due to"

to check the reason it wasn't sleeping and noticed that is was receiving what looked like wake from USB (or LAN) calls even though that was disabled in BIOS.
I was seeing this over and over again until I applied the GPRW patch.

2021-04-24 17:26:24 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to XHCI GBE1/Network Using AC (Charge:0%) 45 secs

It would be handy to just hit the keyboard though - perhaps I'll investigate further.

I did have Device properties set to disable the GPU at first, and while that worked it did cause some Apps to crash, like MacCPUID or Intel Power Gadget. SSDT seems to work better though. I like the idea to add the cosmetic bits back to device properties, will check that out now

Yeah I had that same issue on my Rampage board, only way I could fix it was GPRW patch. Didn't really investigate any further for fixes since it's not a deal breaker lol

Ah I meant just keep the SSDT to disable GPU but modify the model and use device properties for cosmetic parts

 

[NorthAmTransAm]

Ah I figured there was no patched firmware yet but was just curious on extracting the firmware.

Copy that.

Same procedures as before though it is a different chip than the Winbond. I eventually captured 3 identical firmwares but initially had trouble. I ruined my chip actually (stupid stupid stupid) and am getting a socket put in its place right now so I can drop in new ones as I test.

If you do manage to capture a few send them my way and we can compare just in case something is different! God speed.

 

[djlild7hina]

Copy that.

Same procedures as before though it is a different chip than the Winbond. I eventually captured 3 identical firmwares but initially had trouble. I ruined my chip actually (stupid stupid stupid) and am getting a socket put in its place right now so I can drop in new ones as I test.

If you do manage to capture a few send them my way and we can compare just in case something is different! God speed.

Will do! Hopefully your socket thing works well!

just confirming this command works?
sudo flashrom -p ch341a_spi -r Give_the_Contents_a_Name.bin

 

[rustEswan]

Yeah I had that same issue on my Rampage board, only way I could fix it was GPRW patch. Didn't really investigate any further for fixes since it's not a deal breaker lol

Ah I meant just keep the SSDT to disable GPU but modify the model and use device properties for cosmetic parts

Definitely the best method, combine the SSDT and Device properties, no crashes of Powergadget and looks a lot cleaner! Thanks for the pointers

 

[NorthAmTransAm]

Will do! Hopefully your socket thing works well!

just confirming this command works?
sudo flashrom -p ch341a_spi -r Give_the_Contents_a_Name.bin

Yep!

Then press the up arrow on the keyboard and arrow back to before ".bin" and add a number. So like "OEMFirmware.bin, OEMFirmware2.bin, etc..."

That way you can capture a few.

You can also use verify like this:

sudo flashrom -p ch341a_spi -v OEMFirmware.bin

 

[djlild7hina]

Definitely the best method, combine the SSDT and Device properties, no crashes of Powergadget and looks a lot cleaner! Thanks for the pointers View attachment 516421

Very nice! Super nitpicky but your GPU audio controllers are duplicated as Display Controllers

 

[rustEswan]

Very nice! Super nitpicky but your GPU audio controllers are duplicated as Display Controllers

Ha ha - well I've gone this far might as well tidy that up too!

 

[rustEswan]

Very nice! Super nitpicky but your GPU audio controllers are duplicated as Display Controllers

I'm being nitpicky now! Not sure what Im doing wrong here but double check device properties and it seems to be ignoring the device properties for the second device and just duplicating the display controller, also double checked the PciRoot path in Hackintool, seems all good - any ideas? (And it is ok to say "no, its just cosmetic stop wasting time!")

Mine:

Yours: