Upgrading Santa Rosa MBP HDD

As the thread title says i'd like to upgrade my MacBook Pro's shabby 120GB HDD.
I'm under Apple Care and have heared that selfupgrading voids the Apple Care warranty.
Any way Apple can upgrade for me? And what are the pricing options?

There is still the issue of power requirements and perhaps heat generated. Contact an Apple dealer/service centre and ask. I've heard that some will do this kind of thing & others won't. I guess their decision is based on what they know about the proposed drive and possible liability if they get it 'wrong'. I don't think Apple themselves will do this. As the dealers are more or less independent companies they have more flexibility.
In my experience, if you have a good relationship with a dealer they will often do a lot more for you than if they don't know you reasonably well.
Neville

Similar Messages

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.

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

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.

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

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?

What is a Santa Rosa MBP?

Sorry for my ignorance, but I just bought a MBP 17" 2.4Ghz with 4GB RAM and 7200RPM HD and I've read a lot about the "Santa Rosa" and I'm lost. What is it? and how can you tell? Thanks

It's the most recent incarnation of the MBP line that is using a different chipset than previous models. This chipset is nick-named 'Santa Rosa' by Intel. Hence the new MBPs are called the Santa Rosa models. They can be easily identified by their CPU speeds - 2.2 and 2.4 GHz.
If you open System Profiler you will also see that the Machine ID is 3,1 to identify the first of the Santa Rosa models.

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-

Are FW800 and FW400 Ports On Separate Buses...On Santa Rosa MBP?

Hi Folks,
I have yet to get a definitive answer from Apple Support, Apple store techs, the Web, searching these forums, etc. on this question:
On the latest MacBook Pro (Santa Rosa), are the Firewire 800 and Firewire 400 ports on separate buses? In other words, if I have an external FW400 drive (or other FW400 device such as an audio interface) running on the FW400 port, and an external FW800 drive running on the FW800 port, will the 800 run at 800 speeds or 400 speeds?
Here are the answers I've received thus far:
Apple Support: "Yes...they 'should' be on separate buses", "The techs say the 800 'should' run at 800", "You should call an Apple store"
Apple Store #1: "They ARE on separate buses"
Apple Store #2: "They ARE NOT on separate buses"
The Web: I've not found one source that supports that they ARE on separate buses. Every post I've read in this and other forums suggest that they share the same bus and that the FW800 port will degrade in this situation.
Does anyone have the definitive answer on this? Any real-world experience?
Thank you so much.
Rich

Ignore the previous poster.
Here is all you need to know...
There is ONE FireWire bus. It supports up to 800 MB/sec.
*You cannot use both the FW800 and FW400 ports at the same time! You can't!*
If you for example plug in a FireWire 800 hard drive into your FireWire 800 port, and a video camera into the FireWire 400 port, then capturing video in Final Cut Pro simply *WILL NOT WORK.*
So, what is the solution?
One solution is to plug the video camera into the hard drive, assuming it has a FW 400 port on it. This will daisy-chain the video camera through the FW 800 hard drive.
Another solution is to buy a FireWire ExpressCard for your 34mm ExpressCard slot. I got one with two FireWire 400 ports at NewEgg.com for $29.99. There are also ones available that have FireWire 800 ports on them, but they are pricier. Adding the ExpressCard gives you *an additional FireWire bus* that will have its own 800MB/s dedicated just to it. This is the best way to go since now you will have DUAL buses.
For example I hook my FireWire 800 hard drive up on my FW 800 port, and my MOTU 828 up on the ExpressCard FireWire 400 port. That way, the audio signals coming in are not clogging up the bus that the record drive is set up on... I've been able to get better latency for recording this way!
Hope this helps!!

Santa Rosa MBP & Defective Airport on Battery

