Re: cpupower

Allegedly, on or about 25 June 2018, Howard Howell sent: > This typically requires more than just vacuuming the outside. > Typically you have to remove the heatsink and fan, and use a brush or > q-tips to ferret out the various dustbunnies in the nooks and > crannies that are near the CPU. Ah

Re: cpupower

On Mon, 2018-06-25 at 03:55 +0930, Tim via users wrote: > Allegedly, on or about 24 June 2018, JD sent: > > Reason I am posting this is because the normal speed of the cores > > is 2.8GHz, and that is causing numerous kerneloops interrupts > > (overheating). > > Fans are at full speed all the

Re: cpupower

On Sun, 24 Jun 2018 21:26:04 -0700 Joe Zeff wrote: > On 06/24/2018 09:13 PM, Doug wrote: > > What makes you folks think that a computer will run faster in a > > refrigerated environment?  Only if it was too hot to begin with > > should it make any difference. > > Remember, this thread

Re: cpupower

On 06/24/2018 09:13 PM, Doug wrote: What makes you folks think that a computer will run faster in a refrigerated environment?  Only if it was too hot to begin with should it make any difference. Remember, this thread started out talking about working around a CPU overheating.

Re: cpupower

On 06/24/2018 11:10 PM, stan wrote: On Mon, 25 Jun 2018 09:45:27 +0930 Tim via users wrote: Allegedly, on or about 24 June 2018, stan sent: I've thought about buying one of those little fridges and putting the system in it. I remember seeing a page or two about people doing that, many

Re: cpupower

On Mon, 25 Jun 2018 09:45:27 +0930 Tim via users wrote: > Allegedly, on or about 24 June 2018, stan sent: > > I've thought about buying one of those little fridges and putting > > the system in it. > > I remember seeing a page or two about people doing that, many years > ago. Though I can't

Re: cpupower

On 06/24/2018 06:36 PM, Ed Greshko wrote: Of course you could look in /lib/systemd/system to learn it is rc-local  :-) :-) Thank you; that worked. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to

Re: cpupower

On 06/25/18 09:21, Joe Zeff wrote: > On 06/24/2018 05:26 PM, Ed Greshko wrote: >> Read my reply to poc.  It is a "static" service.  It doesn't need to be >> "enabled". > > I too have an rc.local script, but it's just a stub, and doesn't even have > #!/bin/sh in it that's just a stub in case I

Re: cpupower

On 06/24/2018 06:16 PM, Roger Heflin wrote: If you want to debug it the easy way do this: create /usr/local/bin/slowcpus and make it executable and put the commands in it and test it from the cmd line: Then in rc.local do this: That's a good idea. I remember reading, once, that you should

Re: cpupower

On 06/24/2018 05:26 PM, Ed Greshko wrote: Read my reply to poc.  It is a "static" service.  It doesn't need to be "enabled". I too have an rc.local script, but it's just a stub, and doesn't even have #!/bin/sh in it that's just a stub in case I ever need it. systemctl status

Re: cpupower

If you want to debug it the easy way do this: create /usr/local/bin/slowcpus and make it executable and put the commands in it and test it from the cmd line: Then in rc.local do this: /usr/local/bin/slowcpus > /tmp/slowcpu.out 2>&1 On Sun, Jun 24, 2018 at 7:26 PM, Ed Greshko wrote: > On

Re: cpupower

On 06/25/18 08:11, Tim via users wrote: > Allegedly, on or about 24 June 2018, Patrick O'Callaghan sent: >> Note that you now have to explicitly enable rc.local to make it run >> at boot time: >> >> # systemctl enable rc-local.service > I just did that, and nothing more (I hadn't, yet, got around

Re: cpupower

Allegedly, on or about 24 June 2018, stan sent: > I've thought about buying one of those little fridges and putting the > system in it. I remember seeing a page or two about people doing that, many years ago. Though I can't recall what their success was like. I'd be concerned about

Re: cpupower

Allegedly, on or about 24 June 2018, Patrick O'Callaghan sent: > Note that you now have to explicitly enable rc.local to make it run > at boot time: > > # systemctl enable rc-local.service I just did that, and nothing more (I hadn't, yet, got around to making a rc.local file and putting anything

Re: cpupower

