WiFi: No Hardware Installed after Mojave upgrade

Here is the solution, I had the same problem and fixed it yesterday. Look below.

—————————————————-

Fixed it! It is amazing to me that one tiny config file can bring down the whole system! I followed the instructions of someone else in the replies below (forgot the name) and Mohave installed without a hitch. Here are the instructions:

If you're also seeing symptoms like networking failing, bluetooth devices not connecting, etc, and you have been using the mac for a while (or restored it from another machine using migration or time machine), then it's due to an old, out of date system configuration file that is contains settings that are too low for modern macs: '/etc/sysctl.conf

'
This file doesn't even exists on new macs, so if you have it, it will cause problems

A. If you can log in (even if slow), or you're still on High Sierra, and have not yet upgraded, follow these instructions:

1. Start the terminal

app from Applications/Utilities

2. Check if the file exists, by typing

ls -l /etc/sysctl.conf

If this returns a result like the following, then the file exists. If it does not, then your issues are caused by something else

-rw-r--r-- 1 root wheel 136 24 Nov 2013 /etc/sysctl.conf

3. Remove the file: (actually this command will simply rename it, so you can restore it if you really want to mess up your computer again.)

You'll be prompted for your password.

sudo mv /etc/sysctl.conf /etc/sysctl.conf.bak

4. Restart your computer, and you should be all set, or if you've rolled back to High Sierra, you should be good to attempt the upgrade again.

AFG

can you be a little more specific as to the steps taken to rename the sysctl.conf file? I am not so computer literate, but have found the sysctl.conf file. I just don’t know how to rename, using what application, and rename to what? An outline of your procedure would be greatly appreciated by the Mac community

Thanks

No WiFi in Mojave Yet

Thanks

FYI when I tried the Terminal commands they didn’t work, saying something about not being authorized etc. Not sure if I missed some spaces or use l instead of 1 etc.

Anyway what worked for me was to find the file directly and rename it. I went to the Go menu, then chose “Go to Folder” then typed “Volumes/Specific Name/private/etc/“ where “Specific Name” is the name I gave the hard drive volume.

Once the folder was accessed I found the file “sysctl.conf” (mine was from 2009) and renamed it manually. I got a alert box and had to enter my password to rename it.

After restarting everything seems to be working normally (trackpad, WiFi etc.) and it’s not sluggish anymore. Glad I found this.

Worked like a charm for me. Under "Go" in the finder menu, go to folder /etc/. I renamed it aysctl.conf and rebooted. It is now a functional computer. I have a lot of legacy junk so a clean reinstall might be a better solution in the long run, but this works for now.

Had tried to find the offending file several times to no avail. Read a post that highlighted the spaces needed in the search (ls -l etc/). When I figured this out, the whole operation finally worked. Hope the Apple geniuses get the message, so that customers don't have to spend hours on the phone. Many thanks to the OP of this solution.

Access to that link is “Unauthorized.” Piques my curiosity, as attempting to install Mojave on my iMac/3TB fusion drive fouled up the drive big time. Had to take it to MacMedics for repair and revert to High Sierra.

I too had all of the wifi and bluetooth issues after my first attempt to upgrade to Mojave 10.14. I then downgraded back to High Sierra after much cursing. I never had to use Safe Boot and do an Internet Recovery before.

I just ran terminal and found that sysctl.conf file. Mine was dated 2006. I will try the upgrade to 10.14.1 tonight and report back.

Thanks

I have a 5K as well, tried reinstalling update - didn't help. Recommendation must be to reload from time machine. I had hoped that waiting to install would protect me a bit. One should not have to do a clean install - thats for windows users.

If you look back at a few post, in this thread, you may see the solution. It appears that the file sysctl.conf is the culprit. For me, renaming that file solved the problem. I don’t know how to copy and paste a link to a post, at least on my phone.

Regards,

Roy

Could you please break down the process step by step for me. I’m new to the apple world so please break it down Barney style...

I previously had Mavericks and installed Mojave and my machine is running sluggish and has no Wi-Fi hardware detected. I’m also not able to do a time machine back up (I get red i’s next to the last backups and it won’t let me backup)

Apple has me running in circles, thanks and advance.

Great job! This worked for me. I had done a Time Machine restore when I replaced my 2007 iMac with my new one in December 2013. Simple fix for a major problem and Apple Support says they can’t use your fix!

Make sure you search for the file correctly. There are spaces in the suggested search string (as well as the suggested renaming string). The easiest way to be sure you get it right is to copy from the OP instructions, and paste into the terminal screen.

My hardware shows on the system information and appears to be working as

when I click on it the drop box says that wifi is on but there's no connection... but as I have wifi on my macbook working I know its not the router. Recently the exclamation mark has appeared in the wifi icon on the top bar. It says wifi on but no connection.

Heres the interesting thing, the wifi option no longer appears in the left hand box network connections either

iMac (Retina 5K, 27-inch, Late 2015) Mojave 10.14.1 (18B75)

Anyone else had this issue?

Cheers

🙏 THANK YOU 🙏 THANK YOU! 🙏

SHEESH! That was a horrible waste of most of an entire day until I found this thread. Usually, being a long-time Mac user is a good thing – but this works against you.

APPLE: this seems like a known-enough issue. How about removing this file in the install script?!? 👌

Thanks, JoeMan71!

"It just works."

You are a life saver! This is the 3rd time I tried to update to Majove and had these same issues. I was hoping that 10.14.2 would have fixed the problem but it did not. Renaming that config file did the trick.

thank you!