 |
|
#11
10-23-2009, 11:06 PM
|
||||
|
||||
|
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? 
|
|
#12
10-23-2009, 11:08 PM
|
|||
|
|||
|
just keep trying to boot with it. It will eventually work. Im not sure about what happend before though.. power outage?
Computer: Gateway 838GM | 9.5.0 Vodoo Kernel |2.0 RC4 Chameleon Bootloader | Processor:Intel Pentium 4 630 / 3 GHz | RAM: 512MB | OS: Windows 7 32BIT, OSx86 iPC 10.5.6 | Mainboard Chipset: Intel 915G Express | Graphics Card:Integrated Intel GMA 900 | Video Memory: Dynamic Video Memory Technology 3.0 | Audio:ALC 860 |Card Reader:8 in 1 Integrated| Hard Drives:1x 200GB SATA(Win 7), 1x 320GB SATA(OS X) Both Internal
|
|
#13
10-23-2009, 11:12 PM
|
||||
|
||||
|
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?
|
|
#14
10-23-2009, 11:15 PM
|
|||
|
|||
|
no idea but im pretty sure using the flag has never damaged anybodys comp before.
Computer: Gateway 838GM | 9.5.0 Vodoo Kernel |2.0 RC4 Chameleon Bootloader | Processor:Intel Pentium 4 630 / 3 GHz | RAM: 512MB | OS: Windows 7 32BIT, OSx86 iPC 10.5.6 | Mainboard Chipset: Intel 915G Express | Graphics Card:Integrated Intel GMA 900 | Video Memory: Dynamic Video Memory Technology 3.0 | Audio:ALC 860 |Card Reader:8 in 1 Integrated| Hard Drives:1x 200GB SATA(Win 7), 1x 320GB SATA(OS X) Both Internal
|
|
#15
10-23-2009, 11:32 PM
|
||||
|
||||
|
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. Last edited by spalek83; 10-23-2009 at 11:48 PM.
|
|
#16
10-27-2009, 04:34 AM
|
||||
|
||||
|
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  💡 Deploy cloud instances seamlessly on DigitalOcean. Free credits ($100) for InfMac readers. Last edited by spalek83; 10-27-2009 at 04:54 AM.
|
Linear Mode
