[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 19/06/11 12:51, Neil Winchurst wrote:
tom wrote:On 19/06/11 12:21, tom wrote:cat /etc/procinfooh hang on that should be cat /proc/cpuinfo
ah thanks, i knew it was something like that. paul
Please note for anyone doing compilations the flags data listed is really useful as sometimes builds are configured for the original designers machine and may compile in things that your cpu cant handle - and that can be a real bugger to debug... Tom te tom te tomRight. Here is the output processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz stepping : 10 cpu MHz : 1603.000 cache size : 3072 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yesflags : 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 lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexprioritybogomips : 5866.93 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: Is that useful? Neil
-- Paul Sutton Cert SLPS (Open) http://www.zleap.net 17th September 2011 - Software freedom day -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq