Since I have had trouble with drivers for Vega10 in Linux, I have setup another boot drive on my system and installed Ubuntu 18.04 to work with the latest drivers from AMD. My boinc working directory is on another drive which is accessible if I boot to either OS. Since I have installed 18.04 on the additional drive, the original installation still works (the one getting invalid results with ROCm1.8), but when I try to run boincmgr in 18.04, I get the error "Gtk-Message: 22:32:05.221: Failed to load module "canberra-gtk-module". The interface comes up but never connects to the project. During install I did a minimal installation, so not sure if that is an issue or perhaps sharing this data drive between OS version, or maybe an issue with boincmgr in 18.04. Has anyone tried 18.04 yet?

---

GitHub: Ricks-Lab
Instagram: ricks_labs

Hi Rick. I think I was one of the first to jump to 18.04 and am having some minor issues with it.

It runs the Tbar 7.4.44 version fine from the Boinc folder on the desktop. But I got the same problem of of you when I finally was able to dock it and launch from there. The Manager window opens up but never connects to the client.

I have been posting asking for help everywhere. From Boinc and Gnome developers both. The problem comes from there is no standard across Linux distributions for the format of .desktop files.

I managed to get Boinc to work correctly from the dock accidentally somehow when I installed about two dozen additional packages for the Rescheduler. Still don't know which of those allowed Boinc to work from the dock.

I was getting that Canberra-gtk error long before installing Boinc so I don't think the issue lies there.

I would suggest posting jn the Questions and Problems section of the forum so that Jord sees it and can add you to list of people having issues with 18.04.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Ruike,

What BOINC version and where did you install it from?

Ruike,

What BOINC version and where did you install it from?

I’m running 7.8.3 from TBar.

---

GitHub: Ricks-Lab
Instagram: ricks_labs

Hi Rick. I think I was one of the first to jump to 18.04 and am having some minor issues with it.

It runs the Tbar 7.4.44 version fine from the Boinc folder on the desktop. But I got the same problem of of you when I finally was able to dock it and launch from there. The Manager window opens up but never connects to the client.

I have been posting asking for help everywhere. From Boinc and Gnome developers both. The problem comes from there is no standard across Linux distributions for the format of .desktop files.

I managed to get Boinc to work correctly from the dock accidentally somehow when I installed about two dozen additional packages for the Rescheduler. Still don't know which of those allowed Boinc to work from the dock.

I was getting that Canberra-gtk error long before installing Boinc so I don't think the issue lies there.

I would suggest posting jn the Questions and Problems section of the forum so that Jord sees it and can add you to list of people having issues with 18.04.

Hi Keith, Thanks for sharing your experience. It is good to know it is not something strange that I did. I think I am going to wait out 18.04 for a while and use the small amount of spare time I have to work the ROCm issue. I have set up a repeatable bench test and working through other testing.

---

GitHub: Ricks-Lab
Instagram: ricks_labs

Just as a followup Rick, I upgraded my last Win7 system to 18.04 and didn't have any issues with BOINC Manager docking or launching at all. I did already have the BOINC Manager .desktop file in place to start with before I launched the Manager for the first time. No issues at all with the second conversion. Guess practice makes perfect.

Now if I can only figure out why I lost my all cores boost on the Intel i7-6850K system with the ASUS X99-E-10G-WS motherboard. Hadn't even touched that system in a month and somewhere along the way it stopped boosting all cores to the 42 multiplier. Hadn't changed anything in the BIOS. Still set up to Sync all cores at 42. But now only one core boosts to 4000 and the rest only run at 3800. So something changed in the OS. Spent the whole day yesterday researching the cpufreq subsystem and governor documentation. Tried every combination of software configurations and BIOS changes and could never regain my all core boost in the OS.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I had a similar problem when Ubuntu 16.04 installed 384.130
a couple days ago.

I fixed it with the series of actions I document in
https://setiathome.berkeley.edu/forum_thread.php?id=82997

which was advice I think I got from Tbar in march 2017.
Worked then and worked today.

I wonder if I messed something up in .desktop by having the same ssd mounted as /home for the system booted in both 16.04 and 18.04. So busy recently that I just don't have time to investigate. Looks like I will be busy for at least the new few weeks.

That is strange behavior of the X99 MB. My only X99 system is my wife's desktop and just running stock so I don't have to deal with it. Just have to have it stable so she doesn't complain!

Just as a followup Rick, I upgraded my last Win7 system to 18.04 and didn't have any issues with BOINC Manager docking or launching at all. I did already have the BOINC Manager .desktop file in place to start with before I launched the Manager for the first time. No issues at all with the second conversion. Guess practice makes perfect.

