• Become a Premium Member for $25/year with no ads to improve your community experience. Upgrade to Pro Account for faster response and no wait times!

No wifi/bluetooth MSI Z790-p pro wifi DDR4

I know I have intell Wi-Fi and I already tried to use Airportitlwm but it doesn't work the same. that's why I attached my letter. Maybe someone can figure out the problem by looking at my letts and my config.plist

This is my actual EFI. Bluetooth is ok but native wifi doesn't work
Your configuration is a complete mess and is not as per the guide.

Start here:
 
I don't understand why if someone asks for help they are told to learn everything from scratch.....
Meanwhile, my Mac is fine and the only problem I would like to solve is the wifi one. If I go to a forum it's to look for help and not to get a degree in hackintosh. I've already followed a guide, but if I don't like something, I expect someone to tell me how to do it and not to learn everything. But what help is this? It's like if I go to hospital with a broken leg and the doctor tells me: it's a mess, you should graduate from medicine and specialize in orthopaedics.
Anyway, thanks for your help, and I hope that when you need help in life, no one tells you to get a degree.
 
I don't understand why if someone asks for help they are told to learn everything from scratch.....
It's because you're missing the basics. It's like building a home without a design so even after you finish building it and try to fix something, something else will break.

Meanwhile, my Mac is fine and the only problem I would like to solve is the wifi one. If I go to a forum it's to look for help and not to get a degree in hackintosh. I've already followed a guide, but if I don't like something, I expect someone to tell me how to do it and not to learn everything. But what help is this? It's like if I go to hospital with a broken leg and the doctor tells me: it's a mess, you should graduate from medicine and specialize in orthopaedics.
Getting a help from doctor and getting help in terms of IT are simply two different things. As mentioned in the guide, there are people who can invest their time effortlessly in order to fix the junk and keep fixing the broken things instead of starting from scratch.

Forums were always intended for help as long as you follow the instructions and it applies to every forum out there on the Internet. If you don't want to put effort, no one can help you.

If you misunderstood a thing, it's not our problem. Rather than being polite and asking to point out the issues, you began to write garbage. Instead of reading guides carefully, you were not patient and said, it's as per the guide whereas it is not. Anyone can check the EFI you attached and you do not have the required kexts for the Intel WiFi. You didn't even bother to check the forum to check if there's a guide available. It's because you're lazy!

It is your responsibility to put effort if you want a fully working machine. If you're looking for an easy pre-cooked recipe, like a baked cake put on your plate, that's not going to happen either on this forum or some other. Don't blame others when it is your fault.

If you have anger issues, seek medical help instead of writing garbage on forums.

If you really need a reason, READ THE BELOW PARAGRAPH TAKEN FROM THE MAIN GUIDE:

"The purpose of this guide is to show how to create a macOS Bootable USB and create OpenCore EFI which can be used to install macOS on a target Laptop or a Desktop. Where creating EFI is the main essence of the guide as that's what most people are looking for. It is strongly advised to create a configuration (OpenCore EFI) from scratch without the involvement of someone's else configuration and files and this is where this guide comes into place.

Using OpenCore EFI from another system or picking from the Internet (mostly from Github or other forums) is relatively easier than creating on your own, but will not result in many benefits due to the difference in the hardware and the vendor. Although it may be capable of booting macOS on a target system, these pre-made EFIs not only come with a lot of unnecessary and irrelevant SSDTs, Kexts, Quirks, and settings but sometimes also include custom branding and are usually way lot cluttered than the vanilla method and are generally not reliable (missing hardware functionality and/or features or even random freezes, crashes, etc.) which is not the preferred choice. Often, it becomes difficult to inject patches, Device Properties, and Quirks due to being prevented from being injected which is one of the reasons why most of the vanilla guides and/or post-install steps generally don't work with such EFIs. Everything is injected forcibly to ensure the macOS installer boots anyhow on the target system, which still fails in several cases.

Moreover, just because the random EFI you use boots on a target device, it does not necessarily mean every hardware component and the related functions are performing as expected. There could be known performance-related issues i.e. getting less performance than the system is actually capable of or it may not perform well on your system in general (even if it is working for the primary user). In addition, despite having the same hardware configuration, there are chances that your system may require some additional configuration than the EFI you're using to boot. Most of the users just want to boot the macOS installer on their systems, without getting to know the basics involved which is the key and this is why it makes it more difficult to troubleshoot if such configuration fails to boot the macOS installer on the target system and such users don't have clue where the problem is coming from.

Just to avoid reading and investing time into building a proper EFI, several users use the EFI of someone else. This is a very common practice often followed by new users building their OpenCore EFI and this is why such users run into different issues and invest their time effortlessly to fix the junk. Rather than investing time in troubleshooting the installation and fixing someone's else EFI configuration, which is not even intended for your particular system, it would make more sense to create your own OpenCore EFI and move in the right direction in the first place. Using someone's EFI not only makes it difficult to boot the macOS installer, but it invites way more issues than it could have originally. A lot of problems can be eliminated just by following the guide precisely.

