Mac OS 10.4.10 and MacBook AirPort Issues? [Updated]

[mspmacguy]

continuing wireless connectivity problems

I too am experiencing this problem. Signal shows as full strength, and the Internet is sloooow or times out. I am using the new Airport Extreme Base Station (N). This only happens when running on battery power. I have both a MB and a MBP (both C2D) and they worked perfectly BEFORE the update to 10.4.10. I hope Apple fixes this soon. I'm an Apple newbie, and I'm really disappointed by this experience. Not very impressive after spending $5k (for two laptops) to convert to Mac from Microsucks.

 

[kibit]

Wow! and I thought it was just my connection... I'm having this issue too. For the record...I've got a older Macbook Pro 15" Core Duo and I'm connecting to a D-Link DI-624, I've never had any problems until recently. I've noticed my signal went to hell and my networked drives would suddenly disconnect. I'm really glad you guys posted this thread otherwise I'd probably be out looking for new equipment! Thanks!

 

[Florida Gator]

Update: Reports indicate that Apple's engineering team has acknowledged the issue as a bug and is working towards a resolution.

Where did you see that?

 

[bigben334]

problems here too, weird random airport dropouts...very annoying...cmon steve give us an update!

 

[Agent Smith]

It's weird; I've had no problems with the wireless setup at home (AirPort Express), but when I take it to school, Colonel Panic comes by and gives my BlackBook a kick in the arse. It happened at the worst possible time a couple of days ago. I was showing a classmate how to access some readings on the interweb, while extolling the virtues of the Mac platform. Wouldn't you know it - I was talking about stability, and along came Colonel Panic to berate my computer...

 

[meshuk]

Hi there this is my first post. Its a bit of a rant im afraid.
I have a macbook2.0 running 10.4.9. I have had it for 2 weeks so didnt expect any problems however, since ive had it, the internet dropsout randomly (an issue i see many of you guys have experienced). This was easily solvable by disconnecting the airport from the Linksys router and reconnecting. Not an ideal solution but it works. Today I was on the web (1 window open ([MOD NOTE: Do not post links to illegal torrent trackers!])) and had my torrent client (Transmission) open as well. I had just dragged 4 torrents into Transmission and they all started downloading when I got a kernel panic. I had these before on an old iBook G4 but this was when it was old and i saw them as Mac deathrattles indicating that the machine is close to the end. I checked panic.log and found this;

Sat Jul 14 15:21:25 2007
panic(cpu 0 caller 0x0035C240): mbuf address out of range 0x40492a0f
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x1510bab8 : 0x128d08 (0x3cb204 0x1510badc 0x131de5 0x0)
0x1510baf8 : 0x35c240 (0x3eb9c0 0x40492a0f 0x1510bb38 0x2031d3)
0x1510bb18 : 0x23abdb (0x1 0x2 0x1510bc68 0x26dbab00)
0x1510bc28 : 0x237f43 (0x4813394 0x26dbab00 0x1 0x6901a8c0)
0x1510be08 : 0x22e364 (0x26dbab00 0x14 0x1510be58 0x1a1738)
0x1510be48 : 0x22fdc5 (0x26dbab00 0x14 0x6 0x0)
0x1510bf58 : 0x21d53a (0x26dbab00 0x26dbab00 0x44507c 0x1a3010)
0x1510bf98 : 0x203df7 (0x3d3da04 0x26dbab00 0x26b9f812 0x1)
0x1510bfc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x4707dc0)
Backtrace terminated-invalid frame pointer 0x0

Kernel version:
Darwin Kernel Version 8.9.3: Fri Apr 27 14:50:07 PDT 2007; root:xnu-792.19.5~2/RELEASE_I386

I called Apple THREE times, each time getting different info ("login as a different user" & "upgrade to 10.4.10" etc). The third guy didnt even know what I was talking about and HUNG UP ON ME!!!!!!! I dont see the benefit of logging in as a different user and from what Ive heard on here (and elsewhere) 10.4.10 will give me more problems. It must be something to do with the Atheros driver or the Airports kext files but Im not clever enough to try fixing this on my own. Sorry for the mega-long post but I had to get it off my chest. "and exhale...."
anyone got any advice?? many thanks - MESHUK

 

[kelaman]

Thanks to SNIDE for the information in post #69!!!!!!!

THANK YOU, thank you, thank you so much for posting this fix. This issue plagued my daughter's MAC BOOK as well as my MAC BOOK PRO ever since installing 10.4.10. I had reinstalled my daughter's MAC BOOK but my MBP has so much stuff installed I was not looking forward to the process. You saved me a ton of time.

Hope I can pass this on to many people!

Blessings,

Kelaman

 

[Snide]

