lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: linux (Ubuntu Lucid)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: linux (Ubuntu)
Assignee: Andy Whitcroft (apw) => (unassigned)
** Changed in: linux (Ubuntu Lucid)
Assignee: Andy Whitcroft (apw) => (unassigned)
** Changed in: linux (Ubuntu Lucid)
Status: In Progress => Triaged
--
You received this bug notification because you a
Ben A, thank you for you comment. Verified the Trusty configuration as per:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git && cd ubuntu-trusty
&& grep -r CONFIG_X86_POWERNOW_K8= && grep -r CONFIG_X86_ACPI_CPUFREQ= | grep
debian
debian.master/config/config.common.ubuntu:CONFIG_X86_POWE
That canned response doesn't apply, as the problem is not in the kernel
itself, but in the configuration Ubuntu is using to compile the kernel.
The fix is simple: in the kernel config, change
CONFIG_X86_POWERNOW_K8=y
and
CONFIG_X86_ACPI_CPUFREQ=y
to
CONFIG_X86_POWERNOW_K8=m
and
CONFIG_X86_A
Mathieu Velten, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/c
Sure I have old hardware, but I have to recompile the entire kernel with
module enabled for speedstep-centrino instead of just compiling the
module in a few seconds, as I have to patch the driver for accepting the
cpufreq tables for my Sonoma (stepping C0) 2.0 GHz Pentium-M which is
not standard bu
If anyone at the Kernel Team reads this, could they please expand on the
comment "cpufreq: it's hard to do in userspace"?
If I compile the current kernel myself, with just the one difference in
which acpi-cpufreq is a module, everything works perfectly. Just check
PPA for linux-phc if you don't be
Ok.. found some more info from the Kernel Team specs for Natty:
https://wiki.ubuntu.com/KernelTeam/Specs/KernelNattyConfigReview
They have a general policy to build it in because, "it's hard to do in
userspace". No idea what that means, or why no other distro has
difficulty with building acpi_cpu
Is this going to be marked as declined for Lucid, carried forward to
Natty?
I've seen loads of complaints about the move, and no one thanking anyone
for it. At least carrying it forward would show it's still on someone's
radar. Otherwise close it and mark as won't fix.
--
You received this bug n
I also don't understand why if the module is going to be included in the
kernel why it cannot have the patch to allow undervolting included. By
default it does nothing except show what the current settings are. If
you need to undervolt your computer (like I do because it reduces my CPU
temperature
@ Dana Goyette
Even if that's possible, I don't think it's a good idea. The whole module
architecture was made specifically for the case of loading and unloading them,
and it's not good to have another way of basically doing the same thing.
@Scott James Remnant
"Andy, i know where you live.
If
What we really need is a "noload" parameter in that module... I'd
imagine it should be relatively simple to have the driver abort (or do
nothing and return "success") if that parameter is set to true.
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.
Just to keep things together and make you notice that more people care
about this topic:
http://brainstorm.ubuntu.com/idea/24567/
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a m
it turned out i just needed a current version of mplayer to watch 1080p
movies without overclocking. nevertheless i'd like to have the full 3,2
GHz with speedstep enabled
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received t
** Changed in: linux (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-2 => None
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
just because of this i built my own kernel on lucid
2.6.33, built with kernelcheck - with some hacks to make it work (patched
kernelcheck, adapted grub, blacklisted nouveau in favour of nvidia)
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bu
** Changed in: linux (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-1 => ubuntu-10.04-beta-2
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: linux (Ubuntu Lucid)
Milestone: lucid-alpha-3 => ubuntu-10.04-beta-1
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
First of all, such a kernel command-line option would be great... It
will be a nightmare to write it and maintain it though. Go ahead and try
to do it, please! I honestly would be thankful. I doubt it will be in
time for Lucid...
Loading all modules is what is already done, except the modules are
A better approach for the out-of-kernel issue would be to have a kernel
command-line option to select or disable frequency scaling drivers, e.g.
just
scaling_driver=acpi-cpufreq
or
scaling_driver=none
Then users can load another module later if they want.
One major reason these have to
Andy, i know where you live.
If you revert these to modules, I will hunt you down and kill you.
kthxbye
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Changed in: linux (Ubuntu Lucid)
Milestone: lucid-alpha-2 => lucid-alpha-3
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Tags added: jaunty lucid
** Tags removed: kernel-jaunty kernel-lucid
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Changed in: linux (Ubuntu Lucid)
Milestone: lucid-alpha-1 => lucid-alpha-2
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Tags added: kernel-jaunty kernel-lucid
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Ok we moved them in so we could get rid of userspace lash up to get them
loaded under the commit below which appears to have originated from
Scott. I assume in the "no rules in userspace" land we find ourselves
we would need to find some kind of module alias match up to make these
modularisable.
Andy - we should consider pulling these frequency governors back out.
** Also affects: linux (Ubuntu Lucid)
Importance: Low
Assignee: Tim Gardner (timg-tpi)
Status: Triaged
** Changed in: linux (Ubuntu Lucid)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Lucid
+1 from me too
I have a AMD Phenom II Black Edition and want to optimize my system
through custom Cool'n'Quiet. I undervolt my processor on lower power
states and overclock a little bit with default voltage on highest power
state. This allows me to lower power consumption in idle and also get
high
Is there any news on this issue, to me it looks like a very small fix as
no code has to be adjusted.
I don't know anything about the processes behind such a change and I
could be wrong saying this isn't a lot of work to fix, I'm just trying
to see what the odds are of this bug making it into 9.10/
+1 from another AMD Turion and PHC user trying to reduce CPU temperature
(50C -> 30C) and extend battery life.
I would really like to keep using Ubuntu, but compiling a custom kernel
to enable undervolting is very time-consuming and could convince me to
switch to another distro.
Thanks in advance
Tim Gardner is responsible for introducing this, assign him to this bug.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notif
For what it's worth, it is in commit
495f78bd6d8f7a5e35dd962031eb6e639d83e438, which IMHO should be reverted:
UBUNTU: Build in CPU Frequency scaling drivers
Selecting the right CPU Frequency scaling driver is complicated from
userspace, involing a nasty shell script that attempts t
I am in the same boat as most ppl above. I have been using ubuntu since
breezy and undervolting the AMD Turion on my laptop since feisty.
Usually I check to make sure the usual suspects (X, suspend/hibernate)
have no issues before upgrading but did not think something basic as
acpi/powernow would b
I'm having the same problem, I have been undervolting my laptop since at
least feisty fawn which has always worked for me within an hour after
upgrading to a new version of Ubuntu. Unfortunately this is not possible
anymore because it is build in now.
I think, allthough I know it is easy to say th
I have a Raon Digital Everun Note UMPC and I need to replace the not
working powernow-k8 code with a code that at least makes the
conservative governor work.
Currently the Turion X2 TL-56 is always running at 1200 MHz instead of
800 MHz. This results in 70 minutes battery life instead of 115 mins.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Changed in: linux-meta (Ubuntu)
Importance: Undecided => Low
** Changed in: linux-meta (Ubuntu)
Status: New => Triaged
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug notification because you are a
37 matches
Mail list logo
