-
All replies
-
Helpful answers
-
Jan 9, 2014 12:10 AM in response to Topfjoerby Topfjoer,Well... I now also tested my MBP on the University Network running on 11n, and here's everything OK using the older MBA drivers. No latency issues with ping and snappy Safari (can't check Airplay here). I haven't tested the original MBP driver as I'm sticking to the MBA driver for now as it's definitely faster on 11g my home network as doesn't have any negative effects on the other networks for me either.
Still strange that on my home network, issues seem to be limited to Apple apps. Anyway, I my case the issue seems to be driver/software related - not hardware.
-
Jan 9, 2014 2:24 AM in response to Topfjoerby vZwo,How did you install the MBA driver?
Is your MBP network card a Broadcom BCM43xx?
-
Jan 9, 2014 5:32 AM in response to vZwoby Topfjoer,I followed the last part (A how to) of headcase's description here: https://discussions.apple.com/thread/5100655?start=1470&tstart=0.
But before copying that .kext file into your system library, make sure you save the original one somewhere else before overwriting it. That way you can always roll back - which is the same procedure...
After installing the MBA driver this is what the description under Network/Wi-Fi in the system report says:
Card Type: AirPort Extreme (0x14E4, 0x112)
Firmware Version: Broadcom BCM43xx 1.0 (6.30.223.74.22)
-
Jan 9, 2014 6:12 AM in response to Topfjoerby beley,I got my new replacement MacBook Pro last night and got everything moved over. So far, no issues with pings or with dropped internet (but it's early). I'll keep an eye on it and report back this afternoon after a full day of use.
-
Jan 9, 2014 6:18 AM in response to beleyby Topfjoer,Great! So your pings are fast and stable now? What kind of network are you on? 11n or 11g?
-
Jan 9, 2014 6:21 AM in response to Topfjoerby beley,Using an Airport Extreme, how do I check which type of 802.11 I'm using?
-
Jan 9, 2014 6:29 AM in response to beleyby Topfjoer,For an Airport Extreme I don't know, but in general you can log in to the router using your browser (http://ip-address) and check your settings. If your Airport is (quite) new, you're probably on 11ac or 11n - not on 11g.
-
Jan 9, 2014 6:44 AM in response to beleyby nirmalts,You could also ALT+Click the Wifi icon on top right to get these details
-
Jan 9, 2014 9:15 AM in response to nirmaltsby nirmalts,I can confirm that this problem is present not only on MacbookPro/Air but also on iMac. I retuned my MacbookPro and got an iMac (due to reasons other than the above mentioned problem) and face the problem on iMac too. After the iMac sleeps it does not connect back to Wifi
I feel this is not an hardware defekt but a driver issue to do with Mavericks, the new 2013 Mac series (Macbooks, IMac etc.) and specific routers with N support in combination
-
Jan 9, 2014 9:54 AM in response to nirmaltsby beley,At my office (where I had experienced the problem before) I am currenlty on 802.11n
Here is the info from my Wifi
I'll continue to montior throughout the day but so far no issues connecting after sleep, or after being out of the office and having connected to another network. So far so good!
FYI I just noticed I'm on 10.9 - not 10.9.1. I'll update later today and hopefully that won't have any effect.
-
Jan 9, 2014 1:05 PM in response to nirmaltsby Tobintax,"I feel this is not an hardware defekt but a driver issue to do with Mavericks, the new 2013 Mac series (Macbooks, IMac etc.) and specific routers with N support in combination"
Absouktely not. The Problem exists on older OS and Windows (please read the whole thread). This is no mavericks specific issue.
-
Jan 9, 2014 1:18 PM in response to Tobintaxby beley,UPDATE
The issue is NOT fixed with a brand-new MacBook Pro replacement.
I just experienced the exact same issue. First, internet slowed to a crawl. A video I was playing stopped, then access slowed until I got errors even loading Google.com.
I finally turned off wifi and back on trying to see if that would work, but could never get reconnected.
Exact same problem I had before. Definitely a hardware issue and must be VERY widespread. Likely a combination of protocol (g, n, whatever) and networking hardware that is causing the issue - not a software issue as others have reproduced it in windows.
At any rate, I don't have any more time for this... I've spent HOURS on the phone with Apple troubleshooting, only to send it back for a replacement that's just as defective. I'm calling right now to get a return label to send this back for good. I'll keep my mid-2012 MacBook Air or get a new MBA hoping it doesn't also have the issue. This is RIDICULOUS.
-
Jan 9, 2014 2:06 PM in response to beleyby johnniecache,this is bad news, but thanks for posting. Had the same issues on mine, it was extremely disappointing. I am currently back on an old Lenovo, the WiFi is excellent. It even streams large video files via 802.11n perfectly, while my MBPr was stuttering, even on 802.11ac!
I only read from a few people here that are NOT experiencing these issues. And you got two faulty ones already. Really wondering if i should give it another try or not.
-
Jan 9, 2014 2:10 PM in response to johnniecacheby beley,I don't have the time or patience to try another MBP. I still have my mid-2012 Air and will use that until I can get a new Air I guess. I really wanted the 16 GB RAM and 1 TB drive, but I'm at my wits end. I can't get any work done for spending half my time on the phone with AppleCare.
-
Jan 9, 2014 4:08 PM in response to beleyby Topfjoer,Too bad your new MBP hasn't worked out either. It's frustrating to buy such an expensive machine and not being able to use it (to its full potential). I'm keeping mine, so I guess I'm stuck on 11g at home untill Apple and Broadcom get this sorted.
If you consider buying a new MBA, I would hold off a bit with that as well - the MBA is using the exact same wifi chipset as the MBP so you're likely to run into the same issues. The thread about the MBA already started in June and is much longer than this one: https://discussions.apple.com/thread/5100655?start=0&tstart=0.



