Yosemite WiFi bug

How do you disabled AWDL?

I used this command line:

sudo ifconfig awdl0 down

You can validate this with ifconfig. In the ifconfig output, you should see something like this, with status: inactive toward the bottom of the stanza:

awdl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1452

ether 2a:27:89:ab:fa:a2

nd6 options=1<PERFORMNUD>

media: autoselect

status: inactive

Hope that helps!

I was too optimistic... my little bug came back on February 12th. I guess AWDL is off the hook as a direct cause of my issues. I'll keep my script running for a while longer, I guess!

Hey Guys,

Been following this post in the shadows for a while appreciate the work you have been doing Colin.

I have a MBP late 2012 running Yosemite since its release and to have been experiencing exactly the same problems mine are a little worse though its happening daily up to 20 - 30 times (I'm on the PC ALOT due to work) but it happens even more when moving around the house which is odd. I have had the laptop in bits and I am to ruling out hardware (well kind of anyways) also my Bluetooth is constantly "Not Available" with the squiggly line through and refuses to turn on or even be discovered in system report.

But the WIFI is the most annoying the constant disconnects suddenly turning off but showing full signal its all similar to whats been said here.

I'm no pro on Apple hardware but I believe the AirPort card covers both our WIFI and BT? Either way Bootcamp running Windows 8.1 was able to instantly see and use the bluetooth in the machine! SO that made me think cant be hardware + shaking the laptop in all sorts of ways dosent cause a disconnect.

This has to be a firmware issue... I am done troubleshooting I even got so angry I was about to order another macbook tonight and throw this in the bin.

Are you guys still in the same boat?

Hopefully this gets fixed ASAP!

My wifi problem was happening when I was turning off internet sharing where one of the interfaces I was sharing to was wifi.

I ran the script and the airport icon stayed greyed out. But then I re-enabled internet sharing and this worked and then when I stopped it, my ordinary wifi connection to my preferred time capsule access point came back.

Happy to not have to reboot now to recover.

Jim

Same problem happened today and running the script did not help. Reboot was necessary. I run VMware Fusion basically all of the time and I suspect there is a conflict with Fusion's networking stack and Yosemite's networking plumbing. When they get out of sync, chaos ensues that only a reboot will cure.

*sigh*

Sleep - 1 minute wait - wake up by pressing power switch, sorted my problem out.

I have the SOLUTION.

I also had this 'no wifi & no hardware wifi after waking up from sleep" since my upgrade to 10.10 and to 10.10.3.

I've tried ALL the tips & solution, reinstall ... without success. I really tried all and several times after a clean reinstall.

By accident I changed my screen saver (I had a "classic" plus a folder with pictures) to "flotating" and the same folder.

The bug disappeared, vanished and I'm now system stable like before.

So you should check your screen saver ....

HTH.

D.

Thanks for all the help! I'm running the script now 🙂

Before I found this thread I started another: http://apple.stackexchange.com/questions/188058/wifi-problems-after-wake-up-mbp2 011-os-x-10-10-3I'm following this and will post my updates to both threads.

My problem started some days ago and they seem to be the same as yours.

This morning I got the following error in the log once:

22/05/15 07:56:48,707 Wifiscript[1033]: dig attempt via 192.168.0.122

22/05/15 07:56:51,722 Wifiscript[1037]: *** WIFI ERROR #1 DETECTED -- Trying again ***

22/05/15 07:56:51,729 Wifiscript[1039]: dig attempt via 192.168.0.122

Not sure what it means though. I tried to find more info in the wifi.log-file but I couldn't find anything there. Any ideas for where to look for details about the error?

My computer worked fine until today when it crashed with a WiFi problem after wake up.

It wouldnt enable my wifi

I shut wifi down via terminal

I tried to enable it again with:

networksetup -setairportpower en1 on

It crashed and when I looked in the log after the first suspicios thing I noticed is: kernel[0]: en1: Error configuring antenna diversity (index = -1).

Do you have any ideas?

Are your problems solved?

Today my computer crashed again.

I lost Internet connection.I tried:

ifconfig en1 down - all ok.

ifconfig en1 up - and the computer froze.

Have anyone solved this issue?

I think my problems were hardware related. I opened up the cover and saw 2 screws that should hold the antenna that were loose. I screwed both tight, closed the lid and rebooted. Now it works fine.

I've observed the same problem with Wi-Fi card not responding after the laptop goes to sleep.

Sometimes after waking Macbook Pro from sleep, the wireless adapter refuses to turn on. Every time that I click "Turn Wi-Fi On", the /var/log/system.log shows entries like these:

Sep 12 11:59:40 lyra kernel[0]: ARPT: 557330.566010: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff] Sep 12 11:59:40 lyra kernel[0]: ARPT: 557330.566343: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff] Sep 12 11:59:43 lyra kernel[0]: ARPT: 557333.472795: wl0: _wlc_ioctl: dead chip, off[0] bar0[0xffffffff]

I have seen this problem occur once before, and the same behavior was observed. Both times the laptop was just left open overnight while the AC adapter was attached and giving power.

The problem appears similar to this Apple stack exchange question, however unlike the original poster my Macbook was never running any OS X release prior to Yosemite and I have only applied the latest point release updates to Yosemite since it was fresh from the factory. This Macbook Pro is brand new this year, and I highly doubt that it's a hardware issue.

MacBook Pro (Retina, 13-inch, Early 2015)

Processor: 3.1 GHz Intel Core i7

Memory: 16 GB 1867 MHz DDR3

Graphics: Intel Iris Graphics 6100 1536 MB

OS X Yosemite 10.10.5 (14F27)

I have verified that a reboot will fix the issue until the next time that it manifests.

TrinitronX, it could well be a hardware issue. Take your computer in for a diagnosis at your local Apple Store and let them do a hardware test. It doesn't cost anything.