Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

kingvald

macrumors newbie
Original poster
Aug 30, 2020
9
0
Hi, first of all I want to thank you all for helping out and sharing you expertise
🙂
I have successfully installed (cMP 4,1) OC 0.7.3 Martin Lo´s package and dual boot Big Sur 11.2.3 / windows 10. Everything works great except two tings:
  • Windows 10: Driver for the magic mouse to enable scrolling. I have tried several bootcamp drivers but none seem to work... anyone have a link to a working mouse driver?
  • Sleep/wake issue in Big Sur. My Mac doesnt wake from sleep after installing Big Sur. I can hear the machine start but the screen stays black.... any solution?
  • Edit: Windows 10 also wont wake from sleep......
  • Edit 2: Tried to reset pram, didn't work regarding wake issue but now my bluetooth keyboard/mouse is not detected at the boot picker. Defaults to booting windows where the keyboard/mouse also is not detected so I can't log in.... (got hold of a wired keyboard/mouse and booted to macOS... here bluetooth is fine)

    Error:
Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time: 2021-09-23 13:30:34.719 +0200
OS Version: ??? ??? (Build ???)
Architecture: x86_64
Report Version: 32

Data Source: Stackshots
Shared Cache: 1C99695B-39A1-3CF1-BCD1-AB8BF015FD98 slid base address 0x7fff20040000, slide 0x40000

Event: Sleep Wake Failure
Duration: 0.00s
Steps: 1

Boot args: -lilubetaall -wegbeta agdpmod=pikera shikigva=80 unfairgva=1 mbasd=1 -wegtree -no_compat_check no32exec=0 lbloom=30,10,0,150,20

Time Awake Since Boot: 22s



Process: swd [289]
Architecture: x86_64
Footprint: 508 KB
Time Since Fork: 2s
Num samples: 1 (1)

Thread 0x89b 1 sample (1) priority 4 (base 4)
<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
1 start + 1 (libdyld.dylib + 87585) [0x7fff2036d621] 1
1 ??? [0x105e31454] 1
1 ??? [0x105e311e8] 1
1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 143386) [0x7fff2034001a] 1
*1 ??? [0xffffff80002601f6] 1
*1 ??? [0xffffff80009698cb] 1
*1 ??? [0xffffff80008733c1] 1
*1 ??? [0xffffff80002831c9] 1
*1 ??? [0xffffff80002ba3ed] (running) 1

Binary Images:
0x7fff2031d000 - 0x7fff2034bfff libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076> /usr/lib/system/libsystem_kernel.dylib
0x7fff20358000 - 0x7fff20392fff libdyld.dylib (832.7.3) <4641E48F-75B5-3CC7-8263-47BF79F15394> /usr/lib/system/libdyld.dylib
Model: MacPro5,1, BootROM 9144.0.7.3.0, 12 processors, 6-Core Intel Xeon, 3,46 GHz, 48 GB, SMC 1.39f5
Graphics: kHW_AMDRadeonRXVega56Item, Radeon RX Vega 56, spdisplays_pcie_device, 8 GB
Memory Module: DIMM 1, 16 GB, DDR3, 1333 MHz, 0x80CE, 0x4D33393342324737304248302D434B302020
Memory Module: DIMM 2, 16 GB, DDR3, 1333 MHz, 0x80CE, 0x4D33393342324737304248302D434B302020
Memory Module: DIMM 3, 16 GB, DDR3, 1333 MHz, 0x80CE, 0x4D33393342324737304248302D434B302020
AirPort: spairport_wireless_card_type_third_party
Bluetooth: Version 8.0.3d9, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en2
PCI Card: Radeon RX Vega 56, sppci_displaycontroller, Slot-1@7,0,0
PCI Card: pci1002,aaf8, sppci_audiodevice, Slot-1@7,0,1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: Samsung SSD 860 EVO 250GB, 250,06 GB
Serial ATA Device: Samsung SSD 860 EVO 250GB, 250,06 GB
USB Device: USB 2.0 Bus
USB Device: USB 2.0 Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: USB Bus
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:
 
I am in a similar situation except I am on Open Core Legacy Patcher and have a Nvidia Kepler GPU instead.

My machine also wont wake up from sleep...

How did you obtain the above debug output?
 
i will go to home and measure it... but in my case sleep and wake up actually works under Mojave... just that it is broken in Big Sur...
 
I'm following up on this thread. Everything was running fine on my cMP5,1 until recently. I opened it up to dust inside and installed another pcie card, and now it won't wake from the keyboard. I need to press the button on the computer itself. Running Mojave. Any thoughts? Battery shows 100 percent on istats menu, so that's not it.

Should I do some kind of reset? I don't have a start screen, so a bit concerned about how I would even do that.
 
I'm following up on this thread. Everything was running fine on my cMP5,1 until recently. I opened it up to dust inside and installed another pcie card, and now it won't wake from the keyboard. I need to press the button on the computer itself. Running Mojave. Any thoughts? Battery shows 100 percent on istats menu, so that's not it.

Should I do some kind of reset? I don't have a start screen, so a bit concerned about how I would even do that.
You are mistaken, iStat Menus or any other app can't measure the RTC battery, since it's not SMC managed.

Check with a DMM or a voltmeter.
 
Ok, thanks I did t know that. it would be a strange coincidence that it suddenly is the battery. Any other steps you might recommend first?
 
Ok, thanks I did t know that. it would be a strange coincidence that it suddenly is the battery. Any other steps you might recommend first?
Nope, start checking the battery voltage and replace it with a new BR2032 if the voltage is anything below 3.0V.
 
So you think replacing the battery should solve the issue? I don’t have a multimeter, but it is a 2012 machine and a battery is pretty cheap if you think that is the most likely cause I’ll do it.
 
