Detailed Console Logs For the Wireless Problem

Question

So I'm yet another victim of the mysterious Macbook wifi problem. Have been for several months.
Anyway, I dropped into console, narrowed the search to 'airportd' and tried to activate AirPort from a problem spot in the house.
6/3/08 5:22:41 PM airportd[151] No networks found on channels remembered for bagwifi
6/3/08 5:22:41 PM airportd[151] Could not find "bagwifi"
6/3/08 5:22:41 PM airportd[151] Could not find any preferred networks; trying broadcast requests..
6/3/08 5:22:44 PM airportd[151] Broadcast requests also failed..
6/3/08 5:22:45 PM airportd[151] Probing highest ranked networks via directed scan..
6/3/08 5:22:47 PM airportd[151] Error: Apple80211Associate() failed -1
6/3/08 5:23:22 PM airportd[151] Error: Apple80211Associate() failed -6
6/3/08 5:23:22 PM SystemUIServer[95] Error: airportd MIG failed = -6 ((null)) (port = 36623)
6/3/08 5:23:22 PM airportd[151] Error: processcommanddict() failed
6/3/08 5:23:40 PM airportd[151] Error: Apple80211Associate() failed -6
6/3/08 5:23:40 PM SystemUIServer[95] Error: airportd MIG failed = -6 ((null)) (port = 36623)
6/3/08 5:23:40 PM airportd[151] Error: processcommanddict() failed
6/3/08 5:23:45 PM SystemUIServer[95] Error: airportd MIG failed = 1 ((os/kern) invalid address) (port = 36623)
Just for a recap... This problem happens anywhere I go, basically when I'm not in the same room as the access point. I've tried dropping AirPort from the configuration pane, I've changed the MTU, I've flashed the PRAM more times than I can really count.
I'm not that great with the internals of these things but maybe one of you knows what exactly the error codes mean.
I've also tried using the wireless under bootcamp in Windows XP, I have the same problems. Last night I tried the latest Ubuntu Live-CD installer and the wireless problems persisted, so I'm guessing something in one of the updates messed up the hardware.
Can anyone else try to replicate this?
I called the nearest Apple store and the Genius I talked to said that I was the first time he had heard of this problem. Anyway I figure it might be useless but I'm going to make an appointment with them and try to replicate the problem in-store.

Answer 1

Don't pay any attention to anything you see here or on the rest of the Internet, especially when it concerns Apple. What looks like "a ton" is really only a handful of people. And you have no idea what they have done to their machines. There are several million other people who have no problem at all or are smart enough to diagnose a hardware problem on their own and take it in to Apple.
What you have already done in this thread is much, much better information than the average "me too" post you will find. No one posts diagnostics. No one makes an attempt to diagnose the problem. No one make an appointment to have Apple look at the machine. I've seen it over and over again. They just want to rant.
I suspect you will be up and running while all the "others" are still ranting.