Contribute
Register

pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

pastrychef said:
It's a graphics card problem. Check settings related to graphics or try changing from AMD to Nvidia or vice versa or Intel graphics.
Click to expand...
This is insane, I've replaced the EFI with your stock one and it still doesn't boot...
 
By the way, your first post gives instructions on AML files but doesn't give any instructions on DSL files. Should DSL be used in any way?
 
ChaosMonkey said:
By the way, your first post gives instructions on AML files but doesn't give any instructions on DSL files. Should DSL be used in any way?
Click to expand...

The .dsl file is only there for reference for those who want to look at what was done to create the .aml file. It's not meant to be installed anywhere.
 
pastrychef said:
The .dsl file is only there for reference for those who want to look at what was done to create the .aml file. It's not meant to be installed anywhere.
Click to expand...
For the AML file, should we put its name in the Clover's DSDT name window?
For whatever reason, the machine boots from USB key, but doesn't boot from disk, even after replacing my EFI folder with your 3.2 for Vega. Not sure how to move on in such situation...
 
ChaosMonkey said:
For the AML file, should we put its name in the Clover's DSDT name window?
For whatever reason, the machine boots from USB key, but doesn't boot from disk, even after replacing my EFI folder with your 3.2 for Vega. Not sure how to move on in such situation...
Click to expand...

The SSDT-USB.aml file should go in to /EFI/CLOVER/ACPI/patched/.

That doesn't make sense...
  1. Boot up from your USB flash drive.
  2. Then mount the EFI partitions of the USB flash drive and your main system drive.
  3. Copy and replace the EFI folder from the EFI partition of the USB flash drive to the EFI partition of your main system drive. (Remember to copy your serial, board serial, and UUID prior to replacing the EFI folder on your main system drive.)
 
pastrychef said:
The SSDT-USB.aml file should go in to /EFI/CLOVER/ACPI/patched/.

That doesn't make sense...
  1. Boot up from your USB flash drive.
  2. Then mount the EFI partitions of the USB flash drive and your main system drive.
  3. Copy and replace the EFI folder from the EFI partition of the USB flash drive to the EFI partition of your main system drive. (Remember to copy your serial, board serial, and UUID prior to replacing the EFI folder on your main system drive.)
Click to expand...
That's what I did, and now the system boots, but without Bluetooth and with old kexts set. Once I copy over the kexts from your 3.2 EFI to mine, the system doesn't boot any more.
 
ChaosMonkey said:
That's what I did, and now the system boots, but without Bluetooth and with old kexts set. Once I copy over the kexts from your 3.2 EFI to mine, the system doesn't boot any more.
Click to expand...

Doesn't make sense... If the 3.2 set boots from USB flash drive, it will boot from your main system drive. Have you made any changes to the config.plist? What does verbose say? How did it stop booting in the first place?

I don't know how/why Bluetooth stopped working. There are no kexts, patches, or anything used to enable it. BCM94360CS2 works natively. The only thing that can stop it from working is bad USB implementation.
 
pastrychef said:
Doesn't make sense... If the 3.2 set boots from USB flash drive, it will boot from your main system drive. Have you made any changes to the config.plist? What does verbose say? How did it stop booting in the first place?

I don't know how/why Bluetooth stopped working. There are no kexts, patches, or anything used to enable it. BCM94360CS2 works natively. The only thing that can stop it from working is bad USB implementation.
Click to expand...
I don't have 3.2 version on USB key, it's a version from when I was installing this machine few months ago. When I'm copying the EFI from your 3.2 to mine, I'm completely replacing it and only changes I make are the machine ID.
It stopped working yesterday when I was trying to get rid of the mouse lag with the AGPMEnabler.kext which I have removed once it stopped working, and since then the only way I can boot the machine is from USB key.
 
ChaosMonkey said:
I don't have 3.2 version on USB key, it's a version from when I was installing this machine few months ago. When I'm copying the EFI from your 3.2 to mine, I'm completely replacing it and only changes I make are the machine ID.
It stopped working yesterday when I was trying to get rid of the mouse lag with the AGPMEnabler.kext which I have removed once it stopped working, and since then the only way I can boot the machine is from USB key.
Click to expand...

You probably need the newer USB 15 port limit patch. That explains why Bluetooth stopped working.

I'm not sure what the AGPMEnabler.kext does. Did you make any other changes other than installing that kext? Where did you install the kext? What happens when you boot with the 3.2 package? Where does it stop? What does verbose say?
 
WuTian said:
I experienced similar issue when using an reference Vega 64 card as written in Post #1639 of this thread. the issue seems related to HDCP with specific monitors, because I can see an error message from console every time the stutter happens.


I've not solved this issue, as I returned the card at the end and ordered another MSI AirBoost Vega 56, which is still on the international shipment... After seeing you have the same issue on Vega 56, I have a feeling about I will meet the same issue again with my new card.:(
Click to expand...

How was your monitor connected? HDMI? DisplayPort? Did you have Shiki.kext installed?

Did this happen with your X299 system or Z370 system?

I'm trying to understand why some people have this issue...
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top