Due to all these reasons, using OpenCore EFI from some other computer or user is never advised and such practice is highly discouraged, especially on this forum. If you don't follow the guide carefully, after a point of time, you will end up frustrated if you lack time and patience. Of course, it's your computer and you have the right to decide whether to install macOS for your use case or not".


One of the former user on this forum was arrogant, but when he really decided to follow what is being said, he was able to fix the things in no time.

Reference:

It's like visiting a doctor and then asking the doctor to perform surgery or put a bandage in your way. Let the doctor do the job, if for nothing else, then just for the sake of experience!

Anyway, thanks for your help, and I hope that when you need help in life, no one tells you to get a degree.
Don't worry. That's never gonna happen!

The world doesn't follow your principles. It's you who is arrogant, rude, and fails to follow the guides precisely, and keeps copying EFI from random places without knowing what you have to use actually and still expects things to work!

As this is the first inappropriate behavior, we're not taking any community action. Ensure it does NOT happen again or appropriate community actions will be taken accordingly. We do NOT tolerate hate speech, arrogance or rude behavior here.
 
It's because you're missing the basics. It's like building a home without a design so even after you finish building it and try to fix something, something other will break.


Getting a help from doctor and getting help in terms of IT are simply two different things. As mentioned in the guide, there are people who can invest their time effortlessly in order to fix the junk and keep fixing the broken things instead of starting from scratch.

Forums were always intended for help as long as you follow the instructions and it applies to every forum out there on the Internet. If you don't want to put effort, no one can help you.

If you misunderstood a thing, it's not our problem. Rather than being polite and asking to point out the issues, you began to write garbage. Instead of reading guides carefully, you were not patient and said, it's as per the guide whereas it is not. Anyone can check the EFI you attached and you do not have the required kexts for the Intel WiFi. You didn't even bother to check the forum to check if there's a guide available. It's because you're lazy!

It is your responsibility to put effort if you want a fully working machine. If you're looking for an easy pre-cooked recipe, like a baked cake put on your plate, that's not going to happen either on this forum or some other. Don't blame others when it is your fault.

If you have anger issues, seek medical help instead of writing garbage on forums.

If you really need a reason, READ THE BELOW PARAGRAPH TAKEN FROM THE MAIN GUIDE:

"The purpose of this guide is to show how to create a macOS Bootable USB and create OpenCore EFI which can be used to install macOS on a target Laptop or a Desktop. Where creating EFI is the main essence of the guide as that's what most people are looking for. It is strongly advised to create a configuration (OpenCore EFI) from scratch without the involvement of someone's else configuration and files and this is where this guide comes into place.

Using OpenCore EFI from another system or picking from the Internet (mostly from Github or other forums) is relatively easier than creating on your own, but will not result in many benefits due to the difference in the hardware and the vendor. Although it may be capable of booting macOS on a target system, these pre-made EFIs not only come with a lot of unnecessary and irrelevant SSDTs, Kexts, Quirks, and settings but sometimes also include custom branding and are usually way lot cluttered than the vanilla method and are generally not reliable (missing hardware functionality and/or features or even random freezes, crashes, etc.) which is not the preferred choice. Often, it becomes difficult to inject patches, Device Properties, and Quirks due to being prevented from being injected which is one of the reasons why most of the vanilla guides and/or post-install steps generally don't work with such EFIs. Everything is injected forcibly to ensure the macOS installer boots anyhow on the target system, which still fails in several cases.

Moreover, just because the random EFI you use boots on a target device, it does not necessarily mean every hardware component and the related functions are performing as expected. There could be known performance-related issues i.e. getting less performance than the system is actually capable of or it may not perform well on your system in general (even if it is working for the primary user). In addition, despite having the same hardware configuration, there are chances that your system may require some additional configuration than the EFI you're using to boot. Most of the users just want to boot the macOS installer on their systems, without getting to know the basics involved which is the key and this is why it makes it more difficult to troubleshoot if such configuration fails to boot the macOS installer on the target system and such users don't have clue where the problem is coming from.

Just to avoid reading and investing time into building a proper EFI, several users use the EFI of someone else. This is a very common practice often followed by new users building their OpenCore EFI and this is why such users run into different issues and invest their time effortlessly to fix the junk. Rather than investing time in troubleshooting the installation and fixing someone's else EFI configuration, which is not even intended for your particular system, it would make more sense to create your own OpenCore EFI and move in the right direction in the first place. Using someone's EFI not only makes it difficult to boot the macOS installer, but it invites way more issues than it could have originally. A lot of problems can be eliminated just by following the guide precisely.

Due to all these reasons, using OpenCore EFI from some other computer or user is never advised and such practice is highly discouraged, especially on this forum. If you don't follow the guide carefully, after a point of time, you will end up frustrated if you lack time and patience. Of course, it's your computer and you have the right to decide whether to install macOS for your use case or not".


One of the former user on this forum was arrogant, but when he really decided to follow what is being said, he was able to fix the things in no time.

Reference:

It's like visiting a doctor and then asking the doctor to perform surgery or put a bandage in your way. Let the doctor do the job, if for nothing else, then just for the sake of experience!


Don't worry. That's never gonna happen!

