Q: New Retina Macbook pro 13 Haswell system hang/unresponsive

Two issues remain that have not been addressed here in the last few days since the firmware release was made available (as far as I can tell):

1. A number of users reporting here have stated that their machines characterize the RAM chips as "DDR3" when in fact the 13" machines from late-2013 are supposed to have DDR3L.

2. A number of users reporting here have stated that their machines have screens that were manufactured in 2012.

As far as I know, neither of these is an issue with the 15" machines. I would really like to know if #1 and #2 above are still issues with the 13" machines being sold.

I see also DDR3, not DDR3L.

as we talk about the screen, i run various test and no ghosting so far at all.

Alrighty then haha thanks for the info guys, appreciate it

 

1. A number of users reporting here have stated that their machines characterize the RAM chips as "DDR3" when in fact the 13" machines from late-2013 are supposed to have DDR3L.

 

2. A number of users reporting here have stated that their machines have screens that were manufactured in 2012.

 

1 & 2 are offtopic in this thread. Start a new thread for those questions.

Yup.

What he said.

I now love my new 13 inch Pro.

Case closed - moving on.

Bye

multispacy wrote:

 

I have the new Macbook Pro 13 inch retina as well (256 GB SSD version) and I have downloaded the EFI update earlier today and got the message that the power adapter should be connected and that after that has been done at a next restart the firmware update would take place (at least that's what I believe I read).

 

But later on, when I connected the power adapter and restarted, no firmware update would take place. If I look in the installed software in the Software Information (via About this Mac), it says that the EFI update is installed.

 

So now I'm confused, because I didn't see it happening.

 

Could someone with the same Macbook Pro who had a succesfull update of the EFI, check what their Boot ROM version and SMC version is?

 

These are mine:

Boot ROM Version:	MBP111.0138.B03
SMC Version (system):	2.16f58

 

Thanks a lot!

Hi man,

Mine is exactly the same with yours after installing the EFI Firmware Update.

But I did have seen the progress bar while installing the EFI Firmware Update after restarting.

Maybe you can check with others who haven't updated yet as these version numbers may not changed any more.

ReMo77 wrote:

 

What happened here is objectively not a big deal. Nasty Issue -> Firmware update -> Happy life

 

Explanations in detail is not what Apple is going to do. Since they fixed it, this file is now closed.

 

Apple did their job as expected. Nothing more, nothing less. Information level not higher than necessary. Following textbook procedures. So there won´t be any details from Apple. Details are not for the public.

 

btw:

No way they would sell obviously faulty hardware and then try to fix it by software updates on the sly. Earlier or later, someone would find out about ... and game over. Just imagine the press releases. There are enough freaks out there literally anatomizing their macs all up and down and showing up on YouTube. So don´t worry.

Very good and very true comment. Two thumbs up.

gaolei33 wrote:

 

multispacy wrote:

 

Could someone with the same Macbook Pro who had a succesfull update of the EFI, check what their Boot ROM version and SMC version is?

 

These are mine:

Boot ROM Version:	MBP111.0138.B03
SMC Version (system):	2.16f58

 

Thanks a lot!

Hi man,

 

Mine is exactly the same with yours after installing the EFI Firmware Update.

But I did have seen the progress bar while installing the EFI Firmware Update after restarting.

Maybe you can check with others who haven't updated yet as these version numbers may not changed any more.

Since mine is sitting here and waiting to get replaced (not because freezes, but because of the display), I did not update the EFI.

It says:

Boot ROM Version MBP 111.0133.800

SMC Version (system) 2.16f58

As you can see, Boot ROM is different.

Your update was done, simply silent for some reason. I wouldn't get nervous about it.

RIVERSTALKER wrote:

 

i just gave mine back and will get my money back, apple service was briliant in munich store but nobody could tell me a thing about the 13 inch problems. i wait a few weeks and hope everything is ok then.

 

i dont know if it is absolutely save to buy a mac these days. they seem to have problems with mavericks and maybe maybe some hardware issues too. but nobody really knows.

 

for me i checked out the keyboards in the apple store and they are really different. each model i was typing felt different and the arrow buttons at the right side were sometimes ratteling like **** and others were just fine.

this is crap in my eyes, this is apple and the keyboard was allways one of their highlights.

now you just have to be the lucky one that receives a good keyboard. its a shame when some buttons are ratteling and others not. this is a premium product or at least should be one.

 

anyway, i would never buy this notebook with 4gb ram. you can not upgrade yourself and 4gb is way to unsave for the next 3 or 4 years. ssd memory depends on your likes but 8gb ram is the minimum.

Great to hear the service was good. I experienced the same when calling them.
I wouldn't wait weeks.

It is safe to buy one. You just saw today that it is safe. If you're not getting what you expected, you give it back. Otherwise you can simply be happy with that great new MacBook.

Apple is a professional company with a very high reputation. Anyone here seriously think, they would risk that reputation for a couple of millions of dollars? Nonsense. If there would be a serious hardware problem, they would not simply put out a software fix and otherwise keep silent on it.

All MacBooks I ever typed on had a keyboard that I felt normal and good. So this differs a bit from your experience today. Don't know about it. But on the other hand, this topic did not come up before, so I don't really know. Maybe other people are not as sensitive as you.

Once you got your money back, place an order for a new one. That's by far better than waiting weeks or months for some mysterios "second batch", of which you don't know whether it does exist or ever will.

Oli.S72 wrote:

 

gaolei33 wrote:

 

multispacy wrote:

 

Could someone with the same Macbook Pro who had a succesfull update of the EFI, check what their Boot ROM version and SMC version is?

 

These are mine:

Boot ROM Version:	MBP111.0138.B03
SMC Version (system):	2.16f58

 

Thanks a lot!

Hi man,

 

Mine is exactly the same with yours after installing the EFI Firmware Update.

But I did have seen the progress bar while installing the EFI Firmware Update after restarting.

Maybe you can check with others who haven't updated yet as these version numbers may not changed any more.

Since mine is sitting here and waiting to get replaced (not because freezes, but because of the display), I did not update the EFI.

 

It says:

Boot ROM Version MBP 111.0133.800

SMC Version (system) 2.16f58

 

As you can see, Boot ROM is different.

 

Your update was done, simply silent for some reason. I wouldn't get nervous about it.

Hi Oli,

Thanks for sharing:)