On 06/25/18 07:20, Tom Horsley wrote: > On Mon, 25 Jun 2018 07:07:52 +0800 > Ed Greshko wrote: > >> I don't recall how I found my mistake.  I do remember putting in a few >> "touch" >> commands in the script to create files and thereby narrow down where in the >> script >> I'd gone wrong. > Two

Re: cpupower

On 06/25/18 06:53, JD wrote: > # systemctl -l start rc-local > # echo $? > 0 > # > # systemctl -l status rc-local.service > rc-local.service - /etc/rc.d/rc.local Compatibility >    Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled) >    Active: active (exited) (Result: exit-code)

Re: cpupower

On 06/24/2018 03:55 PM, JD wrote: Well, rc-local.service cannot be instrumented with echoes from the shell, which is run with option -x in /etc/rc.d/rc.local Maybe it would be best to do this: start off with date > /root/log.txt (This tells you when you booted and gets rid of any previous

Re: cpupower

On Mon, 25 Jun 2018 07:07:52 +0800 Ed Greshko wrote: > I don't recall how I found my mistake.  I do remember putting in a few "touch" > commands in the script to create files and thereby narrow down where in the > script > I'd gone wrong. Two things that often cause rc.local failures: 1.

Re: cpupower

On 06/25/18 06:53, JD wrote: > Well, this is interesting: > > # systemctl -l start rc-local > # echo $? > 0 Which means the "systemctl" command succeeded. > # > # systemctl -l status rc-local.service > rc-local.service - /etc/rc.d/rc.local Compatibility >    Loaded: loaded

Re: cpupower

On 06/24/2018 04:45 PM, Joe Zeff wrote: On 06/24/2018 03:12 PM, JD wrote: ​I have enabled rc-local: sudo systemctl enable rc-local which is supposed to automagically execute /etc/rc.d/rc.local during bootup, but for some strange reason, rc.local is not being automagcally executed, even

Re: cpupower

On Mon, 2018-06-25 at 06:38 +0800, Ed Greshko wrote: > On 06/25/18 05:43, Patrick O'Callaghan wrote: > > On Sun, 2018-06-24 at 11:25 -0700, Joe Zeff wrote: > > > On 06/24/2018 10:55 AM, JD wrote: > > > > On 06/24/2018 11:37 AM, Joe Zeff wrote: > > > > > On 06/24/2018 10:27 AM, JD wrote: > > > > >

Re: cpupower

On 06/24/2018 04:38 PM, Ed Greshko wrote: On 06/25/18 05:43, Patrick O'Callaghan wrote: On Sun, 2018-06-24 at 11:25 -0700, Joe Zeff wrote: On 06/24/2018 10:55 AM, JD wrote: On 06/24/2018 11:37 AM, Joe Zeff wrote: On 06/24/2018 10:27 AM, JD wrote: But I do not want to do this loop every

Re: cpupower

On 06/25/18 06:12, JD wrote: > > > On Sun, Jun 24, 2018 at 12:25 PM, Joe Zeff > wrote: > > On 06/24/2018 10:55 AM, JD wrote: > > > On 06/24/2018 11:37 AM, Joe Zeff wrote: > > On 06/24/2018 10:27 AM, JD wrote: > > > But I do not want to

Re: cpupower

On 06/24/2018 03:12 PM, JD wrote: ​I have enabled rc-local: sudo systemctl enable rc-local which is supposed to automagically execute /etc/rc.d/rc.local during bootup, but for some strange reason, rc.local is not being automagcally executed, even though (as I explained already, it is an

Re: cpupower

On 06/25/18 05:43, Patrick O'Callaghan wrote: > On Sun, 2018-06-24 at 11:25 -0700, Joe Zeff wrote: >> On 06/24/2018 10:55 AM, JD wrote: >>> On 06/24/2018 11:37 AM, Joe Zeff wrote: On 06/24/2018 10:27 AM, JD wrote: > But I do not want to do this loop every time I boot up. > I want to

Re: cpupower

On Sun, Jun 24, 2018 at 12:25 PM, Joe Zeff wrote: > On 06/24/2018 10:55 AM, JD wrote: > >> >> On 06/24/2018 11:37 AM, Joe Zeff wrote: >> >>> On 06/24/2018 10:27 AM, JD wrote: >>> But I do not want to do this loop every time I boot up. I want to have set once and for all!!!

Re: cpupower

On Sun, 2018-06-24 at 11:25 -0700, Joe Zeff wrote: > On 06/24/2018 10:55 AM, JD wrote: > > > > On 06/24/2018 11:37 AM, Joe Zeff wrote: > > > On 06/24/2018 10:27 AM, JD wrote: > > > > > > > > But I do not want to do this loop every time I boot up. > > > > I want to have set once and for all!!! >

Re: cpupower

On Sun, 24 Jun 2018 11:27:04 -0600 JD wrote: > Manpage of cpu power make no mention of the > selection of governor. > How can set the governor to be the user mode governor > instead of the performance governor and not the ondemand governor? You can check which governor was compiled as default

Re: cpupower

On Sun, 24 Jun 2018 11:27:04 -0600 JD wrote: > Manpage of cpu power make no mention of the > selection of governor. > How can set the governor to be the user mode governor > instead of the performance governor and not the ondemand governor? This might get you closer. I didn't see anything

Re: cpupower

On Mon, 25 Jun 2018 03:55:23 +0930 Tim via users wrote: > Allegedly, on or about 24 June 2018, JD sent: > > Reason I am posting this is because the normal speed of the cores > > is 2.8GHz, and that is causing numerous kerneloops interrupts > > (overheating). > > Fans are at full speed all the

Re: cpupower

Allegedly, on or about 24 June 2018, JD sent: > Reason I am posting this is because the normal speed of the cores > is 2.8GHz, and that is causing numerous kerneloops interrupts > (overheating). > Fans are at full speed all the time, as I can hear them :) :) Sounds like you have inadequate