Hello all,
I have been talking to Level 2 Support on my MacBook Pro and per their support, I have replaced my machine for the third time. However, the same problem still exists:
When I am connecting to WEP secured networks on AC power, I have absolutely no issues. My speeds over the network and Internet are as fast as they should be.
However, when I unplug the Magsafe adapter and run off battery, within 2 to 10 minutes, I will lose connectivity to any network resource and Internet connectivity. Yet I still have an IP address, full signal, and my router can see my computer online.
To get back on the Internet, I have to restart my router and it will work again for 2 to 10 minutes before the same things happens. I can also restart my computer or turn off/turn on my Airport for another 2 to 10 minutes of connectivity.
If I plug my computer back in with power, the issue seems to go away after turning off/turning on my Airport or following any of the above solutions.
Level 2 support keeps having my replace my system under the 14 day swap policy but I know this has to be a driver issue since EVERY machine has this problem. Does anyone have a clue what the heck is going on?
For the record, my home network is a 2Wire Gateway/Router supplied by my ISP, Embarq. It works with every other Intel or PPC mac we have battery or AC powered. It is also using the latest firmware for this model 2700HG-S. Since this works with my MBP while on AC Power, I doubt this is their issue but an Apple problem.
Help! I am tired of returning this machine every 14 days.

Try altering the channel that is on the router to a
different channel. Someone in the neighborhood might
be broadcasting too much traffic on that channel, and
causing a problem.
Of course tune in your airport setup to receive on
that channel too, and not use an automatic
connection.
If uncertain how to do this, you might want to
contact 2Wire and let them know you have this issue.
Someone else found changing the channel solved their
problem.
Also make sure your airport software is up to date,
from http://www.apple.com/swupdates/
I have already tried multiple channels with the same result. I am currently using Channel 11 but have tried them all. Also, I have already downloaded all available software updates.
Again, this is my Third Machine I have gone through with the same exact issues. I am guessing that Level 2 support will tell me to trade in the machine for another one.
I have done a clean format and install on each of the machines. However, for this latest one, I tested it out without migrating my user data. It still did not function.
Any other ideas?

Santa Rosa MBP Blank screen

It's literally blank. Not lit up at all, just plain blank. I can hear the startup sounds and everything. I've tried zapping the PRAM. Anything else I can try?

I also have this problem. My computer was in sleep mode, closed, on a pillow. It seemed very hot, but that is rather normal. Opening it up, there was nothing on the screen but the computer was very much still on. I turned it off by pressing the power button. Turned it on, and heard Skype start up, but the screen was just black! I tried everything you said, and more, but nothing seems to work. I will be taking it into a service shop nearby to see what they can do. Any other suggestions?
TIA!!!!!

8Gb of RAM in a Santa Rosa MBP?

It is possible to install 2 4Gb DIMMS into the latest Macbook Pro and is it even supported? Blogs say it will work, but apparently it remains un-utilized by OSX. Will there be future support via a firmware update perhaps? Or must I wait for Snow Leopard for this....?

From what I understand, you can plug any ram you want into the MPB, but it will only use its maximum of 4gb. That means, if you plug in 8gb, you'll be wasting the other 4gb.
This is how I've heard it - I've never experienced it myself.

MacBook Pro - with Santa Rosa - Kernel Panics

