Still no fix for dropped Wi-Fi after waking up from sleep... I spent 15 minutes (really, I timed it) this evening closing and opening my MBP's lid until I could finally connect to my wireless router (which is literally 7 inches to the right of my MBP).
If you don't know what I'm talking about, read this: http://osxdaily.com/2011/11/06/lion-wi-fi-problems-solution-... - About 300 people have posted on that topic, it's really widespread yet it hasn't been fixed after 15 months. You can also google "lion wireless problems" to see literally thousands of post on online forums about this problem.
And a good news to all fellow iOS users: This "feature" (read "cancer") has spread to iOS 6 betas as well.
I have found ever since upgrading to Mountain Lion that waking up is iffy in general. The login screen displays, but it can take anywhere from 10 seconds to several minutes before I can type in my password. Sometimes it takes so long I just force the machine down and reboot instead.
I 'fixed' this: create a shell script that pings your router every 30 seconds and add it to your launchagents. It forces the wifi to stay alive. Let me know if you'd like me to post more on how to do this. I've had this problem since Lion and my wifi hasn't dropped for months now.
There was a similar issue with Snow Leopard and I would not doubt others had it with Lion. What irked me in my case was my first year i5 iMac (the i5 in twenty seven inch form) was perfectly fine until I upgraded. Then suddenly wireless may or may not work upon waking from sleep. The odd part was, it might work for a few seconds after waking before I would have to manually end it and connect again. It was talking to the Airport Extreme just fine, it could not get beyond it.
The kicker, the copy of windows which I ran through Parallels could connect. I could surf sites and VPN through Windows in a VM while OS X applications could not, until I bounced the wireless connection.
There was definitely some wifi drivers problem in the original Lion. I wrote a fairly popular blog post summarizing reported solutions to the wifi problem in Lion and what solved it for me: http://thoughts.maayank.com/2011/08/wireless-problems-with-m...
I wrote it a long time ago, but maybe it will still give you (or others) leads to a solution. FWIW I haven't had any major wifi problems since the first or second Lion update.
Resetting the SMC [1] on my Macbook Air (late 2010) seems to have fixed the wifi issue. Obviously, no guarantee that'll fix it on yours...
Unfortunately, I've had all sorts of other, less intermittent issues with Mountain Lion. Finder is extremely sluggish (beachballing a LOT), sleep can be iffy, and will cut in while a Time Machine volume on network share is mounted, leaving it in an unclean state and wanting to delete all my backups (!!!) and start over. (I've thus far worked around it with a full fsck and deleting only the most recent snapshot and updating the plist file to reflect this, but that's not really a solution as it takes a few hours at a time to do the fsck over the network)
I'm also getting far worse battery life than before, as the system has 5-10% CPU utilisation when idle for no apparent reason.
I'm hoping these have improved with 10.8.1, otherwise I'll revert to Lion and think about switching back to Linux in the medium term...
"To fix this, I removed all the remembered locations and then in Configure Network Prefrences -> TCP/IP changed Configure IPV6 to Link-local only."
EDIT: It did seem to make things better for me, where after waking up from sleep it at least automatically reconnects, but it is still not same as Lion I think.d
I had no issues in Snow Leopard, but had the dropped Wi-Fi after wake up from sleep on all Lion with my iMac/Atheros chipset and Cisco wireless n router. Had tried downgrading to 10.6.4 Atheros driver, etc, etc, etc, from the apple forums, and nothing worked.
I decided to try something I shouldn't have had to and bought an Airport Extreme.
No more issues. I've since sold the Cisco N router -- that had worked perfectly with every other wifi device in the house, including this same computer before Lion.
I truly love my MacBook Pro from late 2008: "pry-it-from-my-cold-dead-hands-unless-I-get-a-new-machine" love. But I still get that anxious knot in my gut when thinking about upgrading OS X, for one reason: when problems are discovered and reported, Apple will simply hang you out to dry.
Specifically, that machine had known issues with the GPU and dual boot was spotty because the fans would not run in Windows unless you manually started them in OS X. For YEARS, users begged for help and got nothing from Apple, and in some cases, Apple even actively FOUGHT them (e.g. http://www.macrumors.com/2012/04/19/blogger-victorious-over-...). All this to avoid looking like they were anything less than perfect.
I know - waaaaa!. It's still an awesome machine (and OS - I love and hate all platforms in one way or another), but it's a shame that Apple has earned the reputation that Jobs so famously put a face on when he felt personally challenged over these complaints: it's not broken, you are using it wrong, get over it - it's just a machine. It's a tough position to put the consumer in when you are a company that expects that customer to cede so much control in the name of "trust our authority".
I feel the same way about my early 2009 Macbook Pro. One reason I love it is because I have easy access to the battery should I need to replace it, and I even have easy access to the hard drive bay.
I've found Safari to be much MORE reliable, if for no other reason than playing HTML5 video made Safari crash reliably in Lion, which doesn't happen in Mountain Lion.
Specifically, HTML5 video via the YouTube5 extension was fine. Also, HTML5 video that YouTube and Vimeo voluntarily showed me was fine. HTML5 video on The Escapist was not fine, and would crash somewhere between immediately and 30 seconds in (sometimes, but rarely, longer, but never so long as a minute).
This made AllThingsD especially frustrating to deal with, because they have HTML5 video straight on their front page, and while it doesn't auto play, it would cause the webview process to go into a crash loop until I closed that tab between crashes. I felt especially bad for my laptop (and the web server) when I opened a new tab to AllThingsD and went to get some water and it crashed 15-20 times in a row.
Now? Everything works great. Faster, smoother, less crashy.
With multimonitor setup the apps are allowed to use those extra monitors while in full screen. You're supposed to be able to drag pieces of the apps into them if the app supports it.
It actually seems like there's a way around this on an app level-- I downgraded iTerm2 from the current 1.0.2.whatever to the 1.0.0 stable, and Full Screen properly takes up one screen on 10.8 instead of filling my other monitor with felt.
Upgraded the day it was released, last few days I feel that you could cook an egg on my MBP after 2 hours of working (nothing fancy, IDE and browsers open - no heavy GPU usage). Do more people feel that 10.8.x overheats the machine?
This has been a huge issue on my mid-2010 MBP and others have reported the same on Apple forums. My MBP has been overheating, throwing up artifacts all over the screen and freezing requiring a hard reboot. So far so good though... fingers crossed.
I never had this problem when I was using Snow Leopard, but since I've updgraded to Mountain Lion, every time I wake up my computer, the Wifi freezes. What are developers doing to fix this problem. I'm getting tired of force rebooting in order to connect.
Does anyone know if this fixes missing icons? My MBP 2011 will come up with the wifi or other random icons hidden (I can still click on where they 'would' be and it'll show me the wifi networks, for instance)...
[+] [-] pooriaazimi|13 years ago|reply
If you don't know what I'm talking about, read this: http://osxdaily.com/2011/11/06/lion-wi-fi-problems-solution-... - About 300 people have posted on that topic, it's really widespread yet it hasn't been fixed after 15 months. You can also google "lion wireless problems" to see literally thousands of post on online forums about this problem.
And a good news to all fellow iOS users: This "feature" (read "cancer") has spread to iOS 6 betas as well.
[+] [-] city41|13 years ago|reply
[+] [-] marquis|13 years ago|reply
[+] [-] cstejerean|13 years ago|reply
[+] [-] Shivetya|13 years ago|reply
The kicker, the copy of windows which I ran through Parallels could connect. I could surf sites and VPN through Windows in a VM while OS X applications could not, until I bounced the wireless connection.
[+] [-] maayank|13 years ago|reply
I wrote it a long time ago, but maybe it will still give you (or others) leads to a solution. FWIW I haven't had any major wifi problems since the first or second Lion update.
[+] [-] pmjordan|13 years ago|reply
Unfortunately, I've had all sorts of other, less intermittent issues with Mountain Lion. Finder is extremely sluggish (beachballing a LOT), sleep can be iffy, and will cut in while a Time Machine volume on network share is mounted, leaving it in an unclean state and wanting to delete all my backups (!!!) and start over. (I've thus far worked around it with a full fsck and deleting only the most recent snapshot and updating the plist file to reflect this, but that's not really a solution as it takes a few hours at a time to do the fsck over the network)
I'm also getting far worse battery life than before, as the system has 5-10% CPU utilisation when idle for no apparent reason.
I'm hoping these have improved with 10.8.1, otherwise I'll revert to Lion and think about switching back to Linux in the medium term...
[1] http://support.apple.com/kb/HT3964
[+] [-] gnufied|13 years ago|reply
"To fix this, I removed all the remembered locations and then in Configure Network Prefrences -> TCP/IP changed Configure IPV6 to Link-local only."
EDIT: It did seem to make things better for me, where after waking up from sleep it at least automatically reconnects, but it is still not same as Lion I think.d
[+] [-] tambourine_man|13 years ago|reply
But connection drops intermittently with me, not when waking from sleep.
And now I have this weird flickering cursor while typing in Mail.app
God I miss Snow Leopard.
[+] [-] peapicker|13 years ago|reply
I decided to try something I shouldn't have had to and bought an Airport Extreme.
No more issues. I've since sold the Cisco N router -- that had worked perfectly with every other wifi device in the house, including this same computer before Lion.
[+] [-] fein|13 years ago|reply
[+] [-] X-Istence|13 years ago|reply
[+] [-] clupprich|13 years ago|reply
[+] [-] hnriot|13 years ago|reply
7" - maybe you should invest in an ethernet cable...
[+] [-] headbiznatch|13 years ago|reply
Specifically, that machine had known issues with the GPU and dual boot was spotty because the fans would not run in Windows unless you manually started them in OS X. For YEARS, users begged for help and got nothing from Apple, and in some cases, Apple even actively FOUGHT them (e.g. http://www.macrumors.com/2012/04/19/blogger-victorious-over-...). All this to avoid looking like they were anything less than perfect.
I know - waaaaa!. It's still an awesome machine (and OS - I love and hate all platforms in one way or another), but it's a shame that Apple has earned the reputation that Jobs so famously put a face on when he felt personally challenged over these complaints: it's not broken, you are using it wrong, get over it - it's just a machine. It's a tough position to put the consumer in when you are a company that expects that customer to cede so much control in the name of "trust our authority".
[+] [-] dag11|13 years ago|reply
[+] [-] blinkingled|13 years ago|reply
[+] [-] OlivierLi|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] pmjordan|13 years ago|reply
[+] [-] pseudonym|13 years ago|reply
[+] [-] grecy|13 years ago|reply
[+] [-] blinkingled|13 years ago|reply
[+] [-] halayli|13 years ago|reply
Safari is crashing way more frequently than it used to.
[+] [-] danudey|13 years ago|reply
Specifically, HTML5 video via the YouTube5 extension was fine. Also, HTML5 video that YouTube and Vimeo voluntarily showed me was fine. HTML5 video on The Escapist was not fine, and would crash somewhere between immediately and 30 seconds in (sometimes, but rarely, longer, but never so long as a minute).
This made AllThingsD especially frustrating to deal with, because they have HTML5 video straight on their front page, and while it doesn't auto play, it would cause the webview process to go into a crash loop until I closed that tab between crashes. I felt especially bad for my laptop (and the web server) when I opened a new tab to AllThingsD and went to get some water and it crashed 15-20 times in a row.
Now? Everything works great. Faster, smoother, less crashy.
[+] [-] Spooky23|13 years ago|reply
Chrome is just too much better to even bother with Safari.
[+] [-] mullingitover|13 years ago|reply
[+] [-] CaveTech|13 years ago|reply
[+] [-] mvelie|13 years ago|reply
[+] [-] pseudonym|13 years ago|reply
[+] [-] helipad|13 years ago|reply
[+] [-] jpxxx|13 years ago|reply
[+] [-] avimeir|13 years ago|reply
[+] [-] _djo_|13 years ago|reply
[+] [-] rwc|13 years ago|reply
[+] [-] e40|13 years ago|reply
[+] [-] city41|13 years ago|reply
[+] [-] nodata|13 years ago|reply
[+] [-] spleeyah|13 years ago|reply
[+] [-] mglass21|13 years ago|reply
[+] [-] namidark|13 years ago|reply
[+] [-] bangbang|13 years ago|reply
[+] [-] pooriaazimi|13 years ago|reply
[+] [-] _djo_|13 years ago|reply
[+] [-] jedberg|13 years ago|reply
[+] [-] pinko|13 years ago|reply
[+] [-] patrickod|13 years ago|reply
[+] [-] jpxxx|13 years ago|reply
Nope? OK.
[+] [-] ttunguz|13 years ago|reply
[+] [-] yew-right|13 years ago|reply