sleo Posted December 15, 2022 Share Posted December 15, 2022 Hey, I just replaced my Intel wifi card from an E7450 to a DW1830. I have a fresh copy of Monterey 12.5 with OC 0.7.9 files from Jake Lo's tutorial (https://osxlatitude.com/forums/topic/8514-dell-latitude-e7450-uefi-only-clover-and-opencore/). However, the card is not working, please advise. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted December 15, 2022 Moderators Share Posted December 15, 2022 Please post IOReg file using IORegistryExplorer.app v2.1 Link to comment Share on other sites More sharing options...
sleo Posted December 15, 2022 Author Share Posted December 15, 2022 Here you go: Magdalena’s_MacBook_Pro.ioreg Link to comment Share on other sites More sharing options...
Administrators Hervé Posted December 15, 2022 Administrators Share Posted December 15, 2022 Looks like you've retained settings for a DW1560 card in your configuration... You may want to review that. DW1830's PCI is 14e4,43ba remains natively supported by AirportBrcmNIC kext so I was not expecting you to require declaring compatibility with 14e4,43a0. Link to comment Share on other sites More sharing options...
sleo Posted December 16, 2022 Author Share Posted December 16, 2022 Dear Hervé, thank you for answer. I have installed the newest AirportBrcmFixup.kext which include in plugins folder the AirportBrcmNIC_Injector.kext - but as I understand this is not enough? Do I need some other kext (my loaded kexts list below) or I need patch the Info.plist? But in your inventory of supported/unsupported wireless cards #2 there is no information on about the need for patching (btw. this is why I've chosen BCM43602). Please advise. 51 8 0 0x2f000 0x2f000 as.vit9696.Lilu (1.6.1) 5BE860E1-9B41-3013-A0EF-49977EF8E016 <9 7 6 3 2 1> 52 0 0 0x81000 0x81000 as.vit9696.WhateverGreen (1.5.9) 8BD44E1B-66C2-3AF8-8274-184CE24240B2 <51 16 9 7 6 3 2 1> 53 0 0 0x197000 0x197000 as.vit9696.AppleALC (1.7.1) F9D7932E-117A-3C01-8D40-09A07977DC6F <51 16 9 7 6 3 1> 54 0 0 0xe000 0xe000 as.lvs1974.AirportBrcmFixup (2.1.6) D97962CE-310D-3A62-8A5E-AE9F41AC60EA <51 16 9 7 6 3 2 1> 56 0 0 0xa000 0xa000 as.acidanthera.BrightnessKeys (1.0.3) 8D391E3D-6EFA-3895-BAF9-EDA0CAA9EAB4 <55 51 15 9 7 6 3 1> 57 2 0 0x1a000 0x1a000 as.vit9696.VirtualSMC (1.3.0) A742E1F4-BEA8-307F-8B1D-F78C894DA5F8 <51 15 9 7 6 3 1> 59 0 0 0x18000 0x18000 ru.usrsse2.SMCBatteryManager (1.3.0) C765B56F-78C6-3806-A989-05757182C2C3 <58 57 51 15 9 7 6 3 1> 60 0 0 0xa000 0xa000 as.acidanthera.BlueToolFixup (2.6.2) BA861111-6E4D-3653-B9EE-AD7CEC0D3A22 <51 9 7 6 3 2 1> 61 0 0 0x2a4000 0x2a4000 as.acidanthera.BrcmFirmwareStore (2.6.2) 570D21DB-DAB4-3331-B606-55691287CDF9 <7 6 3> 62 0 0 0xf000 0xf000 as.vit9696.SMCProcessor (1.3.0) 03CFAB3E-E424-384A-895B-EFDB9AB6AEA9 <57 51 15 9 7 6 3 2 1> 69 2 0 0x19000 0x19000 as.acidanthera.voodoo.driver.PS2Controller (1.0.6) AC164ECA-3F5C-3209-9FDC-660CD5CCCD91 <15 9 7 6 3 1> 79 0 0 0x2a000 0x2a000 as.acidanthera.mieze.IntelMausi (1.0.8) 4B1485AD-5D5E-3844-B4B3-54DE726E4AA1 <49 16 7 6 3 1> 104 0 0 0xd000 0xd000 as.acidanthera.voodoo.driver.PS2Keyboard (1.0.6) 67E80AA2-1AAD-3468-ADC2-FDC0D5D5BC03 <69 55 9 7 6 3 1> 105 0 0 0x13000 0x13000 com.skyrilhd.PS2Trackpad (1.0.6) D646DE0C-2093-3086-8207-D2CC1E162E68 <69 55 7 6 3> 107 0 0 0x19000 0x19000 me.kishorprins.VoodooInput (1.1.3) 374A88BF-5D62-3ED2-8E75-6A331AF58A2E <55 7 6 3> Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted December 16, 2022 Moderators Share Posted December 16, 2022 If you're using my EFI files, Hervé suggested to remove the compatible string from the config file or delete this whole line under deviceproperties/Add PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0) Link to comment Share on other sites More sharing options...
Administrators Hervé Posted December 16, 2022 Administrators Share Posted December 16, 2022 That card is based on a chipset natively supported by macOS; as such, you should not require any add-on kexts to get it working. Link to comment Share on other sites More sharing options...
sleo Posted December 16, 2022 Author Share Posted December 16, 2022 Thank you for replies. I've deleted the value "pci14e4,43a0" from compatible string under PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0) and AirportBrcmFixup.kext but card still not working. Without the value my System information shows WIFI: Software Versions: CoreWLAN: 16.0 (1657) CoreWLANKit: 16.0 (1657) Menu Extra: 17.0 (1728) System Information: 15.0 (1502) IO80211 Family: 12.0 (1200.12.2b2) Diagnostics: 11.0 (1163) AirPort Utility: 6.3.9 (639.16) With the value: Software Versions: CoreWLAN: 16.0 (1657) CoreWLANKit: 16.0 (1657) Menu Extra: 17.0 (1728) System Information: 15.0 (1502) IO80211 Family: 12.0 (1200.12.2b2) Diagnostics: 11.0 (1163) AirPort Utility: 6.3.9 (639.16) Interfaces: en2: Card Type: Wi-Fi (0x14E4, 0x20) Firmware Version: Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1710.4) MAC Address: 44:1c:a8:e3:4f:83 Locale: FCC Country Code: US Supported PHY Modes: 802.11 a/b/g/n/ac Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 144, 149, 153, 157, 161, 165 AirDrop: Supported AirDrop Channel: 0 Auto Unlock: Supported Status: Off I also try add the value "14e4,43ba" and try install the AirportBrcmFixup.kext without the old value and with "14e4,43ba" but without success. I have dual boot Monterey 12.5 & Windows 11 - but I think this is not a problem... or maybe something in BIOS...? I really don't know. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted December 17, 2022 Moderators Share Posted December 17, 2022 From what I remember, you still need the kext, but leave out the compatibility value. Make sure to update all the kexts to the latest Link to comment Share on other sites More sharing options...
Administrators Hervé Posted December 17, 2022 Administrators Share Posted December 17, 2022 Weird, but the card certainly appears to be properly detected and registered when you inject the compatibility with pci14e4,43a0 statement. It's just that wireless is turned off. No way to turn it back on through the Wireless PrefPane? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now