MacBook Pro (Late 2008) Wireless Issues

Fellows, after the last super-powerful-8th-wonder airport update, my wif-fi stop to work properly, it crashed my kernel_task, so I have to re-install my mac os X. The worst part was the in-genius at Apple store open my notebook, looking my crash log and told me TO DO, so re-install the OS, of course after a back-up.

But this was the worst assistance ever, I do not tested my mac yet in wireless field I'm using the old-fashioned and trustable cable now.

Apple please fix this ASAP.

According to my (I don't have it anymore I re-installed my system remember) when the wi-fi switch the key or try to use different net at same time generating an IOPIC interrupt it hangs the kernel_task and showing the grey screen and lead me to reboot only.

someone have the same behavior in your MAC ?

Did you perhaps have Real Player installed before the fresh re-install? In other parts of this forum many have fixed the performance issue by removing Real Player.

Clearly the core of the problem other are experiencing is this forum is not about Real Player.

Giacecco

All,
I have just tried to collect all of our reasoning around the MBP wifi issue in a diagram you can download at http://www.giacec.co.uk/mbp/ . It's in PDF format so you should have no problem reading it.

If Apple can't fix the problem, at least we can try understanding what the problem is and help them.

Please contribute and let me know of any missing information or mistakes I made. I look forward to collect your feedback and upgrade the diagram regularly. The email address to send your comments to is in the PDF.

Thank you in advance,

Giacecco

Thought I'd add my voice to this. I also have a late 2008 MBP, and I drop anywhere and everywhere. Local businesses, my own wireless network, etc. I spent four hours on the phone with Apple's tech support, and they insisted it was my Airport Express that was the problem without explanation of the drops elsewhere.

Hopefully Apple will get to this soon, as it's really a hindrance in my workflow. I can usually turn off the Airport (the Express or my Extreme card) and turn it back on to get it working again, but sometimes it will stop connecting to my network even when it shows I have full strength, or it will lose the ability to see my network. Pretty frustrating.

this has happened to me as well.. i signed up for mobile me, synced my stuff, cancelled my account, now i can't connect to the internet on my MBP. The iMac i'm typing on is connected just fine, but my MBP won't connect.

is there any other option besides a re-install? I just got my MBP a couple of weeks ago and the settings just right. i don;t want to have to do that all over again.

I also have a late 2008 MBP, I haven't noticed any drops but my wireless internet is SUPER SLOW. I know it's not the problem with the wireless router from AT&T because i've also tired sony z series and it worked very well with sony. With my MBP, even when i am sitting just 5 feet away from the router i still can't stream any video (Hulu, Youtube) without constantly lagging.

I've ended up in the exact same situation: forced to run my AX in 802.11n for the sake of my MBP's connection, and therefore leaving the rest of the non-N devices in my house unable to connect to the network (interestingly enough, they're all Apple products... iPhone, Powerbook, etc)

Are any of you experiencing this noticing AirPort-related error messages appearing in your /var/log/system.log log file?

Macbook Pro users... you're not alone.
My wife & I just picked up a late 2008 Macbook Aluminum.
SAME CONNECTIVITY ISSUE.

As a matter of fact, it's so bad this morning, that I'm typing this from my 2007 MacBook Pro sitting RIGHT NEXT TO the Macbook that won't connect.

Toss out any ideas of it being a Airport Extreme issue... it's the machine or software.
Hopefully Apple will come out and acknowledge it soon. I've heard complaints from 95% of the people I talk to. The other 5% plug into Ethernet directly.

I have tried using 802.11n only but achieved nothing. The only difference is that the network took longer before dying in the usual manner.

Giacecco

Bobby & Carie wrote:
Toss out any ideas of it being a Airport Extreme issue... it's the machine or software.

I recommend the following:

1) Take your MacBook to an Apple Store.

2) If you cannot connect to their in-store network, set up an appointment with a Mac Genius and demand they fix it.

3) If you can connect to their in-store network, there's something about your particular configuration causing the issue and we need to narrow down what it is.

I've said before on these forums that you cannot say "It works with Windows" or "It works with this other Mac" as valid reasons to rule out issues with your router.

That doesn't mean it isn't a hardware issue, nor that it's not a Mac OS X bug, just that more testing needs to be done first.

Exactly , all this stuff should be sorted and made to work before a single machine ships .
All this BS that forums are hospital wards for computers ...I don't think so ! , waay too many reports of this and other problems with the late 2008 MBP are all over the net, of course some will come here just to complain but that said I've read so much in the last month regarding these machines , way more issues than any other Mac that I can see ....silly issues too like smudges behind the glass...screen flickers etc etc etc , things that should be fixed before the machine ship .

what gives Apple ?



edit > maybe some forums are hospital wards ...but most people I know with a computer go on the internet and surprise surprise, are members of forums ,commonly a forum is where people chat about their computers they have bought .... , most folks who buy a machine probably don't know where to go for issues so think that's the way the machine is supposed to be and put up with it , sad thing is these are the people who wont buy one again , which costs Apple and affects us all in the long run

William Kucharski said "That doesn't mean it isn't a hardware issue, nor that it's not a Mac OS X bug, just that more testing needs to be done first. "

yeah . like before they leave the factory !! , no offense intended but really , paying customers shouldn't be expected to BETA test

becca jnr wrote:
William Kucharski said "That doesn't mean it isn't a hardware issue, nor that it's not a Mac OS X bug, just that more testing needs to be done first. "

yeah . like before they leave the factory !! , no offense intended but really , paying customers shouldn't be expected to BETA test

If you don't think Apple tests their software or products, there are quite a few people in Cupertino that would like to have a chat with you about what they do with their days.

The fact is every product can't be tested with every other product in every possible configuration before it leaves the factory. They do what they can, and the fact that you can walk into any Apple Store and the machines they have on display are all connected, wirelessly, to the in-store network shows it's not one where they don't work *at all* out of the box.

If you're experiencing these issues, you should really contact your local Apple Store's Mac Genius or call AppleCare at 1-800-APL-CARE (1-800-275-2273).

These issues get sent up the line to engineers in tech support and then on to Apple Engineering.

If there is a bug (as determined by a large number of customers experiencing the same issue) they're the ones who will fix it in Mac OS X or hardware (if it's Apple's issue) or contact router vendors to tell them to fix their bug.

No your right and I've edited my comment accordingly* .

I realize that the guys and girls at Apple work very hard to produce some amazing designs /products , I suppose I'm just a little disappointed with the final quality control checks at the factory , I'm sure the folk at Apple are too .
I'm trying to buy a machine but have had no luck yet , each one has had one fault or another .

becca.


EDIT>* I couldn't edit my previous post as the edit button is no longer available to use for that comment .