Airport WiFi on Sequoia for Laptop Dell Latitude E5550

[nabilh2020]

- What WiFi Card are you using?
Intel WiFi Hackintool says Wireless 7265
- What macOS version are you using?
MacOS Sequoi 15.7.4
- When following the WiFi guide, what errors are you getting?
No errors while modifying the config.plist
When rebooting I get a kernel panic that says: Refusing new kext, a prelinked copy with a different UUID is already present.

As I said the EFI is too big to attach but I linked up to it from my dropbox, I will repost the link below:

Dropbox

www.dropbox.com

 

[EliteMacx86]

- What WiFi Card are you using?
Intel WiFi Hackintool says Wireless 7265
- What macOS version are you using?
MacOS Sequoi 15.7.4
- When following the WiFi guide, what errors are you getting?
No errors while modifying the config.plist
When rebooting I get a kernel panic that says: Refusing new kext, a prelinked copy with a different UUID is already present.

As I said the EFI is too big to attach but I linked up to it from my dropbox, I will repost the link below:

Dropbox

www.dropbox.com

Your EFI is not as per the guide. Why are you injecting so many irrelevant parameters in PciRoot(0x0)/Pci(0x1C,0x3)/Pci(0x0,0x0)?

You just need to spoof and run OCLP. Once volume is patched, remove the spoof.

As expected, you have a typo. You have com.apple.iokit.IOSkyWalkFamily instead of com.apple.iokit.IOSkywalkFamily in the block section. Thus, the panic.

Also, you should try to implement Apple VT-d.

Your profile indicates you have a Dell Laptop and you should enable CustomSMBIOSGuid and set UpdateSMBIOSMode to Custom.

Why are you forcing IONetworkingFamily.kext?

Also, you should not inject AMFIPass.kext and also amfi=0x80 together

 

[nabilh2020]

Your EFI is not as per the guide. Why are you injecting so many irrelevant parameters in PciRoot(0x0)/Pci(0x1C,0x3)/Pci(0x0,0x0)?

You just need to spoof and run OCLP. Once volume is patched, remove the spoof.

As expected, you have a typo. You have com.apple.iokit.IOSkyWalkFamily instead of com.apple.iokit.IOSkywalkFamily in the block section. Thus, the panic.

Also, you should try to implement Apple VT-d.

Your profile indicates you have a Dell Laptop and you should enable CustomSMBIOSGuid and set UpdateSMBIOSMode to Custom.

Why are you forcing IONetworkingFamily.kext?

Also, you should not inject AMFIPass.kext and also amfi=0x80 together

I got the EFI from this link & it worked for Ventura 100%:

Dell Latitude E5550 · SkyrilHD Dell-Exx50-Hackintosh · Discussion #96

Just announcing that your Opencore EFI worked like a charm for my Dell Latitude E5550 laptop, the only thing missing which I hope to fix is WiFi. This was on Ventura, will try later on Sequoia. I g...

github.com

Interesting just walk instead of Walk in com.apple.iokit.IOSkyWalkFamily

I will make the changes & come back, I need to redo everything like spoofing, etc...

 

[nabilh2020]

Yes changing Walk to walk in the Kernel block tab allowed me to get Airport, thanks, I was banging my head from a typo, which I copied & pasted from a post somewhere.

Anyway now getting Bluetooth to work is easy.

What's the use of Apple VT-d? & if important how to implement it?

Also is it essential to enable CustomSMBIOSGuid and set UpdateSMBIOSMode to Custom?

It's working fine without any of the above.

Only BT which I know how to get working.

 

[nabilh2020]

For reference along with the EFI partition content in the above here is the updated config.plist that is corrected as advised correcting the typo & with the mod to allow for Bluetooth.

Now Airport & BT all work, I do not know about the suggested mods, but if you can correct this config.plist to incorporate them that will be nice...

Apple VT-d? implementation?
My Dell Latitude E5550 had already VT-d enabled, & the config.plist and all the advice referred here already checked as advised, so nothing to do. The laptop does not have a thunderbolt port anyway.