So you think replacing the battery should solve the issue? I don’t have a multimeter, but it is a 2012 machine and a battery is pretty cheap if you think that is the most likely cause I’ll do it.
CR2032 is pretty cheap while BR2032 is not exactly cheap or easy to find. Anyway, it's the first step to debug the issue.
 
Thanks very much. Are you sure a CR2023 wouldn't work as well? The manual for the 2012 cMP says CR2032 and those are easier to find locally.
 
Thanks very much. Are you sure a CR2023 wouldn't work as well? The manual for the 2012 cMP says CR2032 and those are easier to find locally.
CR2032 chemistry is not rated for the temperatures near the GPU. Apple designed the circuit for a BR2032, not a CR2032. While you can use a CR2032, you will have to replace it frequently.

Btw, which page says it's a CR2032? I opened the Apple Technician Manual and searched for CR2032 anywhere and it's not there and Apple never refer to it as anything but battery on the Manual while when parts ordering is only available the BR2032.
 

Attachments

  • Screen Shot 2021-10-31 at 19.05.47.png
    Screen Shot 2021-10-31 at 19.05.47.png
    180.9 KB · Views: 91
Ah, thanks. I'll order a BR2032 and see if that resolves the issue.

I realize the small booklet I have is from my old early 2008 Mac Pro, not my mid 2012 Mac Pro. You'd think they would be the same, but I guess not. That paper booklet definitely says CR2032. (p.64 of the little "Everything Mac" booklet that came with the 2008 Mac Pro.
 
I would like to share that accidentally i found my fix: for some reason i have to enable verbose mode in opencore and then wake up works... I know this is strange.. but I tried turning it on and off again just to be sure and it made the difference for me.
 
Ok, here's the update on my problem which I think I fixed. It seemed to strange to me that the battery would fail precisely after I had opened up the casing and installed a PCIe card. It turns out that I had plugged the USB cable from my Apple 30" cinema display into my aftermarket Newertech USB 3.0 PCIe card and not into the native USB 2.0 plug on the back of the machine. I switched that and all works now. It seems like the NewerTech USB 3.0 card was the problem and was not behaving properly.

Thanks to everyone for your help and suggestions, and I hope this may be useful for someone else experiencing these issue.

That raises the question, what is the best/most compatible USB 3 PCIe card for a cMP 5.1?
 
Ok, here's the update on my problem which I think I fixed. It seemed to strange to me that the battery would fail precisely after I had opened up the casing and installed a PCIe card. It turns out that I had plugged the USB cable from my Apple 30" cinema display into my aftermarket Newertech USB 3.0 PCIe card and not into the native USB 2.0 plug on the back of the machine. I switched that and all works now. It seems like the NewerTech USB 3.0 card was the problem and was not behaving properly.

Thanks to everyone for your help and suggestions, and I hope this may be useful for someone else experiencing these issue.

That raises the question, what is the best/most compatible USB 3 PCIe card for a cMP 5.1?
For your specific use case, AFAIK, changing to a better USB card won't solve the issue of Mac Pro firmware absolute zero support of USB3.0 cards and the poor support of third party USB3.0 controllers by the macOS itself.

Unfortunately, you will continue to have problems with some devices connected to the USB3.0 card when the Mac Pro is entering sleep or wakening.
 
Got it, thanks. That's ok I suppose as for a keyboard/mouse, using the native legacy USB 2 plug works fine. I'm still curious if you have a recommendation for the fasters USB 3 PCIe card that I could plug in external SSDs to get maximum speed. I'm assuming it would be faster than an internal SATA SSD.
 
Got it, thanks. That's ok I suppose as for a keyboard/mouse, using the native legacy USB 2 plug works fine. I'm still curious if you have a recommendation for the fasters USB 3 PCIe card that I could plug in external SSDs to get maximum speed. I'm assuming it would be faster than an internal SATA SSD.

Probably the HighPoint Rocket 1144 line, look at the high end cards that have a PCIe switch. This is the reference thread:



Remember that after your Mac Pro goes to sleep, your SSDs connected to the USB3.0 card will be forcibly disconnected at the wake up time.
 
Thank you, I'll check out the thread. And good reminder that the drives will be forcibly disconnected.
 
Ugh, it happened again and I'm stuck in an endless loop of "Are you sure you want to shut down your computer now?" I don't know what started it. I tested the BR2032 battery and it read 2.82 V on the multimeter, so I replaced it with a CR2032 (I tested it first and it was showing over 3.0V). I did the battery switch very quickly in the hopes that I wouldn't lose dates and when I restarted, all seemed good for a few seconds but then I got the endless loop dialog. The date and time were correct, I did not need to reset them.

Any thoughts on how I can resolve this?

Thanks,

Paul
 
Ugh, it happened again and I'm stuck in an endless loop of "Are you sure you want to shut down your computer now?" I don't know what started it. I tested the BR2032 battery and it read 2.82 V on the multimeter, so I replaced it with a CR2032 (I tested it first and it was showing over 3.0V). I did the battery switch very quickly in the hopes that I wouldn't lose dates and when I restarted, all seemed good for a few seconds but then I got the endless loop dialog. The date and time were correct, I did not need to reset them.

Any thoughts on how I can resolve this?

Thanks,

Paul

You have to reset the RTC when you replace the RTC battery. Reset the RTC, SMC and the NVRAM.
 
Thanks, and sorry, but how do I do that?

Remove power cable from the PSU, press the RTC reset switch next to the RTC battery holder for 2s. Next reset the SMC and NVRAM.

CR2032 is not the correct RTC battery and will self-discharge with the heat from the GPU heatsink in weeks time.
 
Ok, I found the button. When you say remove power cable from the PSU, do you mean just unplug the main cable on the outside, or is there something more to it?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.