Contribute
Register

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

Hi all! hi Casey! :)
OK, I have this crazy random seed with my new build:

-Z390 Designare BIOS F8
-9900KS
-128GB RAM 3200NHz
-NVMe 870 EVO Plus
-Radeon Vega 56

I tried with and without aptiomemoryfix, optiofix2000, fwruntimeservices + ocquircks.
Nothing works

As well, I tested with one stick memory by one stick.

Thank you so much for your help.

-S
 
Hi all, hi casey :)
Ok, i have this crazy randomseed with my new build:

-Z390 designare bios F8
-9900KS
-128GRAM 3200mhz
-NVMe 870 evo plus
-Radeon Vega 56

i tried with and without aptiomemoryfix, optiofix2000, fwruntimeservices + ocquircks.
Nothing works

As well, i tested with one stick memory by one stick.

thank you smuch for your help

-S
Hey, I had this issue. In clover configurator you will need to go SMBIOS -> Memory, and add 8 entries starting at 0. Then tell the computer you have 8 sticks of 16 gb RAM. I only have 64 gb, but I have attached a screenshot that shows you essentially what you need to do.
 

Attachments

  • Screen Shot 2019-12-21 at 3.12.46 PM.png
    Screen Shot 2019-12-21 at 3.12.46 PM.png
    204.5 KB · Views: 338
There's a 17 second delay in the Kernel process (PID = 0). The relevant kernel log message seems to be:

kernel: ifnet_attach: Waiting for all kernel threads created for interface XHC0 to get scheduled at least once.

View attachment 441533

Please check all BIOS parameters again, particularly USB/XHC-related ones. BIOS settings are in Post #1.

I wonder if it's tied to network timeout issues. Try turning off wifi and disconnect any network cable then try a restart. See if things go faster.

Could it also be an nvram issue? His boot shows that it's updating the time at line 17226.

Code:
2019-12-21 08:52:05.049751-0500 0x532      Default     0x0                  60     0    UserEventAgent: (DuetActivityScheduler) [com.apple.backgroundtasks:framework] Establish daemon connection; interrupted: 0
2019-12-21 13:52:04.761636-0500 0x0        Timesync    0x0                  0      0    === system wallclock time adjusted
2019-12-21 13:52:04.761658-0500 0x39b      Default     0x0                  97     0    opendirectoryd: [com.apple.opendirectoryd:session] Processing a network change notification
 
Hi all, hi casey :)
Ok, i have this crazy randomseed with my new build:

-Z390 designare bios F8
-9900KS
-128GRAM 3200mhz
-NVMe 870 evo plus
-Radeon Vega 56

i tried with and without aptiomemoryfix, optiofix2000, fwruntimeservices + ocquircks.
Nothing works

As well, i tested with one stick memory by one stick.

thank you smuch for your help

-S
Hi Sam,

If you can boot from a USB install disk, please compress and upload the CLOVER folder from EFI partition of the macSSD. Some questions:
  • Do you have the Samsung 870 EVO Plus or 970 EVO Plus? Is it running the latest firmware?
  • Which version of Clover is running? Press F1 at the Clover Boot Menu to show the version number.
  • Because you have 128GB RAM, have you filled out the Memory section in SMBIOS section?
    • If you can post your CLOVER folder, I can take a look.
  • Was this system running properly before (with F8, with 128GB RAM, with same NVMe SSD)?
  • Which version of macOS? 10.14.6? 10.15.2?
 
Looks like I spoke too soon... cue the Homer Simpson "doh"!

IOReg shows that this device implements a 4-port USB 3 hub, where port 1 is a card reader. The other 3 ports are active, but nothing is connected to them.

View attachment 441530

Was this IOReg file saved while a USB 3 device was inserted into any of the three USB Type A ports? If not, please try attaching a USB 3 device and save/post the IOReg file again.

I did have a USB stick inserted when I did the IOReg file. I've been doing some more testing, and it's very random and weird. I did suddenly get the T3 SSD to show up when all three devices were plugged in (the other two did not show up), but then when I withdrew one of the USB sticks, the SSD drive also disconnected. Then I pulled the SSD out and plugged in another stick, then that one showed up. I can't seem to find a pattern except for that I need to plug several drives in to get any to show up, but I can only get one to show up at a time.

I am using a USB 3.1 Type C extender cable to connect this to the computer, but it's very high quality, and when I plug in my one USB-type C stick straight to the extender cable it shows up, no problem. I have double-sided taped the hub to the underside of my desk and would love to not have to tare it down, otherwise I would have tested to stick it straight into the back of the motherboard. :)
 
I wonder if it's tied to network timeout issues. Try turning off wifi and disconnect any network cable then try a restart. See if things go faster.

Could it also be an nvram issue? His boot shows that it's updating the time at line 17226.

Code:
2019-12-21 08:52:05.049751-0500 0x532      Default     0x0                  60     0    UserEventAgent: (DuetActivityScheduler) [com.apple.backgroundtasks:framework] Establish daemon connection; interrupted: 0
2019-12-21 13:52:04.761636-0500 0x0        Timesync    0x0                  0      0    === system wallclock time adjusted
2019-12-21 13:52:04.761658-0500 0x39b      Default     0x0                  97     0    opendirectoryd: [com.apple.opendirectoryd:session] Processing a network change notification
@digumo @heythisisdave

Between lines 501 and 762 there are almost no other kernel log messages ("almost no other" means there are about 5-6 kernel messages), but 261 messages from other process IDs. So the kernel is stuck waiting for this...

Line 501:
2019-12-21 08:51:41.456670-0500 0x15d Default 0x0 0 0 kernel: ifnet_attach: Waiting for all kernel threads created for interface XHC0 to get scheduled at least once.
Line 762:
2019-12-21 08:51:56.780930-0500 0x3a1 Default 0x0 0 0 kernel: ifnet_attach: All kernel threads created for interface en0 have been scheduled at least once. Proceeding.

Of course there may be other delays, but this is the first and most obvious one. Because en0 and ifnet are mentioned, I agree that it's network related.
 
The Intel NVMe with Windows should not interfere.

Thanks I can confirm that the MSI card was the problem. I was able to install with a different card. Thanks!

Windows did get messed up but maybe I did something stupid with disk utility
 
Please try an experiment by reducing memory speed to 2666MHz as follows:
  • BIOS Setup --> Keep X.M.P. Profile 1 enabled.
  • BIOS Setup --> Change System Memory Multiplier to 26.66.
Certain sleep issues such as ejecting disks during sleep are fixed by reducing memory speed. Whether this solves your problem remains to be seen, but it's worth a try.
No luck. I even tried swapping new sticks of ram, 8gb modules thinking it might be something related to my specific sticks of ram. No luck there either. I am not sure if it is a sleep issue. I got the bright idea to check the clock when i stopped touching the computer vs when the clock freezes... and it freezes at 6 minutes from the last time I touched the keyboard.
 
Hey, I had this issue. In clover configurator you will need to go SMBIOS -> Memory, and add 8 entries starting at 0. Then tell the computer you have 8 sticks of 16 gb RAM. I only have 64 gb, but I have attached a screenshot that shows you essentially what you need to do.
OH GOD IT IS WORKING !!!! thank you !
So now, how to be sure I have really 128 gram activated? a terminal command?
 
Back
Top