You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

BUG: Mountain Lion kills wifi speed when using airplay or time capsule

Hi,

Here is the situation, I have a MBP 3,1 Core 2 Duo 2,4Ghz.

I've upgraded from 10.7 to 10.8, and now, when I'm trying to use time machine on my time capsule (last gen), or airplay on my airport express (802.11n) the transmission speed drops from 160/200 to 6/13. (As you can see on the screenshots below. First image, without any of these two features / Second image, with time machine trying to find the time capsule drive / Third image, with airplay activate)


The time machine don't manage to find the time capsule drive and failed.

Airplay works for 3 seconds and stops. I've tryed airplay with itunes (the old way) and quicktime with the new airplay option, both stops after 3/4 seconds..


User uploaded fileUser uploaded fileUser uploaded file





I made my 30Go time machine backup with an ethernet cable, it worked ok.

I still use my airport express with my iPhone without any problem.

And all other internet usages are working correctly, I can even acces to my data on the time capsule and copy files from with no problem, without this "transmission speed drop" situation.



I have 3 differents wifi signals in my (large) flat:

The time capsule broadcasts 2 different wi-fi n on 2,4ghz and 5ghz

and another Asus router broadcasts wi-fi b/g on 2.4ghz

I've tried the 3 different connections, all have the same "transmission speed drop" issue with airplay and time machine, and these two features don't work anymore.


And of course, I never had this situation with Lion..


Any solution, or is there definitely a bug with mountain lion handling my wi-fi card: AirPort Extreme (0x168C, 0x87)

I already reseted the PRAM and NVRAM; and did an onyx maintenance nothing changed...



Any help appreciate,

Thx

Posted on Jul 29, 2012 11:15 AM

Reply
152 replies

Mar 18, 2013 8:38 AM in response to Gunny Sack

thanks for the info - i think i will update my 2011 iMac (had not done so due to audio bug) since the audio bug is fixed I will see how I like X.8 then maybe update the MBP after I am done with the critical work I have to do for work done on it till i upgrade if i upgrade. I did a clean install of X.7 as i did not own OX.6 when i was given the MBP a year and half ago. I had to put $500 into it to make it work (ie apple replaced the logic board, top cover, backlight and the LCD for $300 and had to buy new battery and powersupply but the computer works like new alothough a little sluggish due to the 4 gig of ram and supper slow 200 gig hard drive. Overall i am happy with it as this replaced my 17" Powerbook - took a little getting used to the smaller screen. Since apple replaced the Logic board the computer has been running at least 8 hours a day 5 days a week for the past year and half with no hardware issues at all. Might wait till X.9 comes out and if there is no support for the 3.1 MBP then i will play around with X.8 - or if my work is done i will play with it soon just do not want to do a clean install atm as have deadlines with work.

Other than streaming to appleTV and the time capsule wireless backup are there any other issues with X.8 and wireless? anyone test with Airparrot, AirFoil or the older airport express?

May 1, 2013 3:35 AM in response to Gunny Sack

I wonder if anyone has any comments on my particular variant of this problem. I originally posted on this thread back on 5th Dec '12. I had recently "upgraded" to ML and had experienced the Time Machine and Apple TV issues associated with that OS version and my MacBook Pro 3.1. After a lot of investigation/research/reading I came across this thread that seemed the closest to my problem so I gave the kext downgrade a try and everything worked perfectly following the downgrade - happy days!


I follow the updates on this thread quite keenly, so I was aware that there appeared to be an issue with the 10.8.3 patch - so I was aware that I shouldn't be ugrading to that ... and so far haven't. Then recently, I noticed that my TM backups were taking an inordinate time to complete. My machine seems to be taking the same amount of time to backup now as it did following my initial upgrade to ML (but prior to the kext downgrade).


So, despite the fact that I've not upgraded to 10.8.3 I seem to be back where I was ... any ideas?


Also, I'm a little unfamiliar with workings of these kernel extensions and how to manipulate them etc. etc. - how do I check I'm still using the correct kext that I reverted to back in Dec '12? Maybe, even though I've not upgraded to 10.8.3 something else that I may have upgrade to has altered the version of that extension under the radar.

May 1, 2013 9:48 AM in response to wattersd

wattersd,


To find the version number of the installed kext (IO80211Family.kext), use the Finder's "Get Info" option on the kext in /System/Library/Extensions or use Kext Wizard (part of the kext package linked to earlier in this thread). With Kext Wizard, you can use the Kext info option to or the Loaded option to find this info.


If the kext version is 5.0 or higher, you have the buggy version from Mountain Lion installed. If it's an earlier version, report back here which version or just reapply the kext downgrade using the version I provided in the download link.


Also, it would be a good idea for you to run Kext Wizard's maintenance routine (repair permissions and rebuild cache) on /System/Library/Extensions.


The OS X 10.8.3 update works great. Might be easiest if you just apply the 10.8.3 combo updater, followed by the kext downgrade. Then check the kext version number after that.

May 2, 2013 5:44 AM in response to Gunny Sack

Hi Gunny,


Thanks for the all the info - much appreciated. Bulding on yours, and others, experience with this issue has saved me (and I'm sure others) lots of time and aggravation.


I used Finder's "Get Info" as you suggested and it tells me it's v3.2 - so I'm not sure what's gone on to kill my Time Machine back ups.


As you've suggested 10.8.3 seems to be working for you (following the kext reversion). I think I'm going to give that a try (after a good disk clone). Then I'll revert the kext to v4.1.2 to see how that goes.


Thanks once again - I'll report back on my results.


David.

May 2, 2013 9:12 AM in response to wattersd

If you're still having Time Machine problems after updating to 10.8.3 and reapplying the kext patch, you might want to see if the problem is with your Time Machine backup. Run Disk Utility on the backup drive and also do a "verify" of the backup. You won't find a better or more complete collection of Time Machine troubleshooting tips here: http://pondini.org/TM/Home.html

May 26, 2013 4:25 PM in response to sirhyll

I can't believe this worked. For months I have struggled with this on my 2007 Macbook Pro. Now everything is backing up smoothly and airplay is seamless. Thanks everyone.


I can't believe it took a clever user to figure out the solution. And, I can't believe so much time has elapsed since the user found and fixed the problem, and Apple STILL has not fixed it in a patch. Pathetic. My next laptop might not be Apple!

Jun 4, 2013 9:22 PM in response to Gunny Sack

10.8.4 breaks the wifi fix thanks to a change with the drivers. However, I have a fix which makes it work again. :-)


You need the /usr/libexec/airportd from 10.8.3 to replace the one in 10.8.4. I'm sure this undoes some bug fixes and stuff done to the wifi support in 10.8.4, but until apple fixes the wifi problems....


Get it here.


1. Turn off wifi.

2. sudo mv /usr/libexec/airportd /usr/libexec/airportd.old

3. sudo cp airportd /usr/libexec/airportd

4. Turn on wifi.

5. Happy!


Brielle

BUG: Mountain Lion kills wifi speed when using airplay or time capsule

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.