Jump to content
3 posts in this topic

Recommended Posts

SOLVED

The problem happens due to wrong bios settings

Wrong bios setting with vanilla kernel leads to continuous rebooting

So I have to enter CPUS=1 while booting

 

After changing these field I dont have to set CPUS=1

And my computer recognize one cpu with 2 cores now

 

MAX CPUID VALUE Limit : Disabled

Vanderpool or virtualization : Disabled

CPU TM Function : Enabled

Excecute Disable Bit (or called NX or XD on some mobos) : Enabled (the most

important, if not enabled the result is reboot loop with vanilla kernel)

 

ACPI 2.0 Support : Enabled

ACPI APIC : Enabled

 

 

Original Post

My hardware:

E6750

Asus P5KR

Gigabyte 8600GT 256 mb

2G*2 DDR800

A USBDAC sound card

A Realtek RTL8139 based Network card

 

My install settings: Vanilla Kernel and ACPI Platform Fix and EFI MBR

 

Everything works excellent(after buying a 8600GT to replace my HD2400XT)

Since it keeps rebooting, I have added CPUS=1 in the if com.apple.Boot.plist

now in the system profiler it says that this is a Mac Pro with 2.67Ghz

"number of processors: 0, number of cores: 1"

The activity monitor also shows only one core active.

 

Is there anything I can do or any setting I can change to fix this?

(I've done my best to search the solution of this problem

so, please forgive me if I'm asking some old questions.)

 

thanks a lot!

and sorry for my poor english if I make any grammar mistake.

would u like to share ur solution? thx a million in advance!

 

The reason I have to enter "CPUS=1" is the setting in my bios is not correct.

It keeps rebooting if I dont add CPUS=1.

This parameter "CPUS=1" seems to cause leopard fail to recognize the cpu.

After changing the bios to the correct setting

I can boot smoothly without entering CPUS=1

and the system can recognize my processor and cores now

 

Maybe you should check your bios if it's correctly set.

If your bios is correct and you can boot without CPUS=1, you still cant get leopard to recognize your processor. Maybe you're not facing the same problem I got.

×
×
  • Create New...