Chance Posted February 25, 2009 Report Share Posted February 25, 2009 So I have a computer here, that for a number of reasons, mainly that Ubuntu refuses to get my screen resolution right, I have installed Mandriva on. For the most part, everything is sunshine and butterflies and I love it. For the most part. Madriva thinks my CPU speed is a good chunk less than it is- it reads the processor name right, which includes the speed it SHOULD be- 1.7 GHz-, but the speed listed is wrong. Before we go any further- it's not CPU scaling. I have the little CPU scaling monitor open, and it says 13.80GHz (100%). Yes. It's reading it as considerably more than it really is. Some info from my hardware profiles: Identification Processor ID: ‎1 Vendor: ‎GenuineIntel Model name: ‎Intel® Celeron® CPU 1.70GHz Cpuid family: ‎15 Model: ‎1 Model stepping: ‎3 Connection Vendor ID: ‎0x0000 Device ID: ‎0x0000 Sub vendor ID: ‎0x0000 Sub device ID: ‎0x0000 Performances Frequency (MHz): ‎13800.000 Cache size: ‎128 KB Bogomips: ‎3383.32 Anything you folks can do to help me? Programs that check my CPU speed, like SecondLife, claim it's too low, despite it's real speed being higher than the requirements. I'd love to have this working as it should, and you guys certainly seem to be the ones to ask. If you need any additional info, let me know, and I'll get it for you. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted February 25, 2009 Report Share Posted February 25, 2009 I don't see any problem. Your processor speed is gigahertz or GHz. Your frequency is megahertz or MHz, which is considerable less than your processor speed. Now, if that application is actually reporting 13.80GHz and not MHz, then it is just configured incorrectly and this I've seen before. When installing karamba or some other system monitoring tool, and lm_sensors hasn't been configured correctly, as well as the way the application reads the lm_sensors results, it will state incorrect results because they are incorrectly formatted. So, I think you'll find your system is OK, it's just this application reporting the data incorrectly, or that it is MHz, instead of GHz. Hope that helps. PS - Welcome to the board Quote Link to comment Share on other sites More sharing options...
tux99 Posted February 25, 2009 Report Share Posted February 25, 2009 what does cat /proc/cpuinfo typed on a console report? That's what the Linux kernel sees. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted February 25, 2009 Report Share Posted February 25, 2009 It looks like he posted that already above ;) Some at least, if not all of it for that machine. Quote Link to comment Share on other sites More sharing options...
theYinYeti Posted February 25, 2009 Report Share Posted February 25, 2009 Ian, are you sure? To my knowledge, ‎13800 MHz is indeed 13.8 GHz, or is it not? As for the CPU info, what the first post states is probably what harddrake displays, or similar info. It doesn't look like (part of) the content of /proc/cpuinfo. I think seeing this content for real would indeed shed some light of this very strange report… Yves. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted February 25, 2009 Report Share Posted February 25, 2009 Sorry, it looked similar, I assumed it was the /proc/cpuinfo my bad :) There's one more thing, install a package called x86info, and use this to give some info, this is how I used it on mine: root@esprit:/home/ian# x86info x86info v1.21. Dave Jones 2001-2007 Feedback to <davej@redhat.com>. Found 2 CPUs -------------------------------------------------------------------------- CPU #1 /dev/cpu/0/cpuid: No such file or directory Family: 6 Model: 15 Stepping: 10 Type: 0 Brand: 0 CPU Model: Core 2 Extreme [E1] Original OEM Feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflsh ds acpi mmx fxsr sse sse2 ss ht tm pbe Extended feature flags: sse3 [2] monitor ds-cpl vmx est tm2 ssse3 cx16 xTPR [15] SYSCALL xd em64t lahf_lm Cache info L1 Instruction cache: 32KB, 8-way associative. 64 byte line size. L1 Data cache: 32KB, 8-way associative. 64 byte line size. L2 unified cache: 4MB, 16-way associative. 64 byte line size. TLB info Instruction TLB: 4x 4MB page entries, or 8x 2MB pages entries, 4-way associative Instruction TLB: 4K pages, 4-way associative, 128 entries. Data TLB: 4MB pages, 4-way associative, 32 entries L0 Data TLB: 4MB pages, 4-way set associative, 16 entries L0 Data TLB: 4MB pages, 4-way set associative, 16 entries Data TLB: 4K pages, 4-way associative, 256 entries. 64 byte prefetching. The physical package supports 2 logical processors -------------------------------------------------------------------------- CPU #2 Family: 6 Model: 15 Stepping: 10 Type: 0 Brand: 0 CPU Model: Core 2 Extreme [E1] Original OEM Feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflsh ds acpi mmx fxsr sse sse2 ss ht tm pbe Extended feature flags: sse3 [2] monitor ds-cpl vmx est tm2 ssse3 cx16 xTPR [15] SYSCALL xd em64t lahf_lm Cache info L1 Instruction cache: 32KB, 8-way associative. 64 byte line size. L1 Data cache: 32KB, 8-way associative. 64 byte line size. L2 unified cache: 4MB, 16-way associative. 64 byte line size. TLB info Instruction TLB: 4x 4MB page entries, or 8x 2MB pages entries, 4-way associative Instruction TLB: 4K pages, 4-way associative, 128 entries. Data TLB: 4MB pages, 4-way associative, 32 entries L0 Data TLB: 4MB pages, 4-way set associative, 16 entries L0 Data TLB: 4MB pages, 4-way set associative, 16 entries Data TLB: 4K pages, 4-way associative, 256 entries. 64 byte prefetching. The physical package supports 2 logical processors -------------------------------------------------------------------------- WARNING: Detected SMP, but unable to access cpuid driver. Used Uniprocessor CPU routines. Results inaccurate. this can also help if /proc/cpuinfo doesn't have all the info to give. For mine it might not have worked as well since I have x86_64 distro. But it might help in conjunction with the /proc/cpuinfo. Quote Link to comment Share on other sites More sharing options...
Greg2 Posted February 25, 2009 Report Share Posted February 25, 2009 I believe that the complete output of cat /proc/cpuinfo will be very helpful here. Look at my cpu speed using x86info [greg@halfway ~]$ cat /proc/cpuinfo | grep -E -i MHz cpu MHz : 2813.285 [greg@halfway ~]$ x86info -a | grep -E -i GHz 4154503.20GHz processor (estimate). Quote Link to comment Share on other sites More sharing options...
Chance Posted February 26, 2009 Author Report Share Posted February 26, 2009 (edited) cat /proc/cpuinfo Gives me: processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 1 model name : Intel(R) Celeron(R) CPU 1.70GHz stepping : 3 cpu MHz : 13800.000 cache size : 128 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up pebs bts bogomips : 3383.34 clflush size : 64 power management: Sorry about the delay, was out all day and just got the replies. Edit: And this is what x86info gave me [chance@localhost ~]$ x86info x86info v1.23. Dave Jones 2001-2008 Feedback to <davej@redhat.com>. Found 1 CPU -------------------------------------------------------------------------- EFamily: 0 EModel: 0 Family: 15 Model: 1 Stepping: 3 CPU Model: Pentium 4 (Willamette) [E0] Processor name string: Intel(R) Celeron(R) CPU 1.70GHz Type: 0 (Original OEM) Brand: 10 (Intel® Celeron® processor) Number of cores per physical package=1 Number of logical processors per socket=1 Number of logical processors per core=1 APIC ID: 0x0 Package: 0 Core: 0 SMT ID 0 Ps- thanks for the welcome! Edited February 26, 2009 by Chance Quote Link to comment Share on other sites More sharing options...
Greg2 Posted February 26, 2009 Report Share Posted February 26, 2009 Would you please post the output of uname -a and (as root) cd /sys/devices/system/cpu/cpu0/cpufreq/; grep . * Quote Link to comment Share on other sites More sharing options...
{BBI}Nexus{BBI} Posted February 26, 2009 Report Share Posted February 26, 2009 For a nice graphical app try Hardinfo. Quote Link to comment Share on other sites More sharing options...
Chance Posted February 26, 2009 Author Report Share Posted February 26, 2009 uname -a Gives: Linux localhost 2.6.27.14-desktop586-1mnb #1 SMP Wed Feb 18 03:04:31 EST 2009 i686 Intel(R) Celeron(R) CPU 1.70GHz GNU/Linux And cd /sys/devices/system/cpu/cpu0/cpufreq/; grep . * Gives: affected_cpus:0 cpuinfo_cur_freq:13800000 cpuinfo_max_freq:13800000 cpuinfo_min_freq:1725000 related_cpus:0 scaling_available_frequencies:1725000 3450000 5175000 6900000 8625000 10350000 12075000 13800000 scaling_available_governors:ondemand conservative powersave userspace performance scaling_cur_freq:13800000 scaling_driver:p4-clockmod scaling_governor:performance scaling_max_freq:13800000 scaling_min_freq:1725000 scaling_setspeed:<unsupported> Quote Link to comment Share on other sites More sharing options...
Greg2 Posted February 26, 2009 Report Share Posted February 26, 2009 affected_cpus:0 cpuinfo_cur_freq:13800000 -snip- scaling_cur_freq:13800000 scaling_driver:p4-clockmod -snip- I believe this driver is your problem. Please see this bug report: bugzilla.kernel.org It appears that a patch has been submitted, but has never been pushed into mainline. So for now, you could try unloading the module with modprobe -r p4_clockmod and if that works, then blacklist it. Quote Link to comment Share on other sites More sharing options...
Chance Posted February 27, 2009 Author Report Share Posted February 27, 2009 I believe this driver is your problem. Please see this bug report: bugzilla.kernel.orgIt appears that a patch has been submitted, but has never been pushed into mainline. So for now, you could try unloading the module with modprobe -r p4_clockmod and if that works, then blacklist it. That worked perfectly, thank you! How do I blacklist a process? I've never had to do it before. Quote Link to comment Share on other sites More sharing options...
daniewicz Posted February 27, 2009 Report Share Posted February 27, 2009 How do I blacklist a process? Have a look here: https://mandrivausers.org/index.php?showtop...mp;hl=blacklist Quote Link to comment Share on other sites More sharing options...
Chance Posted February 27, 2009 Author Report Share Posted February 27, 2009 I added the blacklist line like I was supposed to, but it continues to load the module on each boot anyway, but I can just unload it at each start until I find a more permanent solution. That tiny hiccup aside, my problem is solved! Thanks to everyone that helped, I greatly appreciate it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.