[04:18] <Eickmeyer> OvenWerks: Changelog issue?
[04:26] <OvenWerks> fixed
[04:27] <OvenWerks> I've forgotten how to do multi-line entries...
[04:29] <OvenWerks> who knows what else I have forgotten  ;)
[04:29] <OvenWerks> Eickmeyer: please install and test since your machine is actually different from mine
[04:33] <OvenWerks> Hmm, it doesn't show up with apt update yet
[04:36] <OvenWerks> now it does
[04:40] <Eickmeyer> OvenWerks: Yeah, just did the build before and confirmed that governor settings did not persist. Waiting on new version.
[04:50] <Eickmeyer> OvenWerks: Just checked, still not persisting.
[04:50] <Eickmeyer> I even installed indicator-cpufreq to verify it's making the change, and it is, but it's not persisting after reboot.
[04:52] <Eickmeyer> I'll try one more time. Just looked at /etc/default/ubuntustudio and it looks correct in there.
[04:57] <Eickmeyer> Rebooted, CPU governor is back to performance, and I have not opened -controls. Checked /etc/default/ubuntustudio and governor should be ondemand, but it wasn't set as such at some point.
[04:57] <Eickmeyer> OvenWerks: ^
[05:04] <OvenWerks> ok.
[05:06] <OvenWerks> Eickmeyer: is there anything in you log (dmesg)?
[05:07] <OvenWerks> search turbo
[05:07] <OvenWerks> I expect: "turbo/boost not available"
[05:29] <OvenWerks> Eickmeyer: just did three reboots... guess this is four
[05:29] <OvenWerks> works fine here
[05:35] <OvenWerks> Eickmeyer: can you check if /lib/systemd/ubuntustudio is executable? (ls -l)
[05:41] <OvenWerks> hmm, it won't be in dmesg but it is in /var/log/syslog search for  Ubuntustudio
[05:42] <OvenWerks> there should be two lines with a line by root in between with the word turbo in it
[05:53] <OvenWerks> Eickmeyer: can you download http://www.ovenwerks.net/paste/ubuntustudio
[05:54] <OvenWerks> use sudo to put it in /lib/systemd/ubuntustudio (will over write the file there already so you may wish to mv it to ubuntustudio.bak or something
[05:55] <OvenWerks> sudo chmod +x /lib/systemd/ubuntustudio
[05:55] <OvenWerks> then send me a file that should appear as /us_log.txt
[06:04] <OvenWerks> My run with that file looks like: http://www.ovenwerks.net/paste/us_log.txt
[06:04] <OvenWerks> Eickmeyer: ^^
[06:51] <OvenWerks> Eickmeyer: In US-installer you have removed the metas and replaced them with setup stuff
[06:56] <OvenWerks> Eickmeyer: Oh, I see what happened it doesn't off packages that are already installed :)
[22:30] <Eickmeyer> OvenWerks: Found the problem. I have an /etc/default/cpufrequtils that is setting it.
[22:30] <Eickmeyer> I need to figure out what package is installing that.
[22:31] <OvenWerks> Eickmeyer: we used to, but in 18.04 and up that shouldn't work...
[22:32] <Eickmeyer> Looks like it was -controls that did it. Must be left over?
[22:32] <OvenWerks> however, it may work because you have and amd?
[22:32] <Eickmeyer> Doubt it.
[22:33] <OvenWerks> the intel needs a kernel module to be loaded first and so cpufrequitls runs before that happens and doesn't work
[22:33] <OvenWerks> in the amd case that kernel module is not needed and so timing is different
[22:35] <Eickmeyer> OvenWerks: Perhaps, but the file is definitely in the ubuntustudio-controls package. That said, cpufrequtils isn't installed, but could there be something else calling the file?
[22:36] <OvenWerks> the solution is to rename /etc/rc5.d/S*cpufrequtils to K02cpufrequtils
[22:36] <OvenWerks> cpufrequtils is a depends for controls
[22:37] <Eickmeyer> I mean, if the CPU governor is being set a different way (with systemd) then should we just eliminate /etc/default/cpufrequtils from the package?
[22:37] <OvenWerks> so it is installed unless you have removed it
[22:37] <OvenWerks> yes
[22:38] <OvenWerks> I didn't see it there
[22:38] <OvenWerks> I will do so. (the package shouldn't build then) whatever.
[22:38] <Eickmeyer> Strange. I just downloaded the source from git and it's definitely there.
[22:39] <OvenWerks> yes I see it too, but if the package isn't installed it should do nothing
[22:39] <OvenWerks> The cpufrequtils package
[22:39] <Eickmeyer> Right.
[22:40] <OvenWerks> anyway, I will remove it. and reupload
[22:40] <Eickmeyer> Okay.
[22:40] <Eickmeyer> There's a million different ways to set the CPU governor. Latest method means using "cpupower frequency-set --governor performance"
[22:45] <OvenWerks> build pending
[22:45] <OvenWerks> BY the way this build does not include the patched file above?
[22:46] <OvenWerks>  http://www.ovenwerks.net/paste/ubuntustudio
[22:47] <OvenWerks> Eickmeyer: I am using the same method the /lib/systemd/ondemand does
[22:47] <Eickmeyer> I don't have a /lib/systemd/ondemand
[22:47] <OvenWerks> set-cpufreq sorry
[22:48] <Eickmeyer> BTW...
[22:49] <Eickmeyer> 0 ondemand
[22:49] <Eickmeyer> 0 ondemand
[22:49] <Eickmeyer> enabled
[22:49] <Eickmeyer> OvenWerks: ^ us_log.txt
[22:49] <OvenWerks> Thats as far as it goes?
[22:51] <OvenWerks> That tells me that your system does not like me checking for "Intel Boost"
[22:53] <OvenWerks> Eickmeyer: Well I could move that part to the end... but I would rather findout what the problem with my code is and fix it.
[22:56] <Eickmeyer> Right.
[22:57] <Eickmeyer> Controls has boost grayed-out, so I figured it just didn't care.
[23:00] <OvenWerks> Eickmeyer: ok http://www.ovenwerks.net/paste/ubuntustudio has been changed again to output more logging can you try it?
[23:02] <OvenWerks> It has to care about it so it doesn't try to set something not there
[23:03] <OvenWerks> So on boot we check to see if a turbo switch exists then we set it only if it does
[23:03] <OvenWerks> the 0 in "0 ondemand" is the boost defeat value
[23:07] <Eickmeyer> Sure, I'll give it a shot.
[23:07] <OvenWerks> TY
[23:11] <Eickmeyer> OvenWerks: Exact same result.
[23:14] <OvenWerks> really... in a terminal what does: logger "Setting system settings"
[23:14] <OvenWerks> do?
[23:14] <OvenWerks> maybe logger needs to be installed
[23:15] <OvenWerks> maybe I should just remove the lines that refer to it
[23:15] <Eickmeyer> logger gives no response.
[23:16] <OvenWerks> tail /var/log/syslog
[23:17] <OvenWerks> no that doesn't show anything here either
[23:17] <OvenWerks> if it gives no responce that is not the same as an erro though
[23:18] <Eickmeyer> Bear in mind, I'm running Plasma, so you'll see references to Kubuntu.
[23:18] <Eickmeyer> https://paste.ubuntu.com/p/P9kv5jjXTY/
[23:19] <OvenWerks> erich: Setting system settings
[23:19] <OvenWerks> its there
[23:19] <OvenWerks> did you reboot after putting that file in?
[23:19] <Eickmeyer> Okay, so that means logger is doing that.
[23:19] <Eickmeyer> Yes.
[23:21] <Eickmeyer> I can reboot again and give you the tail from that.
[23:21] <OvenWerks> and /us_log.txt doesn't even have one more line?  "logged"?
[23:21] <Eickmeyer> No. The only things it gives are 0 ondemand, blank line, 0 ondemand, blank line, enabled
[23:22] <OvenWerks> weird... 
[23:23] <OvenWerks> Ok I have changed the file again removing all the logger commands
[23:25] <Eickmeyer> Ok
[23:25] <OvenWerks> Oh, have you reloaded the browser before redownloading the file?
[23:26] <Eickmeyer> I did just now. Everything is pasted and checked, rebooting.
[23:28] <Eickmeyer> Interesting... rebooted and now OnDemand is set.
[23:29] <Eickmeyer> Possible breakthrough.
[23:29] <OvenWerks> and /us_log.txt?
[23:29] <Eickmeyer> https://paste.ubuntu.com/p/FJ56HdPndD/
[23:30] <OvenWerks> yup. so that logger command works on my machine and not yours... but using logger from the CL does work on yours.
[23:31] <OvenWerks> Ok will drop logging anything
[23:31] <Eickmeyer> Ok, think it's erroring to an exit?
[23:31] <OvenWerks> I have one more thing to try if you have time.
[23:32] <Eickmeyer> I have time.
[23:33] <OvenWerks> another file is ready
[23:35] <Eickmeyer> Okay, rebooting...
[23:39] <Eickmeyer> OvenWerks: https://paste.ubuntu.com/p/VrRPPJ8XDz/
[23:39] <Eickmeyer> brb, gotta move some furniture.
[23:40] <OvenWerks> grep " root:" /var/log/syslog
[23:48] <Eickmeyer> OvenWerks: https://paste.ubuntu.com/p/v5hF4tDpnZ/
[23:54] <OvenWerks> so it seems it was working but stopping right after?
[23:54] <OvenWerks> could be
[23:54] <OvenWerks> All I did was escape a variable ${DESC} instead of $DESC