Currently Being ModeratedSep 9, 2013 12:23 PM (in response to headcase)
Thanks for responding. I've got the .35 driver. I use a Motorola Surfboard SBG6580. Its a DSL router/wifi combo, about a year or so old, and has worked great. No other networks in range.
More troubleshooting info: When the clamshell is open, ping times to 220.127.116.11 are in the 13 to 23 ms range. When I CLOSE the clamshell, the ping times jump to the 400 to 700 ms range! Does this bit of odd info help pinpoint anything?
Currently Being ModeratedSep 9, 2013 12:33 PM (in response to headcase)
Update. Fairly optimistic again. Wireless n at university works like a charm. She said the router back at the dorm is in a closet. If there is also a power socket available she might just be able to plug it into an ethernet port of the zyxel. That should do the trick :-)
Currently Being ModeratedSep 9, 2013 1:38 PM (in response to tlovejr)
Hmm... in terms of joining networks while your MacBook lid is closed, on further thought, it doesn't sound like an issue related to the driver or this support thread.
Try this first, as it may be a problem with the connection information stored in your network profile:
- Go to System Preferences > Network.
- Click the Wi-Fi connection.
- Click the Advanced... button on the bottom right.
- Click the Wi-Fi tab.
- Under Preferred Networks, select your wireless network.
- Click the - (delete) button.
- Turn off your Wi-Fi connection.
- Turn it back on.
- Select and login to your wireless network. This will re-save your connection under Preferred Networks.
- Close your laptop and reopen it to test whether it worked.
Also, most laptops have a better success rate of joining a wireless network where the SSID is broadcast, vs. hidden (which btw, hidden has no impact on security).
In terms of the increased latency you're now seeing, this is a defect of the .35 driver. Scroll back 3-5 pages on this thread on how to roll back to the .22 driver, which should suffice until Apple rolls out the next rev of the driver (likely in the 10.8.5 maintenance release).
Currently Being ModeratedSep 10, 2013 5:33 PM (in response to headcase)
Thanks for your response to my original post a few weeks ago. I still have not made a purchase. One option I am considering is buying a 2012 Macbook Air. I know there wouldn't be anything wrong with this choice, but would I be short changing myself for the long term? Your thoughts, please.
Currently Being ModeratedSep 10, 2013 5:38 PM (in response to Texan forever)
Texan forever -
Which laptop to buy is more a matter of personal preference. But that said, I still believe the 2013 MBA has reached the sweet spot of features, performance, and battery life which out-does its predecessors. My wife has the last-gen MBA, and I prefer this 2013 MBA given the faster storage and battery life. The AC radio is a nice benefit for moving files around on my speedy LAN.
Currently Being ModeratedSep 11, 2013 12:00 PM (in response to headcase)
I have been reading this thread for weeks. I am thinking about buying one of these machines, but I am concerdend about the topic discussed here.
I am not sure if this is a hardware problem or a software one. I read on previous post a theory of poor solding or something like that. Also, a recent posts tell that the .35 driver gives good pings, someyhing anomalous according to what I read. I am so confused.
What do you think? Is it a widespread problem?
PD: I´m from Spain, sorry for my mistakes
Currently Being ModeratedSep 11, 2013 4:24 PM (in response to pietrodelta7)
Apple probaby knows the answer (hardware or software). However as a software engineer the problem is often actually a series of layered problems which may include both software and hardware. Perhaps the new chips had a problem which was contributed to by a software bug or two. They may fix a bug only to find out it doesn't fix the whole problem. They fix another only to find the fix has a side effect which they also fix but find a problem under that. Finally the get to the lowest level and find out the early versions of the chips have a fault in assembly. You just don't know, But that kind of multi-level problem is common in non-trivial systems.
Everyone has schedule ... umm... challenges which usually result in skimping on testing. For some types of programs it's worth being more thorough, but for consumer products it's always a balance between delivering on time and producing a high quality product. Apple might NEVER fix this problem completely (remember the iPhone 4 antenna problem?) if it turns out the hardware is involved and fixing it would require an expensive recall. So if you can't live with the problem, don't buy the computer. If you can, you can choose to take the risk, and it is a risk, don't kid yourself.
Currently Being ModeratedSep 11, 2013 10:25 PM (in response to carbon_dragon)
this is why i am still waiting to buy. hoping at some point volume of reporting the issue decreases, or at least custom build MBAs rolling off the assembly line on X date, have lower probability of the issue. A good friend has been holding open a friends & family discount slot for me pretty much all this year. I'm not wanting to create drama for my friend, nor do the return/replace 3x mambo as others have. I want to come home, and have it work out of the box, like every other Apple laptop I've had.
As a 25 year customer, I ask again, Mr. Cook are you listening?
Currently Being ModeratedSep 12, 2013 6:27 AM (in response to carbon_dragon)
Thaks for the answers.
I am thinking about an idea. I want to make a proposal. For those ones who have problems, could you put the week when your macbook air was built?
This would allow us to know if maybe this is a bad batch.
But we would need to do some distinctions.
-There are people who had the ping problem only with the .35 driver and not with the .22 driver .
-There are people who had the disconnection problem with and with/without the .35 driver.
-There are people who have their disconnection problem solved with the .35 driver.
-And, rarely, there is a person who has a good connection without ping problems with the .35 driver.
If we are going to do this, it would be useful to specify each situation.
I think it is a bit late, because according to the amount of post, the problem is being solved, in my opinion (because we are seeing less cases).
I leave you the webpage where you can find the build week. You only have to put the serial number on it, and you can find it on about this mac and more information.
Thanks to all
Currently Being ModeratedSep 12, 2013 9:24 AM (in response to pietrodelta7)
I would and will gladly give you all the info you asked for. But I will not enter my full serial number into a website I know nothing about. Tell me how to figure out the week build on my own (based on s.n.) and I'll do it.
Currently Being ModeratedSep 12, 2013 10:05 AM (in response to raducan.mihai)
I found it myself. Here you go:
1. week build: 30 (bought in Japan if that matters)
2. ping on .35 driver ~30 ms (with my router)
3. ping on .22 driver ~ 3 ms (with my router)
4. never had disconnecting problems, or VoIP problems or any kind of problems neither with .22 or .35 driver. Tested on a few networks (g and n, on 2.4 and 5 Ghz, with and without security-McDonalds), even on wifi hot-spot via my Android phone.
5. in my environment I get 80-100 Mb/s download speeds on a (theoretical) 120 Mb/s (20-25 feet with 1 wall), exactly like my Win 8 Samsung laptop. My router is a Cisco provided by my ISP, 2.4 Ghz, n network, WPA2 Personal.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points