[2.1.4] Strange CPU speed

ducon · Post by **ducon** » Fri Aug 11, 2006 1:58 pm

This is a very minor bug but when I launch ZDoom in a console, I see this (see line 3):

 adding /usr/local/bin/zdoom.pk3
 adding /usr/share/games/doom/doom2.wad (2956 lumps)
CPU Speed: ~0.062134 MHz
CPU Vendor ID: GenuineIntel
  Name: Intel(R) Celeron(R) CPU 2.66GHzn(R) CPU 2.66GHz
  Family 15, Model 3, Stepping 3
  Features: MMX SSE SSE2 SSE3
  [cut]

Gah, a 60 kHz CPU. I run it with a Debian Etch on x86. The CPU speed is correct two lines after.

Post by **Graf Zahl** » Fri Aug 11, 2006 2:03 pm

http://forum.zdoom.org/potato.php?t=10650

ducon · Post by **ducon** » Fri Aug 11, 2006 2:06 pm

OK, so the bug is still there.

Post by **Graf Zahl** » Fri Aug 11, 2006 2:17 pm

Don't blame me that Linux apparently doesn't have a decent timer to calculate the CPU speed.
If you have an idea how to do it better you are welcome of course.

ducon · Post by **ducon** » Sat Aug 12, 2006 12:18 am

It seems that the correct code uses /proc/cpuinfo, no?

Post by **Bio Hazard** » Sat Aug 12, 2006 12:28 am

I was looking into the kernel source and found cpufreq_get(int cpu) but I can't figure out how to get it to work outside of the kernel source itself.

Hobbs · Post by **Hobbs** » Sat Aug 12, 2006 12:43 am

Its not just Linux. On my laptop it always lists the current processor speed (because, you know, its a Pentium M, so the CPU speed changes) in ZDoom, never the max unless my processor is using the max on any line of the console.

Also on this line

Code: Select all

Intel(R) Pentium(R) M processor 2.2GHz 2.2Ghz

Why is the processor speed listed twice?

ducon · Post by **ducon** » Sat Aug 12, 2006 1:29 am

Perhaps because we did not overclock our processor?

Post by **randi** » Sat Aug 12, 2006 3:20 pm

DoomerX wrote:
Code: Select all
Intel(R) Pentium(R) M processor 2.2GHz 2.2Ghz
Why is the processor speed listed twice?

Because that is the string returned by the processor's CPUID instruction, and Intel decided to store the processor's nominal frequency in it twice.

The CPU frequency is only calculated for doing high-precision statistical timings with RDTSC, so it's not like this really matters to most people anyway.