Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Hello,
I don't know if this issue has been discussed by other people in this thread but I can't perform a search in these 2391 pages :

I booted on Linux from a portable Linux USB key. After that when I wanted to start OS X, I got the good old "Couldn't allocate runtime area". I was able to start after clearing my CMOS AND keeping a USB key plugged (the Linux key, I haven't tried with other keys.)
I've run into this issue a few other times. I'm not 100% sure clearing CMOS and plugging the key is the solution each time, I think another time I had to unplug to key to be able to start, but when I boot my portable Linux distribution I know that I will get runtime allocation errors next and that I'll have to clear the CMOS and try a few times to be able to boot OS X. Any ideas on how to fix this?
I'm using OcQuircks and FwRuntimeServes.

Thanks a lot!
Some questions:
  • Are you running Mojave or Catalina?
  • If running Mojave are you using OcQuirks-4 and FwRuntimeServices?
  • If running Catalina are you using OcQuirks.plist, OcQuirks.efi, and OpenRuntime? (I know you said "FwRuntimeServices" but I'm double-checking.)
  • Are you on Clover 4xxx or 5xxx?
  • Please post a screenshot of the CLOVER folder with the (a) drivers64UEFI or (b) drivers/UEFI folder expanded.
 
@CaseySJ Which volume should I run first aid on, Samsung SSD 970, container disk1, or Mojave?
See that "View" icon on the top left of the screenshot in my last reply? Select that and choose Show All Devices. Then you'll see which disk is Catalina and which is Mojave.

If in double, please post screenshot of the Disk Utility windows after selecting Show All Devices.
 
Hey guys, I am trying to get rid of my numerous maintenance wakes. Here's what my logs say:

2020-07-21 16:03:43 +0200 Assertions PID 206(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000833a [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-21 16:03:43 +0200 Assertions PID 206(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000833a [System: PrevIdle BGTask]

2020-07-21 20:35:48 +0200 Assertions PID 206(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd00008465 [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-21 20:35:50 +0200 Assertions PID 206(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:02 id:0x0xd00008465 [System: PrevIdle]

2020-07-23 12:28:17 +0200 Assertions PID 205(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000858b [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-23 12:28:19 +0200 Assertions PID 205(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:02 id:0x0xd0000858b [System: PrevIdle]

2020-07-23 12:29:56 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using AC (Charge:0%) 755 secs

2020-07-23 12:41:37 +0200 Assertions PID 205(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd000085c1 [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-23 12:41:37 +0200 Assertions PID 205(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd000085c1 [System: PrevIdle BGTask]

2020-07-23 12:43:16 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using AC (Charge:0%) 1241 secs

2020-07-23 13:03:04 +0200 Assertions PID 205(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd000085f8 [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-23 13:03:04 +0200 Assertions PID 205(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd000085f8 [System: PrevIdle BGTask]

Currently in use:

autorestart 0
Sleep On Power Button 1
hibernatefile /var/vm/sleepimage
proximitywake 0
powernap 0
gpuswitch 2
networkoversleep 0
disksleep 10
sleep 20 (sleep prevented by sharingd)
hibernatemode 0
ttyskeepawake 1
displaysleep 20
tcpkeepalive 0
womp 0
@hamzab

I defer this to your expert hands...

Once you have achieved your intended sleep/wake outcome, it would be great if you can create a single post with the lessons learned. I'll either add that to the Sleep Aid or reference it from the Sleep Aid.
 
this is what I see, I'm asking which level of the disk im supposed to run
first aid on, the Samsung bit, the container bit, or the Mojave

Screen Shot 2020-07-23 at 7.29.11 AM.png
 
Some questions:
  • Are you running Mojave or Catalina?
  • If running Mojave are you using OcQuirks-4 and FwRuntimeServices?
  • If running Catalina are you using OcQuirks.plist, OcQuirks.efi, and OpenRuntime? (I know you said "FwRuntimeServices" but I'm double-checking.)
  • Are you on Clover 4xxx or 5xxx?
  • Please post a screenshot of the CLOVER folder with the (a) drivers64UEFI or (b) drivers/UEFI folder expanded.

Hello Casey,
I'm on Catalina 10.15.3, Clover 5103, no OpenRuntime. I haven't touched my config in months.
Here is a screenshot :)
Capture d’écran 2020-07-23 à 15.35.48.png
 
Well I ran it on all 3 while waiting and all came back ok, did a reboot and boot Mojave still isn't in clover
 
Well I ran it on all 3 while waiting and all came back ok, did a reboot and boot Mojave still isn't in clover
One last thing to try before more extreme measures are prescribed...
  • Perform a cold boot. Simply shutdown the system and flip power switch on PSU to off for at least 10 seconds to discharge all capacitors. Then power it back on. Does "Boot macOS Mojave" appear in Clover?
  • If not, let me ask:
    • Is it necessary to use Mojave?
    • Do you have 32-bit applications or plug-ins (which of course won't run on Catalina)?
  • If Mojave is necessary it might be good to install a fresh copy on a spare SSD.
    • Use the same CLOVER folder as you're using now so that the same serial numbers are used
    • Then manually copy all documents to the new drive
    • Reinstall applications and plug-ins on the new drive
    • (Avoid using Migration Assistant)
 
Back
Top