Enabling CustomSMBIOSGuid and set UpdateSMBIOSMode to Custom?

UpdateSMBIOSMode is set as Create with no problem... but I set it to Custom as you advised.

CustomSMBIOSGuid located & enabled.

EFI I used is from SkyRilHD & worked for Ventura OOB.

 

[nabilh2020]

Just including here the hopefully last fully optimised opencore config.plist including most advice upstream, so for all intents & purposes the Sequoia problem for Dell Latitude E5550 is solved.

I am not removing the com.apple.iokit.IONetworkingFamily Kernel -> Force entry as it was in original SkyRilHD config.plist for Ventura, he must have had a reason to do so & it is not harming anything.

Most probably this solves also for Sonoma, but I don't feel the need or urge to test this even though I have an SSD with Sonoma available which works on MacBook Pro 2016.

 

[EliteMacx86]

I got the EFI from this link & it worked for Ventura 100%:

Dell Latitude E5550 · SkyrilHD Dell-Exx50-Hackintosh · Discussion #96

Just announcing that your Opencore EFI worked like a charm for my Dell Latitude E5550 laptop, the only thing missing which I hope to fix is WiFi. This was on Ventura, will try later on Sequoia. I g...

github.com

Interesting just walk instead of Walk in com.apple.iokit.IOSkyWalkFamily

I will make the changes & come back, I need to redo everything like spoofing, etc...

As suggested in the EFI guide, you MUST create the EFI for your hardware on your own.

Yeah, a note was added that letters casing are important.

 

[EliteMacx86]

Yes changing Walk to walk in the Kernel block tab allowed me to get Airport, thanks, I was banging my head from a typo, which I copied & pasted from a post somewhere.

Reason why you should follow the guide strictly.

Hopefully, you're still not mad about having a support being a premium member here. xD. As mentioned before in the main thread, You'll have to follow the instructions to get things working. You can see several cases on this forum and users got it working by sticking to the instructions.

Now Airport & BT all work, I do not know about the suggested mods, but if you can correct this config.plist to incorporate them that will be nice...

Great that it all works now. For sure!

Apple VT-d? implementation?
My Dell Latitude E5550 had already VT-d enabled, & the config.plist and all the advice referred here already checked as advised, so nothing to do. The laptop does not have a thunderbolt port anyway.

Provide a copy of IOReg+MaciASL export to confirm.

Enabling CustomSMBIOSGuid and set UpdateSMBIOSMode to Custom?

Yes, required for Dell truncating SMBIOS. If you have switched between SMBIOS models, then you'll have to delete the existing preferences as well.

UpdateSMBIOSMode is set as Create with no problem... but I set it to Custom as you advised.

CustomSMBIOSGuid located & enabled.

Great!

Checked the EFI and few adjustments still needs to be made:

Remove ResetLogoStatus
Remove the spoof so that the WiFi chip can have the native IDs.
VT-d is still not implemented.
CustomSMBIOSGuid is still not enabled.
Why are you still forcing IONetworkingFamily.kext? Makes no sense. You should remove it from Kernel>Force section.
Why are you still using AMFIPass.kext and amfi=0x80 together? Use either one of them, never both.
UpdateSMBIOSMode is still set to Create.

 

[EliteMacx86]

I am not removing the com.apple.iokit.IONetworkingFamily Kernel -> Force entry as it was in original SkyRilHD config.plist for Ventura, he must have had a reason to do so & it is not harming anything.

Of course, it does not harm. But still unnecessary. If the IONetworkingFamily isn't loading, then only force option should be used. Many people just don't have the real reason and simply copy/paste or following blindly doesn't make sense.

The EFI still needs a few optimizations:
Remove ResetLogoStatus
Remove the spoof so that the WiFi chip can have the native IDs.
VT-d is still not implemented.
You should remove the OCLP-Settings entry from the NVRAM.
Why are you still using AMFIPass.kext and amfi=0x80 together? Use either one of them, never both.
You should disable the dGPU by patching the DSDT and SSDT. The -wegnoegpu flag simply hides it from the OS but still draws power.