MBP Santa Rosa Airport Issues w/ Leopard

Hi everyone,
I've noticed a few "quirks" since upgrading to Leopard. Whenever my Macbook Pro (Santa Rosa, 2.4 GHz, 17", 4GB RAM) is searching for a wireless network to join, the system becomes completely unresponsive. The mouse pointer stutters and jumps around the screen and it's impossible to precisely control its movement. When I can finally manage to click on the Airport icon in the menu bar and select the appropriate network to join, the problems stop as soon as a connection to a wireless network is established. It only happens when the system is searching for a Network. I should mention that it does this when I am at work (where I connect via 802.1x and TTLS) and at home (where I connect via an Airport Express Router).
Also, my computer no longer automatically connects to my work network (it does at home, though) after a restart or waking from sleep). I have my MBP set to prompt me for a password when it wakes from sleep, but it's near next to impossible to enter in the password because the system hangs so badly as it tries to establish a network connection. Of course, it doesn't connect unless I manage to click the Airport icon and specify the network I wish to join. Anyone have any thoughts on this?
All of this is a little frustrating since the latest updates to Airport in Tiger fixed all of the connection issues I had had previously with my MBP. When I first bought the machine I had many issues with network connections (as did many thousands of others who bought this model). I was wondering if other MBP Santa Rosa owners have observed similar behavior since upgrading to Leopard, and if so, does anyone have any suggestions as to how to fix this issue?
I should also mention that my Mac Mini C2D 1.83GHz (latest model) has no such issues so I think this is something that is still linked to this particular model of MBP.
Many thanks!

I am moving this over here, from the boot camp section. Hopefully this is more the location that this needs to be in. Well, my problem is not as extreme as some, but still an annoyance. I installed Leopard the first day, and immediately had HUGE airport issues. The computer would lose my hub. I run an Airport Extreme with an Express as a WDS. The computer would see the express, but lose the extreme completely. So no internet. If I messed with it long enough, I could get the computer to recognize the extreme, but as soon as the computer went to sleep, it would lose it again. I installed the keychain update, and the situation didn't get much better. Most of the time I get the "You are not connected to the Internet" error in Safari, and when I run network diagnostics the computer "finds" the internet again, and I get a "Network configuration change detected" message and all my lights go green.
After I installed the Keychain update, I repaired disk permissions. Any ideas?

Similar Messages

Leopard forgets color profiles when waking from sleep on MBP Santa Rosa

I have a 15" MBP Santa Rosa with a 22" Samsung external monitor. I performed a clean (erase and) install on my machine. Upon waking from sleep, the computer seems to have forgotten the color profiles loaded for the displays. To correct this, I open system preferences and then the display option. As soon as the display options are shown on the window, my MBP loads the correct profile. This has happened for both displays, though far more frequently on the external display. The profile for my Samsung was created using color calibration hardware/software but the MBP display is running the stock profile from Leopard.
Any thoughts? Has anyone else experienced this?