Re: cpupower

On 06/24/2018 10:55 AM, JD wrote: On 06/24/2018 11:37 AM, Joe Zeff wrote: On 06/24/2018 10:27 AM, JD wrote: But I do not want to do this loop every time I boot up. I want to have set once and for all!!! There's probably a proper way to do that, but until somebody finds it, put that into a

Re: cpupower

On 06/24/2018 11:37 AM, Joe Zeff wrote: On 06/24/2018 10:27 AM, JD wrote: But I do not want to do this loop every time I boot up. I want to have set once and for all!!! There's probably a proper way to do that, but until somebody finds it, put that into a shell script and call it from

Re: cpupower

On 06/24/2018 10:27 AM, JD wrote: But I do not want to do this loop every time I boot up. I want to have set once and for all!!! There's probably a proper way to do that, but until somebody finds it, put that into a shell script and call it from rc.local.

cpupower

Manpage of cpu power make no mention of the selection of governor. How can set the governor to be the user mode governor instead of the performance governor and not the ondemand governor? If I can permanently set that governor, next I want to set the cpu frequency (for all cores) to 2134000Hz

Re: Q about cpupower

On 06/28/2015 03:33 PM, g wrote: On 06/28/2015 02:41 PM, jd1008 wrote: cpupower frequency-set -f 2000MHz bad command line. at least according to 'man cpupower with centos, which shows at end; SEE ALSO cpupower-set(1), cpupower-info(1), cpupower-idle(1), cpupower

Re: Q about cpupower

On 06/28/2015 02:41 PM, jd1008 wrote: cpupower frequency-set -f 2000MHz bad command line. at least according to 'man cpupower with centos, which shows at end; SEE ALSO cpupower-set(1), cpupower-info(1), cpupower-idle(1), cpupower-frequency-set(1), cpupower-frequency-info(1

Q about cpupower

cpupower frequency-set -f 2000MHz reports that all cores have been set, and command exits with value 0. But /usr/bin/cpupower frequency-info shows all cores still at lower current frequencies. This is on a laptop with a dual core i5 with hyperthreading enabled. Also, the info shows 2 cores

Re: Q about cpupower

On 06/28/2015 02:33 PM, g wrote: On 06/28/2015 02:41 PM, jd1008 wrote: cpupower frequency-set -f 2000MHz bad command line. at least according to 'man cpupower with centos, which shows at end; SEE ALSO cpupower-set(1), cpupower-info(1), cpupower-idle(1), cpupower-frequency