-
All replies
-
Helpful answers
-
Aug 17, 2011 10:07 AM in response to RMalayby markmal,Ditto. Same problem. But didn't start right away. I've been running Lion for about a week, but it just started today. ANNOYING!
-
Aug 17, 2011 10:10 AM in response to lhaleby coolm6n,it has being 2 hrs + since i deleted my "automatic" location in the network preference and re-created a new location. my wifi is still kicking alive...no drop connection so far.
-
Aug 17, 2011 10:33 AM in response to lhaleby tomo-st16,Was having wi-fi drop issue with my late 2009 iMac. Full wi-fi bars all the time, but connection would drop all the time. tried all the suggestions in this thread to no avail.
updated to 10.7.1, deleted preferred networks, then added my home network back on. Was online for 12+ hours and thought 10.7.1 fixed the problem. Now it has just dropped again. Same behavior: full wifi bars, but no connectivity. So frustrating! Never had any issues under Snow Leopard.
-
Aug 17, 2011 11:06 AM in response to lhaleby Darryl Mylrea,As a lifetime Windows user and a frequent (recently, more frequently with all the new Apple hardware I now own) Mac user, I started thinking to myself how Lion could be Apple's "Vista". I stumbled upon an article by someone with the same conclusion.
I think Apple needs to figure out some of these problems and get Lion working correctly, lest we all will be waiting for 10.8!
-
Aug 17, 2011 11:14 AM in response to tomo-st16by DrVenture,tomo-
When your connection drops (and you still have full WiFi bars), can you try to ping a dns address like, www.google.com? If you can ping that address, but other apps like Safari, mail etc cannot get out, then you do not have a wireless issue rather a stack issue.
If you find you have a stack issue, I would call AppleCare post haste and tell them about this experiment.
Let us know.
-
Aug 17, 2011 11:20 AM in response to DrVentureby tomo-st16,OK... good tip. I will try the next time it happens. Thank you.
-
Aug 17, 2011 12:03 PM in response to LenJC57by Doc Dougherty,If you are having a hard time getting DHCP to renew, just eliminate the problem by making a manual IP assignment to the IP that you get via DHCP. Then there is no renewal at all. See if that fixes your issue.
-
Aug 17, 2011 12:44 PM in response to lhaleby IzzyJG99,I've since downgraded to 10.6.8. AGAIN. I'm going to wait til at least 10.7.3 or hopefully some sort of "Wi-Fi Patch Kit" to come out. If the problem still occurs I'm going to just keep 10.6.8 and partition off another part of my drive to run Debian or Yellow Dog. Cause at this point I'm really sick of what Apple is pretending isn't a "big deal." They run you through all kinds of so-called "fixes" that the guy on the other line KNOWS DON'T WORK, but because of "tiered support" they have to do. As it stands now Apple is about to lose a customer of 25 years. Once this iMac is outddated (another 6 months) I'm taking my hardware requirements elsewhere.
I'm very disappointed, Apple. Very.
-
Aug 17, 2011 2:19 PM in response to LandSharkLawby haggibbor,Nicely put, Abraham.
I think frustration with Lion is running really high. People are starting to call this Apple's Vista. Yikes!
Topher Kessler states: "The updater package does not contain any Wi-Fi related updates, so it is unexpected that this behavior should change." If this is true, why in the world did Apple say .1 would fix the problem?"
Since Apple put the upgrade through the App Store in Snow Leopard, I think they should have a quick and easy downgrade to 10.6.8 available. People could stay with that until discussion boards indicate that all is clear with Lion. I don't think it will work well until 10.7.3, since the .2 upgrade is going to have so many new features designed to work with new cloud technology. Bound to be a lot more problems to sort through. Anyway, a little "downgrade to Snow Leopard" could download 10.6.8, and a "Reinstall Lion" could download and install latest Lion.
Of course, that would be an admission that something is really wrong under the hood with Lion!
-
Aug 17, 2011 2:41 PM in response to haggibborby Undercover101,I wish I could downgrade back to 10.6.8, but I don't know too much about computers thats why i bought the Mac because of its use-ability which with mac os x lion is almost impossible!! This wifi dropping makes me so paranoid while shopping online, thinking my connection is going to drop. Worst part is it always shows full bars so i'll never know if it drops while reading a web site. Apple used to fix these problems quickly, but lately they have been dropping the ball big time! I know a fix is far off. I'm switching to my crappy windows 7 netbook that has reliable wifi (a basic thing!) until one day maybe apple fixes this disaster
-
-
Aug 17, 2011 3:10 PM in response to benboyd5by markmal,@benboyd5: Unfortunately it does not fix this problem.
-
Aug 17, 2011 3:37 PM in response to lhaleby Yecc,The update 10.7.1 doesn't work with my iMac 27" late 2009! It make me angry!!! I don't know how many times I installed and reinstalled Lion!!!
< Edited by Host >
-
Aug 17, 2011 3:49 PM in response to benboyd5by Undercover101,benboyd5 wrote:
10.7.1 is out with WiFi fixes.
I have installed 10.7.1 and I am still having wifi issues. The update did not fix it.
-
Aug 17, 2011 8:45 PM in response to coolm6nby William Kucharski,coolm6n wrote:
yesterday night was the worst, the wifi crashed my imac 27" on lion (has reported to apple)
Below is a snippet of the error log:
Tue Aug 16 22:53:43 2011
Panic(CPU 1): Unresponsive processor (this CPU did not acknowledge interrupts) TLB state:0
RAX: 0x00000000ffffffff, RBX: 0x0000000000002710, RCX: 0x0000000000007000, RDX: 0xffffff807a625078
RSP: 0xffffff8080753c8c, RBP: 0xffffff8080753c90, RSI: 0x0000000000007000, RDI: 0xffffff806be5d004
R8: 0xffffff807a595408, R9: 0x0000000000000000, R10: 0x8000000000100000, R11: 0x0000000000000000
R12: 0x0000000000007000, R13: 0xffffff806be5d004, R14: 0x0000000000000003, R15: 0x0000000000000000
RFL: 0x0000000000000292, RIP: 0xffffff7f80ef5a1f, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 1), Frame : Return Address
0xffffff807a5bef50 : 0xffffff80002c783c
0xffffff807a5bef80 : 0xffffff80002c27b0
0xffffff807a5befd0 : 0xffffff80002d7bf2
0xffffff8080753c90 : 0xffffff7f80ed3bae
0xffffff8080753cf0 : 0xffffff7f80f1e006
0xffffff8080753d10 : 0xffffff7f80f1ed3c
0xffffff8080753d30 : 0xffffff7f80f1f127
0xffffff8080753da0 : 0xffffff7f80ecda3b
0xffffff8080753e20 : 0xffffff7f80ec6f5c
0xffffff8080753e60 : 0xffffff7f80ef74f3
0xffffff8080753e80 : 0xffffff7f80ec3015
0xffffff8080753ec0 : 0xffffff7f80e83936
0xffffff8080753ef0 : 0xffffff8000639536
0xffffff8080753f30 : 0xffffff80006382b0
0xffffff8080753f70 : 0xffffff8000638154
0xffffff8080753fb0 : 0xffffff8000820057
Kernel Extensions in backtrace:
com.apple.driver.AirPort.Atheros40(500.55.5)[01000ACB-C064-3F42-820F-BDE2008267 25]@0xffffff7f80e64000->0xffffff7f80fa3fff
Your machine had a processor get "stuck" in the AirPort driver.
Either this is a hardware bug or a kernel issue.
You may want to contact AppleCare and/or the Genius Bar at your local Apple Store for further diagnosis.