Most recent Linksys firmware updates address Bit Torrent issues

Hi there this is my first post. Its a bit of a rant im afraid.
I have a macbook2.0 running 10.4.9. I have had it for 2 weeks so didnt expect any problems however, since ive had it, the internet dropsout randomly (an issue i see many of you guys have experienced). This was easily solvable by disconnecting the airport from the Linksys router and reconnecting. Not an ideal solution but it works. Today I was on the web (1 window open ([Removed link!])) and had my torrent client (Transmission) open as well. I had just dragged 4 torrents into Transmission and they all started downloading when I got a kernel panic. I had these before on an old iBook G4 but this was when it was old and i saw them as Mac deathrattles indicating that the machine is close to the end.

If you are running a Macbook with 10.4.9, you might be having a separate issue
relating to Linksys routers and Bit Torrent. I was using the Transmission client with
both a Linksys WRT54G (open) and a Linksys WRT54GS (WPA) with no problems
until the most recent version of Transmission. Basically, the routers would hang
when Transmission was running, and would affect all other machines on the network.
I went to the Linksys site and updated the firmware for both units, and the problem was solved.

Here is a qoute from the Release Notes for the WRT54GS; the WRT54G is similar:


Firmware 1.52.0
- Improves compatibility with BitTorrent.

Check the firmware of the router from the admin page - and see if you have the most recent version.

Thanks to SNIDE for the information in post #69!!!!!!!

Credit goes to IamNobody for his post on the Apple forum. Glad it worked!

 

[iLunar]

Credit goes to IamNobody for his post on the Apple forum. Glad it worked!

Yes, thanks to his instructions my Macbook's airport stays connected. I tried his solution yesterday, and so far, my Macbook is back to normal. No more drop-outs at all. I hope it sticks!

 

[jonnylink]

Not to toot my own horn, but I'd figured out how to fix this a little while ago. I didn't realize there was a thread here about this though. Sorry.

It was a huge pain in the butt, I have to say!

If you go to my website you can download just the part of the file you need (skip the huge combo download and pacifist stuff). Then just follow the directions I wrote up which are super simple.

I'm not trying to lure folks to my blog... but it seems easier to just point people there. Sorry, if that is bad form— I've been reading macrumors for years, but haven't taken part in the forum aspect until now (usually I don't feel like I have anything meaningful to add)

 

[ortuno2k]

No problems here with my Linksys 54G router; but do have kernel panics and system lock-ups at my girlfriend's house on her Belkin Pre-N router - if I lose range, or change the router's password while connected to it, my system locks up and I have to do a hard shutdown.
I thought it was a problem with the router, but I guess is OS X.

 

[tomekinc]

My Mac crashes too!

How many macs crash when plugged into an AC adapter? I think that running on battery is causing the problem.

The problem (at least for me) is when I run on battery, at about 70% life it will give me the 'gray screen of despair' and announce I must do a shut down. It will do this twice within 5 minutes. I have a brand new MacBookPro and have tried a few tests such as disconnecting everything. So far it seems to reboot around the 70% and only on battery.

Below are both the kernal panic reports. So is this an Airport issue? Battery? OS 10.4.10? I see a few fixes for restoring Airport to 10.4.9, has anyone done that and it still not work?

FIRST CRASH:

panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00004210, CR3: 0x012fd000, CR4: 0x000006e0
EAX: 0x00004208, EBX: 0x00000056, ECX: 0x00000052, EDX: 0x00000056
CR2: 0x00004210, EBP: 0x480d3bf8, ESI: 0x59dbbd00, EDI: 0x00000004
EFL: 0x00010202, EIP: 0x0035bf70, CS: 0x00000008, DS: 0x4fed0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x480d39e8 : 0x128d08 (0x3cc0a4 0x480d3a0c 0x131de5 0x0)
0x480d3a28 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x480d3b38 : 0x19aeb4 (0x480d3b50 0x48 0x480d3b68 0x381143)
0x480d3bf8 : 0xde65b5 (0x59dbbd00 0xfffffffc 0x6 0x782852a0)
0x480d3dd8 : 0xde8059 (0x465632c8 0x1 0x480d3e38 0x138452)
0x480d3f08 : 0x39b3c3 (0x46563000 0x6a54c00 0x1 0x466260)
0x480d3f58 : 0x39a595 (0x6a54c00 0x135eb4 0x678b640 0x4bb000)
0x480d3f88 : 0x39a2cb (0x6e49900 0x480d3fd4 0x134c09 0x39a2ae)
0x480d3fc8 : 0x19ad2c (0x6e49900 0x0 0x19e0b5 0x678e91c) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(230.8.5)@0xdb4000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x690000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5f2000
dependency: com.apple.iokit.IO80211Family(160.2)@0xa5e000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

