Jump to content

Asus W790 Installation.


Balamut
 Share

64 posts in this topic

Recommended Posts

10 hours ago, etorix said:

I'm afraid I already broke in quite some time ago…

😆

 

10 hours ago, etorix said:

OEM-4 is "CPU  CST", in all caps and with two spaces. "CpuCst" has to be something else, and this offending "CPU0" has to come from somewhere. Are you using the "Generate CStates" option, by any chance?

I'll check in a bit, but I doubt it. 

Link to comment
Share on other sites

Sorry for late response Memorial Day weekend here and it was extremely hectic with work.

 

The generate CStates are off on the Clover config and there are only 2 files in the ACPI, the CPU-WRAP and RHUB and only FakeSMC in the kext so this is very wierd.

 

config.plist

  • Like 2
Link to comment
Share on other sites

On 6/2/2023 at 11:18 AM, yapan4 said:

This is because you need clear NVRAM each time after OC before Clover using

Thank you, I've missed that.

 

Here is the log from the log from the Sonoma with OC USB Booting, same issue. I'm more and more convinced of screwed up ACPI tables.

USB Sonoma.txt

 

 

Went a little further and when booting the Recovery I now get the pmtelemetry panic.

Recovery Ventura.txt

 

Exactly the same thing with Catalina.

Catalina.txt

 

 

 

 

 

Edited by Balamut
  • Like 1
Link to comment
Share on other sites

8 hours ago, Balamut said:

@yapan4 what ASMEDIA card did you use when you hit the root device, trying to test something.

C422 motherboards have onboard Asmedia USB 3.1.

Spoiler

image.png.6445ce9e04b0fd9f6aafe07460a4cb28.png


I'm not sure that PCIe cards have the same bootable capabilities that onboard one.

 

You can pay attention on onboard microSD slot. On WS C422 Pro/SE works perfect as virtual bootable USB drive for macOS install.

Edited by yapan4
Link to comment
Share on other sites

18 hours ago, yapan4 said:

You can pay attention on onboard microSD slot. On WS C422 Pro/SE works perfect as virtual bootable USB drive for macOS install.

Interesting idea, might look into it. The problem is the entire ACPI is so screwed up that almost nothing is where it supposed to be for OS(my hypothesis) so I was looking for a way to get at least the USB working ether with SSDT or device properties to test this theory before going gung-ho on the DSDT.

Link to comment
Share on other sites

  • 3 months later...
19 hours ago, xAyiDe said:

Did anyone of you get yours to boot the installer ?

 

I have thinkstation P920 with 2x Xeon gold, it always kernel panic right after the XNU has parsed ACPI. So I can see it the dsdt row by row them BAM kernel panic.

It means your DSDT does not satisfy macOS conditions.

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

I believe this is the same issue I have. The computer boots if VT-D is disabled. If I enable VT-D and drop DMAR it also boots, trying to replace DMAR and it KPs. VT-D enabled and DisableIOmapper = true also boots. This build even got the NVME error, but only if I put in an extra NVME-drive in the PCI-ports with an U.2 SSD.

 

I drop DMAR with OpenCore and patched my DMAR, but when I enable DMAR patch the computer Kernel panics at boot.

 

I remove DMAR with this:

 

            <dict>
                <key>All</key>
                <false/>
                <key>Comment</key>
                <string>Delete standard DMAR table</string>
                <key>Enabled</key>
                <true/>
                <key>OemTableId</key>
                <data>
                </data>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data>
                RE1BUg==
            </data>

I remove below and save it as SSDT-DMAR.aml and add it to SSDT-patches in OpenCore. But it goes KP. Should I remove more or less, anything else in there? I attach the file to this post.

[198h 0408   2]                Subtable Type : 0001 [Reserved Memory Region]
[19Ah 0410   2]                       Length : 0020

[19Ch 0412   2]                     Reserved : 0000
[19Eh 0414   2]           PCI Segment Number : 0000
[1A0h 0416   8]                 Base Address : 000000006B943000
[1A8h 0424   8]          End Address (limit) : 000000006B954FFF

[1B0h 0432   1]            Device Scope Type : 01 [PCI Endpoint Device]
[1B1h 0433   1]                 Entry Length : 08
[1B2h 0434   2]                     Reserved : 0000
[1B4h 0436   1]               Enumeration ID : 00
[1B5h 0437   1]               PCI Bus Number : 00

[1B6h 0438   2]                     PCI Path : 14,00


 

dmar.aml

Edited by xAyiDe
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 months later...
 Share

×
×
  • Create New...