[12:39] Dear contributors! I went to Ubuntu Studio homepage to propose an idea to implement into Ubuntu Studio. May I write it here or do I need to send it via another channel/way? [14:04] Hello? :) [14:53] OK, if someone can answer, please send the answer to v6itja@protonmail.com - I am closing this window now :) Thanks! [19:05] OvenWerks: Playing around with the latest autobuild of -controls: CPU governor setting still not being remembered (was fine with repo version, not autobuild version), a2jmidid is not starting, pulse bridges don't start, USB bridges are not starting. Only Jack itself starts. I suspect a change to how it handles zita? [19:05] Eickmeyer: which OS (version) [19:06] which python version? [19:06] (3.?) [19:06] Whatever is in 19.10, so guessing 3. [19:07] Are you developing this in/for 18.04 or 19.10? [19:08] it sh9ould work either way.... it does here. I have not changed the way the governor is set [19:08] Python in 19.10 is 3.7.5 [19:08] Where is the config saved again? [19:09] controls config is now ~/.config/autojack/autojackrc [19:09] but it should read the old one ~/.config/autojackrc as well [19:10] I deleted the entire ~/.config/autojack directory, no changes. [19:11] governor setting is kept in /etc/default/ubuntustudio [19:13] I'm rebooting. [19:16] There should be no difference in the cpu governor chain of operation since last release. [19:16] Then -controls isn't properly parsing /etc/defaut/ubuntustudio or the governor. [19:17] does here [19:17] Interesting. Might be my AMD processor. [19:18] Do you remember how to read the CPU governor? [19:18] are you using 19.10 or 20.04 alpha? [19:18] 19.10 [19:18] /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor [19:19] That doesn't exist past cpu* on my system. [19:22] Aha! Something changed between kernels: https://wiki.archlinux.org/index.php/CPU_frequency_scaling [19:22] OvenWerks: ^ [19:25] Looks like we might need to requrie something and add linux-tools-common as a dependency. [19:25] which kernel I don't see anything beyond 3.4 [19:25] and we are even 18.04 at 4.15 [19:28] Hmmm... something changed then. Setting the CPU governor used to be possible in controls, but isn't any longer. I don't know what changed. I guess I'll have to review the commits. [19:29] try /usr/bin/pkexec /usr/sbin/ubuntustudio-system performance [19:29] and the same with ondemand [19:31] No response from either. [19:31] So no errors then [19:31] do you have a cpu speed monitor? [19:31] I don't have one open, but I could... [19:32] Cause if that doesn't work, the gui can't help as it just calls that. [19:33] there are two files that set cpu speed, /usr/sbin/ubuntustudio-system and /lib/systemd/ubuntustudio [19:34] I'm looking at it. [19:34] The systemd one is for boot and the other is on the fly changes [19:35] Right. [19:35] they both seem to change frequency the same way. [19:35] Got this when removing a pulse input bridge: https://paste.ubuntu.com/p/WfFWVbxVYc/ [19:35] If removing the only input bridge, it will not add it back. [19:36] In fact, the entre interface has no response at that point. [19:36] which is sort of reasonable [19:37] Actually, it adds it, but apparently the entire interface just fails to respond at that error. [19:37] ok [19:38] The "Auto Connect Port" needs to be more intuitive. Manually typing-in a port doesn't work since most people won't know what to type there. [19:39] wonko: You around? [19:39] Kinda [19:39] Eickmeyer: I have thought a lot about that... I had thought to have a drop down with possible ports. [19:40] however, if something like Ardour is running with any sized session the list is very long [19:40] I will fix the index problem though [19:41] OvenWerks: Pulse should only be set to automatically connect to hardware, never software unless the user manually goes into a patchbay to do that themselves. [19:41] So, let's leave software ports out of it and only keep hardware ports. [19:42] wonko: Just wanted you involved in this conversation since you've been helping with -controls a lot. [19:42] Ok, let me see if I can find the time to read scrollback [19:43] wonko: No worries. [19:43] I'm just seeing a lot of bugs that, unless we squash them, I'm not comfortable with releasing into an LTS. [19:44] I'll help with the AMD governor issues as much as I can. [19:44] Eickmeyer: no worries it is not ready... but the cpu part does worry me. [19:44] OvenWerks: Agreed. [19:45] Eickmeyer: I would take a look at /lib/systemd/set-cpufreq [19:45] on your system and see if it loooks in more than one place [19:46] OvenWerks: It doesn't exist. [19:46] oh my [19:47] Oops.. typo. Hold on... [19:48] https://paste.ubuntu.com/p/vjYWzpJpSx/ [19:48] OvenWerks: It's there, I just typo'd and it gave me a "not found" error. [19:48] That looks identical to mine [19:50] I am going to reboot [19:56] installing 19.10 [20:00] OK [20:01] So far cpu governor works... but I have not installed latest controls yet... Install not finished [20:01] After installing I will have to update so this may take a while [20:01] Ok. No worries. [20:05] in the new year there will be an AMD system in the house which I will be able to play with during school hours... [20:06] Hahahaha! Sounds like a plan. :D [20:07] I have so far had no success whatsoever with firewire stuff [20:07] Oof. [20:08] I even tried studio 14.04 [20:08] (I think thats the oldest I have) [20:08] Maybe, for the sake of LTS, we might have to depricate firewire. Most of those devices are 10+ years old. While I understand the high monetary investment, but we can't keep supporting ancient hardware. [20:09] Some people have had it run. [20:09] Yeah, but it's hit/miss. We can't guarantee it. [20:10] And, likely, for those that can't get their firewire to run, it's a kernel issue. [20:10] I will continue to work on it (later) but ya, we should probably take it out of controls for now [20:11] Feature Freeze is February 27th, FYI. [20:11] make a mention that if the FW alsa drivers work it should just show up otherwise it will take more work on the user's part [20:12] Yep. I'll stick that on my list. [20:13] I have tried three fw cards so far. And they show up but do not show that anything is connected to them [20:13] Even after reboot? [20:13] I will order another cable just in case... [20:13] Yeah, best to rule-out hardware issues. [20:13] I have booted with it pluged and powered, with out [20:14] every combo I could think of. I should try the generic kernel too (I have tried both lolat and liquorix [20:15] That says a lot. [20:16] Well this unit would personally double my inputs and leave no longer dependent on having PCI slots [20:21] Ok, gotta go. [20:21] k [20:21] I will leave various grunts as I go... [20:22] Hehe [20:43] Ga!, thunar no longer has a delete option... we are stuck with the trashcan :P [20:57] safer but anoying [21:27] Eickmeyer: installed "new controls" on 19.10. cpo governor works. [21:29] including reboot [22:42] OvenWerks: Wonderful. Perhaps it's time for me to wipe my install. [22:45] Eickmeyer: The only thing I can't tell is if AMD has those values somewhere else [22:46] but that web page you gave doesn't say anything about AMD being different [22:48] True. [22:48] Might be my install then. [22:48] (and arch is normally pretty good) [22:49] Yeah. [22:53] I would almost say that with ondemand, performance is better (is on intel for sure) [22:53] There were some tests done where it was found that performance used less power/battery than ondemand whenthings are almost idle [22:54] Makes sense, even though weird. [22:55] peromance can put the cpu in idle with no monitoring of cpu use but ondemand has to wake the processor up frequently to see if it needs to speed up for more load [22:55] The extra wake ups use more power [22:56] Then when the cpu is being used, ondemand increases cpu speed anyway [22:56] I mean, it makes sense, but just seems as though ondemand is counterproductive for whatever is being accomplished. [22:57] Thats why intel doesn't use it anymore :) [22:57] And it [22:57] 's possible that AMD doesn't anymore, which would make sense why I'm having difficulty. [22:57] To be honest, I haven't even tested to see what the governor is set-at when I make the change. [22:59] cpu speed monitors do that pretty good. I use the xfce panel plugin: cpufreq [23:00] Aha. Figured it out. AMD doesn't even have a CPU governor anymore. I speculate that the reason is exactly what we discussed. [23:00] so it always shows performance or ondemand? [23:01] Or does it allow setting highest lowest speed? [23:01] we need to test for that then and disable the dropdown. [23:02] It always shows ondemand in -controls, but there is now governor showing in any utility I've tried, meaning the governor may not exist, which means -controls just can't parse it and defaults. [23:02] *no governor [23:03] cpufrequtils? [23:05] cpufreq-info -g gives no response. [23:06] https://www.kernel.org/doc/html/v4.15/admin-guide/pm/cpufreq.html [23:06] lots to read [23:06] AMD does have boost: Turbo-Core [23:07] That depends on the processor. Mine does not. [23:08] gotta run [23:08] K, see ya. [23:55] OvenWerks: When you get back, the mystery deepens: https://paste.ubuntu.com/p/S7XMR4Zcck/