same issue here. also had it in tiger, but much more frequently in leopard. seems to be whenever my display wakes from sleep.
MBP 2.4 GHz SR purchased 6/07. also driving samsung 245bw external display (which has never been affected, unless perhaps my calibrated and default profiles aren't different enough for me to notice--the difference is severe on my built-in display).
console contains this:
2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Con trast.monitorPanel/Contents/MacOS/Contrast and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry.
2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT.
2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel.
2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch.
2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode.
2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization.
2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions.
Message was edited by: thomas jerde

Anyone with a 17" MBP C2D having AirPort issues?

Most of the reports I've seen of people having issues with their MBP C2D and AirPort have the 15" MBP C2D (myself included.)
Has anyone with the 17" MBP C2D had issues, or is it isolated to the 15"?

Hi William
I had a 2.33 15"MBP 2.33and had no probelm with the airport reception (until security update 2006-007 was installed - I erased and reinstalled to get rid of the update and my machine went back to working fine.) Apple have released an update for Airport on the 15". So using software update the machine installed the airport update first, then installed security update 2006-007. Airport worked great.
Due to an excessively grainy display, my reseller allowed me to return the 15" and upgrade it to the 17". Again, this machine has had absolutely no airport issues. Connects full signal to whatever network I have attempted to connect to without issue.
So, I have had both a 15" and a 17", neither of them have had any airport issues, other than the one mentioned above in regards security update 2006-007 on the 15", but Apple did launch an Airport update which fixed this.

How I Fixed My Dying Santa Rosa Airport Connection

I have the new 15" LED MacBook Pro. I've had it since June 11 and it worked great. Not one problem. No kernel panics. Wireless was fantastic with the Airport Extreme.
Then I ran the 10.4.10 update and everything started to die just as others here have mentioned. Running on battery or AC didn't make a difference.
1. iDisk was freaking out with Mirror Agent errors.
2. WiFi connectivity would be there, then not.
3. iTunes streaming from a network box would work and then not.
4. Downloads were slow and funky.
After reading the messages here and futzing around with some other stuff I found on the web, here's how I was able to return my wireless connection to full functionality and robustness.
1. I turned off iDisk. No syncing. No iDisk as disk.
2. I did the PRAM reset.
3. I logged into my Airport Extreme and changed the channel from "Automatic" to "11" and when I did I was asked for a keychain password and I provided it.
Since making those changes I can now...
1. Listen to iTunes again. I've been streaming from the network for 4 hours without interruption.
2. This morning I listened to WFAN streaming radio for six hours without even a stutter.
3. I downloaded the new 175MB iPhone tutorial and watched it from the network drive.
I have no idea if any of this will solve any of the trouble you're having, but I thought I'd share what I learned and wish you the best. It's incredibly frustration to sort of connect and then not...

If you lose after sleep, that often means that the default network it is trying to connect to is not setup in the network preferences.
If you go to:
Apple menu -> System Preferences -> Network -> change Network Status to Airport, and By default Join Preferred networks, and delete all the networks, and only add the network with the correct username and password for your network, usually that will fix the network so that it only goes to that network after it wakes from sleep. Sometimes if the network settings become corrupted, it is best to clear the preferred networks, and start fresh.

Everyone with a santa rosa macbook pro..

did the wireless fix sort the issues out!? i really need to no. without the wireless working on my macbook pro when i get it in a week..itl be useless!
everyone whats going on???

MBP Santa Rosa 17", now four days old, officially. Forgot completely about all the wireless/networking problems cited here, and, therefore, just joined my household network (LinkSys) Wednesday afternoon without thinking.
Everything went perfectly.
Took said MBP to another location this weekend (wi-fi'd marina), again forgetting about the potential problem joining that setup . . . but no difficulty again.
Hope I'm not the exception. LOVE THE NEW MACHINE thus far: no display problems, no wi-fi problems, no kernal crashes, no nothing. Fingers crossed and smile on mouth!

Brand-new Santa Rosa MBP, Kernel Panics related to Airport

Brand new MBP (2.4GHz 15"), anytime I do anything online I get a kernel panic. I am connecting to a WPA-2 network that is supporting stable connections to several other computers, including another (albeit older) MBP. I have no third-party sw installed, I have no peripherals attached, I have installed all available updates, I have run disk verify/repair and permission repair via the install disk and the problem persists. I have also physically inspected the RAM modules to make sure they're situated properly.
The console log shows mbuf failures (I can only access the log if I have the airport off) that are similar to the problem Apple identified in 10.4.8 but were supposedly solved w/ 10.4.9 (see http://docs.info.apple.com/article.html?
artnum=303712).
So two questions: anyone else out there experiencing this on a WPA-2 or other network? If so, any fixes that don't involve me having to return this computer to Apple? If this is a QA issue that could have been prevented through better testing prior to release...

Hey Don (and others)
I bought a new Santa Rosa MPB yesterday and am suffering the same issues. My office uses WPA (not sure about the specifics) and within the first hour of ownership (of my FIRST Apple machine ever) I suffered kernel panics.
I get back to my workplace from the local Apple Store, get all set up and online. I run all the software updates fine. Next, I shut the lid and proudly carry my new Mac to a meeting. Open the lid and notice I can't get online. I stop and start the wireless and immediately get a kernel panic.
Restart, and it happens again.
Restart, and I can get online finally. With the help of some coworkers I get to the panic.log file and notice the panic happens around the Airport.
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2572b9f8 : 0x128d08 (0x3cc224 0x2572ba1c 0x131de5 0x0)
0x2572ba38 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x2572bb48 : 0x19aeb4 (0x2572bb60 0x2572bb68 0xb92ebbb4 0x6)
0x2572bbf8 : 0x3b3c5e1e (0x17 0x23e1a107 0x6 0x3e77a380)
0x2572bdd8 : 0x3b3c8059 (0x23b052c8 0x1 0x4b285c 0x6)
0x2572bf08 : 0x39b543 (0x23b05000 0x4174b00 0x1 0x3c341e8)
0x2572bf58 : 0x39a715 (0x4174b00 0x135eb4 0x0 0x3c341e8)
0x2572bf88 : 0x39a44b (0x40e9200 0x0 0xee6ae98 0x13818b)
0x2572bfc8 : 0x19ad2c (0x40e9200 0x0 0x19e0b5 0x42bee60) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(230.8.5)@0x3b394000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x634000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a4000
dependency: com.apple.iokit.IO80211Family(160.2)@0x3b375000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Later I discovered that the office uses WPA. So I bring the MBP home and connect via my WEP encrypted WiFi, and haven't had the same problem once (so far it's been over 24 hours, with many "sleeps" in the meantime).
I did have another panic, waking up out of a 'deep sleep' this morning (after having had the lid shut for 6 hours)...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x606000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5f2000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x602000
ACPI seems to have crashed something, hoping I can recreate this tomorrow morning.
At this point, I'm just glad to see I'm not the only owner of a the new MBP's suffering the same WPA-related crashes. Also, I do wonder if I got a replacement if it would solve anything, though I'm up for trying and may try tomorrow.
Overall, a bit frustrated (especially since after craving a MBP for months and holding out for the new models, to have these issues).
Oh, I also have a 2.4ghz 15"
-r-

10.5.2 and santa rosa mbp cinema display issue

not only did the update hang... It took disconnecting everything and reseting the pram just to get it past the initial white screen.. once it booted the display on the mbp flickered like 7 times seemingly adjusting it's color profile over and over. I plugged in my 30 inch and it appeared to be working fine.. but then i noticed that the brightness of the display on the santa rosa wasn't responding at all.. and neither were the keyboard keys that usually control the brightness of the cinema display.
So I decided to reboot.. well. what do you know, won't reboot again unless I unplug not only the cinema display, but the firewire and usb extensions that go with it, and my fire800 external... I'm not sure which it is as I'm not going to test it risking anything.. it's something though.. it seems like a power issue... and I'm worried it could get worse.. if i don't restart and unplug everything the fans speed up all the way and it just sits..
I am not going to reboot for a while now.. hopefully until there is a solution.. help?
and not to mention I was hoping for a fix with 10.5.2.. try calibrating your color in expert mode.. there's not even a button on the right slider.. I was told that this in their database, and escalated by two separate geniuses.. over 2 months ago..

not any ideas?

Leopard on Santa Rosa's - Any problems?

I am getting ready to head down to pick up a copy of Leopard. I was wondering if anyone has installed Leopard on the Santa Rosa chipset MBP models? If so, what was your experience?

Wouldn't dream of declaring an OS defect free - Who'd take my word for it?
But as of today Santa Rosa Macs in Apple Stores will be running Leopard and when I ran it on my machine it was fine so my point was that I'd expect it to be fine - that is take a Santa Rosa machine and add a fresh copy of Leopard and perhaps iLife.
Michael pointed out a couple of glitches and obviously for any third party software, it depends on the software.
As for the Airport drivers - they've been fine on our Santa Rosa machine - so I can't even say that's a defect I've come across.
Message was edited by: Rajesh Sharma

Santa Rosa MBP, Kernel Panics fixed by 10.4.10 Update v1.1

A friend of mine who has the new 2.4GHz MBP just ran the 10.4.10 v1.1, and he no longer has KPs. Has anyone else tried this with their SR MBPs?
I just got my 7th machine last night. I noticed that Apple has made the AC adapter smaller (similar to PB's). Who knows, maybe they changed something from the first release? Anyways, I tested it on battery, and within about 15 min, a KP while surfing the net! I will give the v1.1 a try when I get home tonight. will report back.
SR MBP owners, pls let me know if there's any fix out there that I am not be aware of. Thank you!

I run mine on battery all the time. Out on the deck, airports, hotspots, office buildings, hotels. Never had an issue with KP's.
I purchased mine through PowerMax on a trade-in deal for my old Core Duo model. They are located in Oregon I believe.
Something very wrong with being on 7. This is my 3rd one and only because I voluntarily keep upgrading them. Had a 15" Core Duo traded up for a 17" Core Duo and now a 17" Santa Rosa. Never had a single problem with any of them.
Apple certainly isn't problem free, the same as any other manufacturer isn't.
But honestly..if your on #7 I would have to start thinking that the problem is something other than the MBP. Some software...configuration...combination of hardware....something. I mean you would pretty much have to be the worlds unluckiest person I would think to have 7 bad ones.
Honestly, I really do mean no offense, but you might want to start looking at other factors. Are you using 3rd party RAM in it? Have you tried other routers? Or just one you have at home? What security protocols are you using? What software have you loaded from the default configuration.
I guess anything is possible, but statistically it would seem improbable that 7 of them could be suffering from the same problem.

Problem with Santa Rosa MBP-Unable to Boot

I have a Santa Rosa MBP with the maximum of 4GB of memory.
About 4 months ago I was unable to boot it because there was no video at all. The Genius Bar stated it was a problem with the video in the hardware and kept it for about a week to install a new Logic Board.
I got it back but within a couple days began having new problems. The Wi-Fi would connect but there was no internet on safari, mail, etc. i went to the Apple store again and the Genius Bar was unable to fix it and said it was a problem deep inside the OS. What I did since I had already bought Snow Leopard I did an upgrade from Leopard to Snow Leopard and it solved the problem.
It has worked well the last 3 months or so when my MBP started slowing down. It would sometimes take 10 minutes just to get from the login screen after typing in my password to my desktop where I can use it. Programs would open slow, close slow. My dashboard opens but I can't do anything with it. It has only gotten worse with time and now the computer won't even boot. It gets to the grey Apple with the progress indicator and stays there with the fan running but never goes further.
Fortunately I had done a mirrored backup from Super Duper. I had begun to think it was a hard drive problem. I tried booting from this backup that was made before the problem got very bad and it also runs the same way. I then took this backup to another MBP I have and it worked perfectly. I don't think it's a hard drive problem now. I then thought it may be a memory problem. I used the DVD that came with the MBP to do a hardware test which passed.
I think I have no choice but to go back to the Genius Bar. The problem is with purchasing the additional AppleCare my AppleCare just expired about 3 weeks ago. Yet I know this logic board was put in around 4 months ago and if I'm correct when something like that is done it's often a refurbished board, not new. Either way I had the issue with Wi-Fi just after the replacement and I went back to Apple for it. I think it was related and now this problem. I don't want to have to buy a new MBP but yet I'm convinced all these problems started with the logic board replacement.
Do any of you have other ideas of what the problem could be? Is it possible something I could fix? I have tried a PRAM reset with no luck. Would Apple cover something like this?
Thank you for your help.

Hi,
Looks like partition 2 is set to active after running diskpart script. Here are the details:
DISKPART> list volume
Volume ### Ltr Label        Fs     Type        Size     Status     Info
Volume 0     C   OSDisk       NTFS   Partition    465 GB Healthy
Volume 1                      NTFS   Partition    300 MB Healthy
Volume 2     D   Win7_2.1.6_ NTFS   Removable     14 GB Healthy
DISKPART> select partition 2
Partition 2 is now the selected partition.
DISKPART> detail partition
Partition 2
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 499792216064
Volume ### Ltr Label        Fs     Type        Size     Status     Info
* Volume 1                      NTFS   Partition    300 MB Healthy

Leopard battery life impact on 15-inch 2.4GHz Santa Rosa?

I'm getting ready to take the Leopard plunge by upgrading my Tiger 15-inch 2.4GHz Santa Rosa MacBook Pro to 10.5.2.
I've seen some reports of decrease in battery life with this upgrade, though nothing that seems to suggest there is any sort of wide-spread issue in 10.5.2, so I'm not expecting this to ding my battery life too noticeably (currently 2-3.5 hours depending on usage and settings).
In general I'm not too worried about installing Leopard, but if anyone has any good or bad experiences to share with respect to MBP battery life, I'd appreciate it.

You should have no trouble. The vast majority of the "+Leopard killed my battery+" posts (and the "+10.4.11 update...+ and +10.4.10 update killed my battery+" posts that preceded those) resulted from one of three things:
1. Unfortunate but coincidental timing of a battery failure due to the issues that BillC37 mentioned (and acknowledged by Apple here)
2. The fact that Battery Update 1.2, _which was specifically designed to expose battery problems_, was rolled into 10.4.10 and later updates, and into Leopard, so those people who didn't apply the stand alone battery update got it with the OS update/upgrade
3. A conflict (often a widget or 3rd party app that's not compatible with the update/upgrade) that spawns a rogue process that ramps up the CPU and the fans, which then affects battery run time
So, bottom line, you should be fine.
Hope this helps...

Santa Rosa MBP - DVI to VGA Projector problems

When hooking up a Sharp PG M20X using a [DVI toVGA cable] and a [VGA to DVI adaptor] the MBP sees the projector, but the projector cannot see the computer.
This is a problem because, I may find myself in situations where this is the only configuration for hooking my MBP up to a projector.
Note:
1. A G4 Powerbook works fine with this configuration.
2. The MacBook Pro drives the Sharp PG M20X projector DVI to DVI - without problems
3. The MacBook Pro drives a DVI to VGA CRT monitor - using a [VGA to DVI adaptor] - without problems.
Is there a solution?
Thanks
I have a 2.4 GHz Santa Rosa C2D MacBook Pro Mac OS X (10.4.10) Sharp PG M20X Projector (DVI-input)

I think I solved this problem.
It was in issue for me. My second monitor would only display the Windows XP screen when it was loading, then it would black out. I couldn't even move my mouse arrow to the other side. Then I fixed it, here's how (running Windows XP SP3):
1. Start > Control Panel > Appearance and Themes
2. Display
3. Go to tab "settings"
4. Double click the blue image with the "2" inside it. This is the second monitor, adjacent to your first, or primary, monitor. The blue box may be a desaturated, greyish blue, meaning that the monitor is disabled. Click it and it a box will pop up asking if you want to enable the monitor. Click OK, and then like magic, your monitor is resurected in it's Windows Glory! From there, adjust the resolution, and it should work perfectly.
This isn't a Boot Camp compatability issue, it's just a problem with the lack of familiarity that users of OS X have with using XP.
Have a nice day!
Message was edited by: BlakeTron
Message was edited by: BlakeTron

Help!!! Brand new MBP with Santa Rosa Kernel Panics when started with...

Help!!! Brand new MBP with Santa Rosa Kernel Panics when started with external HD firewire 800 after 20 sec...
I don't know what it could be???
Do you???
Thanx
Jay

I'm actually having a similar issue and I don't think its related to networking at all.
I'm currently working in a corporate environment where we deploy pre-built OS X images to machines. I recently upgraded my images to 10.4.10 before we got our first Santa Rosa machine. This image was built on a MacPro and worked on all Intel Macs down to a MacMini CoreSolo. When I deployed my prebuilt image to the SR MBP, it caused a kernel panic immediately.
Further investigation revealed previous builds of OS X, including 10.4.10 upgraded from any other model Intel Mac will kernel panic the SR MBP. Going backwards the SR Build of OSX will not work on any previous model Mac, as any other build typically does, but causes severe graphical distortion, as if it does not have the display drivers for the other Macs.
To make a long story short, I think your issue comes from the fact that your external hard drive has an older build of OS X 10.4 than the SR MBP will run (even though you may have upgraded it to 10.4.10). Anyone who can corroborate my story with some more testing, please chime in.
I haven't found a solution for this issue yet other than keeping a seperate Santa Rosa Core 2 Duo image for my deployments.

Santa Rosa MBP Application Crashes with EXC_BAD_ACCESS (0x0001)

I am having Application crashing problems with my brand new Santa Rosa MBP that arrived today. This machine is a 2.4 GHz 17" MBP with Hi-Res Glossy display and it came with 2 GB of RAM. I upgraded it to 4 GB but this problem occurs with the original chips or the new 2 x 2 GB chips.
So far the applications that crash are Pages, Keynote, Aperture, Parallels Desktop, and iWeb. Other things I have tried are all right for now. Excerpts from the CrashReporter log of Aperture are below. All applications are crashing with an identical EXCBADACCESS (0x0001) and KERNPROTECTIONFAILURE (0x0002) at ... (this number differs for individual applications). Any ideas?
Bryan
Host Name: brycv
Date/Time: 2007-07-05 20:49:02.460 -0700
OS Version: 10.4.10 (Build 8R2232)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [82]
Version: 1.5.3 (1.5.3)
PID: 1196
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 <<00000000>> 0x00000000 0 + 0
1 com.apple.Aperture 0x00003149 0x1000 + 8521
2 com.apple.Aperture 0x0000323e 0x1000 + 8766
3 com.apple.Aperture 0x0000336e 0x1000 + 9070
4 com.apple.Aperture 0x0000294e 0x1000 + 6478
5 com.apple.Aperture 0x00002875 0x1000 + 6261
Thread 1:
0 libSystem.B.dylib 0x900248c7 semaphorewait_signaltrap + 7
1 com.apple.ColorSync 0x915a86cf pthreadSemaphoreWait(t_pthreadSemaphore*) + 35
2 com.apple.ColorSync 0x915c2de0 CMMConvTask(void*) + 60
3 libSystem.B.dylib 0x90024227 pthreadbody + 84
Thread 2:
0 libSystem.B.dylib 0x900248c7 semaphorewait_signaltrap + 7
1 libGLProgrammability.dylib 0x9418afdb glvmDoWork + 150
2 libSystem.B.dylib 0x90024227 pthreadbody + 84
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x010f7020 ebx: 0x92b217da ecx: 0x01872000 edx: 0x00000011
edi: 0xbffffbd8 esi: 0x01872000 ebp: 0xbffffc08 esp: 0xbffffbdc
ss: 0x0000001f efl: 0x00010246 eip: 0x00000000 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)

I am also having this problem with Adobe Bridge CS3, and QuickTime but only if I try to open a video file. It seems to be a problem when I access anything that wants to deal with the video hardware in the machine. I am planning on calling Apple tomorrow but any help would be appreciated.

Xcode3 Completely Freezes Leopard 10.5.3 on Santa Rosa MacBook Pro

Hi
I am recently workin on a software project on Xcode3 (with all the latest Updates)
with great disappointments i found out that very often (not every day or every time i use it) while in the process of editing source files the leopard user interface completely freezes (something like a kernel panic happens) and the only thing i can do is to force a shutdown.
it happened to me at least 10 times (sometimes more than one time a-day). i have had user interface freezes before while using other applications but that i'm not having them anymore, the problem clearly re emerged by using xcode (which i never used before)
i suspect it has to do with bugs in the graphics drivers for the GeForce 8600M GT graphics chip that is used by my Core 2 Duo Santa Rosa Macbook Pro (2.2 Ghz) and that Mac Os 10.5.3 Still has not fixed
Anyone has the same problem? or any idea?
Thanks

It happened once again while i was copying (Apple-C) a selected line of code on the Xcode Source file Editor
I officially submitted tha Bug Report to Apple (Bug ID# 5985528).
In Responce to the System User Interface Freeze i obtained a SystemUIServer Crash Report of which i report the first lines
Process: SystemUIServer [158]
Path: /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer
Identifier: com.apple.systemuiserver
Version: 1.5.4 (248.1)
Build Info: SystemUIServer-2480100~8
Code Type: X86 (Native)
Parent Process: launchd [110]
Date/Time: 2008-06-04 19:03:09.759 +0200
OS Version: Mac OS X 10.5.3 (9D34)
Report Version: 6
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x000000000da2384f
Crashed Thread: 1
Thread 1 Crashed:
0 ??? 0x0da2384f 0 + 228735055
1 ...e.ImageCaptureNotifications 0x000d1a65 _StaticICNRecognizedDevice + 4052
2 ...e.ImageCaptureNotifications 0x000d3f86 _StaticProcessIOObjectsArray + 315
3 libSystem.B.dylib 0x940a26f5 pthreadstart + 321
4 libSystem.B.dylib 0x940a25b2 thread_start + 34

MBP Santa Rosa Airport Issues w/ Leopard

Similar Messages

Maybe you are looking for