[AboutSystem] Core 2 Quad is detected as Core 2 Extreme

[diver]

cat /var/log/syslog | grep CPU

KERN: CPU 2: type 0 family 6 extended_family 0 model 7 extended_model 1 stepping 10, string 'GenuineIntel'
KERN: CPU 1: type 0 family 6 extended_family 0 model 7 extended_model 1 stepping 10, string 'GenuineIntel'
KERN: CPU 3: type 0 family 6 extended_family 0 model 7 extended_model 1 stepping 10, string 'GenuineIntel'
KERN: CPU 2: vendor 'Intel' model name 'Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz'
KERN: CPU 3: vendor 'Intel' model name 'Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz'
KERN: CPU 2: features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov KERN: pat pse36 clfsh ds acpi mmx fxsr sse sse2 ss htt tm pbe sse3 monitor dscpl est tm2 
KERN: CPU 1: vendor 'Intel' model name 'Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz'
KERN: CPU 3: features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh ds acpi mmx fxsr sse sse2 ss htt tm pbe sse3 monitor dscpl est tm2 
KERN: CPU 1: features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh ds acpi mmx fxsr sse sse2 ss htt tm pbe sse3 monitor dscpl est tm2 

[v]

Similar problem as ticket:3541.

Options as far as I can tell: -use the model name string. -differentiate based on number of cores -find out if reported amount of cache is useful for differentiation.

[v]

Patch attached to ticket:3541

[stippi]

/*

• Copyright 2008-2009 Haiku Inc. All rights reserved.
• Distributed under the terms of the MIT License. *
• Authors:
• Pieter Panman */

[stippi]

Seems I must have used Command-V where I wanted to use Command-C. Sorry. This should be fixed in hrev33462. Please re-open if it's not.

[diver]

Tested hrev33462 and it's still the same, reopening.

[diver]

In hrev33462 sysinfo is now telling me that I have Core 2 Extreme, while before it was Intel Core 2 Quad CPU.

[v]

Diver, could you attach the new sysinfo ? (don't replace the older one)

[stippi]

Maybe it works better now with hrev33470?

[diver]

Tested hrev33470 and same thing still.

[diver]

sysinfo from VirtualBox

[v]

I don't think VirtualBox supports cpuid. If you're going to run Haiku in a virtual machine, I don't think you have any right to complain that the displayed cpu string doesn't match that of your real machine.

[v]

Replying to v:

I don't think VirtualBox supports cpuid.

... processor strings in cpuid.

[diver]

First sysinfo and screenshot were taken from real hardware, later I noticed that VirtualBox display the same cpu string, so I thought it's ok to use sysinfo from VirtualBox too. Unfortunately, Haiku doesn't boot on my hw anymore due to #4399.

[v]

Okay. I hope #4399 gets resolved soon so that you can test AboutSystem properly ;-)
I'm tempted to set the "Blocked By" field..

[korli]

diver, is it still with us ? The code looks like it should display Core 2.

[diver]

Yes, it's still here, but I can only test in VirtualBox.
Windows XP SP3 running on this PC in VirtualBox detects it as Core 2 Quad (as it should).
Haiku detects it as Core 2 Extreme.

[diver]

Tested hrev36332 and now it's detected as Intel Pentium.

[korli]

It wasn't intended. Could you try to add the following to headers/private/shared/cpu_type.h after the block

case B_CPU_INTEL_PENTIUM_CORE_2_45_NM:
   get_cpuid_model_string(cpuidName);
   printf("cpuidName: %s\n", cpuidName);

then rebuild sysinfo (jam sysinfo) and run it. Thanks!

[diver]

svn diff

Index: headers/private/shared/cpu_type.h
===================================================================
--- headers/private/shared/cpu_type.h   (revision 36332)
+++ headers/private/shared/cpu_type.h   (working copy)
@@ -189,6 +189,7 @@
                        return "Core 2";
                case B_CPU_INTEL_PENTIUM_CORE_2_45_NM:
                        get_cpuid_model_string(cpuidName);
+                          printf("cpuidName: %s\n", cpuidName);
                        if (strcasestr(cpuidName, "Core") == NULL)
                                return "Pentium";
                        if (strcasestr(cpuidName, "Celeron") != NULL)

[diver]

sysinfo

[Disreali]

I am experiencing similar issue now. Using hrev36336 on real hw.

/boot/home> cat /var/log/syslog | grep CPU
KERN: CPU 0: type 0 family 6 extended_family 0 model 15 extended_model 0 stepping 11, string 'GenuineIntel'
KERN: CPU 0: vendor 'Intel' model name 'Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz'
KERN: CPU 0: features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh ds acpi mmx fxsr sse sse2 ss htt tm pbe sse3 monitor dscpl est tm2 
KERN: setting up apic for CPU 0: apic id 0, version 327700
KERN: CPU 1: type 0 family 6 extended_family 0 model 15 extended_model 0 stepping 11, string 'GenuineIntel'
KERN: CPU 3: type 0 family 6 extended_family 0 model 15 extended_model 0 stepping 11, string 'GenuineIntel'
KERN: CPU 2: type 0 family 6 extended_family 0 model 15 extended_model 0 stepping 11, string 'GenuineIntel'
KERN: CPU 3: vendor 'Intel' model name 'Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz'
KERN: CPU 2: vendor 'Intel' model name 'Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz'
KERN: CPU 3: features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh ds acpi mmx fxsr sse sse2 ss htt tm pbe sse3 monitor dscpl est tm2 

Including sysinfo and AboutSystem screenshot.

[v]

Disreali, in your case it's intentional; hrev33646 Your Core 2 Quad is still a Core2 (and the Quad part is noted by the line above "4 processors").

[stpere]

Hi Diver,

Could you test hrev42405? Thank you!

[diver]

I can't check this PC right now, but my

model name	: Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz+

is now detected as:

Intel Core 2

[diver]

The one from the description

model name      : Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz

now also detects as:

Intel Core 2

[diver]

Still here in hrev44635.

[pulkomandy]

Is there something we should do here? I think detecting as "Intel Core 2" is intentional, the full information is in sysinfo if needed, and it's better to have a generic model name as we're never sure what Intel marketing will do with the model names.