Hacker News Reader

Comment by pooriaazimi | Hacker News Reader

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.

View on HN

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.

Same here: with Lion - open lid, type in password.

Mountain Lion - open lid, push first character of password, no response? keep trying again until asterisk appears, then type rest of password.

Another vote on this. Annoying "issue".

I had the same issue on my iMac and it was really annoying. I found that un-checking the box that reads "automatically connect to networks" (or something to that order) helped fix my issue. It may work for you too!

I have this problem as well; it's my most frustrating experience with Mt. Lion so far.

Where is that? I tried Spotlight searching for "automatically" and "networks" and couldn't find it.

If you just go to Network Preferences you should see it.

I noticed a simple solution: Wait for the mouse pointer to show, then you're good to log in

I close my lid and my MBP (last of the 17" line) never sleeps. Really frustrating.

If the cause of this on your machine is the same as on mine, I know why it happens and a (fairly awkward) workaround.

My MacBook does this whenever some process runs away with all the CPU cycles, sometimes it takes ages to properly wake up and log in and sometimes it doesn't manage it at all.

The work-around is to SSH in from another machine and kill the process that's hogging the CPU. Your MacBook will spring back to life! (Assuming, as I said, that we are experiencing the same issue - I only know for sure that we are experiencing the same symptoms)

If this does prove to be the cause, if you know or suspect a process is going to use a lot of CPU, to keep the system stable and perky you can either launch it from the command-line with "nice", e.g.

$ nice ./some_beastly_script.pl

Or if the process is already running, you can "renice" it:

$ renice $PID

Both of these will give that process lower CPU priority, stopping it bogging down other things.

I've mean meaning to look into the possibility of making essential things like the screensaver / unlock / core OS bits have higher priority than anything else, I'll write it up if I figure anything out.

I'm getting the same on my new rMBP. It shipped with Mountain Lion and an SSD installed, so I expected waking up to be almost instant, but it takes at least 5+ seconds for the screen to update (battery/clock display old info) or I can input my password.

I also get a lot of graphical glitches (mostly in Safari).

Safari 6 is awful. I find that I have to close all of my tabs, quit it, and reopen at least three times a day. Never had this problem with 5.x. Also, the developer tools are so unusable for me that I've started doing my web design work in Chrome just to get a sane, tolerable HTML/CSS editing experience.

I don't understand why anyone, least of all a developer, would use Safari.

Modulo the aforementioned issues, I think that the user experience is far superior to Chrome. Here are a couple examples:

    * iOS-like pinch/zoom
    * Quick access to bookmark bar bookmarks with Cmd-[0-9]
    * iCloud tabs (w/ Mobile Safari)
    * Reader
    * Better feedback on page back/forward gestures

* Chrome has that.

* I don't really see the usefulness. I prefer Cmd-[0-9] for tab access.

* Chrome syncs between my three computers, phone, tablet. It's not just bookmarks. It's everything

* Doesn't Safari not have a reader anymore?

* I guess it's a matter of preference but I get a nice arrow indicator for page forward and backward. The Safari effect is a bit much in my opinion.

I like Cmd-[0-9] to map to my bookmarks, I like Safari Reader, I like iOS-like zoom (chrome only fakes it, and does so not very well), I like the rendered text on Safari a million times better (it's not anti-aliased on Chrome on most pages - at least that's the miserable state Chrome was till v19 I think), I like iCloud tabs and I like Safari's UI much better.

That's why I use Safari. I couldn't possibly live with Chrome even if Safari was worse that it - I absolutely hate the stupid download bar, or "Downloads/Preferences" not being standard windows but silly webpages. And don't get me started on custom contextual menus Chrome team thought were cooler than standard OS X menus (even if they were cooler, they're at least 5 times slower. So what's the point of them?)

That said, it all comes down to what your personal preferences are. The difference between browsers are not huge. Some like Safari, some like Chrome, and some like Lynx.

Most of your complaints are flatly wrong. And some of them were never even accurate.

Just because you disagree with his opinion doesn't mean he is wrong.

No, several of the things he listed are literally lies or misconceptions or are factually wrong.

I don't know why he prefers the things he does, but I don't dispute that he may well feel that way, nor do I care that he does.

    * Chrome changes the font size; it doesn't zoom the page. At least in v22.
    * I don't see the usefulness in tab access. To each their own.
    * Chrome on iOS doesn't have access to Nitro.
    * Come again? Reader is the Safari feature adapted from Arc90's Readability bookmarklet.
    * Right.

I've got this too. And strange problems with the Finder/Dock. Stuff like clicking a folder or the trash can not opening it, not being able to empty the trash, and programs that are running not showing up in the cmd-tab switcher. No show stoppers like the WiFi bug, but it's still disappointing.

Strange- this issue dates back to at least snow leopard for me. I remember thinking it was tied to my setting the screen saver to lock the screen/slow disk. I live with it but would love to see it fixed.

For me this is a new MBP with an SSD. With Lion I could open the lid, immediately type in my password, and be back on wifi instantly. It was probably my favorite thing about the machine. Now waking up has become rather frustrating. I'm considering going back to Lion until this is fixed.

You have to press (not just tap) the touchpad. It will wake up much faster.

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.

Try turning off your bluetooth. I had the same issues with wifi reconnect after sleep and they went away after turning off bluetooth on the laptop.

I have bluetooth off on my Air and it still has this wifi issue. Its some race condition because it doesn't happen all the time and for it only happens when waking up from a deep sleep(ram persisted to disk).

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.

That matches my experience, too. I had dropping problems when I got my MBA (mid-2011) and it magically fixed itself sometime after Lion shipped. I have no problems now.

It was a major disappointment for me at the time as after years with Linux I bought a Mac exactly because I wanted to focus on my work and not on solving fringe kernel issues. Luckily, no major problems since then.

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...

[1] http://support.apple.com/kb/HT3964

Have you tried:

"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

Yes, but no luck...

I thought I was alone with this.

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.

Are you on Mountain Lion? I couldn't use Mail.app on Lion as it was incredibly slow. The I realized it wasn't Mail.app's fault, but GPGMail's, and now that GPGMail has stopped working in ML my Mail.app feels as snappy as ever.

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.

"Fix permissions using the Disk Utility"

I bet people will continue to give this suggestion as an attempted fix to random problems long after all memory of what it was actually for will be lost (i.e. classic environment screwing with HFS+ extensions introduced by OS X).

To be fair, munged permissions are a real problem; Just the other day, Parallels released an advisory document[1] about an issue their users had been seeing related directly to filesystem permissions.

I believe that "fix permissions" scans the installed package receipts and corrects the file permissions where necessary. In a world where any errant package install can mangle modes and ownership, fix permissions will not go derelict.

What it's actually for is the fixing of mangled permissions.

[1]: http://kb.parallels.com/en/113749

I still hear "did you reset your PRAM?" from people occasionally. Good times.

Is there a reason that you have to open/ close instead of just giving airport a kick in the pants?

Turning Airport off and on doesn't seem to fix the problem for me, so I have to close the lid. My father's MacBook on the other hand only gets fixed when you turn off/on the Airport from the menu bar.

What version of the MBP is this? I have a 2009 MacBook Pro 13", and two 2007 MacBook Pro 15" and I haven't had any issues at all with Wifi.

2009 15" MBP and 2010 13" MacBook (white).

My MBA 2011 will still not wake up from sleep. Need to hard shutdown it every time. :(

No warranty left? I would return it with such problems.

no issues here with 13" 2009 MBP.

7" - maybe you should invest in an ethernet cable...

Reply on news.ycombinator.com