Model: MacBookPro3,1, BootROM MBP31.0070.B00, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB
Graphics: GeForce 8600M GT, GeForce 8600M GT, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), 1.1.8.5
Bluetooth: Version 1.9.0f8, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: ST9160823AS, 149.05 GB
Parallel ATA Device: MATSHITADVD-R UJ-85J
USB Device: Built-in iSight, Apple Inc., Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 1.5 Mb/sec, 500 mA
USB Device: USB Device, Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: USB Receiver, Logitech, Up to 1.5 Mb/sec, 500 mA

SECOND CRASH:

panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0xfffffe01, CR3: 0x012fd000, CR4: 0x000006e0
EAX: 0xfffffe01, EBX: 0xfffffe01, ECX: 0x90000000, EDX: 0x59e27b00
CR2: 0xfffffe01, EBP: 0x47f2bbb8, ESI: 0xfffffe01, EDI: 0x465632c8
EFL: 0x00010206, EIP: 0x0035d0ce, CS: 0x00000008, DS: 0x00010010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x47f2b9a8 : 0x128d08 (0x3cc0a4 0x47f2b9cc 0x131de5 0x0)
0x47f2b9e8 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x47f2baf8 : 0x19aeb4 (0x47f2bb10 0x65c0b000 0x0 0x22cf2080)
0x47f2bbb8 : 0x35d151 (0xfffffe01 0x804c 0x47f2bbf8 0x33)
0x47f2bbd8 : 0x35d4b3 (0x59e27b00 0x804c 0x1 0x800)
0x47f2bbf8 : 0xde61b7 (0x59e27b00 0x47f2bcbc 0x6 0x782761b0)
0x47f2bdd8 : 0xde8059 (0x465632c8 0x0 0x0 0x0)
0x47f2bf08 : 0x39b3c3 (0x46563000 0x6c7a500 0x1 0x679043c)
0x47f2bf58 : 0x39a595 (0x6c7a500 0xe03 0x47f2bf78 0x4b2038)
0x47f2bf88 : 0x39a2cb (0x6c992c0 0x40 0x34 0xffffffff)
0x47f2bfc8 : 0x19ad2c (0x6c992c0 0x0 0x10 0x6785700) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(230.8.5)@0xdb4000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x690000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5f2000
dependency: com.apple.iokit.IO80211Family(160.2)@0xa5e000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

Model: MacBookPro3,1, BootROM MBP31.0070.B00, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB
Graphics: GeForce 8600M GT, GeForce 8600M GT, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), 1.1.8.5
Bluetooth: Version 1.9.0f8, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: ST9160823AS, 149.05 GB
Parallel ATA Device: MATSHITADVD-R UJ-85J
USB Device: Built-in iSight, Apple Inc., Up to 480 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 1.5 Mb/sec, 500 mA

 

[mspmacguy]

the problem continues...

Unbelievable! I posted a few “posts” above. I called AppleCare, and the technician I spoke with (who was very nice) said he hasn’t heard of this issue, and the company hasn’t issued any kind of internal information for technicians to be aware of regarding this or similar issues. I am very disappointed by this. With all due respect to those who have posted workarounds to this issue that have worked for them (and some others), I believe that Apple should acknowledge and fix the issue that they caused. Also, I, a person who is not a computer wiz, don’t want to implement some fix that someone else, in good faith, has supplied, only to potentially make matters worse or make my machine inoperable. Have others tried the fix (cut and paste into terminal, restart in safe mode, etc.)? I am very new to this, so I don't want to screw something up.

Please tell me, is this the typical Apple M.O.? Apple was very good at marketing to get me to buy two computers at a total cost of $5,000, but so far I have not been impressed by the Apple “It just works...” motto.

 

[powerbuddy]

Unbelievable! I posted a few “posts” above. I called AppleCare, and the technician I spoke with (who was very nice) said he hasn’t heard of this issue, and the company hasn’t issued any kind of internal information for technicians to be aware of regarding this or similar issues. I am very disappointed by this. With all due respect to those who have posted workarounds to this issue that have worked for them (and some others), I believe that Apple should acknowledge and fix the issue that they caused. Also, I, a person who is not a computer wiz, don’t want to implement some fix that someone else, in good faith, has supplied, only to potentially make matters worse or make my machine inoperable. Have others tried the fix (cut and paste into terminal, restart in safe mode, etc.)? I am very new to this, so I don't want to screw something up.

Please tell me, is this the typical Apple M.O.? Apple was very good at marketing to get me to buy two computers at a total cost of $5,000, but so far I have not been impressed by the Apple “It just works...” motto.

