** Changed in: indicator-cpufreq
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
indicator-cpufreq 0.2-0ubuntu1: 2.20 frequency shows up
This bug was fixed in the package indicator-cpufreq - 0.2.1-0ubuntu1
---
indicator-cpufreq (0.2.1-0ubuntu1) raring; urgency=low
* New upstream bugfix release (LP: #1130508):
- Correctly display turbo mode option in menu (LP: #1110429).
- Install hicolor icons (LP:
** Changed in: indicator-cpufreq
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
indicator-cpufreq 0.2-0ubuntu1: 2.20 frequency shows up twice
Bug remains: http://ubuntuone.com/42JFbmRDXdz0lcrF1bJGbr
** Summary changed:
- indicator-cpufreq 0.2-0ubuntu1: 2.20 frequency shows up twice [raring]
+ indicator-cpufreq 0.2-0ubuntu1: 2.20 frequency shows up twice [raring/quantal]
--
You received this bug notification because you are a member
it is a confirmed bug like at https://bugs.launchpad.net/indicator-
cpufreq/+bug/1008438
** Changed in: indicator-cpufreq (Ubuntu)
Status: Triaged = Confirmed
** Changed in: indicator-cpufreq
Status: New = Confirmed
--
You received this bug notification because you are a member
Hi there. 'Triaged' here means that this bug report contains enough
information for a developer to work on a fix, and that's the right
status for this bug. See https://wiki.ubuntu.com/Bugs/Status for more
details.
** Changed in: indicator-cpufreq (Ubuntu)
Status: Confirmed = Triaged
--
Andrea, sorry, my mistake, I had the wrong state in my mind ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
indicator-cpufreq 0.2-0ubuntu1: 2.20 frequency shows up twice
I actually thought that might be it after seeing the results. Maybe you
can make the appindicator reflect this, like: if there are two values:
2201000 and 220, for the first one use: 2.20 GHz (turbo mode) in
the indicator menu...?
--
You received this bug notification because you are a
Word. I've been too thinking of doing this very thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
indicator-cpufreq 0.2-0ubuntu1: 2.20 frequency shows up twice [raring]
To manage
I think it's better in such cases to exclude the smaller one so here,
between 2201000 and 220 you'd exclude 220. I don't see a reason
why someone would want to switch between 2 so close frequencies...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, in your case the system uses 2201000 quite often judging by the
cpufreq-info output, so by dropping lesser one I actually meant to
exclude the smaller one, which is 220. However, I'd like to make
sure that there is no real world performance difference, that's what
nbench is for.
--
You
Is this the tool you're talking about:
http://www.tux.org/~mayer/linux/bmark.html ? If so, the compilation
fails unfortunately with nmglobal.h:29:21: fatal error: pointer.h: No
such file or directory...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
oh, that file is found in linux-headers package: linux-
headers-3.8.0-3-generic seems to be the latest one for raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
indicator-cpufreq
It's already installed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
indicator-cpufreq 0.2-0ubuntu1: 2.20 frequency shows up twice [raring]
To manage notifications about this bug
Hmm, I see. It's got it's own pointer.h. The solution seems to run:
echo #define LONG64 pointer.h
and rerun 'make'. Not sure why make didn't create the file for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It worked now, thanks!
Here are the results, although I for one don't understand anything here.
I wasn't sure how to run the benchmarks so I ran it once for 2201000 and
once for 220.
2201000:
BYTEmark* Native Mode Benchmark ver. 2 (10/95)
Index-split by Andrew D. Balsa (11/97)
Linux/Unix*
Unfortunately the double bug remains :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
indicator-cpufreq 0.2-0ubuntu1: 2.20 frequency shows up twice [raring]
To manage notifications
This is something I found by quick Googling:
http://lkml.indiana.edu/hypermail/linux/kernel/0812.1/02670.html
(btw why do I have two states - 2201000 and 220 ??)
2201000 is the marketing speed of your processor, plus 1MHz.
This is used by the ACPI BIOS to enable Turbo Mode,
aka Intel
Hmm, I'm still considering this a bug and a pretty confusing one. But
unfortunately, I can't change the importance for the Ubuntu task back
from Wishlist, because I'm not in bugcontrol :)
Anyway. I haven't done any CPU benchmarking on Linux and I am still
unsure how to do it, but nbench (no
Strange, I thought I fixed this in this version.
Andrei, can you tell me the output of cpufreq-info | grep stats on your
machine?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
cpufrequtils wasn't installed on my system so I've installed it and
here's the cpufreq-info | grep stats output:
cpufreq stats: 2.20 GHz:14.19%, 2.20 GHz:0.21%, 2.00 GHz:0.10%, 1.90
GHz:0.10%, 1.80 GHz:0.11%, 1.70 GHz:0.12%, 1.60 GHz:0.14%, 1.50 GHz:0.16%, 1.40
GHz:0.18%, 1.30 GHz:0.16%, 1.20
Right. However, cpufrequtils (cpufreqd) may conflict with the indicator,
so I suggest it's okay to remove cpufrequtils now.
Apparently, the frequencies are wrongly convolved into a set in Python,
so can you also do the following? Run python3 in a terminal and run the
following commands within the
Here it is for me:
Python 3.3.0 (default, Jan 26 2013, 15:44:18)
[GCC 4.7.2] on linux
Type help, copyright, credits or license for more information.
from indicator_cpufreq import cpufreq
cpufreq.get_available_frequencies(0)
[2201000, 220, 200, 190, 180, 170, 160,
I also wonder what happens if you clock the CPU to either frequency and
run a benchmark. Andrei, would you be willing to perform such a test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
So, you've got a frequency of 2201000 KHz, which is roughly equal to
2.20 GHz. Hmm, is this some kind 'slightly overclocked' CPU option or
some other special processor feature?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I didn't overclock or tweak anything. Sure, I'll do whatever it takes,
just let me know exactly what I must do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110429
Title:
indicator-cpufreq
Marking as wishlist, as this seems just an issue with rounding.
** Changed in: indicator-cpufreq (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: indicator-cpufreq (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
27 matches
Mail list logo