Now if I can only figure out why I lost my all cores boost on the Intel i7-6850K system with the ASUS X99-E-10G-WS motherboard. Hadn't even touched that system in a month and somewhere along the way it stopped boosting all cores to the 42 multiplier. Hadn't changed anything in the BIOS. Still set up to Sync all cores at 42. But now only one core boosts to 4000 and the rest only run at 3800. So something changed in the OS. Spent the whole day yesterday researching the cpufreq subsystem and governor documentation. Tried every combination of software configurations and BIOS changes and could never regain my all core boost in the OS.

---

GitHub: Ricks-Lab
Instagram: ricks_labs

Pretty sure it was the change from the 4.13 to 4.15 kernel that caused the issue. The intel_pstate driver is the only cpu driver by default now. They dumped the older acpi_freq driver. It is not even available anymore in the kernel as a fall through if you disable the intel_pstate driver. The only governors are powersave and performance. But both governors get their max freqs and default Intel boost specs from the hardware registers and ignore what the motherboard says is available. So the feature of the Asus workstation motherboards for all core boost is ignored. And I have not figured a way to edit the max freq files even as root. The files are locked. I think I will have to boot to emergency terminal and see if I can edit the files from there. But I have my doubts even that will work since the cpufreq system initializes very early in the kernel.

I have found that setting the intel_pstate driver to passive at least gets you the traditional governors, but I have been unsuccessful so far in changing the governor away from performance even when I set the governor up in the cpufrequtils file in /etc/default and /etc/init.d. Still locked down to only two cores, the Intel default, boosting to the max 4Ghz frequency and the rest only running at 3800Mhz.

Did you say that your wife's X99 18.04 system boosts to an all-core clock?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

No, my wife is running Win10.

Pretty sure it was the change from the 4.13 to 4.15 kernel that caused the issue. The intel_pstate driver is the only cpu driver by default now. They dumped the older acpi_freq driver. It is not even available anymore in the kernel as a fall through if you disable the intel_pstate driver. The only governors are powersave and performance. But both governors get their max freqs and default Intel boost specs from the hardware registers and ignore what the motherboard says is available. So the feature of the Asus workstation motherboards for all core boost is ignored. And I have not figured a way to edit the max freq files even as root. The files are locked. I think I will have to boot to emergency terminal and see if I can edit the files from there. But I have my doubts even that will work since the cpufreq system initializes very early in the kernel.

I have found that setting the intel_pstate driver to passive at least gets you the traditional governors, but I have been unsuccessful so far in changing the governor away from performance even when I set the governor up in the cpufrequtils file in /etc/default and /etc/init.d. Still locked down to only two cores, the Intel default, boosting to the max 4Ghz frequency and the rest only running at 3800Mhz.

Did you say that your wife's X99 18.04 system boosts to an all-core clock?

---

GitHub: Ricks-Lab
Instagram: ricks_labs

An update to my all core boost woes. I saw that there was a new 0903 BIOS for the motherboard with manufacturer implemented Meltdown/Spectre fixes. So I flashed the new BIOS.

That forced a completely new and virgin BIOS configuration so I lost all my previous user profiles. The BIOS set up the memory and core clocks differently than what I had used before. It achieved the XMP 3000 memory setting by changing to a 125Mhz BCLK setting and an Sync All Cores multiplier of 32. That accomplished a cpu core clock of 4000Mhz and the expected 3000Mhz memory strap of the XMP profile of the kit.

But what I found in the OS was that I had my all core boost again at the normal system clock of 4000Mhz. But the BIOS says to use if possible a standard front side bus frequency of 100Mhz and achieve the desired core clock and memory strap settings with a higher multiplier. This is how I had the system set up previously. 100 Mhz BCLK and 42 multiplier for 4200Mhz cpu clock and the XMP 3000 Mhz memory strap.

When I did that though I lost my all core boost again and was back again with the original problem of only two cores boosting to 4000Mhz and the rest at 3800Mhz. All the BIOS settings were set by default to Auto just as before.

As soon as I went back to the BLCK of 125Mhz and the multiplier of 32, I got my all core boost back again at 4000Mhz. So I set up a 34 Sync All Cores multiplier for a derived 4250Mhz cpu core clock and the XMP 3000 memory profile. I was able to get my same Vcore voltage back by setting a manual voltage of what I was running previously with an Auto with Offset voltage setting.

So once again I am boosting all cores at my desired core clocks.

So, there is definitely a difference between what the cpu exports in the MSR registers to the OS when achieving the desired cpu Turbo Boost settings via a BCLK of 125Mhz and one of 100Mhz. The 100Mhz BCLK setting prevents a all core Turbo Boost with the default intel_pstate scaling driver and performance governor. So for anyone that lost their all core Turbo Boost with the new 4.15.0-20 kernels, this is the way to get it back.

[Edit] Addendum. What this accomplished was reducing my BLC cpu task completion times from 51 minutes down to 32 minutes. Now the Intel system can run the BLC cpu tasks as fast as the Ryzen systems.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)