Don't worry, from what I know Apple has acknowledged this issue finally. I have talked to the P.S's recently and from what I understand the engineers are working on a fix. I was even interviewed and got an offer to replace my Macbook with the defected airport for investigation. I am sure we will see a fix in the following days.

 

[BEET]

I had the same problem, my macbook pro suddenly couldn't get any airport connection. Having tried various fixes, I found nothing worked.
As a last measure I reinstalled (choosing the archive option) the os x disks that came with the laptop and it works fine now.

 

[macpeter]

I hope Apple finds a fix soon

It is a relief to read the update to this story that Apple has acknowledged the bug and is working towards a resolution. I rolled back to 10.4.9 to overcome a series of kernel panics which began immediately after 10.4.10 and a WEP wifi service I regularly use. I guess in the short term, simply replacing the relevant kext files is better. But it will be nice if Apple sorts this before Tiger is overtaken by Leopard...

 

[mspmacguy]

Don't worry, from what I know Apple has acknowledged this issue finally. I have talked to the P.S's recently and from what I understand the engineers are working on a fix. I was even interviewed and got an offer to replace my Macbook with the defected airport for investigation. I am sure we will see a fix in the following days.

Thanks, powerbuddy! That's good to hear.

 

[macpeter]

Not to toot my own horn, but I'd figured out how to fix this a little while ago. I didn't realize there was a thread here about this though. Sorry.

It was a huge pain in the butt, I have to say!

If you go to my website you can download just the part of the file you need (skip the huge combo download and pacifist stuff). Then just follow the directions I wrote up which are super simple.

I'm not trying to lure folks to my blog... but it seems easier to just point people there. Sorry, if that is bad form— I've been reading macrumors for years, but haven't taken part in the forum aspect until now (usually I don't feel like I have anything meaningful to add)

This is really helpful, thank you

 

[ioanan]

Check your crash logs in console

if you see, Finder, Safari, Dock, even airport crashes in the crash log, it is a good sign you need to back your machine and reinstall your OS. I don;t like it either, had the same issue, But it makes sense.

 

[mspmacguy]

logic board

I have heard several people indicate that AppleCare has diagnosed similar problems for them as a logic board issue, and they are having to have their logic boards replaced.

Could this mean that there are a number of faulty logic boards out there that this update has brought to light? Can an update cause a faulty logic board? I'm not a computer wiz, so if someone understands more about this type of thing, it would be helpful if they could respond. Thanks!

 

[brooklyn]

At the Apple store I noticed that their macbooks were having conection issues also. I mentioned it to the rep and he blamed the problem on the T1 line.

Came in a few days later to pick up my 2.4 Macbook Pro and they were still having the same issues.

My new Macbook Pro came with 10.4.9 and was left that way. No Problems conecting... flawless wireless!

On the other hand... My "Black" Macbook running 10.4.10 is lagging and losing conections even though I am inches away from the router.

 

[Amdahl]

MB & MBP problem

My MB is experiencing the crashes and 100% CPU load on startup. I kill the airport process on the MB.

The MBP is having the crashes.

10.4.10 on both. I've been sending the reports to Apple every time they happen, although sometimes it seems the report can't be sent or wasn't fully 'saved' in the crash.

Both have trouble with the connection sometimes, but overall not bad.

 

[MsWrite]

Computer Crashes

I am having the same problems with kernel panics on brand new mac book pros. It has been an issue with both the lower end and midrange model. I have exchanged this computer at least 4 times already in the last month. The apple care tech said engineers are aware of the issue and are working on a solution...in the meantime...I am miserable with my purchase.

 

[mspmacguy]

KPs

I am having the same problems with kernel panics on brand new mac book pros. It has been an issue with both the lower end and midrange model. I have exchanged this computer at least 4 times already in the last month. The apple care tech said engineers are aware of the issue and are working on a solution...in the meantime...I am miserable with my purchase.

What did AppleCare say was wrong to justify 4 returns, which is ridiculous for anyone to have to deal with, especially for high-end personal computer systems?

Does anyone know if KPs caused by a software issue, which most of us assume is the case in relation to the 4.5.10 update, can permanently damage the computer?

 

[mspmacguy]

Back to 10.4.9

Last night I did an archive and install back to 10.4.8 and then updated to 10.4.9 using the combo update. I updated the airport to 2007-002 (but not -003, because I've read there have been airport issues similar to what everyone has been experiencing with the 10.4.10 update), and updated to the latest security. So far, everything is back to normal. No more wireless drops. I don't plan to go back to 10.4.10 until I feel confident that Apple has corrected this issue with a patch. In the meantime, I will let the forum know if I experience and of the problems I was having after previously installing 10.4.10 (followed by all of the reinstall work).