-
All replies
-
Helpful answers
-
Feb 1, 2015 4:23 PM in response to dszakal89by jndupuis1,Very good point as well. This could possibly just come down to a bad lot of Broadcom boards. Which, is quite difficult to find and define as such. Just merely a thought I had in trying to help in a solution. Yosemite 10.10.1 didn't work for some, Yosemite 10.10.2 didn't work for others. In fact, 10.10.2 runs fine on my Mac Mini (late 2012). Didn't work out for others. Investigating the Broadcom board of my Mac Mini model just made me question the possibility of RF interference both in chip placement on the board and board placement in the unit together with proper shielding. That's all.
-
Feb 1, 2015 4:37 PM in response to Akos G. Garaiby jndupuis1,Nice links, by the way. Broadcom Driver being "closed source" may be the legal agreement between Broadcom and Apple for Apple's use of their product and driver. Certainly not helpful in the process of writing a new OS X with enhanced features that utilize the Broadcom features as advertised. This may not be a finger pointing at Apple or Broadcom, but, a conflict of interest.
-
Feb 1, 2015 5:29 PM in response to tomstephens89by The Fan Club,Started having problems after updating to 10.10.1 and got worse with the 10.10.2 update, super slow, un-usable internet speed. Fell from 40Mbps to 0.1Mbps on Speedtest on my MacBook Pro 13" (Mid 2010) with Broadcom Wi-Fi adaptor.
Spent close to 15 hours trying every single workaround mentioned in this thread, and elsewhere, with no luck. Finally by accident I discovered a fix that works for me.
Changing the MAC address of the Wifi Adaptor does the trick - yes this sounds very strange, but it works.
To temporarily change the MAC address of your Wi-Fi Adaptor (it will revert back to the real MAC address when you reboot) :
- Make sure your Wi-Fi is switched ON and you are connected to your Wifi Network.
- First disassociate from your current network. The Wi-Fi Icon will turn grey. Open a terminal window and enter:
airport=/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resour ces/airport && sudo $airport -z
- Next enter the following to get the device name of your Wi-Fi adaptor:
device=$(networksetup -listallhardwareports | grep -A1 "Wi-Fi" | grep "Device:" | cut -d ":" -f2 | sed 's/^ *//')
- Then generate a new MAC address with:
newmac=$(openssl rand -hex 6 | sed 's/\(..\)/\1:/g; s/.$//')
- Finally set the new MAC address:
sudo ifconfig $device ether $newmac
Then just re-connect to your Wi-Fi network by selecting it from the taskbar Wi-Fi menu. You should have full speed internet joy.
* Note : Sometimes the MAC address is not changed on the first try, and you need to just repeat the steps again. I have had to sometimes repeat the steps a few times before my internet speed was back to normal. Once it is back to normal it keeps working perfectly until I reboot. Putting the laptop to sleep does not affect the speed.
The above steps can be easily be put into a script and run when needed.
-
Feb 1, 2015 5:48 PM in response to The Fan Clubby The Fan Club,Step 2 above has a extra space in the word Resources, and I cannot correct it in the post as the editor keep adding the space for some reason.
-
Feb 1, 2015 11:54 PM in response to The Fan Clubby mazzjnr,Just did this, my wifi appears to be back.
Didn't have any issues with my wifi prior to 10.10.2, using macbook pro retina 13 late 2013.
Has been painful since i updated last week, interestingly i've had no issues with my 27in iMac.
-
Feb 2, 2015 3:12 AM in response to tomstephens89by Bogheadben,Well, here's my tuppence worth.
I'm a complete non-technical (new) Apple user. I bought my Retina Mac Book in late December. Came with Yosemitie. Worked great. In fact. it was the reason I bought the RMP in the first place. No issues. Connection to Wi-Fi was stable. Loved it.
Upgraeded to 10.10.2 yesterday. Why? Because it's what you do when you're not into technical stuff. And ... since then my lovely shiny RMP is a wi-fi brick. Connectivity issues. Drops every 2/3 mins.
I'm not willing, or even capable of performing many of the tricks and tips I've read on this forum/thread. Simply beyond me. So, a couple of calls to Apple Support and I have a Genius Bar appointment booked. For next weekend. The earliest appointment. It's a 40 mile trip.
I'm scunnered as they say in Scotland. I cannot get pleasure out of my RMP for at least a week and even then I'm not confident of a fix given the anecdotal stories doing the rounds.
Surely to goodness Apple can recognise that the latest upgrade is not working?
Fingers crossed for the weekend.
-
Feb 2, 2015 3:24 AM in response to Bogheadbenby zappee,I have the same issue, bricked after 10.10.2.
Though I don't see any need for you to go to the genius bar, they won't be able to help you.
I got my case escalated to engineering and are working with them now to solve that problem.
-
Feb 2, 2015 3:31 AM in response to zappeeby Bogheadben,And how do you get the case escalated to engineering?
I've been given lots of online options - which is funny seeing as I can't get access - and fiddly fixes which I simply don't understand. All I want to do is switch the machine on and use it. It was the reason I bought it in the first place.
Why won't the Genius Bar be able to help? Is that not what the guys are there for? I certainly hope so, otherwise I've wasted my money.
-
Feb 2, 2015 3:45 AM in response to Bogheadbenby zappee,I tried somethings myself, then used chat support. He escalated so that second line support called me and he had the same issue on his computer, so it got escalated to engineering.
But I also opened an thread here and apparently Apple was reading that because I then got an email from the Wireless Engeneering team with questions for logs etc.
Genius bar is just like calling or chatting, they cannot solve this kind of problem. They are just first line.
So I wouldn't recommend you to do that travel.
-
Feb 2, 2015 3:52 AM in response to zappeeby Bogheadben,Ok, thanks for the info. Appreciate it.
The nice young lady I was speaking to suggested that the Genius people would be able to do the things that I cannot. Surely worth a try? If it all goes wrong then I'm not to blame! Or that's the theory at any rate.
I have a case number. Perhaps I should get back on to them. I'm not comfortable with the suggestions of SMC or PRAM resets. It sound simple enough, but it's the kind of things that can go wrong for me (in past experiences with laptops etc). If both procedures can perhaps fix it, then I'd be much happier if it was carried out by Apple people.
-
Feb 2, 2015 3:57 AM in response to Bogheadbenby zappee,Sure they can do some other things, but I don't think it will help.
Yeah, get back to them and show them this thread. Maybe you can get it escalated.
-
Feb 2, 2015 4:16 AM in response to zappeeby Bogheadben,Chat facility no longer available!
Ach well.
-
Feb 2, 2015 4:39 AM in response to Bogheadbenby DavidDundonald,Here is an update on my wifi issues. I updated to Yosemite again when the new patch (10.10.2) came out. Previously I had installed Yosemite during the beta, and again when it was released to the public, but both times had to return to Mavericks due to wifi issues. My wifi at work could not keep a stable connection, but my home wifi was working fine. I sent a bug report into Apple during the beta, and after release I contacted Apple support and had a Genuis Bar appointment (they were unable to replicate the problem in the store since the wifi seemed to work fine).
This time, after upgrading to Yosemite for the third time, I was disappointed to note that I again couldn't keep a connection. This time though the connection wasn't dropping as such - it was telling me that it was still connected, but nothing could get through (webpages timed out, mail couldn't reach the server etc). I went home over the weekend and kept with Yosemite for a bit since as for previous versions my home wifi works fine. This morning I was ready to revert back to Mavericks, but to my surprise, my work wifi seems to be working. It took a very long time to connect (and I had to switch wifi off and on again) but now that it is connected, it hasn't dropped. I have been working for a few hours now, so I am hopeful that this is now fixed (fingers crossed!)
I am not aware of having done anything different this morning compared to Friday when it wasn't working at all. Very odd...
-
Feb 2, 2015 7:14 AM in response to DavidDundonaldby antoniopp,The connection works for a few hours, and then stops working for another few hours. during this downtime the connection is impossibly slow, and keeps dropping and coming back several times.
I think this behavour tricks people who think they have found a solution, but after a few hours... stops working again.
Only an apple solution will do the trick.
Are they really working on it? 4 months later they have nothing?
-
Feb 2, 2015 7:40 AM in response to antonioppby justinfromsussex,I'd just like to add my info on the basis that Apple, the most valuable company in the world (?), must have someone monitoring this thread... Please tell me they are...
OSX Yosemite 10.10.2 (14C109)
MacBook Pro (Retina, 15-inch, Mid 2014)
Processor: 2.2 GHz Intel Core i7
Memory: 16 GB 1600 MHz DDR3
Graphics: Intel Iris Pro 1536 MB
Router: BT Home Hub 3.0 settings - Type B, plus Huawei EchoLife HG612
Had no problems whatsoever before update to 10.10.1, then MBP wouldn't automatically hook up to my wifi after starting or waking up. 10.10.2 has made no difference, except that it's probably even worse in that it has slowed my broadband download speed right down. MBP still won't hook up to my wifi unless I click on the icon and wait ages for it to find my router (which it is positioned right next to). Lists all my (distant) neighbour's routers quickly but not mine. And it still won't hook up automatically after waking from sleep or after start up. It stops me taking loo breaks as I don't want to lose connection...
I'm a completely non-technical person, and choose Apple so that I never have to do anything with the software. I want it to be pick up and go. Please.