Sorry to hear you have troubles again Stephen. The latest driver from the graphics-drivers ppa is 390.25. I don't know why you got 384.116. I just installed a new Ubuntu 16.04 system on my new kitchen tabletop system and had no problems.

I installed the ppa. I rebooted. I went back to Software & Updates and selected the Additional Software tab. It offered the proprietary 384.111 driver which is a big no-no as Juan and myself found out. It also offered the 390.25 open-source Nvidia driver which I am already using on my first Linux system. I checked that radio button and selected Install.

It downloaded the driver and asked me to reboot. Voila!. I went from the bone-stock Nouveau 640 X 480 default basic driver and desktop resolution straight to the Nvidia 390.25 driver and 1280 X 960 resolution of the panel I am using to test with.

I can finally scroll around and see all my programs correctly. Been updating system files and adding all the usual programs I use in Ubuntu. The only thing that took longer than usual is the download speed as I am using a wireless card instead of my usual wired 1GB wired connection because I am installing and updating the system from the kitchen table.

I think if I remember correctly that you are using some sort of kludged USB install or something like that. Correct? Maybe that is why you always have issues. Can't you just install to a normal hard drive?

---

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

A proud member of the OFA (Old Farts Association)

Sorry to hear you have troubles again Stephen. The latest driver from the graphics-drivers ppa is 390.25. I don't know why you got 384.116. I just installed a new Ubuntu 16.04 system on my new kitchen tabletop system and had no problems.

. . No, I installed video drivers 390.25 but it also updated Linux to release 116, which surprised me as there was no mention of that in the process.

I installed the ppa. I rebooted. I went back to Software & Updates and selected the Additional Software tab. It offered the proprietary 384.111 driver which is a big no-no as Juan and myself found out. It also offered the 390.25 open-source Nvidia driver which I am already using on my first Linux system. I checked that radio button and selected Install.

It downloaded the driver and asked me to reboot. Voila!. I went from the bone-stock Nouveau 640 X 480 default basic driver and desktop resolution straight to the Nvidia 390.25 driver and 1280 X 960 resolution of the panel I am using to test with.

. . I always avoid Nouveau drivers as I was warned against them early on.

I can finally scroll around and see all my programs correctly. Been updating system files and adding all the usual programs I use in Ubuntu. The only thing that took longer than usual is the download speed as I am using a wireless card instead of my usual wired 1GB wired connection because I am installing and updating the system from the kitchen table.

I think if I remember correctly that you are using some sort of kludged USB install or something like that. Correct? Maybe that is why you always have issues. Can't you just install to a normal hard drive?

. . I could possibly do that on one system but I would not want to lose the Host ID that has built up the credits it has. I should probably study Juan's process for preserving the host ID and jump to Linux 16.04 and BOINC 7.8.33. bring it all up to date, and maybe go to CUDA90 as well :) I just get nervous knowing that one small error can trash it all and force me to start from scratch ...

. . It isn't a kludged install, just running from a USB flashdrive instead of SSD or mechanical drive. It worked fine from the original release (was it 68 or 72?) but started going wrong with all releases after 96 ...

Stephen

