-
All replies
-
Helpful answers
-
Dec 14, 2014 5:46 PM in response to Drumwizby jndupuis1,Hello Drumwiz. Just simply Command+R at startup, erase the HD and reinstall the OS X that was installed when you purchased. I don't look back on IBM compatible machines running Windows. I run Windows 7 Pro in Boot Camp. Macs are awesome with the OS X that came installed. Boot Camping Windows is a choice. Upgrading to the newest OS X is a choice as well. Note that Recovery will always revert to the OS X that was on your machine at the time of purchase no matter how far long you keep up with Apple OS X upgrades. If it's working, why fix it?
-
Dec 14, 2014 5:57 PM in response to jndupuis1by Drumwiz,I have a Macbook Air and don't have a disc drive so I don't have a copy of the OS to install easily. And to be honest, I'm done doing workarounds for something that shouldn't be happening.
-
Dec 14, 2014 6:51 PM in response to Drumwizby jndupuis1,I have a friend who has a Mac Air. Runs great with Mavericks ( it came with Mavericks ). if your Mac Air has OS X Mountain Lion or higher, you do not need a disc drive to revert back to your original OS X. If you do need a disc drive, the Mac USB SuperDrive is the way to go. It is Windows compatible with the Apple Mac Air SuperDrive driver from Apple. I do not look back to Microsoft. Their, "we own your computer approach" is over the top. Let's not forget the anti virus updates and a gazillion Windows updates just so you can check your email for 5 minutes. Apple provides the honor system using their OS. You can copy it for "your use" as many times as you need and, right now, Yosemite is available for Anyone to try for free on any PC that meets the System Requirements. My friend's Mac Air and my Mini has MS Office for Mac 2011, a USB SuperDrive and we both run Mavericks 10.9.5. We downloaded a free burning App called "Burn". Both are 100% usable and reliable. I'm not trying to sell you. Just don't quite give up yet. We're MS converts. Yosemite, this early in the game is leaving a bitter taste kind of like Windows 8. All my jokes and ribbing aside, Mac is worth its price, performance and support. Again, if you have a newer Mac Air and WIFI. Unplug all non required peripherals, Power up, hold down Command + R until the Apple shows on screen then erase Macintosh HD. Reinstall a new copy of OS X. Follow on screen instructions. Before hand save all your pertinent data. Take care. Their are lots of Apple Support instructions that are "good to know and good stuff". Take care.
-
Dec 15, 2014 3:42 AM in response to tomstephens89by hefest,Here is quick dirty "solution" until they fix the issue.
Currently on my Yosemite Macbook pro everything works fine until it doesn't. Once in 20-30 minutes wifi stops responding and after quick turn off/turn on it quickly goes back to normal. I wrote small script that's pinging gateway (wifi router) every 5 seconds and in case there is no response it resets wifi.
Save this to reset-wifi.sh file:
#!/bin/bash
while true;do
GWIP=$(netstat -nr |grep '^default' |awk '{print $2}')
STATUS=$(ifconfig en0 |grep 'status: active')
if [ "${GWIP}" != "" ] && [ "${STATUS}" != "" ];then
if ping -c 1 -t 1 $GWIP 2>&1 >/dev/null ;then
echo "It's alive"
else
echo "Resetting en0"
ifconfig en0 down
ifconfig en0 up
fi
fi
sleep 5
done
As user type in the following commands in console:
$ chmod 755 reset-wifi.sh
$ sudo ./reset-wifi.sh
The last command should be executed every machine is restarted
-
Dec 15, 2014 12:58 PM in response to tomstephens89by Zacky,I have the same exact issue as all of you +1!!
I have a time capsule which is not working properly anymore and all my airport express are facing problems, it becomes a nightmare to listen to the music
Very disappointed by Apple!
-
Dec 15, 2014 1:39 PM in response to gadgetcomaby gadgetcoma,Apple Support Experience
- Made a third call to Apple and explained what had been tried. (They actually had most of the history and didn't need me to repeat it.)
- The advisor immediately transferred me to a senior advisor who confirmed a few details and then brought a wireless senior engineering associate (or something like that.) Based on her knowledge, I'm guessing she was a senior support person with direct access to wireless engineers/developers.
- She sent me a diagnostic tool to run when the problem occurs so they can get more detail. I captured this information and sent it to Apple along with the two wireless diagnostic reports. That was this morning (12/6), so they won't get to work on this until Monday, most likely. I was told to expect a follow up call later next week.
- I give Apple support credit for not pushing this off as a hardware issue and for accepting my troubleshooting skills. (I've done a lot of system support over the last 22 years.)
Let's hope this gives them more to go on for finding a fix. I'll report more as I hear back.
Time for an update. I received a request from Apple to run wireless diagnostics when the problem occurs and send that to them too. Since then, I realized that I have been hit by both of the problems identified by Mario Ciabarra (https://medium.com/@mariociabarra/wifriedx-in-depth-look-at-yosemite-wifi-and-aw dl-airdrop-41a93eb22e48). The wake from sleep/bonjour proxy issue was what I was able to capture in my first submission to Apple. So, I used Mario's instructions on how to reproduce the performance problem and sure enough, I got slow performance. When I turned off awdl0, performance returned to normal. I captured diagnostics from both scenarios (awdl0 on and off) and captured speed test results for both. (With awdl0 on, speedtest reported 8M download 13M upload, with it off, speed was 57M/60M). I then sent Apple the diagnostic results, speedtest results and, as a way to explain how I reproduced the issue, I included a copy of Mario's article . Let's hope that gets their attention.
-
Dec 16, 2014 6:56 AM in response to tomstephens89by ayrtonf1,Hi to all,
with the 10.10.2 (14C81f) third seed from dec 12, 2014 (pre-release) my iMAC27" mid2011 wifi issues went away.
Hope they bring a 10.10.2 OSX update to the appstore very soon.
-
Dec 16, 2014 8:24 AM in response to ayrtonf1by Florian Innocente,I noticed the same improvements on 2 iMac (exactly the same as yours) but a few days later, the disconnexions came back.
The same thing happened with beta 2 : everything was OK the first days and the problems came back. So I switched back to Ethernet on one of the 2 machines.
-
Dec 16, 2014 8:34 AM in response to ayrtonf1by nhcowboy,I just received an Apple invitation to be part of the wifi beta testing. I thought that was nice, someone was listening and wanted me to participate in helping sort out a fix, not such a voice crying out in the wilderness after all. I'm glad to hear that it's looking good but I'm still debating if I want to do it, only for the fact that my Mini Mac is my only computer and my business computer at that, so if anything went amiss I'd be in a pickle to put it lightly. It's heartening to know that Apple is listening in and asking others to be part of a solution. Problems are frustrating but I always say that it's not the problem that counts but what's done about it that does. On that front I tip my hat to Apple :-)
-
Dec 16, 2014 12:56 PM in response to Zackyby kevinski_uk,I had the same problem Zacky, along with all the other issues and to resolve the time capsule issue i followed this http://www.garth.org/archives/2011,08,27,169,fix-time-machine-sparsebundle-nas-b ased-backup-errors.html
just so you know I've been on this forum sine the begining and have had stable systems since page 55 with everything was working great and only occasional dropouts which were easily resolved by bouncing the network similar to how hefest describes in the post before yours although without a script, but long story short after doing the fsck on my time machine no more dropouts,
So it just goes to show how screwed up this bug is, if fsck'ing TM sparsebundles makes things better elsewhere
-
Dec 16, 2014 1:35 PM in response to tomstephens89by RitchieC,After many attempts to fix my wifi connectivity issue since Yosemite, I tried this
http://fieldguide.gizmodo.com/the-worst-bugs-in-os-x-yosemite-and-how-to-fix-the m-1652690924
and it worked!
Go to "this Reddit thread" link this Reddit thread
I then did only these steps
Kext Utility is available here
- Open Kext Utility.
- Let it repair permissions, it will tell you when it's done
I didn't even reboot and all seems fine! Only confusing bit was the message saying "Drag files onto window to process them" the program will run automatically and tell at the bottom of the window when it's complete
hope this works for others because I was getting sooooooooo frustrated!
RJC
-
Dec 16, 2014 2:37 PM in response to RitchieCby mccosha,That fix was temporary for me. after a day or 2 the problem was back.
The only way I managed to make it permanent - and it has been for some time now - was to assign my machine a fixed IP (.200). As soon as I did that, all **** quieted down. -
Dec 16, 2014 4:23 PM in response to tomstephens89by Blower17,Try this, It worked for me
1: Remove Network Configuration & Preference Files
Manually trashing the network plist files should be your first line of troubleshooting. This is one of those tricks that consistently resolves even the most stubborn wireless problems on Macs of nearly any OS X version. This is particularly effective for Macs who updated to Yosemite that may have a corrupt or dysfunctional preference file mucking things up:
- Turn Off Wi-Fi from the Wireless menu item
- From the OS X Finder, hit Command+Shift+G and enter the following path:
/Library/Preferences/SystemConfiguration/
- Within this folder locate and select the following files:
com.apple.airport.preferences.plist
com.apple.network.identification.plist
com.apple.wifi.message-tracer.plist
NetworkInterfaces.plist
preferences.plist- Move all of these files into a folder on your Desktop called ‘wifi backups’ or something similar – we’re backing these up just in case you break something but if you regularly backup your Mac you can just delete the files instead since you could restore from Time Machine if need be
- Reboot the Mac
- Turn ON WI-Fi from the wireless network menu again
This forces OS X to recreate all network configuration files.
-
Dec 16, 2014 4:51 PM in response to Blower17by Ron R,I used this method about 2 months ago. Fixed the yosemite wifi dropout problem and hasn't returned. working perfectly.
- Within this folder locate and select the following files:
com.apple.airport.preferences.plist
com.apple.network.identification.plist
com.apple.wifi.message-tracer.plist
NetworkInterfaces.plist
preferences.plist- Move all of these files into a folder on your Desktop called ‘wifi backups’ or something similar – we’re backing these up just in case you break something but if you regularly backup your Mac you can just delete the files instead since you could restore from Time Machine if need be
- Reboot the Mac
- Turn ON WI-Fi from the wireless network menu again
This forces OS X to recreate all network configuration files.
-
Dec 16, 2014 5:18 PM in response to tomstephens89by MattyB199,One thing I forgot to mention in my last post. It's not just the fact Wi-Fi just doesn't work, or works at prehistoric speeds. When I have my Mac connected to my network it slows everything else down as well and to the same degree. My wife and I were watching Netflix via Apple TV a few weeks ago and the picture was appalling. Totally pixelated and barely watchable (I should add that this was prior to me becoming aware of the absurd issues with Yosemite). I began searching online for possible issues, but noticed that as soon as I closed my Mac and it entered sleep mode, the picture quality was immediately restored. Same issue with the iPad running on the same network. One can only achieve speeds consistent with 1980's dial-up if the Mac is on and connected at the same time. Shut down the Mac and the problem goes away and normal (fast) service is resumed.
It seems therefore that it's not just an issue with the MacBook dropping out or achieving slow speeds. Rather the MacBook is in fact corrupting and slowing down the entire network itself thus affecting other hardware which also relies on the same connection.
I gather from here that little progress has been made in resolving this issue. Personally I am fast running out of patience, and I pity anyone who relies on their Wi-Fi for work or anything remotely resembling productivity. I outright refuse to try and of the band aid fixes suggested in here (though that is definitely NOT a dig at the good people that have spent their own time and effort trying to fix this issue and make things better for others). It is more a matter of principal. Frankly I dont see why I should have to. I spend $2k plus on a MacBook and I expect it to work and be able to perform the most basic functions like connecting to the Internet. Apple appear to be clueless on this issue and I would have expected a permanent and lasting solution by now.