This discussion is locked
-
All replies
-
Helpful answers
first
Previous
Page
12
of 14
last
Next
-
Apr 5, 2009 3:49 AM in response to colinbutcherby colinbutcher,An update:
I replaced the 10.5.6 version of the IO80211Family.kext file with the 10.5.2 version. Since then, no drop-outs in the past 4 hours or so. Previously it was dropping out every 5 or 10 minutes.
I used 'Pacifist' to extract the IO80211Family.kext file from the 'MAC OSX 10.5.2 Combo' software update (obtained from the Apple downloads area), then deleted the 10.5.6 version in the /System/Library/Extensions directory and put the 10.5.2 version in it's place.
I put a copy of the 10.5.6 file into a directory called 10.5.6 on my desktop. I put the extracted 10.5.2 file into a directory called 10.5.2 on my desktop.
Here's the commands used at the shell prompt (use terminal.app) to put the replacement 10.5.2 version of IO80211Family.kext in place after deleting the 10.5.6 version, and then to 'flush the kext cache':
sudo -s
mv /Users/<username>/Desktop/10.5.2/IO80211Family.kext /System/Library/Extensions
chmod -R 755 /System/Library/Extensions/IO80211Family.kext
sudo chown -R root:wheel /System/Library/Extensions/IO80211Family.kext
cd /System/Library/Extensions
rm -rf Extensions.mkext
rm -rf Extensions.kextcache
After doing this you will see that 'software update' will offer to update the Airport client driver - don't install that update, or you will undo what's just been done manually!
If this continues to work successfully, then it really has to be a bug in the latest (post 10.5.2) Airport client driver.
Cheers, Colin.
PS: I gathered the above information from various posts in several forums, then pieced this together and tried it. Thanks to those who've all contributed to pieces of this puzzle. -
Apr 7, 2009 1:37 PM in response to colinbutcherby colinbutcher,Spoke too soon. It dropped out (again) later on.
However, on resorting to a wired connection I noticed that the wired connection also failed to come up after the MACbook went into power-save and came back.
So, I've reverted to the 10.5.6 update versions, but switched from DHCP client mode to "manually configured static IP" mode. So far, that works, both with wired and wireless ethernet.
If this proves to be successful, then it looks like a bug in the IP interface or static routing layers with the IP routing layer not realising that the interface layer has changed state.
Cheers, Colin. -
Apr 10, 2009 3:59 AM in response to colinbutcherby ScottW75,I gave up messing with settings in the end and bought a new official apple airport card from ebay. it cost £20 and is the new n spec one.
Problems are fixed the and signal all over the house is way better than it ever was with the old one. -
Apr 10, 2009 6:10 PM in response to PaoloMactuxby rv|nny,see and I have the problem with a Dell and 2 Macs dropping so I was leaning more that it was an Airport issue.... When I hookup my old Linksys, no problems ever. -
Apr 11, 2009 6:00 AM in response to ScottW75by Chanraj Bamrah,hi mate is it quite easy to install also which model airport card did you buy?
thanks! -
Apr 13, 2009 8:47 AM in response to Chanraj Bamrahby ScottW75,It was this one:
http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&ssPageName=STRK:MEWNX:IT&item=40 0037536922
Took 15 mins due to all the screws but its pretty easy.
There is a step by step guide here:
http://www.ifixit.com/Guide/Repair/MacBook-Core-Duo-Airport-Card/287/1 -
Apr 13, 2009 9:55 AM in response to colinbutcherby willingc,As Colin suggested, I switched DHCP client mode to "manually configured static IP" mode. Huge improvement. Thank you!
I'm hoping this will be fixed in SnowLeopard (if not sooner). -
Apr 14, 2009 2:35 AM in response to Jetfan630by bregje,Hello,
I was suffering from the same problem: frequent dropping of speed in the connection. I am running leopard on a macbook.
After lots of searching I came across this:http://www.macosxhints.com/article.php?story=20071031114140862
It has to do with faulty dns in the system preferences. Mine suddenly had a prefix of '85' in front of them that I had not put there.
I deleted the plug in file etc and my speed is a lot faster.
Not sure if it solves everything but it is a step!
Hope this is a help. -
Apr 14, 2009 9:30 PM in response to ScottW75by Brian Lee2,My Router: Time Capsule
My Computer:
Macbook 2.4Ghz (Santa Rosa)
Broadcom 802.11a/b/g/n Airport card
My issue:
Poor network performance with (1) 802.11b, 802.11b/g, 802.11g/n. (2) All 2.4GHZ frequency. (3) With WEP, WPA2, no wireless security. (4) All channels. (5) all multicast rates (6) all transmit power levels (7) with or without interference robustness. Used the Time Capsule to test out all of these settings.
Signal strength (RSSI) was steady. However, the transmit rate was fluctuating all over the place. As a result, the internet was unresponsive and slow download speeds.
But at 2.4GHZ frequency - 802.11n only is fine.
At 5GHZ - 802.11a, 802.11n (with 802.11a), 802.11n only - all work flawlessly.
Which would be OK with me if I could use 802.11a or 802.11n exclusive wireless networks. But the other Macbook is 802.11g, the iPhones are 802.11g, and almost all of the wireless hotspots outside of home are 802.11g (including at work).
So after zapping PRAM, archive and install (by an Apple Genius), new network location profiles, replacing the .kext files (going all the way back to 10.5.0), using a USB 802.11n stick (which worked very well), running a 802.11n only router with another router for 802.11g, several trips to the Genius Bar - I replaced the Airport card.
I chose the Airport Card from the Macbook CoreDuo (not Core2Duo) because the other Macbook in the household has this card (802.11b/g) and it has never had any problems with any wireless networks (most of the world is 802.11g at the fastest).
Apple Part Number 603-8214-A or Apple part numbers 661-3890
Model number AR5BXB6 (Atheros)
Now the wireless just works. After almost a year of this, I'm just relieved the issue is finally resolved for me.
A note about replicating the poor network performance at the Apple Store Genius Bar.
The first time I brought it in - the ping latency times for me at home were in the hundreds of milliseconds. When the Apple Genius tested it - no problems.
Then I realized that in the Apple stores there are two wireless networks running - a 802.11n only and a separate 802.11g network (at least in the Boston store).
Depending on which wireless network your Macbook joins, it may or may not replicate the issue. The Macbooks in the store are usually connected to the 802.11n only networks so they work fine. In contrast the majority of us at home are using 802.11g or 802.11n mixed networks. -
Apr 15, 2009 5:48 PM in response to ScottW75by Chanraj Bamrah,Hi mate cheers for that information, just wondering if it's worth me getting an apple atheros airport card over a broadcom one as my current card is a broadcom... Any recommendations on that?
Thanks! -
-
Apr 15, 2009 10:05 PM in response to Chanraj Bamrahby Brian Lee2,Hi
The one you are looking at is a 802.11n wireless card.
It looks like from a previous post that people have been having issues with BOTH the Broadcom and the Atheros 802.11n cards. Same issues over at the Macbook Pro forums. Because of these issues with the 802.11n cards - I decided to go with the 802.11g card since in my limited experience (with the other Macbook in the household) they just seem to work (it seemed like the problems were more prevalent with the Core2Duo Macbooks with the 802.11n cards looking at the forum postings). But I might have just gotten lucky.
If your Macbook is currently under warranty - you should probably have Apple replace the wireless card to save yourself the money and to avoid voiding your warranty. You can try insisting on a different chipset for the replacement card (Atheros vs Broadcom) but I'm not sure if Apple can accommodate such requests.
If the new/replacement 802.11n card doesn't work, then you can always try this option.
Thanks -
Apr 18, 2009 11:17 AM in response to Jetfan630by Scott.AR,Just wanted to chime in and say i'm also having random disco's. Some logs:
Apr 18 12:54:54 scott-gardners-macbook-pro kernel[0]: 11D beacon causing regdomain change to CC 840
Apr 18 12:54:54 scott-gardners-macbook-pro configd[14]: AppleTalk shutdown
Apr 18 12:54:55 scott-gardners-macbook-pro kernel[0]: en1: 802.11d country code set to 'US'.
Apr 18 12:54:55 scott-gardners-macbook-pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Apr 18 12:54:55 scott-gardners-macbook-pro kernel[0]: AirPort: Link Down on en1
Apr 18 12:54:55 scott-gardners-macbook-pro configd[14]: AppleTalk shutdown complete
Apr 18 12:54:57 scott-gardners-macbook-pro kernel[0]: AirPort: Link Up on en1
Apr 18 12:54:57 scott-gardners-macbook-pro configd[14]: AppleTalk startup
Apr 18 12:55:00 scott-gardners-macbook-pro kernel[0]: AirPort: Link Down on en1
Apr 18 12:55:01 scott-gardners-macbook-pro mDNSResponder[16]: Note: Frequent transitions for interface en1 (192.168.1.103); network traffic reduction measures in effect
Apr 18 12:55:01 scott-gardners-macbook-pro mDNSResponder[16]: Note: Frequent transitions for interface en1 (192.168.1.103); network traffic reduction measures in effect
Apr 18 12:55:02 scott-gardners-macbook-pro configd[14]: AppleTalk startup complete
Apr 18 12:55:02 scott-gardners-macbook-pro configd[14]: AppleTalk shutdown
Apr 18 12:55:02 scott-gardners-macbook-pro configd[14]: AppleTalk shutdown complete
Apr 18 12:55:04 scott-gardners-macbook-pro mDNSResponder[16]: Note: Frequent transitions for interface en1 (192.168.1.103); network traffic reduction measures in effect
Apr 18 12:55:57 scott-gardners-macbook-pro login[65386]: DEAD_PROCESS: 65386 ttys001
Apr 18 12:57:36 scott-gardners-macbook-pro kernel[0]: AirPort: Link Up on en1
Apr 18 12:57:36 scott-gardners-macbook-pro configd[14]: AppleTalk startup
Apr 18 12:57:41 scott-gardners-macbook-pro configd[14]: AppleTalk startup complete
Apr 18 13:01:27 scott-gardners-macbook-pro login[9950]: USER_PROCESS: 9950 ttys001
Apr 18 13:02:39 scott-gardners-macbook-pro kernel[0]: AirPort: Link Down on en1
Apr 18 13:02:39 scott-gardners-macbook-pro configd[14]: AppleTalk shutdown
Apr 18 13:02:39 scott-gardners-macbook-pro configd[14]: AppleTalk shutdown complete
Apr 18 13:03:09 scott-gardners-macbook-pro kernel[0]: AirPort: Link Up on en1
Apr 18 13:03:09 scott-gardners-macbook-pro configd[14]: AppleTalk startup
Apr 18 13:03:14 scott-gardners-macbook-pro configd[14]: AppleTalk startup complete -
Apr 22, 2009 12:22 PM in response to Brian Lee2by Brian Lee2,Just an update - I've spent the past week testing the 802.11b/g card from the (CoreDuo Macbook) in various hotspots outside of the house to check the compatibility and wireless performance. No problems/issues. Everything works great - quick connection, good response time and good throughput. -
Apr 28, 2009 8:17 AM in response to Brian Lee2by A.J. Jones,Does anyone have this issue... ( I didn't read all the multiple post)
I just changed my airport extreme (n) to broadcast at the 2.4 (n) rate from B & G compatible, because, we no longer use our wireless 2nd gen imac, which would not accept the (n) signal.
However, while all my new imacs, and wireless devices see the (n) signal and work fast, my wifes 2.0 duo core 2 mac book no longer will connect, however, see's the base station.
Anyone with this issue? I've switched back to B/G compatibility where it works, but would like to switch to the 2.4 Ghz (n)