Hello Benito,
It's up to me to close the bug report?! I'll do that immediately.
Since a while the kernel updates for the 9.04 are compiled with the
correct configuration regarding CPU frequency scaling so I stopped using
my custom compiled kernel.
Sincerely.
Eric
** Changed in: linux (Ubuntu)
Hi Eric and all,
I have found the solution for this and other two bugs happened after
upgrade from 8.04 - 8.10 - 9.04.
I did a sudo polkit-gnome-authorization and verified wrongly
permission set to frequency change action. After grant right
permissions the gnome applet can, now, change kernel
The problem is not with the Gnome frequency scaling applet. I used the
cpufreq-selector command and it doesn't change the frequency either. I
managed to get some reaction yet, by switching the ACPI daemon and
related on and off quickly. Then, sometimes, for a few seconds, the
frequency will
I may have done a mistake somewhere but following the standard procedure
to compile a custom kernel and dutifully copying
/boot/config-2.6.28-11-generic to /usr/src/linux-source-2.6.28/.config I
get qconf telling me that the kernel frequency has been locked to the
maximum frequency and cannot be
Well that was indeed the problem. Once the custom kernel was running,
with the CPU frequency throttling simply and basically turned on, there
was no more problem. The low frequency and power saving governors ran
perfectly.
On the other hand I had no more Wi-Fi. 'Going to try to solve that one
** Package changed: gnome-applets (Ubuntu) = ubuntu
--
cpu frequency scaling monitor does not change frequency in Ubuntu Jaunty (9.04)
alpha 5 on Core 2 system
https://bugs.launchpad.net/bugs/337780
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
There was no obvious graphical way to have the Wi-Fi driver reinstalled
for the custom compiled kernel but commenting away the b43 module and
its friends in the blacklist in /etc/modprobe.d/ and maybe installing
the proprietary driver using b43-fwcutter did the job. So now I have
both a silent and
** Package changed: ubuntu = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
cpu frequency scaling monitor does not change frequency in Ubuntu Jaunty (9.04)
alpha 5 on Core 2 system
https://bugs.launchpad.net/bugs/337780
You received this bug notification because
I really can't agree to close this ticket. The gnome applet worked in
past release and now it does not do a complete job as before.
I use AMD64 since 7.10 and use this application to change frequency of
my AMD64 since 8.04 with no problem. I just updated to Jaunty and had
some good surprises like
bugs get closed when they don't are good quality enough because there is
some ten thousand open right now and a small team to work on those and
keeping thousand of bad quality bugs open should makes work hardy for
everybody, you can reopen a closed by when adding informations as stated
before
--
some extra notes:
- the bug is low for ubuntu because that's only an applet and not a core
feature for most users
- similar issues have been fixed in jaunty
- your bug description is not clear, doesn't work is not useful, do you get
an error, does it just ignore your action, does it do the
There's no error from the applet. There's nothing worth taking a screen
shot. It applet just simply doesn't change the frequency. If you need
more information, how about asking Could you post the output of the
__ file after trying to switch the frequency? or some other
question that helps get
there is just a way higher of bugs than of people working on those so
there is no lack of bugs there and either we let the number and system
get out of control and not usuable or we do quite active closing, the
second option is the one used right now, it might not be perfect but
that's what we can
way higher number of bugs than ...
--
cpu frequency scaling monitor does not change frequency in Ubuntu Jaunty (9.04)
alpha 5 on Core 2 system
https://bugs.launchpad.net/bugs/337780
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ok, the comment had typo and didn't make sense let's summarize clearly:
* there is lot of open bugs
* there is not so many people working on those
* having thousand of bugs and an outgoing count makes harder to find what to
work on
* one way to get the list workable is to close actively bugs
Why do the bugs at launchpad get closed so quickly? Bugs do not rot. I
didn't even realize there was activity on the bug and 30 days isn't all
that much time to respond anyway.
I also don't understand why this bug was being closed because I did post
what appears to be the proper information
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
** Changed in: gnome-applets (Ubuntu)
Sourcepackagename: None = gnome-applets
--
cpu frequency scaling monitor does not change frequency in Ubuntu Jaunty (9.04)
alpha 5 on Core 2 system
https://bugs.launchpad.net/bugs/337780
You received this bug notification because you are a member of Ubuntu
Which application are you using for changing that? could you take an
screenshot of it? does the command line tools works fine?
** Changed in: gnome-applets (Ubuntu)
Importance: Undecided = Low
Status: New = Incomplete
--
cpu frequency scaling monitor does not change frequency in
19 matches
Mail list logo
