Wifi Constantly Dropping in Lion

If a Retina is doing this too then Apple clearly have had no idea about the issue this last year.... Yes some tiny pockets of Apple Care do, but they aren't going to go bleating to Tim Cook about things..... What someone needs to do is email Tim's office and suggest for the good of the company that he reads every last page of this thread.

.... Furthermore, after fixing it, they then should contact every contributor here, especially the ones that say they're done with Apple, and give them a personal update, and an assurance that they will be treated as priority customers until they feel that they can trust in Apple again.

Stuff the talk of radio cross talk or interference here... Even if that is the case then the point is the hardware and software should be coping with that in exactly the same way that anything prior to Lion does. I'm totally fed up with reading the same posting time and time again saying it's probably not Apple's fault.

I continue to read this thread with abject horror. I too was tearing my hair out until I resolved my own issue, so I can't do the escalation here anymore.... Apple won't listen to someone that can't exhibit the fault anymore.

So I hope someone does email Tim.... apparantly it's quite easy as it's tcook at apple dot com

One day I hope to read that there's a fix that gets everyone back working again, and that you don't have to shell out for new hardware in doing so.

That part that will really **** you off, Try to get Apple to admit it's their software Not a hardware issue. My 2 macbooks side by side and only on does it.

Well, on a slightly unrelated but unsurprising issue I have yet to get the promised code for the Mountain Lion upgrade for my rMBP, but was desperate to try anything that may fix my WiFi issue. Bought Mountain Lion and upgraded, everything seemed fine for about an hour and lo and behold the issue has returned. Now i feel doubly screwed.

Not really sure what else there is to do.

And on the topic of it being a "hardware" issue and not a software issue, i am slightly confused....

they have selected and installed all the components in these machines. It may be a specific component is the problem, in this case the wifi chipset power, but quite frankly if apple is not responsible for the components they put into their machines that make up the total computer then who is?

fingers crossed but I have another week til i can get a full refund so hoping for a solution until then...

try enabling debugging with this command:

sudo /usr/libexec/airportd debug +alluserland +alldriver +allvendor +LogFile

I'm aware that this shouldn't make a difference, but after I did it worked fine. Before it wouldn't last 3 hours, so far it's been about 8 days.

SavMed wrote:

Well, on a slightly unrelated but unsurprising issue I have yet to get the promised code for the Mountain Lion upgrade for my rMBP, but was desperate to try anything that may fix my WiFi issue. Bought Mountain Lion and upgraded, everything seemed fine for about an hour and lo and behold the issue has returned. Now i feel doubly screwed.

Not really sure what else there is to do.

And on the topic of it being a "hardware" issue and not a software issue, i am slightly confused....

they have selected and installed all the components in these machines. It may be a specific component is the problem, in this case the wifi chipset power, but quite frankly if apple is not responsible for the components they put into their machines that make up the total computer then who is?

Apple, ultimately will have to decide how to fix this issue, clearly. But, if the people plagued by this, can find a work around, that certainly makes it easier to what for that to happen.

fingers crossed but I have another week til i can get a full refund so hoping for a solution until then...

You might be able to have some leverage with Apple, if you call them every day and assert that it's not working today, and that you have X days till you can't return it, but that is your plan if a fix can not be provided.

You might need to change wifi to forget this wifi then try setting up the wifi again that it might work!

that's been suggested multiple times and is only a temporary solution (a few days at most)

It's been already 2 days, where is the update fix for this? I'm on a 2011 MBA and I'm having this issue happen almost every time I come back to the computer after being away for more than a few minutes. There's no reason why this worked perfectly with Lion but all of a sudden it's not with Mountain Lion, it's a bug! The MBA can't even take a network cable, it's only WiFi, this is urgent!

It's actually been a year, not just 2 days... You're just suffering the "Lion" bug in a delayed reaction.

Ha....many of us have been waiting over a year for a real fix...

If it's really urgent I recomend that you go buy a USB Wi-Fi device. They are only about $15

I would downgrade to Lion before I do that, Mountain Lion is not that exciting after all. In addition to this bug, all of a sudden the scrolling on the trackpad is accelerating, iCloud Tabs are just not working, and the whole notification center thing is overrated.

DRW9 wrote:

anyone that does have issues: try enabling debugging with this command:

sudo /usr/libexec/airportd debug +alluserland +alldriver +allvendor +LogFile

or you can replace IO80211Family.kext with the one from Snow Leopard.

Lion introduced incompattiblities with certain pieces of wireless hardware. There have been a lot of theories as to what exactly is causing these incompattibilities and a lot of possible fixes you coudl try (Google it). Unfortunately, for many people (myself included), none of the fixes, nor the updates to Lion, have fixed the issue.

That said, it is likely that if you bought a new wireless router (or used a USB wireless card, instead of your built-in card) it would start working again, because you have removed the incompattible piece of hardware.

But I'm cheap, so I just downgraded back to Snow Leopard.

When I put the line in it asks for a password but it won't let me type it in.

I finally got it to turn on debugging.

Thanks