GalagBasha

Q: Yosemite (OS X 10.10) killed my WiFi :(

I just updated to Yosemite on a brand new 15" MBP Retina Display. For some reason my WiFi is not working. I turn it on and select the network I want to join (my regular network at home that I've been using with this same computer before updating). So, I turn it on and select the network and doesn't seem to want to join it and then my WiFi switches back off completely.

 

Is anyone else having problems with their WiFi on Yosemite?

MacBook Pro (Retina, 15-inch, Mid 2014), OS X Yosemite (10.10)

Posted on Oct 16, 2014 5:46 PM

Close

Q: Yosemite (OS X 10.10) killed my WiFi :(

  • All replies
  • Helpful answers

first Previous Page 19 of 20 last Next
  • by MasterBuck,

    MasterBuck MasterBuck Dec 9, 2014 10:36 AM in response to GalagBasha
    Level 1 (0 points)
    Dec 9, 2014 10:36 AM in response to GalagBasha

    Well, finally sorted.

    Turned out to be the WiFi cable, replaced by Apple.  Very strange that this happened immediately after installing Yosemite and having the same problems as you guys.  Wonder if the new upgrade somehow affected the recognition of the cable?
    Everything is very slow since :-(

  • by johnzimmerman,

    johnzimmerman johnzimmerman Dec 9, 2014 10:51 AM in response to MasterBuck
    Level 1 (0 points)
    Dec 9, 2014 10:51 AM in response to MasterBuck

    So, basically you're not sorted out. You're experiencing the same issues as many people here - slow or otherwise compromised wifi performance since upgrading to Yosemite. Often this slow performance is across the whole network and not just limited to the Yosemite device and in many cases it has also caused issues with streaming to ATVs.

  • by YBrion,

    YBrion YBrion Dec 9, 2014 11:25 AM in response to MasterBuck
    Level 1 (0 points)
    Dec 9, 2014 11:25 AM in response to MasterBuck

    Could you please explain what a wifi cable is? Wifi is wireless...

  • by MasterBuck,

    MasterBuck MasterBuck Dec 9, 2014 11:33 AM in response to YBrion
    Level 1 (0 points)
    Dec 9, 2014 11:33 AM in response to YBrion

    It was the cable from the Airport card to the antennae/display screen that was allegedly faulty

  • by Csound1,

    Csound1 Csound1 Dec 9, 2014 11:41 AM in response to MasterBuck
    Level 9 (50,486 points)
    Desktops
    Dec 9, 2014 11:41 AM in response to MasterBuck

    A mechanical fault.

  • by johnzimmerman,

    johnzimmerman johnzimmerman Dec 9, 2014 12:21 PM in response to Csound1
    Level 1 (0 points)
    Dec 9, 2014 12:21 PM in response to Csound1

    Possibly, but that seems too simplistic when there is a litany of people here citing specific software related issues with Yosemite, wifi and air play.

  • by EA1KF,

    EA1KF EA1KF Dec 9, 2014 12:31 PM in response to GalagBasha
    Level 1 (0 points)
    Dec 9, 2014 12:31 PM in response to GalagBasha

    I have recently bought a retina MacBook Pro 13'' but I am really 'scared' of upgrade to Yosemite. I am afraid of this kind of update every time I receive a communication about this. I never had had problems before with my other devices (iPod, iPhone, iMac, iPad) but this laptop is brand new. Since last week I bought and saw the update I didn't know what to do. By the way, I will stay with the old OSX operative system. I don't want to get into troubles with my WiFi network I need this computer for working every single day and I can't play with this. I will no take risks.

  • by Csound1,

    Csound1 Csound1 Dec 9, 2014 12:47 PM in response to johnzimmerman
    Level 9 (50,486 points)
    Desktops
    Dec 9, 2014 12:47 PM in response to johnzimmerman

    johnzimmerman wrote:

     

    Possibly, but that seems too simplistic when there is a litany of people here citing specific software related issues with Yosemite, wifi and air play.

    A broken cable is "possibly"

     

    Really?

  • by johnzimmerman,

    johnzimmerman johnzimmerman Dec 9, 2014 1:05 PM in response to Csound1
    Level 1 (0 points)
    Dec 9, 2014 1:05 PM in response to Csound1

    Csound... read his 1st post and then look at it in the context of this now 19 page thread on the crappy wifi issues surrounding the roll out of Yosemite.

     

    Sure, the cable could have been fried and sure, it could have failed at the exact moment he upgraded from a stable OS to this new (P)OS but it's far more likely that Yosemite is causing Wifi issues and they have plastered over it with a story about his cable being fried. He says right in the 1st post that he continues to suffer slow Wifi speeds.

     

    Certainly, it seems you're not experiencing these issues which is wonderful but for Apple to ignore that for many of us this has caused massive disruptions is wrong. I spent the better part of 4 hours trying to sort my own issues out before reverting to Mavricks and immediately having them solved. I didn't drop $2500 on a MacBook pro to be saddled with Windows style BS. I could have saved $2200 to have the same results, in fact - lately, my Lenovo laptop that I paid $299 for 5 years ago has been far more stable and is running the most recent Windows release...

  • by Erik Landi,

    Erik Landi Erik Landi Dec 9, 2014 1:34 PM in response to EA1KF
    Level 1 (0 points)
    Dec 9, 2014 1:34 PM in response to EA1KF

    Unless you really want the new features of Yosemite (continuity quite frankly is half baked), I would wait for the point release after this latest beta (10.10.3). I have a 2012 rMBP and the 5 Ghz stability is not something to be desired (plus all the other 2.4 Ghz issues people seem to be having here). I think there are a couple of things at work against us here, first I think apple has been far too aggressive with the wifi power management (reducing the TX power to save battery) and poor antenna placement in the MBPs in general. It seems like the Retina models are very susceptible to directional interference (i.e. if your off angle towards you router, physical objects blocking signals, etc), and the Broadcom chip used in the wifi module is quick to sleep. My hope is that new drivers will address the latency issues in the wifi chipset and the wifi power management will be slightly less aggressive in its battery savings method. I wish apple would have a setting in the energy saver preference pane on wifi sensitivity (i.e more battery life vs performance).            

  • by Csound1,

    Csound1 Csound1 Dec 9, 2014 1:59 PM in response to johnzimmerman
    Level 9 (50,486 points)
    Desktops
    Dec 9, 2014 1:59 PM in response to johnzimmerman

    What is your problem.

     

    In hs case ( a broken cable ) there was a mechanical failure. Imagine what else you like.

  • by johnzimmerman,

    johnzimmerman johnzimmerman Dec 9, 2014 3:49 PM in response to Csound1
    Level 1 (0 points)
    Dec 9, 2014 3:49 PM in response to Csound1

    Csound... I have no problem with you and I'm certainly not looking to create one. My point is that I don't accept that the cable in his case was at fault or that his issues are solved, he says as much when he says his wifi remains very slow.

     

    This is similar to what many of us are experiencing. Apparently, not you. My problem - if I have one - is that I have been an Apple supporter for many years. I have made a point to replace over time my home entertainment and computing needs with each of their products so as to enjoy the benefit of an ecosystem of devices designed to work together, seamlessly and lately the seams are showing in the half baked releases Apple is pushing out.

     

    Specifically, I have an iPhone, iPad, Apple TV, Time Capsule and MacBook Pro. These all worked beautifully together with iOS 7 and Mavricks. iOS 8 came out and there were some small hickups (I still cannot get weather information to consistently show in my widgets menu, for example) but overall I have been happy. Then, I update the Macbook to Yosemite and the whole house of cards fell. My iOS devices cannot see the ATV, none of my devices can access the internet with speeds above dial up, my MacBook starts going into forced re-boots, it all happened at once. I spent hours trying to sort out the iOS devices not seeing the Time Capsule or ATV, never assuming it could be related to Yosemite and then gave up and started trying to figure out the issues with Yosemite. Gave up there too after about an hour and reverted to Mavricks out of desperation and - what do you know - everything in the network bounced back. No way, I figured must be an install issue, so I reinstalled Yosemite and - once again - all **** broke loose.


    I - along with millions of others - paid a premium for a product that is no longer living up to its hype. That's my only problem and frankly, I am annoyed. Seems this company lost it's way with the death of Jobs and the cracks are starting to show now.

  • by Csound1,

    Csound1 Csound1 Dec 9, 2014 4:15 PM in response to johnzimmerman
    Level 9 (50,486 points)
    Desktops
    Dec 9, 2014 4:15 PM in response to johnzimmerman

    OK, we'll disagree.

  • by gaialive,

    gaialive gaialive Dec 16, 2014 8:28 PM in response to GalagBasha
    Level 1 (5 points)
    Dec 16, 2014 8:28 PM in response to GalagBasha

    I just encountered this problem at it's worst, this evening. At one point my WiFi was disconnecting and reconnecting every 30 seconds.

    I read through every one of these posts, and after trying each of the 'reasonable solutions' :  Reset PRAM - Delete SystemConfiguration folder - Create NEW WiFi Hardware Network Device with alternate name etc I then found a solution which worked on my 2013 Retina MacBook Pro

     

    [ My setup : My router's WiFi connection is meant to be WPA2 Personal. It serves everything from MBP and iPad1, up to iPad Air2 and rMBP and every Apple device in between including all generations of AppleTV. All these Apple devices are compatible with 802.1 n. My router had reset itself for some reason to WPA & WPA2, so I first changed it back to WPA2 only. ]

     

    In my router's config, I switched OFF compatibility with 802.1 b/g. Then I switched ON compatibility with ONLY 802.1 n (and above.)

     

    My WiFi has now returned back to normal and is working fine with no interruptions, dropouts, lost connectivity or problems at all.

     

    Some of the alternative solutions discuss switching between 5GHz and 2.4GHz.

    802.1g runs at 2.4GHz, whilst 802.1n is capable of running at 5GHz but also simultaneously supporting 2.4GHz for compatibility with 'g'

    I would suggest that for my system, only by switching OFF the 2.4GHz compatibility on my router, was the Yosemite bug squashed

    Hope this helps

  • by Patnet,

    Patnet Patnet Mar 12, 2015 3:29 AM in response to GalagBasha
    Level 1 (0 points)
    Mar 12, 2015 3:29 AM in response to GalagBasha

    Hi, yours was the first fix I tried and it worked, thanks for sharing!

first Previous Page 19 of 20 last Next