![]() |
aww, i was hoping that wasn't the case. thanks for clarifying
damn. any idea of why cpus=2 worked for several hours and not all the time? |
just keep trying to boot with it. It will eventually work. Im not sure about what happend before though.. power outage?
|
what makes you think it will eventually work?
Is cpus=2 burning anything into the cpu, creating new files, modifying files while it is enabled? Or something else besides just setting a force instruction for 2 cores enabled? |
no idea but im pretty sure using the flag has never damaged anybodys comp before.
|
so i booted back into osx with cpus=2 again
this boot there is no bug, and istat shows 2 cores working. I'll let you know how it goes. Also, is there any sort of event log so if/when it does crash I can see what messages were given by system as warning before the shit hit the fan? cpus=2 worked again on second reboot. |
For some reason, without reason it just decides to have the dual core timing bug every once in a while. I can get days and multiple boots working fine with cpus=1, cpus=2 and no flag at all. Last run I didn't install anything, nothing was changed... Then I boot up today and the bug is there, and it dosn't go away when i boot with cpus=1, the dual core timing bug happens even with one core.. I wonder what could be making that happen...
so i switch kernels to qoopz and it worked again. I feel like I am playing musical chairs, with no chairs or music :( |