Jief Posted March 14, 2018 Share Posted March 14, 2018 Hi, I'm trying to change the pci id of my wifi card (AW-NB290) with DSDT patch. I have this Device (EXP2) { Name (_ADR, 0x001C0001) // _ADR: Address Name (RID, 0x00) OperationRegion (PECS, PCI_Config, 0x00, 0x0100) Field (PECS, DWordAcc, NoLock, Preserve) { Offset (0x62), PS, 1, PP, 1, Offset (0xDB), , 7, PMCE, 1, Offset (0xDF), , 7, PMCS, 1 } Name (LPRT, Package (0x04) { Package (0x04) { 0xFFFF, 0x00, \_SB.LNKB, 0x00 }, Package (0x04) { 0xFFFF, 0x01, \_SB.LNKC, 0x00 }, Package (0x04) { 0xFFFF, 0x02, \_SB.LNKD, 0x00 }, Package (0x04) { 0xFFFF, 0x03, \_SB.LNKA, 0x00 } }) Name (APRT, Package (0x04) { Package (0x04) { 0xFFFF, 0x00, 0x00, 0x11 }, Package (0x04) { 0xFFFF, 0x01, 0x00, 0x12 }, Package (0x04) { 0xFFFF, 0x02, 0x00, 0x13 }, Package (0x04) { 0xFFFF, 0x03, 0x00, 0x10 } }) Method (_PRT, 0, NotSerialized) // _PRT: PCI Routing Table { If (\GPIC) { Return (APRT) } Else { Return (LPRT) } } } I don't understand : "Name (APRT, Package (0x04)". Where should I insert the Device(ARPT), like you show at the beginning of the wireless card inventory thread ? Thanks. Jief Quote Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted March 14, 2018 Moderators Share Posted March 14, 2018 @jief, You can easily do this in Clover Config file. Add it to Devices, Fake ID /WFI If you want it on the the DSDT, then you need to determine where to patch it by looking at IOReg. Attach it here if you need assistance. Quote Link to comment Share on other sites More sharing options...
Administrators Hervé Posted March 14, 2018 Administrators Share Posted March 14, 2018 It seems you possibly made erroneous shortcuts and confused ACPI device ARPT with a function called APRT under a device EXP2 found at address 1C,1 (i.e. 0x001C0001). The syntax difference is very subtle and may have eluded you... As suggested by Jake, identify your wireless device in IOReg (with tools/apps such as IORegistryExplorer) before you consider any patches in your DSDT. I remind you that this is clearly stated in the thread you've mentioned. Did you miss that too? [...] In the same respect, in the case of the Broadcom BCM4322x cards (e.g.: chip BCM43225 14e4,4357), adding compatibility with a chip known to be supported OOB such as BCM94360 14e4,43ba or 14e4,43a0 (as found in the vanilla AirPortBrcm4360 kext) in a _DSM method for the identified DSDT device does the trick once and for all since it'll make the OS load the associated kext: Device () // Identified wireless device through IORegistryExplorer (usually: ARPT) {[...] You may find out that the device EXP2@1C,1 has nothing to do with your wireless card. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.