Jump to content

fabiosun

Recommended Posts

Giving sleep one more try on Big Sur. At least the system now doesn't lock up but immediately wakes (DarkWake so without display) after I touch the keyboard the display turns on and I get the login prompt.

 

In: pmset -g log is see these coming back which seems to be the cause:

2020-11-13 11:01:13 +0100 DarkWake            	DarkWake from Normal Sleep [CDN] : due to D0A1 D0A2 D0A3 D0A4 D0A5 D0A6 D0A7 D0B0 D0B1 D0B2 D0B3 D0B4 D0B5 D0B6 D0B7 D1A0 D1A1 D1A2 D1A3 D1A4 D1A5 D1A6 D1A7 D1B0 D1B1 D/ Using AC (Charge:0%) 3 secs    
2020-11-13 21:06:20 +0100 DarkWake            	DarkWake from Normal Sleep [CDN] : due to D0A1 D0A2 D0A3 D0A4 D0A5 D0A6 D0A7 D0B0 D0B1 D0B2 D0B3 D0B4 D0B5 D0B6 D0B7 D1A0 D1A1 D1A2 D1A3 D1A4 D1A5 D1A6 D1A7 D1B0 D1B1 D/ Using AC (Charge:0%) 20 secs   
2020-11-13 21:23:54 +0100 DarkWake            	DarkWake from Normal Sleep [CDN] : due to D0A1 D0A2 D0A3 D0A4 D0A5 D0A6 D0A7 D0B0 D0B1 D0B2 D0B3 D0B4 D0B5 D0B6 D0B7 D1A0 D1A1 D1A2 D1A3 D1A4 D1A5 D1A6 D1A7 D1B0 D1B1 D/ Using AC (Charge:0%) 4 secs    
2020-11-13 21:25:12 +0100 DarkWake            	DarkWake from Normal Sleep [CDN] : due to D0A1 D0A2 D0A3 D0A4 D0A5 D0A6 D0A7 D0B0 D0B1 D0B2 D0B3 D0B4 D0B5 D0B6 D0B7 D1A0 D1A1 D1A2 D1A3 D1A4 D1A5 D1A6 D1A7 D1B0 D1B1 D/ Using AC (Charge:0%) 8 secs    
2020-11-13 21:30:16 +0100 DarkWake            	DarkWake from Normal Sleep [CDN] : due to D0A1 D0A2 D0A3 D0A4 D0A5 D0A6 D0A7 D0B0 D0B1 D0B2 D0B3 D0B4 D0B5 D0B6 D0B7 D1A0 D1A1 D1A2 D1A3 D1A4 D1A5 D1A6 D1A7 D1B0 D1B1 D/ Using AC (Charge:0%) 1 secs    

And when snooping around in my DSDT I find them back:

            Device (D0A0)
            {
                Name (_ADR, 0x00010001)  // _ADR: Address
                Method (_PRW, 0, NotSerialized)  // _PRW: Power Resources for Wake
                {
                    Return (GPRW (0x08, 0x04))
                }

                Method (_PRT, 0, NotSerialized)  // _PRT: PCI Routing Table
                {
                    If (PICM)
                    {
                        Return (AG04) /* \_SB_.AG04 */
                    }

                    Return (PG04) /* \_SB_.PG04 */
                }

                Device (D0A7)
                {
                    Name (_ADR, 0xFFFF)  // _ADR: Address
                }
            }

            Device (D0A1)
            {
                Name (_ADR, 0x00010002)  // _ADR: Address
                Method (_PRW, 0, NotSerialized)  // _PRW: Power Resources for Wake
                {
                    Return (GPRW (0x08, 0x04))
                }

                Method (_PRT, 0, NotSerialized)  // _PRT: PCI Routing Table
                {
                    If (PICM)
                    {
                        Return (AG05) /* \_SB_.AG05 */
                    }

                    Return (PG05) /* \_SB_.PG05 */
                }

                Device (D0A8)
                {
                    Name (_ADR, 0xFFFF)  // _ADR: Address
                }
            }

In total there are 64 of these, looks like something CPU related??? Does anybody know of CPU BIOS setting related to sleep?

Link to comment
Share on other sites

Still switch to my Proxmox boot now and again. Thought Id load up the Proxmox Catalina Cinebench 23. Here's results. Proxmox has its uses such as certain Intel primed compiled progs like Camtasia, new Davinci 17 (it flies), Adobe all compatible without hacked dylibs...etc...

 

 

1895125512_ScreenShot2020-11-14at03_21_551.thumb.png.71cd802639b144305cd5090a16c4de2e.png

Screen Shot 2020-11-14 at 03.24.37.png

Edited by Driftwood
  • Thanks 1
Link to comment
Share on other sites

  • Supervisor
5 hours ago, shutterbug168 said:

@Rox67er, what GPU are you using in your hack?  I have the same sleep problem as you do.  And I am using a Radeon VII card, which is known to have sleeping issues...

Screen Shot 2020-11-13 at 6.34.10 PM.png

Welcome here

probably is a problem of your motherboard

Sleep is working fine with radeonVII

in big sur for sure

in catalina some problem

to have success you have to play with your MMIO and bios settings

  • Like 1
Link to comment
Share on other sites

13 hours ago, shutterbug168 said:

@Rox67er, what GPU are you using in your hack?  I have the same sleep problem as you do.  And I am using a Radeon VII card, which is known to have sleeping issues...

Screen Shot 2020-11-13 at 6.34.10 PM.png

Use a Sapphire Radeon VII, I also used it in my old Mac Proc 5,1 where sleep was fine. If I look at the pmset -g log it looks like something CPU related.

11 hours ago, ckrueger99 said:

Are the new versions  Final Cut Pro 10.5, Logic Pro 10.6 and Compressor 4.5 working normally on AMD?

FCP 10.5 is running fine.

  • +1 1
Link to comment
Share on other sites

1 hour ago, shutterbug168 said:

@fabiosun: Thanks!  I didn't realize an AMD bare metal hack would have so many problems running my main apps like Photoshop and Davinci Resolve...:-(  I think I need to try a Proxmox install.  Do you mind re-sharing your Proxmox install guide?

For those who dont know you can share the same catalina/bs NVME INSTALL between two different EFIs for Proxmox & bare metal. ie you dont need to have two separate OS X installs.

 

In my case, one EFI on a USB for bare metal, and the Proxmox efi coming off the boot sector on another nvme. Keeps em safe from corruption.

 

But it means if you need Intel 100% compatibility apps like Camtasia (or you dont wanna dylib hax for Adobe/Davinci) you can simply reboot to Proxmox. I can update apps in both environments - within bare metal & proxmox - and when you return to the other u should have no problems and see everything.

 

Of course for Proxmox you'll need a separate usb (e.g. 64gb thumb or an old ssd drive on the sata/ext usb) for its host system files.

 

Life's easy and enjoy the best of both worlds!

 

PS Logic 10.6 works fine on both Cat latest build and Big Sur.

Edited by Driftwood
Link to comment
Share on other sites

Hmm... The DV version I downloaded this morning was 17.0B1... I will also roll back to Photoshop 21.2.4 and test it... Intel has removed the cpu_type environment variable earlier this year form the MKL library.  I think that's why these patches will not work with newer/future versions of these apps... until we manage to come up with new ways to patch them🤣

Link to comment
Share on other sites

  • fabiosun changed the title to [Discussion] - TRX40 Bare Metal - Vanilla Patches

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.