-
All replies
-
Helpful answers
-
Jan 30, 2015 11:38 AM in response to tomstephens89by Jim Bauwens,My brother had a similar problem with Yosemite. Turned out that it couldn't handle the fact that the routers time was incorrect. After correcting this his laptop connected to router without any problem.
-
Jan 30, 2015 12:06 PM in response to bcanuelby Vognbygger,Now there seems to be some mistakes made here. Yosemite is not free, I paid to upgrade from snow leopard to lion, and this is just an upgrade to lion, not a new OS. Yes yes it has some new features.
However even involving the price of a product in the discussion on missing BASIC functionalities are stupid. Working WiFi on a laptop is after all pretty elementary.
Just as a note, installed Linus Mint on a Dell E4200 I found in a dumpster, worked within minutes (after I found a charger). Over the last couple of days this have been a more stable and productive machine, than my MacBook which I paid 13000dkk, with lion for which I paid some 400dkk. And the ones suggesting that purchasing new WiFi hardware to solve the issues, come on, that is a stupid solution, although it might work.
My point is that Apple seems to ignore the troubles they cause for some users. And sadly some customers defend them for distributing faulty products.owNow back to the problem and sorry for the long post. I have found some improvements after performing the SMC reset. Continuous reboots for some reason also seems to improve the time WiFi is working. But I have found no improvements moving around in my buildings, where I an Airport extreme, an Archer C2, a D-link Dir-655, a Cisco WAP4410, and a WAP4400. All access points connections yields the same error. Now when I upgraded to lion back in the days, I also had problems with WiFi. At that time it simply did not work, at all. (apple support solution at that time was to by a new macbook, not kidding. They disclaimed that as soon as they came aware that the MacBook was under warrenty). I cannot recal the exact solution, but it involved removing the WiFi software completely.
-
Jan 30, 2015 12:26 PM in response to jndupuis1by steve626,jndupuis1 wrote:
I have monitored Wi-Fi in Mavericks on my internal HD and monitoring Wi-Fi in 10.10.2 on my external HD. Yosemite 10.10.2 is more stable since it's release in October on my Mac Mini in my Home environment. I was getting 5 to 6 Trashed software maps per session, now, zero. My biggest complaint, as I feel for those in this situation, is that Mavericks is not readily available for download. The option should be there. I do not have an iPhone running iOS 8. I don't want my calls and texts on my computer. That being said, there will be a point where upgrading OS X will be necessary. Mavericks is not that old yet and not dead yet. Reverting back is not like swallowing the bitter pill. It's the frustration of not being able to click on Apple Store and Download Mavericks Now for those who really need it back.
Having previously downloaded Mavericks, when I look in the App Store I see options to download Lion, Mountain Lion, and Mavericks (and Yosemite), all of which I had downloaded in the past. These options are shown in the "Purchases" area. You can't INSTALL right away since it won't allow you to install an older OS over a newer one, but after downloading it, you can create a 8-GB bootable jump drive and OS installer for Mavericks (there are many online sources explaining how to do this). Then you would need to completely back up all your files and data (and 3rd-party applications), erase and reformat your primary boot drive, install Mavericks from the small jump drive, and then restore the files you backed up.
Another simpler option would be to erase and restore from a Time Machine backup (or a clone-type backup) which was using Mavericks. Taking care to first back up more recent/changed files since that backup so they can be brought over when that is done.
-
Jan 30, 2015 12:39 PM in response to steve626by peppermint,@ steve626:
i think its obvious, if i did not experience any single sudden wifi disconnect the last years, until i updated from 10.10.1 to 10.10.2.
with 10.10.2 i had multiple wifi disconnects, without any reason the last 3 days. (at least 30 or 40 for one day)
i tried to delete the wifi keychain and erased all wifi settings in system prefs, to do a fresh new wifi setting, but that did only help for 1 or 2h.
so i rolled back to 10.10.1 via time machine backup, and now my wifi is working 100% like before.
-
Jan 30, 2015 12:57 PM in response to peppermintby steve626,peppermint wrote:
@ steve626:
i think its obvious, if i did not experience any single sudden wifi disconnect the last years, until i updated from 10.10.1 to 10.10.2.
with 10.10.2 i had multiple wifi disconnects, without any reason the last 3 days. (at least 30 or 40 for one day)
i tried to delete the wifi keychain and erased all wifi settings in system prefs, to do a fresh new wifi setting, but that did only help for 1 or 2h.
so i rolled back to 10.10.1 via time machine backup, and now my wifi is working 100% like before.
This is indeed part of the conundrum because some people have reported here the opposite (problems with 10.10.1, fixed with 10.10.2). More clues for Apple, I presume, to troubleshoot. To be honest, I am still on Mavericks at home, still waiting for all this to settle down. However when we all get converted at work, my work laptop will have Yosemite and they I'll see how it works. However sometimes here at work they do not install the very latest version, so we may be rolled up to 10.10.1 for all I know. Our IT people do careful testing, but it's somewhat controlled because they do go with a standard setup that is mostly the same on all our Macs. Here on the forums, everyone has a somewhat tailored arrangement, settings, routers, etc.
-
Jan 30, 2015 2:28 PM in response to steve626by jndupuis1,I am with you. I have made a backup of Mavericks. I am in defense of those who have upgraded to Yosemite and are not able to download Mavericks from Purchases or download it anywhere else. Those who upgraded and cannot revert back on there own would have to go to the Genius Bar at this point. My sympathy goes out to those with new Macs out of box with Yosemite, only to find, they are not able to revert without jumping through hoops. My primary OS X is Mavericks that shipped with my machine and will remain that way. Yosemite 10.10.2 is working well for me, but, not willing to replace Mavericks with it. I created a new Apple ID just to run Yosemite and take it for a spin. It would appear that all has been tried and doesn't hold true for most in review of this thread. Apple Feedback has been notified. Now, it's a waiting game. Apple is listening - the updates are slow to appear and slow to resolve.
-
Jan 30, 2015 2:43 PM in response to Jim Bauwensby hexdiy,.My brother had a similar problem with Yosemite. Turned out that it couldn't handle the fact that the routers time was incorrect. After correcting this his laptop connected to router without any problem.
Thank you Jim, in all of these 156 longish pages, this has not been published! Relatedly also note that there is a serious NTP (setting the time from internet clocks) security hole that has just been made public and is possibly being exploited. Nothing to panic about, but curious coincidence indeed.
Could you expand on the router's make and model please?
http://www.zdnet.com/article/major-ntp-security-holes-appears-and-are-being-expl oited/
-
Jan 30, 2015 3:02 PM in response to tomstephens89by tswell,Lots of whining here, not much solid information. From the (very) few comments that include system information, it seems possible that newer Macs have the problem more than older ones. Some having problems with the latest fix, some with the previous fix. Of these hundreds of comments there is nothing that can help Apple find a pattern. So, let off steam if you want but have the decency to put some useful information here just in case Apple is studying the problem.
I use much older Macs than many of you and have no problems with Yosemite 10.10.1 WiFi. I found this discussion after reading a more informative discussion of the issue at Slashdot ( http://apple.slashdot.org/story/15/01/30/1730207/wi-fi-issues-continue-for-os-x- users-despite-updates ) Good luck!
-
Jan 30, 2015 4:50 PM in response to Mr. Morryby leandrofrommonroe,Same problem here.
Upgraded directly from Mavericks to 10.10.2 on both of my macs. Wifi is not dropping but speed degrades with time becoming incredibly slow, specially for file transferring (internet and file sharing between macs on same wifi). Besides that, Network Utility keeps showing the same speed (maximum in accordance to my AirPort Extreme configuration - 300 Mbit/s). Before the upgrade everything was just fine.
Specs:
AirPort Extreme 4th Gen.
MacBook Air Early 2014
iMac 27" late 2009
-
Jan 30, 2015 5:48 PM in response to tomstephens89by estpalley,I'm certainly late to the party, but since I went from Mavericks to any version of Yosemite, including the 10.1.x and 10.2.x updates, wifi is not usable. If I turn off bluetooth, wifi is okay. This makes my "magic" mouse less than magical, as well as any bluetooth device I may wish to use. I was a very reluctant convert to Apple, but was impressed when I started using my new (2014 vintage) macbook air. As soon as the "update" to Yosemite was completed, the honeymoon was over. Everything that the Mac was supposed to be that made it better than any other product went right out the window. Wifi is now unusable and I'm now looking for a new Windows based solution for my portable needs. I've followed this message thread since I found it, and have the impression that Apple has committed few resources to correcting this serious issue. At every opportunity, I'll discourage the purchase of Apple products to everyone who inquires, and will point them to this message thread as evidence of the poor response of Apple to a major concern.
-
Jan 30, 2015 6:28 PM in response to tomstephens89by romcodox,Horrible horrible update, it crashed my new mac ( macbook pro 13 retina 2014 ) and now is unusable to seriously working...wifi.. I had no problem with wifi on 10.10.1, but after 10.10.2 update, connection permanently falls. Very interesting thing is, so my apple usb keyboard also stop working after this update, and I must use USB hub!!! ( "solution" taken from this forum ). I don't now how Apple tested this software, but this situation, for this price for their products, it is unacceptable. I wait impatiently for fixHorrible horrible update, it crashed my new mac and now is unusable to seriously working...wifi.. I had no problem with wifi, but after 10.10.2 update, connection permanently falls. Very interesting thing is, so my apple usb keyboard also stop working after this update, and I must use USB hub!!! ( "solution" taken from apple support forum ). I don't now how Apple tested this software, but this situation, for this price for their products, it is unbelievable. I wait impatiently for fix
-
Jan 30, 2015 6:55 PM in response to tomstephens89by jtcs87,Faced the same issue which is connected to my own SSID and keep looking for networks. Hope Apple can resolved this issue by as soon as possible.
-
Jan 30, 2015 7:07 PM in response to tomstephens89by nucleon2000,Ok, apple. Enough is enough. 3.5 months, thousands of mentions on hundreds of pages in this thread alone! We know Apple is aware of problems. I am asking here and now that someone from apple (Tim Cook himself would be a good start) acknowledge the problem here IN THIS FORUM AND in public, and tell us what's being done.
Either this glitch doesn't affect the vast majority of folks or Apple has its head in the sand. I personally own 5 Apple computers and the family has iPods and iPhones galore. Apple can can feel free to buy back the lot at full retail plus interest if this problem doesn't get fixed NOW.
Mr. Cook, and Apple: this is NOT the way to keep your customers happy and loyal. It IS however, how class-action suits begin.
-
Jan 30, 2015 7:50 PM in response to nucleon2000by j-m-d,nucleon2000 wrote:
Ok, apple. Enough is enough. 3.5 months, thousands of mentions on hundreds of pages in this thread alone! We know Apple is aware of problems. I am asking here and now that someone from apple (Tim Cook himself would be a good start) acknowledge the problem here IN THIS FORUM AND in public, and tell us what's being done.
Either this glitch doesn't affect the vast majority of folks or Apple has its head in the sand. I personally own 5 Apple computers and the family has iPods and iPhones galore. Apple can can feel free to buy back the lot at full retail plus interest if this problem doesn't get fixed NOW.
Mr. Cook, and Apple: this is NOT the way to keep your customers happy and loyal. It IS however, how class-action suits begin.
I'm wondering if:
a) they really have no clue what is causing it
b) they really have no clue how to fix it
Guessing they are so far down some new architecturally path that they can't back up and fix it now (severe tire damage)
I think many people would be satisfied if they just maned up (no offense ladies) and let folks go back to Mavericks easily - which they will never do because embarrassing.
-
Jan 30, 2015 9:43 PM in response to j-m-dby Ikester,j-m-d wrote:
I'm wondering if:
a) they really have no clue what is causing it
b) they really have no clue how to fix it
Guessing they are so far down some new architecturally path that they can't back up and fix it now (severe tire damage)
I think many people would be satisfied if they just maned up (no offense ladies) and let folks go back to Mavericks easily - which they will never do because embarrassing.
That's the thing. I don't think they can really fix this without losing face and removing a big chuck of functionality that was heralded as one of the major new features of Yosemite: Handoff.
This is obviously speculation on my part, but given all the testing and error reports over the last few months, I believe it's quite clear that this is a software problem that was introduced with 10.10 and that they're desperately trying to fix/make work.
So if I had to guess, regarding your statements above I would say
a) false: they do know.
b) true: because, sadly, there may be no true, absolute fix. It's possible that the only way to fix it for good is to disable all the Handoff features and revert back to the Mavericks networking stack and drivers.