Search results

Where did you got the info about Intel Wifi 6 in the new iPad Pro? I looked at the kernelcache of iPadOS 13.4 for ipad8,11. There are these kext: com.apple.driver.BCMWLANFirmware4378_Hashstore com.apple.driver.AppleBCMWLANCore com.apple.driver.AppleBCMWLANBusInterfacePCIe I can not find any...

This is a board with six pci root bridges/complexes? It will never boot. IOPCIConfigurator takes the first root bridge and use it to config all PCI devices. Someone else struggled with this board before. My advice to that person was to give up. I have a board with two root bridges. I never...

This one giving up is wise. I have been looking for a way to fix this for several months with two host-bridges. From IOPICFamily source code: // fix - all config cycles use first host bridge if (!fHostBridge) { fHostBridge = hostBridge; space.bits = 0...

External(_SB.PC01, DeviceObj) Scope (\_SB.PC01) {Name (_HID, EisaId ("GNP0A08")) Name (_CID, EisaId ("GNP0A03")) }

Set "Name (_HID, EisaId ("GPNP0A08") Name (_CID, EisaId ("GPNP0A03")" for each of them. ACPIPlatform matches PNP0A08 or PNP0A03 to PCI bridges. There might be an order that could make it work.

You may try keeping one or two of them and see if that changes anything. Comment out " Name (_HID, EisaId ("PNP0A08") /* PCI Express Bus */) // _HID: Hardware ID Name (_CID, EisaId ("PNP0A03") /* PCI Bus */) // _CID: Compatible ID " should do it. If you have the bios, you may try to locate...

The problem is not AppleNVMe Assert rather multiple PCI root complexes. Is there really four of them? Do you have a DSDT from Linux?

The problem is that there seem to be multiple PCI root complexes. I have a board the has two PCI root complexes. One of the has to be enumerated first to boot. Yours seem to treat each bridge as a separate root complex! Try PCIRootUID=1 boot flag and see if it helps.

Something strange happened in PCI device enumeration. The device must be missing from MCFG table.

Xcode adds com.apple.security.get-task-allow entitlement so the other processes(debuggers) can attach. Full listing of flags are in the xnu source http://82.196.10.231/xnu-4903.221.2/html/xnu-4903.221.2/bsd/sys/csr.h.html . Note CSR_ALLOW_EXECUTABLE_POLICY_OVERRIDE is new.

There is neither VRAM,totalMB nor VRAM,totalsize property on the IGPU. Somewhere else there is Dynamic max 1536G, from Apple report. If the hardware monitor reads these properties for total VRAM it must make up a number if none of them exist. If there is only 8G or RAM, allocation of 7G for...

16 is 0x10, 32bit little endian 0x10000000. Base64 encode every 6 bit to 8 bit. The first 6 bit 000100, that is 4 base64 E, the following sextets are all 000000, encoded as A, there are five of them, total 36 bits, the padding bits are represented by ==.

Property injection can be done with DSDT/SSDT, like this https://www.tonymacx86.com/threads/inject-fb-name-for-amd-radeon-rx-vega-64.240252/page-4#post-1698037 . Give it a try.

Made of Gold.

Some of EVGA X299 boards do not lock MSR 0xE2. X299 DARK does lock it. The code segment looks almost the same as ASUS Dominus extreme and easily patched.

Find a way to set XUSB2PR—xHC USB 2.0 Port Routing Register on the EHCI controllers, route all EHCI ports to the XHCI port. Rehabman had some instructions about this. And delete all USB port definitions from ACPI. Let the generic port enumeration kick in.

Do you still have two Radeon VIIs? I put a Radeon VII and Vega FE in the same box, never gotten both of them working in MacOS. An addition of Raid controller caused permanent boot failure. Some IO memory mapping was seriously messed up by boot.efi.

0x4310 is the Sub-vendor id. The driver does not use it. Change it back let lspci show correct vendor name. Subsystem is on the next line: "lspci -nn -vv|less" and type "/ Ether" to search for the card: 09:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Connection X553/X557-AT...

0x260, 0x261 is the PCI vendor id, 0x8086, you don't want to change that. Because you already changed offset 0x240, 0x241 to 0x0a00, it indeed shows 0x0a00. This is correct, Intel data sheet says SubSystem and PCI vendor ids are 0x20 bytes apart. If you really want to be sure, you may read...

You need to change the Sub-System ID not the Sub-Vendor ID. Offsets are next word, 0x242 and 0x243. The order of Sub-System ID and the Sub-Vendor ID are switched for X520 and X550.