On Thu, 7 Jun 2018, Mac wrote: So, I was running a old version of Ardour on ubuntustudio 16.04. Which is old... use 18.04 > I updated to Ardour 5.1.2. > When the Ardour install file (.run) ran it warned me that I should turn > off > frequency scaling. > After some googling it appears UBS doesn't ship with any of the typical > tools one > would use to adjust the cpu frequency. > Most of the search results talk about installing gnome applets and other > stuff. > Seem to me a distro that is targeted at such cpu intense usage would have > facilities to manage this. > So, before I go off on an apt spree, I figured I ask if I'm missing > something. No you are not missing something :) The ubuntustudio-controls in 18.04 does include cpu governor setting, 16.04 does not. The same application for 18.10 does a lot more and also allows Boost to be shut off. Some things to be aware of: - I don't know about debian in general, but Ubuntu sets Ondemand or Powersave at boot... about 60 seconds after everything else. This means that cpufrequtils sets performance at boot and then ondemand sets it back 60 sec later. Ondemand in /etc/rc*.d needs to be disabled - cpu governing does not seem to affect audio with buffer size greater than 64. - at low latency Boost also affects audio and should be truned off. It seems to be the change in cpu speed that causes trouble as I have run a cpu fixed at 800mhz with no trouble as compared to 1.6 Ghz on the same machine with Ondemand and xruns. -- Len Ovens www.ovenwerks.net _______________________________________________ Linux-audio-user mailing list Linux-audio-user(a)lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-user

Mac <macdroid53(a)gmail.com> writes: 18.04. I've found the in-place upgrades in the last few years increasingly unspectacular. I had upgraded both my parents' computers remotely for the last two or three updates. While I made sure that it would have been possible to get onto the train the next day for each of them, it wasn't necessary. -- David Kastrup

Mac <macdroid53(a)gmail.com> writes: Rescatux boot disk should work for repairs. So should booting up in rescue mode. -- David Kastrup

You could use command line without a tool. Set the governor to performance by running echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor Check the status by running cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor Disable performance mode by either running echo powersave | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor when on an Intel CPU or by running echo ondemand | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor if your CPU should be an AMD.

Am Donnerstag, den 07.06.2018, 19:36 +0200 schrieb Ralf Mardorf: That's the old way you did it, but you can't do that with debian and ubuntu, nowadays. [snip]

Am 08.06.2018 um 05:27 schrieb Ralf Mardorf: I'd be interested in an answer to this as well.

On Fri, 8 Jun 2018, Christopher Arndt wrote: easiest place to look: /lib/systemd/set-cpufreq This is the way that ubuntu and probably debian set cpu governor today. Notice that they do not include Performance, If Performance is wanted at boot... the way to do that without getting errors when upgrading sw: create another file in the same directory maybe call it performance and use the same code, but replace all governor choices with performance. Then create a directory: /lib/systemd/system/ondemand.service.d in that directory create a file performance.conf will do and put some lines like: ------------------------8<--------------- [Service] ExecStart= ExecStart=/lib/systemd/performance ------------------------8<--------------- Assuming the file you created was also called performance. The blank ExecStart= is important as I found out, it resets Execstart to empty first. Doing things this way has the advantage that /lib/systemd/system/ondemand.service already makes sure the correct kernel modules are loaded first and updates will go smoothly.