Help

Current version by rousp,

Text:

== Update ==
 
I'm not very sure about this.. Think that the narcoleptic solutions is less plausible now.. Very good writeup by the way..
 
When it works with external display all the time, and with the internal at startup I feel that your solution might just lie between the GPU and the internal display.
 
My logic is that the GPU isn't used before the final phases of the boot (this is an assumption). Then, when the GPU tries to send it's signal to your internal it get some sort of error that causes it to crash. Maybe a short somewhere? A short fits your story about a tea entering the machine...
My logic is that the GPU isn't used before the final phases of the boot (this is an assumption). Then, when the GPU tries to send it's signal to your internal it get some sort of error that causes it to crash. Maybe a short somewhere? A short fits your story about a tea entering the machine...
 
The reason that it does not crash when it's on the external monitor is that the fault lies after the signal for the external is separated from the signal to the internal.
 
Then again this logic could be applied to any number of things that is not activated until the final phases of the boot and is not activated when using an external display.
 
But I can not stress enough that this is very much based on assumptions... Do not shoot me if the problem is something very different... ;)
 
== Not very plausible me thinks ==
 
Digging up this thread.
 
To me thins sound like the narcoleptic MacBook syndrome.
 
You can read about it here:
 
http://www.ifixit.com/Answers/View/21756/How+do+I+diagnose+a+narcoleptic+Mac
 
When the tea was sucked into the machine it might just shorted out the ambient light sensors.

Status:

open

Edit by rousp,

Text:

== Update ==
 
I'mI'm not very sure about this.. Think that the narcoleptic solutions is less plausible now.. Very good writeup by the way..
I'mI'm not very sure about this.. Think that the narcoleptic solutions is less plausible now.. Very good writeup by the way..
 
When it works with external display all the time, and with the internal at startup I feel that your solution might just lie between the GPU and the internal display.
When it works with external display all the time, and with the internal at startup I feel that your solution might just lie between the GPU and the internal display.
 
My logic is that the GPU isn't used before the final phases of the boot (this is an assumption). Then, when the GPU tries to send it's signal to your internal it get some sort of error that causes it to crash. Maybe a short somewhere?
The reason that it does not crash when it's on the external monitor is that the fault lies after the signal for the external is separated from the signal to the internal.
My logic is that the GPU isn't used before the final phases of the boot (this is an assumption). Then, when the GPU tries to send it's signal to your internal it get some sort of error that causes it to crash. Maybe a short somewhere?
The reason that it does not crash when it's on the external monitor is that the fault lies after the signal for the external is separated from the signal to the internal.
 
ThenThe reason that it does not crash when it's on the external monitor is that the fault lies after the signal for the external is separated from the signal to the internal.

Then
again this logic could be applied to any number of things that is not activated until the final phases of the boot and is not activated when using an external display.
ThenThe reason that it does not crash when it's on the external monitor is that the fault lies after the signal for the external is separated from the signal to the internal.

Then
again this logic could be applied to any number of things that is not activated until the final phases of the boot and is not activated when using an external display.
 
But I can not stress enough that this is very much based on assumptions... Do not shoot me if the problem is something very different... ;)
 
==Not== Not very plausible me thinks==thinks ==
==Not== Not very plausible me thinks==thinks ==
 
Digging up this thread.
 
To me thins sound like the narcoleptic MacBook syndrome.
 
You can read about it here:
 
http://www.ifixit.com/Answers/View/21756/How+do+I+diagnose+a+narcoleptic+Mac
 
When the tea was sucked into the machine it might just shorted out the ambient light sensors.

Status:

open

Edit by rousp,

Text:

== Update ==
 
I'm not very sure about this.. Think that the narcoleptic solutions is less plausible now.. Very good writeup by the way..
 
When it works with external display all the time, and with the internal at startup I feel that your solution might just lie between the GPU and the internal display.
 
My logic is that the GPU isn't used before the final phases of the boot (this is an assumption). Then, when the GPU tries to send it's signal to your internal it get some sort of error that causes it to crash. Maybe a short somewhere?
The reason that it does not crash when it's on the external monitor is that the fault lies after the signal for the external is separated from the signal to the internal.
 
Then again this logic could be applied to any number of things that is not activated until the final phases of the boot and is not activated when using an external display.
 
But I can not stress enough that this is very much based on assumptions... Do not shoot me if the problem is something very different... ;)
 
==Not very plausible me thinks==
 
Digging up this thread.
 
To me thins sound like the narcoleptic MacBook syndrome.
 
You can read about it here:
 
http://www.ifixit.com/Answers/View/21756/How+do+I+diagnose+a+narcoleptic+Mac
 
When the tea was sucked into the machine it might just shorted out the ambient light sensors.

Status:

open

Original post by rousp,

Text:

Digging up this thread.<br /> <br /> To me thins sound like the narcoleptic MacBook syndrome.<br /> <br /> You can read about it here:<br /> <br /> http://www.ifixit.com/Answers/View/21756/How+do+I+diagnose+a+narcoleptic+Mac<br /> <br /> When the tea was sucked into the machine it might just shorted out the ambient light sensors.

Status:

open