Search the Community

root@sysresccd /root % lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Model name: Intel(R) Pentium(R) CPU G630 @ 2.70GHz Stepping: 7 CPU MHz: 1699.365 CPU max MHz: 2700.0000 CPU min MHz: 1600.0000 BogoMIPS: 5387.66 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 3072K NUMA node0 CPU(s): 0,1 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm epb tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm arat pln pts root@sysresccd /root % gcc -march=native -Q --help=target | grep march -march= sandybridge This processor is clearly a sandybridge processor, but when it comes time to chroot into a fresh install on my system this subarch is not the right one. I could not find wether this is constitutes a bug or some sandybridge cpus are less capable than others or different in some fundamental way. My question is: is this something that I can fix myself? And, how would I go about it? (I think it's time I get involved with my system on a deeper level.) If nothing can be done, I will just continue using the generic 64 image.