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
It was fixed in 10.5.3-4, I thought this thread was dead, some good hints too, have you read this thread from the first five pages or so? what are your issues regarding wireless connectivity?
10.5.8 hasn't fixed my wireless problem. But I might be having different issues than those discussed in this thread.
If I close the lid on my MacBook, when I open it again I lose my Internet connection. Network settings then says I have a self-assigned IP address. This started happening out of the blue one day. And it will sometimes (but not often) just go into that mode right when I'm using the computer, which means I lose my Internet connection and have to reboot right in the middle of my work.
Well, actually, I have to turn off Airport, then reboot, then turn Airport back on to snap it out of this mode. I discovered this by accident, I don't know if it makes sense or not. I have an AEBS that has worked pretty well since I bought it. My 3 iPhones have no problems using it, never lose their connections. My Apple TV sometimes loses its connection, or just locks up because I looked at it -- it's just flakey
Anyway, I had hoped that 10.5.8 would help, or even fix the problem, but there is no change. I am not sure what to do anymore but I have definitely started disliking my MacBook
I hear what you are saying and these are all issues discussed in this thread, Im actually surprised that even up to this date you are still experiencing some of these issues, the updates helped somewhat but the following hints here helped a lot of folk.
Hints: create a new location is system prefs. avoid naming it "Automatic" set Airport to the top of the list by accessing the gear wheel at the bottom of the source list. In the network pane deselect "Ask to join new networks" in the advanced section select "Disconnect from wireless when logging out" only and nothing else, within the same pane your network should be the only network listed.
if this does not work go to the next level hints:
in user>library>preferences delete the systempreferences.plist file and the systemuiserver.plist file, in HD>library>preferences delete the following files:
DirectoryService, System Configuration, in Keychain app. in the Utilities folder delete the keychain related to your network. restart and configure your network. Make sure to input the proper information in the DNS section of the network pane such as any DNS numbers that your router provides.
please try to peruse through the hints in this thread they are very informative, if this does not work I suggest you take it to the Apple store, it could be hardware issue regarding the actual Airport card or they may be able to diagnose it deeper.
Hints: create a new location is system prefs. avoid naming it "Automatic" set Airport to the top of the list by accessing the gear wheel at the bottom of the source list. In the network pane deselect "Ask to join new networks" in the advanced section select "Disconnect from wireless when logging out" only and nothing else, within the same pane your network should be the only network listed.
if this does not work go to the next level hints:
in user>library>preferences delete the systempreferences.plist file and the systemuiserver.plist file, in HD>library>preferences delete the following files:
DirectoryService, System Configuration, in Keychain app. in the Utilities folder delete the keychain related to your network. restart and configure your network. Make sure to input the proper information in the DNS section of the network pane such as any DNS numbers that your router provides.
please try to peruse through the hints in this thread they are very informative, if this does not work I suggest you take it to the Apple store, it could be hardware issue regarding the actual Airport card or they may be able to diagnose it deeper.
Thanks Mlobo01 for the helpful reply. Was out of town for a few days, finally back to looking into this again. By the way, overnight my MacBook went into its "self-assigned IP" mode and lost Internet connection. Had to do the usual turn-off-airport-restart-turn-on-airport sequence to get it straightened out.
Well, after skimming through all the pages and attempts people have made, it seems most of it is just guesswork. No one seems to know exactly what causes this, or what to do about it. It's just like being back on Windows. So I am on the verge of deciding to go one of two ways: 1) reinstall OS X from scratch and see if it magically works correctly again, or 2) go back to Windows for real (which I use at work). Actually, I guess I'd do #1 first, then #2 if there are any signs at all of continued problems.
The funny part is that reinstalling Windows is the standard recommendation when no one can seem to figure out why "it just won't work". I really never expected that switching to Mac would bring me to the same situation.
Part of my reason for thinking about reinstalling OS X is that it has gone unstable in other ways too. Very often it cannot shut down properly, just sits there beach balling on me for 5-10 minutes (if I am patience enough to wait that long). And since I have to restart almost daily to get around the "self-assigned IP address" problem, it is extremely aggravating.
OK, I admit I am frustrated and unhappy. I should go to an Apple store first of all and see if they can do anything. Or is it worthwhile to contact Apple support (where and how?) with something so vague?
Well, after skimming through all the pages and attempts people have made, it seems most of it is just guesswork. No one seems to know exactly what causes this, or what to do about it. It's just like being back on Windows. So I am on the verge of deciding to go one of two ways: 1) reinstall OS X from scratch and see if it magically works correctly again, or 2) go back to Windows for real (which I use at work). Actually, I guess I'd do #1 first, then #2 if there are any signs at all of continued problems.
The funny part is that reinstalling Windows is the standard recommendation when no one can seem to figure out why "it just won't work". I really never expected that switching to Mac would bring me to the same situation.
Part of my reason for thinking about reinstalling OS X is that it has gone unstable in other ways too. Very often it cannot shut down properly, just sits there beach balling on me for 5-10 minutes (if I am patience enough to wait that long). And since I have to restart almost daily to get around the "self-assigned IP address" problem, it is extremely aggravating.
OK, I admit I am frustrated and unhappy. I should go to an Apple store first of all and see if they can do anything. Or is it worthwhile to contact Apple support (where and how?) with something so vague?
I can relate to you well...
The reason this thread is so long its because as you mentioned, some hints worked for some, others did not, but our frustration (I think) came from just upgrading into Leopard from an already-stable Tiger platform, it took at least until 10.5.5 for this wireless issue to start winding down and on occasion someone would start the thread again, We observed that the main culprit would be corrupt keychains and corrupt caches left over from the upgrade from Tiger.
I can relate a lot so you are not alone in this struggle, this iteration of OS X has put us to the ultimate test of troubleshooting but Im a stubborn mule and I like searching and trying out all the hints, its always been part of the OS X community. On the Apple forums I wrote extensively as well and I even had some posts removed because I linked this thread and maybe they did not like that the wireless issue was a prevalent one and I was making folks aware of it and some posters shared that when they called customer service Apple did not readily admit to the issue, they will always recommend a clean install, (back-up everything and erase and install) but in these forums the key is to pinpoint and fix issues ourselves as long as it does not damage your computer and you are aware of what you are doing.
Im a mac fan though and through but Im also practical, so if you feel that going back to Windows will get your productivity up then I suggest you do it because on occasion I have given up myself. If this is starting to affect your work and state of ease then let it be and use Windows or any system that is stable enough, because countless other have done it and it has happen to people who get a bad experience and go back, like any product its should not reflect anything negative about you just be practical and detached. One other hint I can recommend is to try and make a new account to see if its a corrupt account or set-up the root user account and make a new account from there. Some other people experienced a loose wireless card wire when they went to Apple so your issue can be that as well. but feel free to post any question Ill be happy to answer.
The reason this thread is so long its because as you mentioned, some hints worked for some, others did not, but our frustration (I think) came from just upgrading into Leopard from an already-stable Tiger platform, it took at least until 10.5.5 for this wireless issue to start winding down and on occasion someone would start the thread again, We observed that the main culprit would be corrupt keychains and corrupt caches left over from the upgrade from Tiger.
I can relate a lot so you are not alone in this struggle, this iteration of OS X has put us to the ultimate test of troubleshooting but Im a stubborn mule and I like searching and trying out all the hints, its always been part of the OS X community. On the Apple forums I wrote extensively as well and I even had some posts removed because I linked this thread and maybe they did not like that the wireless issue was a prevalent one and I was making folks aware of it and some posters shared that when they called customer service Apple did not readily admit to the issue, they will always recommend a clean install, (back-up everything and erase and install) but in these forums the key is to pinpoint and fix issues ourselves as long as it does not damage your computer and you are aware of what you are doing.
Im a mac fan though and through but Im also practical, so if you feel that going back to Windows will get your productivity up then I suggest you do it because on occasion I have given up myself. If this is starting to affect your work and state of ease then let it be and use Windows or any system that is stable enough, because countless other have done it and it has happen to people who get a bad experience and go back, like any product its should not reflect anything negative about you just be practical and detached. One other hint I can recommend is to try and make a new account to see if its a corrupt account or set-up the root user account and make a new account from there. Some other people experienced a loose wireless card wire when they went to Apple so your issue can be that as well. but feel free to post any question Ill be happy to answer.
one more thing...
When I was searching through the Apple forums I did notice that some where experiencing bad connections or system slowdowns caused by bad RAM, if you purchased RAM with a third party vendor then it could be a bad chip, if you have two chips installed see if by removing one or the other the system gets better, also see if the RAM chips are properly installed it could be that they may be off on one side or loose.
When I was searching through the Apple forums I did notice that some where experiencing bad connections or system slowdowns caused by bad RAM, if you purchased RAM with a third party vendor then it could be a bad chip, if you have two chips installed see if by removing one or the other the system gets better, also see if the RAM chips are properly installed it could be that they may be off on one side or loose.
I have got the most mystic/annoying WiFi problem, when I run on battery my AirPort starts to become unstable, slow and iTunes can no longer find my AirTunes speakers... This is not because I leave coverage, because it will happen sitting at my desk if someone loans my power plug... It is just so random!!!
It started after I installed the 1.5.8 update - before that I had no WiFi problems...
Anyone know how I can "downgrade"? Or would that require me to do a clean install??
EDIT:
I found this solution: http://blog.hep-cat.de/?p=4760#Mac
I haven't tried it yet, but I think I'm going for it when I have a done a complete back up...
It started after I installed the 1.5.8 update - before that I had no WiFi problems...
Anyone know how I can "downgrade"? Or would that require me to do a clean install??
EDIT:
I found this solution: http://blog.hep-cat.de/?p=4760#Mac
I haven't tried it yet, but I think I'm going for it when I have a done a complete back up...
thanks W.Zoo
I think we touched on that subject here and on another thread, this is what I would like Harry to know that we in the Macrumors community post good solutions or at least we lead you to a possible solution, I hope you find the solution to the issue, meanwhile if I find something or remember another hint I'll post it.
I think we touched on that subject here and on another thread, this is what I would like Harry to know that we in the Macrumors community post good solutions or at least we lead you to a possible solution, I hope you find the solution to the issue, meanwhile if I find something or remember another hint I'll post it.
I found an old Macfixit link related to networking issues...
One of the most successful workarounds for this issue involves deleting networks and AirPort keychains then re-establishing them, as described here and in our tutorial "Improving AirPort reception, avoiding dropouts/lost connectivity, working around card/Base station recognition issues."
Now some users have reported that deleting the following file:
/Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist
can resolve the issue.
MacFixIt reader Matthew Powell writes:
"I updated my Mac Mini Core Duo from 10.4.6 to 10.4.7 and had an AirPort problem. After a reboot, the machine appeared to associate to the access point, but didn't get a DHCP address. The interface got a self-assigned address instead. The 'Renew DHCP Address' button had no effect.
link:http://www.macfixit.com/article.php?story=2005093011343164
One of the most successful workarounds for this issue involves deleting networks and AirPort keychains then re-establishing them, as described here and in our tutorial "Improving AirPort reception, avoiding dropouts/lost connectivity, working around card/Base station recognition issues."
Now some users have reported that deleting the following file:
/Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist
can resolve the issue.
MacFixIt reader Matthew Powell writes:
"I updated my Mac Mini Core Duo from 10.4.6 to 10.4.7 and had an AirPort problem. After a reboot, the machine appeared to associate to the access point, but didn't get a DHCP address. The interface got a self-assigned address instead. The 'Renew DHCP Address' button had no effect.
link:http://www.macfixit.com/article.php?story=2005093011343164
You all have shoddy routers then. I've had 4 Mac notebooks and none of them had ANY network problems. One laptop was stolen, one was my Dad's work laptop, and the rest are mine. Along the way, I've had over 5 routers. Linksys, Airport, Netgear, another Linksys, and another Netgear. Everything works fine. Either the Airport card was defective, you have defective routers or both.
I was having the same problem. I did an Archive and Install to Leopard and then updated to 10.5.7. So far no such problems occurred on 5.7, but on 5.8 that's when Airport started acting up. I suggest you do the same and wait till Apple come up with some kind of solution.
in the Apple forums...
In the apple forums I found the same general feeling which is to let Apple come out with an update or a fix to their issue, some people found it difficult and/or had a lot of genuine resistance to the hints process, some where legitimately outraged about buying a 2K+ item and you still had to do some personal tweaking to their systems, I can relate to this entirely and some even compared it to buying other merchandise such as cars:"if you buy a car and it does not work then take it back to the dealer..." except that with software related matter it is different and many more unexpected things DO happen, some folks you could tell where not as curious about their systems, I really do not want to mention what age they where or what type of tech-inclinations they had but some simply took a resentment to the hints and staunchly refused until "Apple comes up with the fix" most people are too young to remember that the beginnings of computing where marred with issues and that it was fun if you came up with solutions, it was a heart-felt activity, most of our advances have yielded some good techno-nuggets due to people tweaking themselves to sleep back then, Im not saying everyone should do this its just that at times you need to get under that hood and at least check the wires, because if you wait for the mechanic to call you regarding a minute detail that can render your system working again then you will be waiting a long time, or you may be waiting forever, we are up to 10.5.8 I did not hear anything regarding wireless issues for at least 4 updates, some applied the fixes understood them and Im sure that once in a while it creeps up again and the hints are re-applied and you get the fix yet again, self-sufficiency! what a blessing. My suggestion is that if you have 10 minutes or so try the hints please, its worth it, there are a lot of them here, if not try the clean install, thats why people emphasize the back-ups so you are not worried about loosing your stuff, I have done them once in a while and kept my productivity up, its part of the computing process, make it fun.
And as Harry said there's always going back to Windows which is a legitimate solution as well, in the Apple forums I stated that a computer engineer needs to do an update that will be coalescent with a myriad of computer systems and yours may be the one its not compatible with, its tough but you may have many solutions at your calling:Apple customer service, a Genius at the store, macfrumors forums, macfixit forums, macosxhints.com. the Apple discussions forums, and the least tasty of them (for me) is to revert back to Windows so think about it and you may decide.
In the apple forums I found the same general feeling which is to let Apple come out with an update or a fix to their issue, some people found it difficult and/or had a lot of genuine resistance to the hints process, some where legitimately outraged about buying a 2K+ item and you still had to do some personal tweaking to their systems, I can relate to this entirely and some even compared it to buying other merchandise such as cars:"if you buy a car and it does not work then take it back to the dealer..." except that with software related matter it is different and many more unexpected things DO happen, some folks you could tell where not as curious about their systems, I really do not want to mention what age they where or what type of tech-inclinations they had but some simply took a resentment to the hints and staunchly refused until "Apple comes up with the fix" most people are too young to remember that the beginnings of computing where marred with issues and that it was fun if you came up with solutions, it was a heart-felt activity, most of our advances have yielded some good techno-nuggets due to people tweaking themselves to sleep back then, Im not saying everyone should do this its just that at times you need to get under that hood and at least check the wires, because if you wait for the mechanic to call you regarding a minute detail that can render your system working again then you will be waiting a long time, or you may be waiting forever, we are up to 10.5.8 I did not hear anything regarding wireless issues for at least 4 updates, some applied the fixes understood them and Im sure that once in a while it creeps up again and the hints are re-applied and you get the fix yet again, self-sufficiency! what a blessing. My suggestion is that if you have 10 minutes or so try the hints please, its worth it, there are a lot of them here, if not try the clean install, thats why people emphasize the back-ups so you are not worried about loosing your stuff, I have done them once in a while and kept my productivity up, its part of the computing process, make it fun.
And as Harry said there's always going back to Windows which is a legitimate solution as well, in the Apple forums I stated that a computer engineer needs to do an update that will be coalescent with a myriad of computer systems and yours may be the one its not compatible with, its tough but you may have many solutions at your calling:Apple customer service, a Genius at the store, macfrumors forums, macfixit forums, macosxhints.com. the Apple discussions forums, and the least tasty of them (for me) is to revert back to Windows so think about it and you may decide.
I had the wireless issue with 10.5.8
I had the wireless issue with 10.5.8, I could not believe it, I thought we had beat this thing, so I went back and re-applied the hints that I posted and needless to say Im back with out a hitch, My fix to my system:delete the Location in the Network pane, I only use the wireless connection so I delete everything in the source list except for the Airport connection, delete the keychain related to my network in Keychain and restart by doing a PRAM zap.
If you feel that your system is stable in 10.5.7 or any iteration then leave it alone, I wrote in the Apple forums that we needed to perform an intelligent method of upgrading to new versions by having an external drive that has a current version and testing it out on that then if its "safe" then do it on your general system, I have a small external firewire drive that always gets the update until I feel its not-too-bad nor disruptive. Im currently testing Snow Leopard on another external drive and Im glad to tell you guys its becoming stable, but I would not do it on my general system because I really do not want to take that chance, its a simple idea but it has save me many aggravations.
I had the wireless issue with 10.5.8, I could not believe it, I thought we had beat this thing, so I went back and re-applied the hints that I posted and needless to say Im back with out a hitch, My fix to my system:delete the Location in the Network pane, I only use the wireless connection so I delete everything in the source list except for the Airport connection, delete the keychain related to my network in Keychain and restart by doing a PRAM zap.
If you feel that your system is stable in 10.5.7 or any iteration then leave it alone, I wrote in the Apple forums that we needed to perform an intelligent method of upgrading to new versions by having an external drive that has a current version and testing it out on that then if its "safe" then do it on your general system, I have a small external firewire drive that always gets the update until I feel its not-too-bad nor disruptive. Im currently testing Snow Leopard on another external drive and Im glad to tell you guys its becoming stable, but I would not do it on my general system because I really do not want to take that chance, its a simple idea but it has save me many aggravations.
Been chasing this crap all over the internet for 3 days
Suddenly a few days ago lost my connection and had a 'self-assigned IP' on my home router, but not on other networks i use.
tried a good number of the fixes on this thread, but couldn't get anything to stick.
finally today, I found that for some reason, the variable is my power cable. my airport works with this particular modem only when plugged into the wall.
Macbook Pro
Early 2008
2.4gHz
Suddenly a few days ago lost my connection and had a 'self-assigned IP' on my home router, but not on other networks i use.
tried a good number of the fixes on this thread, but couldn't get anything to stick.
finally today, I found that for some reason, the variable is my power cable. my airport works with this particular modem only when plugged into the wall.
Macbook Pro
Early 2008
2.4gHz
Still having trouble here (been too busy with work to have time for this lately)
I deleted some of the plist files, such as com.airport.preferences & NetworkInterfaces. Ran Keychain First Aid and indeed it found a problem which I had it repair. And I did the PRAM reset thing (but how do you know if you did it right or that it worked?) Anyway, was feeling pretty hopeful but alas today the behavior is the same. "Self-assigned IP Address", no Internet connection when I opened the lid this morning, and I had to reboot and all that.
Then I saw a mention of deleting the location in the Network pane. Just tried it: first added a new one, "Home", then deleted "Automatic", and System Preferences crashed! (err, no wait, we say "quit unexpectedly" right?
I relaunched it and my changes hadn't taken effect. Maybe I'll try them one step at a time, and relaunch it between each step.
By the way, I may have mentioned this already, but my 3 iPhones all work perfectly well on this Airport Extreme Base Station. And when I boot Windows XP through BootCamp (for my work), it has never had a problem using the AEBS. So I conclude the error is somewhere in the software on this MacBook. That's why I mentioned reinstalling OS X when I jumped in to this thread (I know, it's the standard Windows user's response, but I honestly never expected to have such persistent unsolvable problems on a Mac when I switched). But with Snow Leopard just around the corner I am wondering if it would be better to wait for that and try a complete OS wipe and reinstall on this machine.
Oh, almost forgot one thing (sorry this has gotten long...) Whenever it goes into self-assigned IP address mode and I have to turn off airport and then restart the machine, when I then turn on airport again I always get a pop-up asking if I should grant network access to "configd". It never does this until I am correcting the self-assigned IP mode, and does it every time. Never seems to remember the setting however (but I don't know if it should or what)
I deleted some of the plist files, such as com.airport.preferences & NetworkInterfaces. Ran Keychain First Aid and indeed it found a problem which I had it repair. And I did the PRAM reset thing (but how do you know if you did it right or that it worked?) Anyway, was feeling pretty hopeful but alas today the behavior is the same. "Self-assigned IP Address", no Internet connection when I opened the lid this morning, and I had to reboot and all that.
Then I saw a mention of deleting the location in the Network pane. Just tried it: first added a new one, "Home", then deleted "Automatic", and System Preferences crashed! (err, no wait, we say "quit unexpectedly" right?
I relaunched it and my changes hadn't taken effect. Maybe I'll try them one step at a time, and relaunch it between each step.
By the way, I may have mentioned this already, but my 3 iPhones all work perfectly well on this Airport Extreme Base Station. And when I boot Windows XP through BootCamp (for my work), it has never had a problem using the AEBS. So I conclude the error is somewhere in the software on this MacBook. That's why I mentioned reinstalling OS X when I jumped in to this thread (I know, it's the standard Windows user's response, but I honestly never expected to have such persistent unsolvable problems on a Mac when I switched). But with Snow Leopard just around the corner I am wondering if it would be better to wait for that and try a complete OS wipe and reinstall on this machine.
Oh, almost forgot one thing (sorry this has gotten long...) Whenever it goes into self-assigned IP address mode and I have to turn off airport and then restart the machine, when I then turn on airport again I always get a pop-up asking if I should grant network access to "configd". It never does this until I am correcting the self-assigned IP mode, and does it every time. Never seems to remember the setting however (but I don't know if it should or what)
I really think these problems must relate to either hardware, or some settings in your system.
I have 2 AESB, the old round one it 801.11g, the older 801.11n and an express, I have never had problems with 2 MacBooks, 2 MBP, 2 imacs, 1 Mac mini, 3 iPhones.
however my buddy had problems with his dlink dl-524, would not assign ip, unless we switched off WPA, WPA2, WEP etc, then it worked fine. to solve the problem we got a linksys 801.11n and all runs fine.
I would suggest trying running the network with not security, just hide the SSID, and see if you have the same problems (This is not a fix just a test todo).
I have 2 AESB, the old round one it 801.11g, the older 801.11n and an express, I have never had problems with 2 MacBooks, 2 MBP, 2 imacs, 1 Mac mini, 3 iPhones.
however my buddy had problems with his dlink dl-524, would not assign ip, unless we switched off WPA, WPA2, WEP etc, then it worked fine. to solve the problem we got a linksys 801.11n and all runs fine.
I would suggest trying running the network with not security, just hide the SSID, and see if you have the same problems (This is not a fix just a test todo).
I found the following article on MacFixit:
MacBooks affected by Airport bug not able to install Airport Client Update 1.0
Written by Topher Kessler
Some people who had Airport problems after upgrading to 10.5.8 may not be able to install the patch Apple released today, especially if they have modified their system with various workarounds to get Airport working again.
When we posted our workaround for the problem, we specifically mentioned to back up the current kernel extensions before replacing them with old versions that were more stable. Before applying the current patch from Apple, be sure to revert the workaround and copy the replaced extensions back to the Extensions folder. After this is done, restart the computer and try running the installer again.
A second option is to download the AirPort Client Update installer manually and use Pacifist to extract the kernel extension replacement from it. This should only be done if you are sure your system is one of the ones mentioned in Apple's documentation for the update. These include the following:
MacBook (13-inch, Late 2007)
MacBook (13-inch, Early 2008)
MacBook (13-inch, Late 2008)
MacBook Pro (15-inch, Early 2008)
MacBook Pro (17-inch, Early 2008)
MacBook Pro (17-inch, Late 2008)
To revert workarounds and install the update manually, be sure to copy back the most recent version of the "AppleAirPort.kext" extension that we mentioned to replace in the workaround (this apparently was not involved in the problem, and a replacement is not included in Apple's update). After this, use Pacifist to open the installer file and navigate to the kernel extension provided there. Then either extract it or install it to the /System/Library/Extensions/ folder, replacing any current extension you may have there. You can then load it into the extensions caches by running the following commands in the Terminal:
mv /System/Library/Extensions.mkext ~/.Trash
kextload -t /System/Library/Extensions/IO80211Family.kext
kextcache -k /System/Library/Extensions
WARNING: After running the "kextload" command, if there are any errors do not continue, and remove the new kernel extension (replacing it with an older version). This command will test the kernel extension for dependencies and if some are not met, you may destabilize your system if you continue.
After these commands are run, restart your system to load the kernel extension.
A final option is to download and apply the latest "Combo" updater for 10.5.8, which should refresh the Airport extensions. After this is done, run the Airport client update again.
Questions? Comments? Send us feedback: http://www.macfixit.com/contact
MacBooks affected by Airport bug not able to install Airport Client Update 1.0
Written by Topher Kessler
Some people who had Airport problems after upgrading to 10.5.8 may not be able to install the patch Apple released today, especially if they have modified their system with various workarounds to get Airport working again.
When we posted our workaround for the problem, we specifically mentioned to back up the current kernel extensions before replacing them with old versions that were more stable. Before applying the current patch from Apple, be sure to revert the workaround and copy the replaced extensions back to the Extensions folder. After this is done, restart the computer and try running the installer again.
A second option is to download the AirPort Client Update installer manually and use Pacifist to extract the kernel extension replacement from it. This should only be done if you are sure your system is one of the ones mentioned in Apple's documentation for the update. These include the following:
MacBook (13-inch, Late 2007)
MacBook (13-inch, Early 2008)
MacBook (13-inch, Late 2008)
MacBook Pro (15-inch, Early 2008)
MacBook Pro (17-inch, Early 2008)
MacBook Pro (17-inch, Late 2008)
To revert workarounds and install the update manually, be sure to copy back the most recent version of the "AppleAirPort.kext" extension that we mentioned to replace in the workaround (this apparently was not involved in the problem, and a replacement is not included in Apple's update). After this, use Pacifist to open the installer file and navigate to the kernel extension provided there. Then either extract it or install it to the /System/Library/Extensions/ folder, replacing any current extension you may have there. You can then load it into the extensions caches by running the following commands in the Terminal:
mv /System/Library/Extensions.mkext ~/.Trash
kextload -t /System/Library/Extensions/IO80211Family.kext
kextcache -k /System/Library/Extensions
WARNING: After running the "kextload" command, if there are any errors do not continue, and remove the new kernel extension (replacing it with an older version). This command will test the kernel extension for dependencies and if some are not met, you may destabilize your system if you continue.
After these commands are run, restart your system to load the kernel extension.
A final option is to download and apply the latest "Combo" updater for 10.5.8, which should refresh the Airport extensions. After this is done, run the Airport client update again.
Questions? Comments? Send us feedback: http://www.macfixit.com/contact
THANKS!
Finally fixed the problems (famous last words) with a bit of tweeking and trying a few of the newer things
(i was heavily involved in this thread a year ago and now have 48 posts in the thread - 2nd highest )
fingers crossed this might have done it.
Finally fixed the problems (famous last words) with a bit of tweeking and trying a few of the newer things
(i was heavily involved in this thread a year ago and now have 48 posts in the thread - 2nd highest
)fingers crossed this might have done it.
I see this thread is still alive, so I thought I'd add my update:
I reformatted my disc and did a clean install of Snow Leopard. That solved my wireless issues -- haven't had any problems since then.
Well, no problems with the wifi, I should say. I did have a few upgrade pains, not unexpected and nothing that I would complain about here. And I even got a real, live "You need to restart your computer" crash. AWESOME!
So, I am happy that the wifi is working, and happy with Snow Leopard.
I reformatted my disc and did a clean install of Snow Leopard. That solved my wireless issues -- haven't had any problems since then.
Well, no problems with the wifi, I should say. I did have a few upgrade pains, not unexpected and nothing that I would complain about here. And I even got a real, live "You need to restart your computer" crash. AWESOME!
So, I am happy that the wifi is working, and happy with Snow Leopard.
well yet again it's failed, but i really have narrowed down the cause now.
I use a mac pro and i think it's a combination of a thick aluminium enclosure, thick walls and a weaker (but still perfectly good) router.
I've moved upstairs and am now hard wired to the router and obviously have a perfect connection. Also my Airport signal strength (transmit rate) is at a solid 54 and am getting full signal.
So thats it. No wireless for me in this house. It's not a huge issue it's sunlight where i'm working now anyway!
Im not saying leopard is not to blame in someway with all this but i think it's more a case of thick walls and thick aluminium in my case.
good luck all!
I use a mac pro and i think it's a combination of a thick aluminium enclosure, thick walls and a weaker (but still perfectly good) router.
I've moved upstairs and am now hard wired to the router and obviously have a perfect connection. Also my Airport signal strength (transmit rate) is at a solid 54 and am getting full signal.
So thats it. No wireless for me in this house. It's not a huge issue it's sunlight where i'm working now anyway!
Im not saying leopard is not to blame in someway with all this but i think it's more a case of thick walls and thick aluminium in my case.
good luck all!
I was having this problem up until yesterday when someone from Apple support really helped me out. I thought I should share what was going on with me.
First, he had me boot from the SL install disk and try to connect to my network. Then he had me ping my router from the network utility. Since that worked he deduced that the problem was related to some sort of conflict between something on my machine and SL. If it had not worked he would have deduced that the problem was with firmware on my router.
So given that it was software for me, he had me send in my system log to Apple. He looked at it and had me delete a few entries under System Preferences -> Accounts -> Login Items. The main one he was concerned with was a Real Player Downloader, he had me keep the iTunes helper and the Logitech drivers that I use for my bluetooth mouse. I rebooted and have been online since then.
Hope this helps someone else. I had tried everything else and this was my third call to Apple. I honestly was preparing to revert to Leopard. Good luck!
First, he had me boot from the SL install disk and try to connect to my network. Then he had me ping my router from the network utility. Since that worked he deduced that the problem was related to some sort of conflict between something on my machine and SL. If it had not worked he would have deduced that the problem was with firmware on my router.
So given that it was software for me, he had me send in my system log to Apple. He looked at it and had me delete a few entries under System Preferences -> Accounts -> Login Items. The main one he was concerned with was a Real Player Downloader, he had me keep the iTunes helper and the Logitech drivers that I use for my bluetooth mouse. I rebooted and have been online since then.
Hope this helps someone else. I had tried everything else and this was my third call to Apple. I honestly was preparing to revert to Leopard. Good luck!
leopard wireless trouble
i just got a new macbook and latest leopard and have been having very bizarre wireless issues that i think fall into the same category as is being discussed here:
the wireless does not seem to hold the connection and keeps searching every few minutes - that being said it only seems to be a problem in one area : i am currently in my backyard where the wireless i share with the neighbours above is working fine, the old computer that is on its last legs (mac 2002) still works in the apartment and the new computer works everywhere else... we've rebooted, changed passwords, removed passwords.... but doesn't make any logical sense...
i know this isn't an answer but it seems similar trouble to what i'm reading here
i just got a new macbook and latest leopard and have been having very bizarre wireless issues that i think fall into the same category as is being discussed here:
the wireless does not seem to hold the connection and keeps searching every few minutes - that being said it only seems to be a problem in one area : i am currently in my backyard where the wireless i share with the neighbours above is working fine, the old computer that is on its last legs (mac 2002) still works in the apartment and the new computer works everywhere else... we've rebooted, changed passwords, removed passwords.... but doesn't make any logical sense...
i know this isn't an answer but it seems similar trouble to what i'm reading here