Search results

fine :)

Error-free DSDT for Asus Prime A II plus some patches ...

@applemacosxGOD I have the "ASUS Prime X299 Deluxe" and am interested in the new "ASUS Prime X299 Deluxe II". I see you have it. Could you do me a favor? Since the documentation of the manufacturer is a bit sparse, I would like to know the following. Does the "AQC-5G-LAN" work without...

Oh, really. OK, use the "SystemProfilerMemoryFixup.kext". It works. :)

SystemSerialNumber, SystemUUID, MLB, ROM, BoardSerialNumber and ChassisSerialNumber from DataHub, Generic, PlatformNVRAM and SMBIOS are deleted.

The "Titan Ridge" now works here too. I made the mistake of not connecting the Thunderbolt header cable to the motherboard. However, I have my own SSDT, with slightly different data. I've extracted these from a MacBook Pro 2018, this model is known to work with Titan Ridge. I am still...

The Thunderbolt card works. Unfortunately (still) no hot plug.

No, your cooling is too weak.

The program "Parallels" uses "Vt-X". Without it, it would be very slow and unusable.

Only VT-X. VT-D is not supported via macOS.

New project for next week, just arrived from the USA, GC-TITAN RIDGE from Gigabyte. The latest Thunderbolt3 technology, I'm looking forward to it. So far there has been TB3 Falcon Ridge, Titan Ridge should (hopefully) be supported as well. I'm curious … :)

That does not have to have any obvious effects. I just wanted to emphasize that the cited code then has no function. And the developers of the ACPI certainly had a reason for that. ;)

Exactly. Go to the first page of this thread and read again.

In that case I would rather work with the Clover patch, "GBE1 -> ETH0". If you only work with the SSDT, the existing device "GBE1" is hidden and a new device "ETH0" is inserted in the same place. This works great with many other devices. The problem here is that there are other connections to...

@rawx Because … • the processor is more expensive • you have to use another board (C422 Chipset)

@kgp A new device: "Thermal SubSystem" Thanks to "ANONYMOUS WRITER" for the first step, after some trying I could integrate it. Scope (\_SB.PCI0) { Device (THSS) { Name (_ADR, 0x00140002) // _ADR: Address Name (THSS, One) Method...

Give me a hint, and I'll push that ... ;)

@kgp A theoretical possibility: Extract the relevant "blabla.ffs" from the original ROM from the Mac (via UEFITool), convert to "blabla-64.efi" and integrate via Clover. One could talk about it with the "OZMOSIS" people who understand more of the BIOS ...

I had already completely implemented that. Including all missing entries in the DSDT to which many external methods in the SSDT refer. It does not change anything. There is still a lot missing. Such as "IP over Thunderbolt", there are no assigned fixed IP addresses per port, etc. The reduction...

@kgp Thunderbolt SSDT is finished in my opinion. I once integrated the complete iMacPro TB-SSDT with all external methods into the DSDT. It changed nothing. It can not be federated via SSDT as if it were a real Mac. This would require changing the EFI-ROM of the controller with the specific...