:(

OK, I was thrown by your mention of 116 and thought you were referring to video driver. Now understand you are referring to kernel build numbers. What distro are you running? Totally unfamiliar with those kernels you mention.

---

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

A proud member of the OFA (Old Farts Association)

Steven, when building a new system and preserving stats, just copy your old stats files to the new system BEFORE you attach to the SETI project.
So install BOINC, Copy, Attach.
The version of Linux doesn't matter, it's more a Win/Linux change that does.

. . No, I installed video drivers 390.25 but it also updated Linux to release 116, which surprised me as there was no mention of that in the process.

That is why I like to use the Synaptic Package Manager. It allows you to see exactly what packages you are downloading and installiing BEFORE you commit to anything. I like being able to see exactly what is going to be installed. I also monitor the installation window and look for any error messages or comments on the package installation to see if there is a conflict or error.

If you had used Synaptic, you would have been apprised that other packages were also going to be upgraded along with the video driver. You could then have gone back to the selection process and untoggled the application commit on the newer kernel and just installed the 390.25 drivers.

---

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

A proud member of the OFA (Old Farts Association)

OK, I was thrown by your mention of 116 and thought you were referring to video driver. Now understand you are referring to kernel build numbers. What distro are you running? Totally unfamiliar with those kernels you mention.

. . Ubuntu 14.04 LTS.

Stephen

. .

Steven, when building a new system and preserving stats, just copy your old stats files to the new system BEFORE you attach to the SETI project.
So install BOINC, Copy, Attach.
The version of Linux doesn't matter, it's more a Win/Linux change that does.

. . OK, that will work on Bertie where Boinc is in the home folder under BOINC, not sure I can make that happen on the machine using the repo version of BOINC where it is under 2 or more folders under the root directory.

Stephen

. .

. . No, I installed video drivers 390.25 but it also updated Linux to release 116, which surprised me as there was no mention of that in the process.

If you had used Synaptic, you would have been apprised that other packages were also going to be upgraded along with the video driver. You could then have gone back to the selection process and untoggled the application commit on the newer kernel and just installed the 390.25 drivers.

. . Maybe I should try one more time using Synaptic ...

Stephen

:(

What issues did you have before with Synaptic. I've never ever had any issues with the program. It just works.

---

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

A proud member of the OFA (Old Farts Association)

What issues did you have before with Synaptic. I've never ever had any issues with the program. It just works.

. . Sorry, I have never had any problems with Synaptic, I meant one more try to update the drivers, using Synaptic. On that subject when I fired it up (Synaptic) I discovered I am running 390.25 already, the regression to version 96 and the repair in recovery mode did not revert the video drivers. I presumed it had because the AP tasks still will not run. :(

. . Whatever is interfering with OpenCL it may not be driver related. I guess I will just have to deal with it as is.

Stephen

:(

Stephen, I helped Benji66 out in the GPU Not Detected - Linux thread and it raised some interesting things for you to check.

Since you have Synaptic installed, put nvidia* into the Search box and scroll through all the nvidia drivers and applications that it shows as installed on your system. You need to make sure you have the Cuda drivers that you want as well as the matching version number OpenCL-icd drivers as well as the matching libcuda drivers for the same version level as the main nvidia drivers.

He couldn't get BOINC to see his Nvidia cards until he installed the OpenCL-icd drivers and the libcuda-390 drivers that matched the Nvidia 390.25 drivers he installed. Once he installed those missing drivers, BOINC is now reporting seeing his card.

You need to check all your installed drivers related to the 390.25 driver installation you have attempted.

---

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

A proud member of the OFA (Old Farts Association)

Stephen,
it raised some interesting things for you to check.

Since you have Synaptic installed, put nvidia* into the Search box and scroll through all the nvidia drivers and applications that it shows as installed on your system. You need to make sure you have the Cuda drivers that you want as well as the matching version number OpenCL-icd drivers as well as the matching libcuda drivers for the same version level as the main nvidia drivers.

You need to check all your installed drivers related to the 390.25 driver installation you have attempted.

. . I have all of the following:

libcuda 1-390
hbgl1-mesa-glx-lts-xenial {openGL so should not matter}
nvidia-390 {binary driver}
nvidia-opencl-icd-390
nvidia-prime
ocl-icd-libopencl1
ububtu-drivers-common

Stephen

. .

Oh well, just thought of something to check since the OpenCL-icd and libcuda 390 drivers being missing for Benji66 was causing his card to not be seen. Fixed that and he now sees the card. Just thought following the same troubleshooting path would fix your AP issue.

---

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

A proud member of the OFA (Old Farts Association)

Oh well, just thought of something to check since the OpenCL-icd and libcuda 390 drivers being missing for Benji66 was causing his card to not be seen. Fixed that and he now sees the card. Just thought following the same troubleshooting path would fix your AP issue.

. . Anything that is in any way relevant is worth a try. Sadly I have no idea where the issue arose because I received so few AP tasks on that rig back then that I cannot say when the last successful run was. Strangely, since I have set it to NOT receive AP tasks I have never received so many. The SETI servers must be female, ... oh I am so gonna pay for that one :)

Stephen

:)

. . Since my 1050ti lost its fans and had to be sent away (no progress for over 6 days) I decided to run the rig using the built in Intel GMA 4500 graphics chip. No good for crunching but it has enabled me to run the rig and move the stalled tasks to the CPU to get them done for the sake of my wingmen.

. . The problem is that runs in a default resolution of 1024 by 768, is there anything in Linux (Ubuntu 14.04 LTS) that will let me monitor and/or adjust the settings on this built in graphics chip?

Stephen

??

Have you looked in System Settings yet for the Display tool and see what resolutions are offered for your monitor yet in the drop-down menu? If there is only one screen resolution offered you will have to add the mode you desire with the xrandr tool in a Terminal session.

First run

 xrandr

and see what the monitor and drivers offer. Then add the desired resolution to the .profile and reconfigure Xorg.conf.

How to Set A Custom Screen Resolution in Ubuntu Desktop

Ubuntu Wiki - Resolution

---

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

A proud member of the OFA (Old Farts Association)

Have you looked in System Settings yet for the Display tool and see what resolutions are offered for your monitor yet in the drop-down menu? If there is only one screen resolution offered you will have to add the mode you desire with the xrandr tool in a Terminal session.

First run

 xrandr

and see what the monitor and drivers offer. Then add the desired resolution to the .profile and reconfigure Xorg.conf.

How to Set A Custom Screen Resolution in Ubuntu Desktop

Ubuntu Wiki - Resolution

. . Thank you kindly Keith.

. . That has it sorted out. The second link went further than I needed but the first was excellent and solved the problem. I now can see everything I need without looking at a distorted screen with only a fraction of the page showing :)

Stephen

:)

. . Well I guess it's time I got the Ryzen working and updated to a new setup with the latest versions. When I get the harware sorted I will publish a new "Starting Guide" with the appropriate links.

. . Keep the faith ...

Stephen

:)

Good. Just in time to see all the new AMD Ryzen+ chips and X470 motherboards come onto the market.

---

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

A proud member of the OFA (Old Farts Association)

Hi Stephen,
When using the repository version of BOINC, don't you have to install OpenCL and Cuda for BOINC as well as for the video driver?
Open Synaptic and type in BOINC, you should see OpenCL and Cuda listings for it. You need to install those also.
Maybe that will fix your problem. Hope so.
Good Luck.

---

Bruce