The world doesn't follow your principles. It's you who is arrogant, rude, and fails to follow the guides precisely, and keeps copying EFI from random places without knowing what you have to use actually and still expects things to work!

As this is the first inappropriate behavior, we're not taking any community action. Ensure it does NOT happen again or appropriate community actions will be taken accordingly. We do NOT tolerate hate speech, arrogance or rude behavior here.
Don't worry. That's never gonna happen!


you wrote this and I would be arrogant???
listen: I'm not arrogant or lazy. I'm simply 49 years old and have a family and a job to support it and I don't have time to study to become an expert in building a hackintosh. I simply followed the guide to create an installable USB and installed. That's all. I also lost about 10 hours changing the various kexts and those for my intel from what I read around in my EFI folder which I attached, are there and how. Then if they aren't there and you know which ones are needed, you would have done better to tell me instead of writing a book. Couldn't you have spent the time you wasted writing that book fixing my config.plist? Absurd how much time wasted for nothing. You wrote all the things that don't make sense to me. I repeat: I need to make a hackintosh to use it without too many worries. I don't think it's mandatory to have to become a programmer to do this. Or am I wrong? to me you are a nerd and I don't say this to offend you. You, on the other hand, offended by saying that I wrote rubbish and calling me arrogant without even knowing me. My doubt is that you need to relax and take a walk. Hello and thanks MATE

ps: I forgot that I got my efi from a user on another forum who had shared it and had the same motherboard, processor and video card as me. So since everything was fine with him I tried but nothing.
 
Last edited:
you wrote this and I would be arrogant???
Well, that's what your previous reply indicates!

listen: I'm not arrogant or lazy. I'm simply 49 years old and have a family and a job to support it and I don't have time to study to become an expert in building a hackintosh. I simply followed the guide to create an installable USB and installed. That's all. I also lost about 10 hours changing the various kexts and those for my intel from what I read around in my EFI folder which I attached, are there and how. Then if they aren't there and you know which ones are needed, you would have done better to tell me instead of writing a book.
That's understood. But seems like you missed reading the post #8.

Couldn't you have spent the time you wasted writing that book fixing my config.plist? Absurd how much time wasted for nothing.
It is your responsibility to make the mentioned changes, not us. We never work on someone's else EFI, fix things in it or build it from scratch and then post it. If we do that, the purpose of the guide fails. Yeah, see how much time you wasted by not following the guide where it takes like 30mins or so roughly. But you want the easy route. You're 49yrs old and you should be knowing this by this age.

You wrote all the things that don't make sense to me.
Neither your does!

I repeat: I need to make a hackintosh to use it without too many worries. I don't think it's mandatory to have to become a programmer to do this. Or am I wrong? to me you are a nerd and I don't say this to offend you.
Of course not. But you're missing things here. Simply take out 30mins time, follow this video guide if you're having issue while following the written guide on the forum. 30mins later, you can compare why the previous one you had from some other place was a mess and you'll definitely feel sorry for what you did a while ago. If not, then you'll feel you should have actually followed it in the first place. You'll see how fast the system performs. Of course, let's accept that you invested a lot of time and you're tired. No need to rush, try tomorrow or day after tomorrow. BUT, START WITH SCRATCH. It's because it will ELIMINATE most of the problems you either have with your build or about to encounter it in any given point of time.


You, on the other hand, offended by saying that I wrote rubbish and calling me arrogant without even knowing me. My doubt is that you need to relax and take a walk. Hello and thanks MATE
That response was expected as things went beyond. No offence intended. You should be good to go when you follow the guide. C'mon, you can do it!
 
  • Like
Reactions: Alegundam
ok I'm reading the guide but I think it will take more than 30 minutes :cautious:
 
ok I'm reading the guide but I think it will take more than 30 minutes :cautious:
Oops. No Italian. English only!

All you need is the video guide which is linked above!

Follow it carefully. As you have Raptor Lake, make the changes what's specific to Raptor Lake. That's it.
 
Oops. No Italian. English only!

All you need is the video guide which is linked above!

Follow it carefully. As you have Raptor Lake, make the changes what's specific to Raptor Lake. That's it.
ok, I followed the guide in the video and I cleaned everything by putting the variables only for my raptor lake but it doesn't start. I drove myself crazy doing various tests but nothing. Maybe I have to reinstall everything from scratch?
 
ok, I followed the guide in the video and I cleaned everything by putting the variables only for my raptor lake but it doesn't start. I drove myself crazy doing various tests but nothing.
Can you please be clear and precise? What does not work? The WiFi/BT or the system fails to boot to macOS? Please be patient!

Maybe I have to reinstall everything from scratch?
Not required unless the system is borked
 
Can you please be clear and precise? What does not work? The WiFi/BT or the system fails to boot to macOS? Please be patient!


Not required unless the system is borked
So: I'm starting again in small steps from my efi that was going. Now I clean up one step at a time and restart and see when it doesn't restart again. Surely if you set the booter quirks for Raptor Lake as per the guide in the video, the PC won't start. That's for sure. Now I'm seeing more and then I'll update you
 

Latest posts

Forum statistics

Threads
1,933
Messages
18,021
Members
27,774
Latest member
kovacs1122