how do i boot without cpus=1 ?

[spalek83]

Typically I have to boot with cpus=1 to avoid mouse/system lag/stutter. On advice I've booted with cpus=2 and it has worked twice, following posts explain what happen but basically it doesn't seem to work every time.. yet?

with both cores osx is almost unusable. soo slow, but the slowness is worse or less depending on the minute, so its always fluctuating

so this problem doesn't happen if I boot with cpus=1. How do I fix it so i can boot with both cores?

I have done marvins amd patcher on /system/library and did patching at boot. do i need to do cpuid patching on more then /system/library?

using cham rc3, back to mach_kernel.test7
kexts in extra/extensions are
smbios.plist
AppleUpstreamUserClientDisabler.kext
Disabler.kext
fakesmc.kext v2
NullCPUPowerManagement.kext
OpenHaltRestart.kext

Also using azalia from iatkos v7 for audio


--------------------
10.6.1 ~ iATKOS v7 10.5.7 ~ Win 7 RTM
AMD 3800+ x2
MSI K8NGM2-FID Nforce 4, ALC880
8500 GT

[Taisto]

That's the "Dual Core" bug. Unless we'll have a kernel with cpu_ids patching - You have to stick to cpus=1 mode. Unless someone knows any solution to this. If not ( and probably that's the case ) we'll just have to wait.

[spalek83]

i find that every 1/100 tries, if i shutdown from a session of snow with cpus=1, and boot back into osx without the cpus=1 flag, I get a working snow with both 2 cores of my 3800+ x2 working with no bug/lag/stutter.

But if i shut down and reboot, the bug/lag/stutter is back. and i can't repeat it reliably, only done it twice. most of the time the bug is allways there with a 2 core amd environment

[xXrkidXx]

sometimes ive heard of people being able to boot using cpus=2 ot sure if it applies to a core2 duo tho,. you could give it a try.

[spalek83]

the cpus=2 worked on this boot. have both cores working and no mouse/lag/stutter.
awesome
[UPDATE] It seems that after many hours the cpus=2 flag made my system shutdown and reset my powercenter at the same time.. no so sure about that,, I explain more in post 39 below. Basically remade dsdt.aml and removed AppleRTC and got boot with cpus=1 with no bug.

thanks !!!


to taisto, does it work for you with cpus=2 as well?

[xXrkidXx]

mhm :) no problem, always happy to help

EDIT

you may get KP's sometimes... just keep trying. it will eventually boot with both working.

[Taisto]

Unfortunately no - cpus=2 gives me the same as no flag at all. After 1,5 - 2 hours system starts to work badly ( sound distortion, mouse getting "jumpy" etc. ). I had the same issue with pre-voodoo leopard.

[punk_zappa]

Can you extract a DSDT.aml?

[spalek83]

the cpus=2 flag doesn't always work for me. I had my computer running on it last night downloading off newsgroups, and when I woke up my power center had shut everything down like there was a spike... then I rebooted in cpus=2 and bug was there, then booted into cpus=1 and bug is there as well.. WTF!!! So it seems whatever is going on is left in some sort of memory inside osx. Is there anything I can reset on boot that might control this?

[UPDATE] I remade dsdt.aml from inside of snow, rebooted into cpus=1 and mouse bug was gone. In the instructions of the dsdt patcher it said it would make it so I could boot with then removed AppleRTC.kext & AppleCPUPowerManagement.kext running (no disabler), but when I tried that I got kernel panic at boot. I then removed AppleRTC.kext as well as put NullCPUPowerManagement.kext back into /Extra/Extensions
So I booted into cpus=1, no bug, yet system info says 2 cores, why?

THIS BELOW IS WITH CPUS=1 !!!! Why does it say 2 cores? Are both cores being used?

Hardware Overview:

Model Name: Mac Pro
Model Identifier: MacPro2,1
Processor Speed: 2.08 GHz
Number Of Processors: 1
Total Number Of Cores: 2
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MP21.005C.B01
SMC Version (system): 1.30f3
Serial Number (system): SOMESRLNMBR
Hardware UUID: 00000000-0000-1000-8000-001346E34902

This stays the same on reboot back into cpus=1. It shows both cores in system properties. Is it possible that it is showing both cores in system properties, but in reality it is not using both cores, how would I check that?
Istat menus shows only 1 processor/core's stats.. wonder where else I could look. maybe it is just reporting 2 cores from before, but in reality the second one is not in use??

[xXrkidXx]

it shows 2 cores, 1 is active.

[spalek83]

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?

[xXrkidXx]

just keep trying to boot with it. It will eventually work. Im not sure about what happend before though.. power outage?

[spalek83]

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?

[xXrkidXx]

no idea but im pretty sure using the flag has never damaged anybodys comp before.

[spalek83]

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.

[spalek83]

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 :(