You must be a warm-hearted man.

Hi Oli,

 

Thanks for sharing:)

You must be a warm-hearted man.

You're welcome.

According to sTrollnic, I work for NSA, KGB and Apple

Paapaa wrote:

 

Oli.S72, don't mind sTronic. But it would be interesting to know how often you get the log events with your older computer? Do you get them always when touching it after a few second pause. Or less often? Can you figure out what situation causes the events?

 

And there is nothing odd that you get always 2 events: As can be clearly seen from the log: the other is form hub and the other is from the keyboard itself.

Right now, I do not get them at all.
No USB device plugged in, running on battery. Even if I wait 10 seconds, no log entries.

Very hard to reproduce.

Guess it's those "rare circumstances" Apple was writing about, lol.

I'll keep an eye on my log and let you know what happens.

Since I was curious, I searched through the older (gzipped by logrotate) system.log logfiles. Here is what I found:

Nov  8 09:15:22  kernel[0]: The USB device Keyboard Hub (Port 2 of Hub at 0x26000000) may have caused a wake by issuing a remote wakeup (2)

Nov  8 09:15:22  kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x26200000) may have caused a wake by issuing a remote wakeup (3)

Nov  6 08:48:07  kernel[0]: The USB device Keyboard Hub (Port 2 of Hub at 0x26000000) may have caused a wake by issuing a remote wakeup (2)

Nov  6 08:48:07  kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x26200000) may have caused a wake by issuing a remote wakeup (3)

Nov  5 08:55:24  kernel[0]: The USB device Keyboard Hub (Port 2 of Hub at 0x26000000) may have caused a wake by issuing a remote wakeup (2)

Nov  5 08:55:24  kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x26200000) may have caused a wake by issuing a remote wakeup (3)

Nov  4 09:19:25  kernel[0]: The USB device Keyboard Hub (Port 2 of Hub at 0x26000000) may have caused a wake by issuing a remote wakeup (2)

Nov  4 09:19:25  kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x26200000) may have caused a wake by issuing a remote wakeup (3)

I seems to happen once a day (but not every day, November 7th is missing) and always in the morning, some time after I started working.

Now, please do not ask me, what is this about ...

Is it safe?  Is it safe?  The dentist says it's safe. 

Anybody know if the 13"rMBP has a TLS chip?  I'm gonna look, but if someone knows for sure I won't bother.