The local Apple store has replaced my new Santa Rosa MacBook Pro once already and when I received the machine, I did a brand new install and then transferred my files over. They told me that if I still get Kernel Panics on this second machine to go ahead and do an Archive and Install or Full Install option.
Until Time Machine is out, what is the best backup method for keeping all files and settings if you want to do a complete new install and format?
Does anyone think a brand new install will fix this? Also, this machine is getting a lot less KP's than the previous Santa Rosa MBP got. Any ideas why?
Here is my panic.log below. Does anyone have any ideas what this Unresolved Kernel Panic Means?
Sat Jun 9 23:57:50 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x012cf000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x3c41d5fe, ECX: 0x00000000, EDX: 0x0000000e
CR2: 0x00000000, EBP: 0x2580ba78, ESI: 0x0409da00, EDI: 0x80000000
EFL: 0x00010202, EIP: 0x00000000, CS: 0x00000008, DS: 0x25800010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2580b828 : 0x128d08 (0x3cc224 0x2580b84c 0x131de5 0x0)
0x2580b868 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x2580b978 : 0x19aeb4 (0x2580b990 0x202 0x2580b9e8 0x1416ad)
0x2580ba78 : 0x56222d (0x409da00 0xe 0x0 0xffff)
0x2580bae8 : 0x55bddd (0x409da00 0x3f54480 0x0 0x38181e)
0x2580bb08 : 0x389cae (0x3f54480 0xe0000100 0x409da00 0x1)
0x2580bb48 : 0x38a97b (0x409da00 0xe0000100 0x3f54480 0x1)
0x2580bb78 : 0x38a8da (0x409da00 0x3ea5c00 0x1 0x0)
0x2580bbb8 : 0x5601cc (0x409da00 0x3ea5c00 0x1 0x0)
0x2580bbd8 : 0x561a64 (0x409da00 0x3ea5c00 0x1 0x0)
0x2580bc08 : 0x5619b4 (0x409da00 0x409da00 0x1 0x561228)
0x2580bc38 : 0x56b340 (0x409da00 0x3ea5c00 0x1 0x0)
0x2580bc88 : 0x56b54d (0x3ea5c00 0x409da00 0x2580bce8 0x202bd0c)
0x2580bcb8 : 0x56ee2d (0x3ea5c00 0x202 0x2580bcd8 0x39a515)
0x2580bcd8 : 0x39be5c (0x3ea5c00 0x1 0x0 0x0)
0x2580bd18 : 0x3b2cf3 (0x3ef0340 0x56ee3e 0x1 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOHIDFamily(1.4.11)@0x555000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Wed Jun 13 07:24:00 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x3d176ec8, CR3: 0x0133a000, CR4: 0x000006e0
EAX: 0x00cfcf00, EBX: 0x0040cbe1, ECX: 0x00cfcfcf, EDX: 0x0000cf00
CR2: 0x3d176ec8, EBP: 0x25bcbb58, ESI: 0x3d176ec8, EDI: 0x00000006
EFL: 0x00010006, EIP: 0x0037ee27, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25bcb888 : 0x128d08 (0x3cc224 0x25bcb8ac 0x131de5 0x0)
0x25bcb8c8 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x25bcb9d8 : 0x19aeb4 (0x25bcb9f0 0x0 0x25bcba08 0x131d98)
0x25bcbb58 : 0x37f2ed (0x109380 0x3ccf4000 0x0 0x2)
0x25bcbc18 : 0x1ac351 (0x3d35c8 0x1 0x0 0x120)
0x25bcbc48 : 0x5e13ce (0x5e11ae 0x3 0x612160 0x0)
0x25bcbca8 : 0x5d6446 (0x400b800 0x2 0x25bcbc7c 0x4006a40)
0x25bcbcc8 : 0x3abf47 (0x405c300 0x4b063c 0x3 0x260000)
0x25bcbd08 : 0x3bb2f2 (0x400b800 0x3f21d4 0x3fae348 0x391c89)
0x25bcbd48 : 0x394663 (0x3fae100 0x4 0x1d 0x2)
0x25bcbd88 : 0x394b99 (0x3fae100 0x0 0x25bcbdc8 0x0)
0x25bcbda8 : 0x395a78 (0x3fae100 0x3f86c00 0xb 0x1)
0x25bcbde8 : 0x394bc2 (0x3fae100 0x407d500 0x25bcbe28 0x0)
0x25bcbe08 : 0x395a78 (0x407da00 0x3f86c00 0xb 0x1)
0x25bcbe48 : 0x394bc2 (0x407da00 0x40d3d00 0x25bcbe88 0x0)
0x25bcbe68 : 0x395a78 (0x4091c80 0x3f86c00 0xb 0x1) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x5d5000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5c1000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x5d1000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Wed Jun 13 08:37:37 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x3d21f9c8, CR3: 0x0133a000, CR4: 0x000006e0
EAX: 0x00baba00, EBX: 0x0040cbe1, ECX: 0x00bababa, EDX: 0x0000ba00
CR2: 0x3d21f9c8, EBP: 0x25563b78, ESI: 0x3d21f9c8, EDI: 0x00000006
EFL: 0x00010002, EIP: 0x0037ee27, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x255638a8 : 0x128d08 (0x3cc224 0x255638cc 0x131de5 0x0)
0x255638e8 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x255639f8 : 0x19aeb4 (0x25563a10 0x0 0x25563a28 0x131d98)
0x25563b78 : 0x37f2ed (0x109380 0x3cbd9000 0x0 0x1)
0x25563c38 : 0x1ac351 (0x3d35c8 0x1 0x0 0x120)
0x25563c68 : 0x5e13ce (0x5e11ae 0x3 0x612160 0x0)
0x25563cc8 : 0x5d6446 (0x3d19800 0x2 0x25563c9c 0x3d02400)
0x25563ce8 : 0x3abf47 (0x3d6a300 0x4b063c 0x3 0x248000)
0x25563d28 : 0x3bb2f2 (0x3d19800 0x3f21d4 0x25563d88 0x394211)
0x25563d68 : 0x39459b (0x3cbc100 0x4 0x1d 0x2)
0x25563da8 : 0x395a78 (0x3cbc100 0x3c94c00 0xb 0x1)
0x25563de8 : 0x394bc2 (0x3cbc100 0x3d8b500 0x25563e28 0x0)
0x25563e08 : 0x395a78 (0x3d8ba80 0x3c94c00 0xb 0x1)
0x25563e48 : 0x394bc2 (0x3d8ba80 0x3dc9680 0x25563e88 0x0)
0x25563e68 : 0x395a78 (0x3dc9e80 0x3c94c00 0xb 0x1)
0x25563ea8 : 0x394bc2 (0x3dc9e80 0x3ddca00 0x25563ee8 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x5d5000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5c1000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x5d1000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Thu Jun 14 00:28:21 2007
panic(cpu 0 caller 0x0035CF4B): mget MCHECK: m_type=ffffb954 m=375bca00
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x259c3be8 : 0x128d08 (0x3cc224 0x259c3c0c 0x131de5 0x0)
0x259c3c28 : 0x35cf4b (0x3ed024 0xffffb954 0x375bca00 0x19a319)
0x259c3c48 : 0x3638c3 (0x1 0xe 0x4 0x376dfa00)
0x259c3c88 : 0x22f11d (0x259c3cac 0x14 0x14 0x0)
0x259c3cf8 : 0x240c7a (0x477fa00 0x259c3d2c 0x3764f134 0x37648d00)
0x259c3d48 : 0x2410ce (0x1c 0x0 0x3b9aca00 0x1)
0x259c3e08 : 0x22f364 (0x3764f100 0x14 0x3c 0x19a001)
0x259c3e48 : 0x230dc5 (0x3764f100 0x14 0x11 0x0)
0x259c3f58 : 0x21e53a (0x3764f100 0x375bcc00 0x44707c 0x1a37c0)
0x259c3f98 : 0x204df7 (0x4d1000 0x375bcc00 0x375bccfc 0x1a373d)
0x259c3fc8 : 0x19ad2c (0x0 0x0 0x10 0x4937f40) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386

Hi Kaleb,
I got a similar problem with my MacBook Pro. Kernel panic with Airport atheros driver. My router is Linksys WRT300n. A brand new install didn't fix the problem. This is the panic.log of the most recent KP.
Tue May 22 15:50:17 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x14306c68, CR3: 0x01745000, CR4: 0x000006e0
EAX: 0x14306c60, EBX: 0x00000098, ECX: 0x00000098, EDX: 0x14306c60
CR2: 0x14306c68, EBP: 0x14b7bd28, ESI: 0x26610a00, EDI: 0x00000004
EFL: 0x00010206, EIP: 0x0035b0dc, CS: 0x00000008, DS: 0x03a50010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14b7bb18 : 0x128d08 (0x3cb134 0x14b7bb3c 0x131de5 0x0)
0x14b7bb58 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x14b7bc68 : 0x19ada4 (0x14b7bc80 0x0 0x4b0c9c 0x199ef1)
0x14b7bd28 : 0x2b611a94 (0x26610a00 0xfffffffc 0x6 0x2b9de300)
0x14b7bf08 : 0x39a463 (0x12e182c8 0x32f6180 0x1 0x37fc4a8)
0x14b7bf58 : 0x399635 (0x32f6180 0x135eb4 0x0 0x37fc4a8)
0x14b7bf88 : 0x39936b (0x37e6f80 0x0 0x450 0x1303)
0x14b7bfc8 : 0x19ac1c (0x37e6f80 0x0 0x10 0x0) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x2b5e0000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x2ab68000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x249b6000
dependency: com.apple.iokit.IO80211Family(154.1)@0x2b5c3000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Thu May 24 20:11:02 2007
panic(cpu 0 caller 0x0035C2B2): mbuf address out of range 0x14306c60
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14003ab8 : 0x128d08 (0x3cb134 0x14003adc 0x131de5 0x0)
0x14003af8 : 0x35c2b2 (0x3eb8f4 0x14306c60 0x14003b68 0x1416ad)
0x14003b18 : 0x23abdb (0x1 0x2 0x2c0208 0xd6e31900)
0x14003c28 : 0x239783 (0x31edc9c 0x3f10d055 0x3f10d5fd 0xa3aaa8c0)
0x14003e08 : 0x22e364 (0x25b6ae00 0x14 0x14 0x6)
0x14003e48 : 0x22fdc5 (0x25b6ae00 0x14 0x6 0x0)
0x14003f58 : 0x21d53a (0x25b6ae00 0x25b6ae00 0x44507c 0x1a3010)
0x14003f98 : 0x203df7 (0x2c52804 0x25b6ae00 0x25a7181a 0x1)
0x14003fc8 : 0x19ac1c (0x0 0x0 0x10 0x2fe64c0) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Fri May 25 21:05:50 2007
panic(cpu 0 caller 0x0035BFBD): mbuf address out of range 0x18306c60
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13fd3d18 : 0x128d08 (0x3cb134 0x13fd3d3c 0x131de5 0x0)
0x13fd3d58 : 0x35bfbd (0x3eb8f4 0x18306c60 0x13fd3d88 0xd14c)
0x13fd3d78 : 0x35c815 (0x1 0x1 0xa1aaa8c0 0x10000e0)
0x13fd3db8 : 0x21da6e (0x25a07c00 0x1c 0x27b7940 0x0)
0x13fd3e08 : 0x22e32c (0x25a07c00 0x14 0x14 0x2)
0x13fd3e48 : 0x22fdc5 (0x25a07c00 0x14 0x2 0x0)
0x13fd3f58 : 0x21d53a (0x25a07c00 0x25a07c00 0x44507c 0x1a3010)
0x13fd3f98 : 0x203df7 (0x2bf6804 0x25a07c00 0x25a9e81a 0x1)
0x13fd3fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x2b3e718) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Sat May 26 18:06:48 2007
panic(cpu 0 caller 0x0035C2B2): mbuf address out of range 0xe28c
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x1457bab8 : 0x128d08 (0x3cb134 0x1457badc 0x131de5 0x0)
0x1457baf8 : 0x35c2b2 (0x3eb8f4 0xe28c 0x1457bb68 0x1416ad)
0x1457bb18 : 0x23abdb (0x1 0x2 0x2c0208 0xd6e31900)
0x1457bc28 : 0x239783 (0x3225e08 0xe26725f3 0xe2672b4b 0xa3aaa8c0)
0x1457be08 : 0x22e364 (0x25a37800 0x14 0x14 0x6)
0x1457be48 : 0x22fdc5 (0x25a37800 0x14 0x6 0x0)
0x1457bf58 : 0x21d53a (0x25a37800 0x25a37800 0x44507c 0x1a3010)
0x1457bf98 : 0x203df7 (0x2bcbe04 0x25a37800 0x25aa881a 0x1)
0x1457bfc8 : 0x19ac1c (0x0 0x0 0x10 0x2ad0540) Backtrace terminated-invalid frame pointer 0x0
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Sun May 27 09:52:05 2007
panic(cpu 0 caller 0x0035C30A): mbuf address out of range 0x16dd6c60
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13e7ba08 : 0x128d08 (0x3cb134 0x13e7ba2c 0x131de5 0x0)
0x13e7ba48 : 0x35c30a (0x3eb8f4 0x16dd6c60 0x124fe004 0x2be9004)
0x13e7ba68 : 0x35c6aa (0x25b15500 0x25b6b100 0x13e7ba88 0x124e74bc)
0x13e7ba88 : 0xa0e98e (0x25b15500 0x25b15500 0x124fe004 0x80)
0x13e7bb68 : 0xa238f5 (0x124fe004 0x25b15500 0x30 0x35ac8a17)
0x13e7bd28 : 0xa2daf5 (0x35ac8a17 0x25aee800 0xffff 0x376ec560)
0x13e7bf08 : 0x39a463 (0x124e72c8 0x29fc300 0x1 0x26f8a7c)
0x13e7bf58 : 0x399635 (0x29fc300 0x135eb4 0x0 0x26f8a7c)
0x13e7bf88 : 0x39936b (0x2a06440 0x0 0x13e7bfc8 0x203e3e)
0x13e7bfc8 : 0x19ac1c (0x2a06440 0x0 0x19e0b5 0x2ee4ed4) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x9fc000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6bf000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
dependency: com.apple.iokit.IO80211Family(154.1)@0x7fb000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Sun Jun 3 19:48:03 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x16dd6c68, CR3: 0x00e1c000, CR4: 0x000006e0
EAX: 0x16dd6c60, EBX: 0x0000009a, ECX: 0x0000009a, EDX: 0x16dd6c60
CR2: 0x16dd6c68, EBP: 0x144dbd28, ESI: 0x25a5b800, EDI: 0x00000004
EFL: 0x00010206, EIP: 0x0035b0dc, CS: 0x00000008, DS: 0x02b30010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x144dbb18 : 0x128d08 (0x3cb134 0x144dbb3c 0x131de5 0x0)
0x144dbb58 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x144dbc68 : 0x19ada4 (0x144dbc80 0x0 0x144dbc98 0x3801e3)
0x144dbd28 : 0xa2da94 (0x25a5b800 0xfffffffc 0x6 0x3796e710)
0x144dbf08 : 0x39a463 (0x124e72c8 0x29f5980 0x1 0x2b3acec)
0x144dbf58 : 0x399635 (0x29f5980 0x135eb4 0x0 0x2b3acec)
0x144dbf88 : 0x39936b (0x2b271c0 0x0 0x8000 0xf0b)
0x144dbfc8 : 0x19ac1c (0x2b271c0 0x0 0x19e0b5 0x2eda6c8) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x9fc000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6bf000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
dependency: com.apple.iokit.IO80211Family(154.1)@0x7fb000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Sun Jun 3 20:51:21 2007
panic(cpu 0 caller 0x0035C2B2): mget MCHECK: m_type=6c60 m=25ae2800
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13eabc18 : 0x128d08 (0x3cb134 0x13eabc3c 0x131de5 0x0)
0x13eabc58 : 0x35c2b2 (0x3eb83c 0x6c60 0x25ae2800 0xa20181)
0x13eabc78 : 0xa043c3 (0x1 0x2 0x13eabcc8 0xa4a4e0)
0x13eabcc8 : 0xa0acca (0x124f9004 0x2 0x1 0x0)
0x13eabcf8 : 0xa06f05 (0x124e74bc 0x0 0x1 0xa4a07f)
0x13eabd28 : 0xa2e08b (0x124e74bc 0x13eabeec 0x13eabd48 0x325)
0x13eabf08 : 0x39a463 (0x124e72c8 0x2a12880 0x1 0x258e8b0)
0x13eabf58 : 0x399635 (0x2a12880 0x135eb4 0x0 0x258e8b0)
0x13eabf88 : 0x39936b (0x2a18bc0 0x0 0x8000 0x3403)
0x13eabfc8 : 0x19ac1c (0x2a18bc0 0x0 0x19e0b5 0x258e8b0) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(223.47.4)@0x9fc000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6bf000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
dependency: com.apple.iokit.IO80211Family(154.1)@0x7fb000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
I tried WPA, WPA2, WEP. TKIP, AES. 802.11b, 802.11g and 802.11n... with the same issue -> Kernel Panic...
I have no answer from my Apple resellers in France. Alone in the dark :'-(
BUT everything goes well since I stop using the '$' in the pre-shared key and the SSID. I haven't experience any new KP since 03/06 with a intensive Airport use... I hop this can help you.
Core 2 Duo MacBook Pro 15" • 120GB HD • 1GB RAM Mac OS X (10.4.9)

What discs come with the current (Santa Rosa) macbook pros?

I own a Rev1 Macbook Pro (but that's not really important). I convinced my friend to get a new Macbook Pro. She loves it. But she did something somewhat silly. She asked me what the discs were for that were included in her box and I told her they are only to reinstall the included software. Anyway, she was looking for Comic Life and she concluded it must be on the cds, so she ended up reinstalling Mac OS X! But now the installer is asking for Disc 2 which she can't seem to find...
Now it was my understanding that the OS came on 1 dvd, not two. There are additional parts on another disc for things like Xcode and whatnot, but the main installer should only need 1 disc, correct? Does anyone happen to recall where the second disc is found? I seem to believe it's actually in the same sleve as disc one but she says it isn't.
So yeah maybe the packaging has changed or maybe my memory isn't that great. Any suggestions?
Thanks!

I own a Rev1 Macbook Pro *but that's not really important*.
It may be important, if she asks to borrow your DVDs. The OS X Install DVDs for the Intel Macs are machine- and build-specific. So your Install DVDs for a pre-Santa Rosa MBP will most likely not work on an SR machine.
However, if she's missing disc(s) she can call AppleCare and they will send her replacement(s) for a nominal charge (something like $30, I think).
You might also point her to this link:
http://docs.info.apple.com/article.html?artnum=301229
which describes how to do a custom installation. For apps, etc., not listed there, she could use Pacifist:
http://www.charlessoft.com/
to extract them from the Install DVDs.
Hope this helps...
Ps. the iLife suite that was pre-installed on the Mac is located on Install DVD 2.

Mac Book Santa Rosa 13" 2.2 GHz, HDD upgrade

Hello,
I would like to change the hard drive of my MacBook Santa Rosa 13" 2.2 GHz.
I would like to go fo an SSD Drive. I checked and find out that the kingston have got a good price.
There is something that is quite annoying me though, they propose model with Serial ATA III and serial ATA II. I tought Serial ATA III was compatible with older technology. So my questions are:
Why do they propose two versions (especially when the SATA II version is more expensive) ?
Will a SATA III SSD will work in my old macbook ? any idea of the perf ?
Thanks a lot,
Regards,
Julien

Before 2009, all SATA Macs only supported 1.5 Gbps SATA.
Starting in 2010 they started supporting higher speed SATA.
During 2009, Apple provided firmeware updates for 2009 models that didn't support higher speed SATA to support it. That said, many SATA drives offer a jumper to slow down the bus speed so older machines can support them. Until the unibody models, only the 17" MacBook Pro supported higher than 9.5mm drive heights..
If the drive in question has to be thinner, naturally it might cost more because of the shrinking of components..
Slower speed SATA drives are becoming less common, thus can become more expensive as supply is outweighed by demand.
Before you jump the SSD bandwagon, remember, there is no technology that can totally wipe the drive, unlike with platter drives. If your machine is sold in the future, be sure not to put any personally identifying data on it, once you switch to SSD, unless they erasing technology improves. .

Upgrading Santa Rosa MBP HDD

Similar Messages

Maybe you are looking for