Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
When the hell is Apple gonna fix the Wireless problem in Leopard?!
- Thread starter Neutral Gamer
- Start date
- Sort by reaction score
remove preferred networks
For me, removing all "Preferred Networks" from System Preferences => Network => Advanced => AirPort, fixed the wireless dropouts on Leopard.
I was applying fixes one at a time, keeping notes as I went along, verifying that they did not work, until finding a solution.
Here are the details on the fixes for Leopard 10.5.2 AirPort wireless drops.
It has not been fixed for me in 10.5.4thanks apple for this product that "just works"...
For me, removing all "Preferred Networks" from System Preferences => Network => Advanced => AirPort, fixed the wireless dropouts on Leopard.
I was applying fixes one at a time, keeping notes as I went along, verifying that they did not work, until finding a solution.
Here are the details on the fixes for Leopard 10.5.2 AirPort wireless drops.
I started having the problem after I moved. Not sure why it started now considering I didn't change anything with my AirPort or MacBook, and every other devices (TiVo S3, iPhone, Airport Express for streaming music, Dell laptop) works perfect.
So I did a few things:
1. Deleted the preferred network setting for my network,
2. Deleted the network password that was stored separately in Keychain,
3. Rebooted the computer,
4. Re-entered the data.
No problems so far despite numerous times restarting, turning off, and putting my MacBook to sleep.
So I did a few things:
1. Deleted the preferred network setting for my network,
2. Deleted the network password that was stored separately in Keychain,
3. Rebooted the computer,
4. Re-entered the data.
No problems so far despite numerous times restarting, turning off, and putting my MacBook to sleep.
Has anyone changed the Channel on the Airport Extreme so that the signal does not get interfered with say, a cordless phone or something? Also, I have my own story to add:
I bought a PowerBook 1GHz 12" G4 on eBay (it's going back though) and here's what happened... I think it has this issue. Continue reading below:
I initially turned it on and things were working fine. Then I installed Leopard on it. I did a complete erase and install (since there was nothing on it anyway). Then I was at 10.5.0, so I decided to check for Updates and install any updates. I was connected to my Airport Extreme (original dome shaped one) and all was going well until I started downloading the updates. It would start and get a few MB and then it would suddenly stop and tell me that I was not connected to the internet so my updates couldn't be downloaded. So, I connected again and the same thing happened. Then I moved the computer as close to my router as possible and the same thing still happened... I couldn't stay connected. I was even using a static IP address and everything. I was frustrated, so I re-installed Tiger and sent the computer back to the eBay owner.
By the way, if anyone is interested, this isn't the sole reason I sent the computer back. Here's what else was wrong with it.
1: The battery was physically damaged (dented) and would fall out of the bottom with very little force.
2. The screen was cleaned with some sort of chemical and there's unremovable streaks all over it.
3. The screen was actually loose and the LCD pixels would ripple if you moved the computer a little... that's not normal.
4. Something was wrong with the DVD drive, CDs and DVDs would get hung up while trying to insert them. Something was preventing them from sliding in smoothly and I even think it was scratching the CD/DVD and that's not cool.
5. The computer was in pretty banged up shape, scratches, dings and even bent in some areas. As well as it seems like someone had tape stuck to the bottom at one time (probably to hold the battery in) because there was sticky residue on it.
6. The Airport issue (although now, I think it was a Leopard thing).
Here's the kicker though: My BROTHER has the SAME EXACT PowerBook G4 1GHz 12" running 10.5.3 and he has NO problems staying connected to MY Airport Extreme. Is that weird or what? Also, he's in a totally different room and I was having trouble getting it to stay connected with the router only a foot away from the eBay PowerBook.
I bought a PowerBook 1GHz 12" G4 on eBay (it's going back though) and here's what happened... I think it has this issue. Continue reading below:
I initially turned it on and things were working fine. Then I installed Leopard on it. I did a complete erase and install (since there was nothing on it anyway). Then I was at 10.5.0, so I decided to check for Updates and install any updates. I was connected to my Airport Extreme (original dome shaped one) and all was going well until I started downloading the updates. It would start and get a few MB and then it would suddenly stop and tell me that I was not connected to the internet so my updates couldn't be downloaded. So, I connected again and the same thing happened. Then I moved the computer as close to my router as possible and the same thing still happened... I couldn't stay connected. I was even using a static IP address and everything. I was frustrated, so I re-installed Tiger and sent the computer back to the eBay owner.
By the way, if anyone is interested, this isn't the sole reason I sent the computer back. Here's what else was wrong with it.
1: The battery was physically damaged (dented) and would fall out of the bottom with very little force.
2. The screen was cleaned with some sort of chemical and there's unremovable streaks all over it.
3. The screen was actually loose and the LCD pixels would ripple if you moved the computer a little... that's not normal.
4. Something was wrong with the DVD drive, CDs and DVDs would get hung up while trying to insert them. Something was preventing them from sliding in smoothly and I even think it was scratching the CD/DVD and that's not cool.
5. The computer was in pretty banged up shape, scratches, dings and even bent in some areas. As well as it seems like someone had tape stuck to the bottom at one time (probably to hold the battery in) because there was sticky residue on it.
6. The Airport issue (although now, I think it was a Leopard thing).
Here's the kicker though: My BROTHER has the SAME EXACT PowerBook G4 1GHz 12" running 10.5.3 and he has NO problems staying connected to MY Airport Extreme. Is that weird or what? Also, he's in a totally different room and I was having trouble getting it to stay connected with the router only a foot away from the eBay PowerBook.
Wireless Connection Drops after Full Sleep (Leopard)
I have a brand new iMac with Leopard 10.5.4. I have no problem with my wireless connection unless I let the computer go to full sleep (system and hard drive sleeps).
When I let the computer go to full sleep, I loose the connection. Restarting usually allows me to connect again.
With Apple's tech support, I have reset parameters and network settings. They are telling me the next step is to reinstall the system, but that may not solve the problem.
So far the only fix (work-around) is to adjust my settings so only the monitor goes to sleep.
Does anyone else have this problem? Or a solution?
PS. I don't have this problem on my older iMac running Tiger!
I have a brand new iMac with Leopard 10.5.4. I have no problem with my wireless connection unless I let the computer go to full sleep (system and hard drive sleeps).
When I let the computer go to full sleep, I loose the connection. Restarting usually allows me to connect again.
With Apple's tech support, I have reset parameters and network settings. They are telling me the next step is to reinstall the system, but that may not solve the problem.
So far the only fix (work-around) is to adjust my settings so only the monitor goes to sleep.
Does anyone else have this problem? Or a solution?
PS. I don't have this problem on my older iMac running Tiger!
Wireless Issue
Now I haven't read through this topic completely, but I am able to empathize 100%. Before I got Leopard, my wireless was just fine. I got signal all the time, it never dropped, it was as speedy as it needed to be.
Since Leopard, it's not a rare occasion for my Signal to drop down 2 bars and stop working completely. Sometimes I can turn it off and on again and it will work, sometimes I have to go to my sisters computer (running Tiger) use Aiport Admin Utility and change the channel. That way it will work for at least another day.
I'm not sure if it may have to do with our Aiport. We have a rather old Snow Aiport, maximum support is 802.11b. My family will be getting a Time Capsule soon, so that may improve things. But yeah, Leopard has killed my wi-fi.
Now I haven't read through this topic completely, but I am able to empathize 100%. Before I got Leopard, my wireless was just fine. I got signal all the time, it never dropped, it was as speedy as it needed to be.
Since Leopard, it's not a rare occasion for my Signal to drop down 2 bars and stop working completely. Sometimes I can turn it off and on again and it will work, sometimes I have to go to my sisters computer (running Tiger) use Aiport Admin Utility and change the channel. That way it will work for at least another day.
I'm not sure if it may have to do with our Aiport. We have a rather old Snow Aiport, maximum support is 802.11b. My family will be getting a Time Capsule soon, so that may improve things. But yeah, Leopard has killed my wi-fi.
I feel your pain. I had the same problem as you, and I agree it is very frustrating.
My issues were on a 2008 mac pro, but this should also work for you.
Basically your hardware is probably fine. It's 10.5.3/4 that causes the problem. I'm not sure why it only affects some people and not everyone, but I do have a solution for you.
Update to 10.5.2, then you need to open terminal and create a backup folder. If you're unfamiliar with the terminal i'll try to walk you through it.
Become a sudo user, to do this type "sudo -s" without quotes and enter your password. Then you need to create a folder to move the old wireless kext. So type "mkdir /backup". Now copy the 10.5.2 wireless kext to that folder by typing "cp -R /System/Library/Extensions/IO80211Family.kext/ /backup/IO80211Family.kext"
Now you can install 10.5.4. Once that's installed, you just need to move the old kext over that was used in 10.5.2. Gain sudo again "sudo -s", and then type "rm -R /System/Library/Extensions/IO80211Family.kext" and move over the old one by typing "mv /backup/IO80211Family.kext /System/Library/Extensions/"
Now reboot and you should have the same wireless stability you had before.
You're welcome.
PS: I know this is retarded that it has to be done, but you and I must be the only ones using wireless since I don't see many others complaining
Try this people. The guy was helpful enough to post this, and it helped me. So i'll spread the love.
my log files are just full of this:
Jul 6 21:29:30 Taps-Mac-2 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
Jul 6 21:29:32 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:29:33 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:29:36 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:30:06: --- last message repeated 6 times ---
Jul 6 21:30:07 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:30:29: --- last message repeated 6 times ---
Jul 6 21:30:29 Taps-Mac-2 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
Jul 6 21:30:31 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:30:33 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:31:03: --- last message repeated 2 times ---
Jul 6 21:31:23 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:31:28: --- last message repeated 1 time ---
Jul 6 21:31:28 Taps-Mac-2 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
Jul 6 21:31:28 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:31:28: --- last message repeated 4 times ---
Jul 6 21:31:28 Taps-Mac-2 SystemUIServer[96]: Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 26659)
Jul 6 21:31:28 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:31:30 Taps-Mac-2 SystemUIServer[96]: Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 26659)
Jul 6 21:31:32 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:31:32 Taps-Mac-2 kernel[0]: AirPort: Link Up on en1
Jul 6 21:33:28 Taps-Mac-2 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
Jul 6 21:33:29 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:33:45 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:33:58 Taps-Mac-2 SystemUIServer[96]: Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 26659)
Jul 6 21:34:01: --- last message repeated 1 time ---
Jul 6 21:34:01 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:34:01 Taps-Mac-2 kernel[0]: AirPort: Link Up on en1
i've tried to reset the airport by removing the preferred network, and removing keychain etc. i've also tried resetting the airport preferences in the system configuration folder. nothing seems to work, and as you can tell, my connection drops about every minute or so. only thing i can do is turn it off and on. so annoying
any help would be much appreciated.
Jul 6 21:29:30 Taps-Mac-2 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
Jul 6 21:29:32 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:29:33 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:29:36 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:30:06: --- last message repeated 6 times ---
Jul 6 21:30:07 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:30:29: --- last message repeated 6 times ---
Jul 6 21:30:29 Taps-Mac-2 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
Jul 6 21:30:31 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:30:33 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:31:03: --- last message repeated 2 times ---
Jul 6 21:31:23 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:31:28: --- last message repeated 1 time ---
Jul 6 21:31:28 Taps-Mac-2 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
Jul 6 21:31:28 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:31:28: --- last message repeated 4 times ---
Jul 6 21:31:28 Taps-Mac-2 SystemUIServer[96]: Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 26659)
Jul 6 21:31:28 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:31:30 Taps-Mac-2 SystemUIServer[96]: Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 26659)
Jul 6 21:31:32 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:31:32 Taps-Mac-2 kernel[0]: AirPort: Link Up on en1
Jul 6 21:33:28 Taps-Mac-2 kernel[0]: AirPort: Roam (DeAuth/DisAssoc)
Jul 6 21:33:29 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:33:45 Taps-Mac-2 kernel[0]: AirPort: Roam (Beacons Lost)
Jul 6 21:33:58 Taps-Mac-2 SystemUIServer[96]: Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 26659)
Jul 6 21:34:01: --- last message repeated 1 time ---
Jul 6 21:34:01 Taps-Mac-2 kernel[0]: MAC AUTH succeeded
Jul 6 21:34:01 Taps-Mac-2 kernel[0]: AirPort: Link Up on en1
i've tried to reset the airport by removing the preferred network, and removing keychain etc. i've also tried resetting the airport preferences in the system configuration folder. nothing seems to work, and as you can tell, my connection drops about every minute or so. only thing i can do is turn it off and on. so annoying
any help would be much appreciated.
Just updated my MBP 2.11 to 10.5.3 (had to wait for Protools to drag itself into the 21 century) and whoda thunk it...
Damn thing wouldn't stay on the network for more than a minute, signal wanders around etc...
Did as you suggested, and rebooted, logged back into the network and it's solid as a rock.
Thanks.
So my sister is having some problems with her wireless. The connection picks up fine, full bars but after a while it'll just drop. The bars will be full still but nothing will load. The fix is to turn airport off then back on. But that's annoying and shouldn't be happening in the first place. I tried it on my MB (we have same models) and same problem, so it's not just her MB.
I think the issue is some type of address is getting lost (I know practically nothing about routers and airport so forgive me.) But when everything is running fine I get this:
And when it stops working I get this:
So obviously something is going wrong. The only problem is I don't know what those numbers mean or how to fix it. I've tried deleteing all networks and passwords and deleting the .plsit file, but still it keeps dropping.
I think the issue is some type of address is getting lost (I know practically nothing about routers and airport so forgive me.) But when everything is running fine I get this:
And when it stops working I get this:
So obviously something is going wrong. The only problem is I don't know what those numbers mean or how to fix it. I've tried deleteing all networks and passwords and deleting the .plsit file, but still it keeps dropping.
For those of you with WiFi problems, especially when connecting to encrypted networks (WEP or WPA), try this:
Delete your network setup (the name of the network in advanced network settings).
Then, go to your Keychain application in your Utilities folder. Delete the password for your network.
Repair permissions.
Reboot your computer.
Reenter the information.
Worked like a charm on both my laptops plus my parents laptop.
Delete your network setup (the name of the network in advanced network settings).
Then, go to your Keychain application in your Utilities folder. Delete the password for your network.
Repair permissions.
Reboot your computer.
Reenter the information.
Worked like a charm on both my laptops plus my parents laptop.
I've now seen the same wireless problem on my MBP a few times since upgrading 10.5.4.
Jul 13 14:44:27 hostname mDNSResponder[22]: Note: Frequent transitions for interface en1 ( address removed ); network traffic reduction measures in effect
Jul 13 14:44:28 hostname airportd[1939]: Error: Apple80211Associate() failed -6
Jul 13 14:44:28 hostname airportd[1939]: Error: process_command_dict() failed
Jul 13 14:44:28 hostname SystemUIServer[111]: Error: airportd MIG failed = -6 ((null)) (port = 68811)
Things were fine on 10.5.3 ... but these errors also occurred in a new location, too. I don't know if I used 10.5.4 long enough in a location (home) that I knew well enough on 10.5.3 and before to compare. I will see ....
Jul 13 14:44:27 hostname mDNSResponder[22]: Note: Frequent transitions for interface en1 ( address removed ); network traffic reduction measures in effect
Jul 13 14:44:28 hostname airportd[1939]: Error: Apple80211Associate() failed -6
Jul 13 14:44:28 hostname airportd[1939]: Error: process_command_dict() failed
Jul 13 14:44:28 hostname SystemUIServer[111]: Error: airportd MIG failed = -6 ((null)) (port = 68811)
Things were fine on 10.5.3 ... but these errors also occurred in a new location, too. I don't know if I used 10.5.4 long enough in a location (home) that I knew well enough on 10.5.3 and before to compare. I will see ....
Does this problem show right off the bat, or does it appear later on in your mac's life, and can't you just take it into apple for a replacment (if bought with leopard)?
I've this problem since 10.5.0, all versions till and also on 10.5.4
Tried every know workaround... and nothing worked well even did a fresh install of osx, changed everything possible on the router, always the same sh*t. But ubuntu, windows and tiger works so well on the same macbook pro.. grrrrrrr
Tried every know workaround... and nothing worked well
even did a fresh install of osx, changed everything possible on the router, always the same sh*t. But ubuntu, windows and tiger works so well on the same macbook pro.. grrrrrrrSo my sister is having some problems with her wireless. The connection picks up fine, full bars but after a while it'll just drop. The bars will be full still but nothing will load. The fix is to turn airport off then back on. But that's annoying and shouldn't be happening in the first place. I tried it on my MB (we have same models) and same problem, so it's not just her MB.
I think the issue is some type of address is getting lost (I know practically nothing about routers and airport so forgive me.) But when everything is running fine I get this:
And when it stops working I get this:
So obviously something is going wrong. The only problem is I don't know what those numbers mean or how to fix it. I've tried deleteing all networks and passwords and deleting the .plsit file, but still it keeps dropping.
how do you get the detailed info like that in the airport dropdown ?
I have tried various button combos with no luck
Cheers
Im furious right now.
This problem has occured throughout the life of my macbook...2 years ago when my macbook was new...a year ago...and again now. I had this problem before leapord and after it. I've tried every solution, and I'm about to give up and just buy a Windows laptop. I need internet access (who doesnt these days??), this is a basic expectation of the machine, and ive spent countless hours trying to solve it. Go to apples macbook forum and every other thread is about this. Yet they cant solve the problem still? I bet they worked it out ages ago, and is related to hardware and just dont want to spend $millions on a recall. If it was really a software issue, why does it only occur on macbooks, and they still have not solved it 2 years later? Pathetic.
This problem has occured throughout the life of my macbook...2 years ago when my macbook was new...a year ago...and again now. I had this problem before leapord and after it. I've tried every solution, and I'm about to give up and just buy a Windows laptop. I need internet access (who doesnt these days??), this is a basic expectation of the machine, and ive spent countless hours trying to solve it. Go to apples macbook forum and every other thread is about this. Yet they cant solve the problem still? I bet they worked it out ages ago, and is related to hardware and just dont want to spend $millions on a recall. If it was really a software issue, why does it only occur on macbooks, and they still have not solved it 2 years later? Pathetic.
This is not the case. I have no encryption (because im an idiot) and am facing the problem. People dont risk your account info.
thanks I was trying to option - click on the network name and not the airport icon
learn something new every day
The problem is WEP encryption for some reason Leopard hates it. I had used the same router for 4 different Macs with no problem. My friend upgraded to 10.5 and couldn't connect. I have a laptop with 10.5 and the same thing. A solution that WORKS is to change your router setting to WPA from WEP. My laptop is very happy now. To change to WPA with my router (zoom adsl x6) had several steps. Went to the website and got the PDF of the manual. With the ethernet cable in my computer connected to the router, I opened a browser (Firefox). Enter the router address in the address field. Use the name and password the instruction mentioned. Clicked aound and changed the wireless security from WEP to WPA and gave it a new password. Clicked "Save" and "Save to flash" and reloaded the page. Turned off the router and turned it back on. Voila! When I entered the new password and WPA Leopard loved it. Why this matters to OS 10.5 is a mystery to me. I feel like posting on the Apple site but don't see how. Good luck to all.
So my sister is having some problems with her wireless. The connection picks up fine, full bars but after a while it'll just drop. The bars will be full still but nothing will load. The fix is to turn airport off then back on. But that's annoying and shouldn't be happening in the first place. I tried it on my MB (we have same models) and same problem, so it's not just her MB.
I think the issue is some type of address is getting lost (I know practically nothing about routers and airport so forgive me.) But when everything is running fine I get this:
And when it stops working I get this:
So obviously something is going wrong. The only problem is I don't know what those numbers mean or how to fix it. I've tried deleteing all networks and passwords and deleting the .plsit file, but still it keeps dropping.
Have you tried another channel - say channel 11? I'm sitting on channel 11 without too many problems right now.