Macbook Pro Mid 2007 17 Inch - Mavericks hangs after starting.

No, the point is, if you have an old Macbook Pro, don't upgrade. Not yet. Wait until 10.9.1 is out, and the issues with your computer have been confirmed fixed. Or until you absolutely must for some reason.

You are always asking for trouble installing the first released version of any OS upgrade; more so when you have an older computer.

Ok, understand, but It annoying that can't also upgrade to 10.8.5

Thank you

Thank you !

I was beginning to get crazy ... 😢

This confirm what I have read somewhere else in this thread :

wait a n.1 version and don't run for the n.0, in particular when you own a old computer ...

I confirm that the problem occures as soon as I plug my old MacBookPro 3,1 to an ethernet network,

or a little time after I turn off airport, and that it never occures when Airport is on!

I followed your advice and disabled ipv6 but only on ethernet and my computer behave perfectly for the moment.

How a so huge failure can get through the test processes ? (I can't believe there isn't any in Cupertino's Labs)👿

Many thanks to Xiao Doudou and rajsayshai who initited this thread.

😍

Sébastien

(this post was wrote on a very old Powerbook G4 Titanium 1GHz running OsX 10.4)

The model MBP you have was notorious for problems with the graphics chip. I had the Late 2007 MBP too, and had to have the logic board replaced due to a failure. It is possible that your system is experiencing hardware issues. If you have an Apple Store nearby, you might setup an appointment with the Genius Bar. THey can run diaagnostics for you for free to determine if you have hardware issues. If they do find issues, they will let you know what it wold cost to repair and you will have the choice to have them do the work or not.

I also had this problem. Leaving wifi on all of the time fixes it.

Thanks a lot GeekBoy,

but my model actually had this graphic chipset problem two or three years ago and had its motherboard replaced for free by Apple after I finally found the cause (thanks to all the threads on various forums 😍) and brought my machine to an approuved Apple reseller who confirmed this diagnosic (there was no AppleStore in Strasbourg, France, by that time 😢)

Working fine after this replacement still with Snow Leopard until Mavericks update.

I confirm that leaving airport on or disabling ipv6 on ethernet prevents Mavericks from freezing.

(Thanks again to Xiao Doudou)

The processors are not overheating any more since ipv6 on ethernet has been disabled.

And from what I read here and there, MacBookPros 3,1 are not the only one affected by Mavericks' freezing.

Best regards

Sébastien

MBP 2012 with 8GB memory, 17", highest MBP in the market, i7 and i am getting the same problem, the laptop hangs ever few minutes for about 10 to 30 seconds. I can move the mouse, but nothings is clickable, even though the clicks are registered and after the freeze, the clicks are applied!

I am conntect on a local network through ethernet and the internet through the wifi. Can't do without the local network as i have a setup to share files with other macs on the network.

I have a minimac that was also updated to Mavericks, and this is an older minimac, i guess around 2010 and it also connected to the local network and sharing files through it's ethernet port and connected to the internet through it's wifi, it didn't have this problem at all!!!!

weird!

i have tried to unplug the eathernet wire, the freeze still happens but the intervals are far apart, maybe 10 - 20 minutes apaert, once pluged back in, intervals are way more, maybe every few minutes!

What's happening to Apple after Steve is gone!

Also Apple's App Store is getting more and more like Android Market, is carrying so much junk now!

Apple seem to be turning into a scary level of decency that it used to have!

Hey raj and everyone else who participated in this thread,

I've experienced pretty much all you've written in here. I was wondering if anything changed for you guys after the last update released by Apple. Please let me know.

Thanks!

Hi CassHeger,

I did not upgrade yet as I am afraid to do it. So far I am using my Macbook Pro Mid 2007 with wi-fi turned on constantly, and even I can use ethernet BUT through USB adapter ( not using ethernet port itself ). Everything works fine so I do not see the need to upgrade. My advice - never upgrade without actual time machine copy of your entire staff.

All the best,

Kostarson

Hello CassHeger,

I've done it !

But this problem has not been corrected ...

I have a MacBookPro 3,1 (15" 2,4Ghz late 2007)

I already had a hanging problem with the first Mavericks version :

everything was allright until I turned off Wifi and worked with the ethernet socket.

So I apply what Xiao Doudou said upper in this thread

Re: Macbook Pro Mid 2007 17 Inch - Mavericks hangs after starting.

and it worked perfectly for the first Mavericks install.

It seems that Mavericks is not ipv6 friendly over internet on MBP 3,1.

It seems that the last Mavericks update activated ipv6 again (or reset this parameter), so the same problem occured at the first restart :

computer hanged either on the apple logo screen, or the blue screen before office screen or very shortly after the office screen had appaered.

I confirm that before I deactivated ipv6 again, when I was using Wifi everything worked fine, but as soon as i dturned off the wifi with the ethernet wire pluged in, the computer hangs : pointer hanges, keyboard hangs, nothing you can do appart from a hard reboot !

So thanks again to Xiao Douodou for his post and advice.

I hope that Apple computer will correct this issue pretty soon now.

Happy X-Mas to all

Sébastien

Thought I'd add my experience to this thread:

Symptoms

- Mid-2007 MBP, started freezing after upgrading from Snow Leopard to Mavericks.

- Freeze often starts as a non-responsive web browser, followed by spinning beachball. During this time the computer becomes non-responsive except for mouse movement and occasionally the ability to move between windows.

- Usually becomes un-frozen after 10-15 minutes. At this point every mouse/keyboard action taken during the freeze is executed in rapid succession.

Fixes That Didn't Work

- Took it to the Apple Store. Genius Bar claims this is not a known issue. Suggested I first reinstall Mavericks, and if that doesn't work, erase the HD and do a clean install.

- Reinstall didn't fix anything. Based on user comments here (and similar threads), I decided not to waste my time doing a clean install.

- Keeping WiFi turned on and unplugging Ethernet seemed to decrease the problem's frequency, but did not solve it.

Fixes That Seem to Work

- "Turned off" spotlight indexing by removing all disk locations from the spotlight indexing preferences. Also used sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

to remove spotlight entirely. FYI Spotlight can be reinstalled with sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

- Disabling/removing Spotlight seems to fix the problem, as long as WiFi is turned on and connected.

- As a Spotlight alternative, I installed the Spotlight alternative called Found. It works great, but doesn't seem to return folders in the search results. Hopefully I'm just missing something in the preferences.

Ongoing Concerns & Uncertainties

- When I turn off WiFi and use Ethernet, the problem returns.

- Haven't determined whether WiFi needs to be connected to a network, or just enabled.

- Haven't determined whether Ethernet connection contributes to the problem, or it's just isolated to WiFi.

- I understand that disabling/removing Spotlight may have unintended consequences, because of the multitude (and increasing number) of apps that use the Spotlight index for their normal operation.

Hope that helps.

I have been testing the MBP with an external USB disk with OS X 10.9.1.

I have a WiFi network at home, so it's configured and connected. I also connected to the Ethernet network, and the system works fine.

** If I turn WiFi off, I get immediately a kernel panic, so the Mac freezes and need to force shutdown by pressing the power button until it does.

With this update, the system is benevolent. When I turn the Mac on again, it recovers with WiFi on, as it was before the kernel panic. Earlier versions corrupted badly the system, forcing me to start from scratch again.

I've tried to disconnect the Ethernet cable, and apparently it doesn't cause problems.

So basically, I'm using the Mac with WiFi enabled, and Ethernet plugged in. TimeMachine backups are much faster with Ethernet than on WiFi. I have a newer MBP and WiFi is much faster I barely use Ethernet for TimeMachine backups. The wireless network difference is noticeable.

I'm trying to get a kernel core dump by connecting both Macs with a FireWire cable. Normally the core dump can be done with Ethernet, but since it seems to be compromised by this problem, I'm trying FireWire IP. If I force a kernel panic I correctly get a core dump, but if the kernel panic is triggered by switching WiFi off, I don't get the core dump. I'm trying to get help on this subject.

Apple is working on this problem. A kernel core dump would be great for them to figure out where the problem is.

So be patient, we're almost there.

In my case, I can say that the latest update is pretty stable, providing I don't switch WiFi off. Although my test system was just idle when the kernel panics occur, meaning that I wasn't doing something important at the moment of the freeze, and maybe work could get lost.

OS X 10.9.1 seems to be stable providing I don't play with the WiFi connection.

I use TimeMachine for regular backups, plus SuperDuper to have a clone or snapshot on an external disk.

It's much easier to restore with SuperDuper.

Hope this helps

Update:

This week the freezing started happening more often - every hour or even every 30 minutes. For 5-10 minutes at a time, the computer becomes unusable.

This is with WiFi enabled and connected, without Ethernet connection, and Spotlight disabled. So, those things which once seemed like fixes (in my post above), now seem not to be effective.

Planning to return to Snow Leopard via my SuperDuper backup.