Sure. Don't know why there would be any difference in a DVD based ISO install versus the normal one of USB based ISO install, but post what you found.

What exactly apparently "blows up" during the install? A few well known ones are easily avoided by adding "nomodeset" to the kernel command load lines in the grub file at boot with a simple edit.

https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu

---

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

A proud member of the OFA (Old Farts Association)

In the past I've had "issues" creating working, bootable DVD installation ISOs - sometimes a particular utility will work, other times not.
In the end I tried using a USB stick, and, apart from when I did a "brain fade" I've never had any problems with quite a wide range of "USB-ISO" creating apps.
It's also worth remembering that one can use a USB device to try Linux before you install it WITHOUT risking your existing (windows) installation.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

In the past I've had "issues" creating working, bootable DVD installation ISOs - sometimes a particular utility will work, other times not.
In the end I tried using a USB stick, and, apart from when I did a "brain fade" I've never had any problems with quite a wide range of "USB-ISO" creating apps.
It's also worth remembering that one can use a USB device to try Linux before you install it WITHOUT risking your existing (windows) installation.

No problem to burn a DVD from ISO that worked fine using CDBurnerXP freeware. Booting from DVD also allows you to Liveboot and try without damage to Win.
Issue I had was that the system would freeze during the slideshow while installing. No keyboard, no mouse, icon stopped rotating, etc.
A bit of research revealed known bugs related to this. Two possibilities.
First, a needed Ubiquity update (n/a in my case, as the ISO was freshly downloaded).
Second, a display scaling setting at 200% when it needed to be at 100%.
While it was properly set to 100%, I changed it to 200%, then back to 100%, applied it and that solved the lockup. {shrugs} Installers hate me.

---

So, a quick question for someone who has the all in one installed and running. Pardon me, if it's in a read me I missed or something I should know, but it's been 30 years since I've done much with UX, and those brain cells are in rough shape.
First the good news.
I am amazed by the performance I'm seeing on my test box, which is a core2quad equivalent Xeon with 2xGTX-980s. MBs are running in about 60 seconds, VLARs and GBT in about 120 sec.
Bad news is I can't get BOINC to start on boot, and even when starting BOINCMGR manually I have to select the host manually and reenter the password each time to get the client loaded. I must be missing something, just can't figure out what. My recollection is that in Win once you walked the Manager through the connect once it was saved.
So, a couple questions.
First, is the directory location an issue? I chose to create the BOINC folder in the Home/Desktop directory. I know if you use sudo install rather than the all-in-1 it would probably end up in /usr/bin.
Second, what's the right way to invoke BOINC for auto start. I've tried adding both boinc and boincmgr to startup, with no joy, as well as trying to start using run_client and run_manager.
I should note that the significant changes I made were to replace the supplied cc_config.xml with my own, and used my own gui_rpc_auth.cfg and remote_hosts.cfg to enable BoincTasks management from another machine (which is working just fine once I finally get it all up.) BOINC log indicates it's acting on that, and gives no errors.
I'd appreciate it for someone who has it starting up correctly to pass on what they did.
Thx,
Jim ...

---

So do I understand that simply double-clicking on boincmgr DOES NOT start the client in your case?

Once you have both the client and Manager running, have you docked the Manager for easy access and startup and added it as a Favorite?

You might need to create a desktop file for the Manager. This is the one I am using that I copied from my old Ubuntu 16.04 installation.

[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=BOINC Manager
Icon=/home/keith/Desktop/BOINC/boincmgr.32x32.png
Path=/home/keith/Desktop/BOINC
Exec=/home/keith/Desktop/BOINC/boincmgr
StartupNotify=false
StartupWMClass=Boincmgr
OnlyShowIn=Unity;
X-UnityGenerated=true

Once you create the file, dump it down in /home/keith/.local/share/applications but edit in your username and put it in your own user home directory. Set the execute flag for Permissions.

You can try adding the client to the Startup Applications menu. I don't run the client at startup but prefer to start it by choice by simply clicking on the Boinc Manager icon I have in the Dock.

---

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

A proud member of the OFA (Old Farts Association)

So do I understand that simply double-clicking on boincmgr DOES NOT start the client in your case?

Correct. It will sit there Disconnected, and I must manually tell boincmgr to File>select computer, then select localhost and replace the password that pops up with the once located in the RPC auth file to accomplish the connect.

Once you have both the client and Manager running, have you docked the Manager for easy access and startup and added it as a Favorite?

No.

You can try adding the client to the Startup Applications menu. . .

As noted, I've tried during that 4 different ways (start the client, start the manager, start run_client, start run_manager)

---

In the past I've had "issues" creating working, bootable DVD installation ISOs - sometimes a particular utility will work, other times not.
In the end I tried using a USB stick, and, apart from when I did a "brain fade" I've never had any problems with quite a wide range of "USB-ISO" creating apps.
It's also worth remembering that one can use a USB device to try Linux before you install it WITHOUT risking your existing (windows) installation.

Hi Rob,

I've been using Rufus to burn Linux and Windows 10 ISOs to USB sticks. Now I use Micro$oft's Media Creation Tool for Windows. I have had no problems with Rufus or MCT for USB sticks.

Have a great day! :)

Siran

[edit] OOPS! Wrong URL. :( Fixed it. :) [/edit]
[edit2] BTW, I use the portable version, no installation required. :) [/edit2]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

So, a quick question for someone who has the all in one installed and running. Pardon me, if it's in a read me I missed or something I should know, but it's been 30 years since I've done much with UX, and those brain cells are in rough shape.
First the good news.
I am amazed by the performance I'm seeing on my test box, which is a core2quad equivalent Xeon with 2xGTX-980s. MBs are running in about 60 seconds, VLARs and GBT in about 120 sec.
Bad news is I can't get BOINC to start on boot, and even when starting BOINCMGR manually I have to select the host manually and reenter the password each time to get the client loaded. I must be missing something, just can't figure out what. My recollection is that in Win once you walked the Manager through the connect once it was saved.
So, a couple questions.
First, is the directory location an issue? I chose to create the BOINC folder in the Home/Desktop directory. I know if you use sudo install rather than the all-in-1 it would probably end up in /usr/bin.
Second, what's the right way to invoke BOINC for auto start. I've tried adding both boinc and boincmgr to startup, with no joy, as well as trying to start using run_client and run_manager.
I should note that the significant changes I made were to replace the supplied cc_config.xml with my own, and used my own gui_rpc_auth.cfg and remote_hosts.cfg to enable BoincTasks management from another machine (which is working just fine once I finally get it all up.) BOINC log indicates it's acting on that, and gives no errors.
I'd appreciate it for someone who has it starting up correctly to pass on what they did.
Thx,
Jim ...

To get BOINC to start on boot run this in a terminal:

sudo systemctl enable boinc-client

Bad news is I can't get BOINC to start on boot, and even when starting BOINCMGR manually I have to select the host manually and reenter the password each time to get the client loaded. I must be missing something, just can't figure out what. My recollection is that in Win once you walked the Manager through the connect once it was saved.
So, a couple questions.
First, is the directory location an issue? I chose to create the BOINC folder in the Home/Desktop directory. I know if you use sudo install rather than the all-in-1 it would probably end up in /usr/bin.
Second, what's the right way to invoke BOINC for auto start. I've tried adding both boinc and boincmgr to startup, with no joy, as well as trying to start using run_client and run_manager.
I should note that the significant changes I made were to replace the supplied cc_config.xml with my own, and used my own gui_rpc_auth.cfg and remote_hosts.cfg to enable BoincTasks management from another machine (which is working just fine once I finally get it all up.) BOINC log indicates it's acting on that, and gives no errors.
I'd appreciate it for someone who has it starting up correctly to pass on what they did.
Thx,
Jim ...

First, the Berkeley version of BOINC is copied, Not Installed, to the users Home Folder, /home/Username.
You should Never have to use a Password to run boincmgr from /home/username/BOINC. This implies you have changed the Owner from Me to something else.
Running the Berkeley version from the All-In-One is as easy as expanding the download to your Home folder, opening the BOINC folder, and double clicking the file boincmgr.
If that doesn't work, then you have changed something.

To run the Berkeley version of BOINC from the Terminal, you Change Directories to the Folder containing boincmgr, and then run boincmgr. cd home/username/BOINC, then ./boincmgr.
The Old, Outdated, instructions are here, https://boinc.berkeley.edu/wiki/Installing_BOINC#The_Berkeley_Installer The updated instructions are simple, expand to Home folder, open folder, double click on boincmgr.

I will admit that I have turned a spare MB and 750ti into a linux cruncher, the installation was OK but the Nvidia drivers took a while to install.

I also used the "special app" first time for me, I now have a 750ti completing tasks quicker than my 1660ti ;-) (Around 5 mins)

https://setiathome.berkeley.edu/show_host_detail.php?hostid=8730293

The errors were CPU tasks that I didn't mean to download as I won't be using the CPU

Only problem is it will run headless but I cannot get Boinc Tasks to connect.

Any help with that would be welcome.

Next question, how easy will it be to add a second 750ti (I have 4 spare)

Next question, how easy will it be to add a second 750ti (I have 4 spare)

As long as the PSU will hold it. Shut down machine. Install video card. Boot.

I have been using up to two gtx 750Ti's under the All-in-One and along as I have slots open I have been pretty much been able to add cards.

---

A proud member of the OFA (Old Farts Association).

@Jimbocous, as TBar says, you must have changed something. Maybe you tried to install it the old repo client version way. With the AIO, just unpack and double-click the boincmgr file.

[Edit] Did you by chance copy your gui_rpc_auth.cfg file from a Windows host? That probably is the issue if you did. Windows and Linux don't use the same LF and CR conventions. Your gui_rpc_auth.cfg file probably has extraneous characters that Linux is balking at. I would delete the gui_rpc_auth.cfg file and recreate with the Text Editor in Linux with a manual entry of the password. Don't hit the Enter key after putting in the password to make a new line, just enter the password and Save it.

@Bernie, normally the problem with BT not finding a host has to do with the password in the gui_rpc_auth.cfg file. I would first try the Find Computers function from the Computers menu option. The subnet address for your network should be automatically filled in. Next put in the password that you have in your gui_rpc_auth.cfg file. I have simply the set the password to be the same across all my hosts which simplifies things. Then hit the scan address range button in BT and see if your host shows up. If it does, then simply select it and then hit the Add Selected Computer button.

The other method is when your host shows in your list of computers but the status says Not Connected or Password. Then you can simply click on the blanked out ***** in the hosts line which will open an edit or entry line. Put in the password from your gui_rpc_auth.cfg file and then hit Enter. The host status should then change to Connected after the polling takes place. If it doesn't show up after 30 seconds, exit BT fully by using the File >> Exit menu option and then relaunch BT. Sometimes you need to restart BT for it to pick up a new computer. It can also be helpful to highlight the computer in the left hand computers list since that forces the polling again for that computer.

---

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

A proud member of the OFA (Old Farts Association)

To get BOINC to start on boot run this in a terminal:

sudo systemctl enable boinc-client

Failed to enable unit: Unit file boinc-client.service does not exist.

I assume this is due to how TBar has it installed, i.e. unpacking files. As he noted, an actual install does not happen.
But I don't get why adding it to Startup Applications Preferences doen't work, as I would think it would.
Thx, Jim ...

---

Good point Jimbocous. I forgot to mention the use of the MAC address as a surefire way to identify the host. If you don't have a hosts file that defines the common names of your hosts on your network, then then IP address may not work as well. I have hosts files on all my computers that simplifies identifying them on the network and makes it easier to map their resources to the File Manager for simple access of shares.

I play a silly game here.
I configure everything on the network (crunchers, other PCs, smart TVs, smart BDs, printers, cameras, etc.) as DHCP.
I then go into the DHCP section of my router and define, by MAC address, what IP I want the router to give each device, with IP ranges assigned by device type.
If I want to make a change, I have one place to go to, one type of change to make. No HOSTS files, no config at all on the actual unit.
Seems to work well for me.

---

Yes, that suggestion offered is only for the repo service install version. You are not using a service install, you are using a user install. The reason that adding the client to Startup Applications does not work is that you have not created the Desktop file I posted earlier. For some reason Ubuntu 18.04 does not create the BOINC Manager desktop file that was always created by default without intervention on Ubuntu 16.04. Something to do with the change from Unity desktop interface to Gnome desktop interface.

Again the AIO SHOULD run the client and startup the Manager just by double clicking on the boincmgr file. I would first try to make the desktop file for the Manager, fix any issues with gui_rpc_auth.cfg and then if nothing works, delete the Boinc folder and reinstall the AIO by unpacking the application. Then do nothing but double-click the boincmgr file and see if it launches and connects to the client normally. Then you can go about adding in your cc_config and gui_rpc_auth.cfg and remote_hosts files.

---

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

A proud member of the OFA (Old Farts Association)

I will admit that I have turned a spare MB and 750ti into a linux cruncher, the installation was OK but the Nvidia drivers took a while to install.
I also used the "special app" first time for me, I now have a 750ti completing tasks quicker than my 1660ti ;-) (Around 5 mins)
https://setiathome.berkeley.edu/show_host_detail.php?hostid=8730293
The errors were CPU tasks that I didn't mean to download as I won't be using the CPU
Only problem is it will run headless but I cannot get Boinc Tasks to connect.
Any help with that would be welcome.
Next question, how easy will it be to add a second 750ti (I have 4 spare)

. . Way to go Bernie!

. . I am impressed with the 750ti, I had thought the run times would be closer to 6 mins, 5 mins is very impressive. My 1050ti takes 4 so 5 is very impressive to me. Keep up the good work. If you can another one or three 750ti's into that rig it will be a mighty little machine.

Stephen

:)

Did you by chance copy your gui_rpc_auth.cfg file from a Windows host?

Indeed. I assumed that the extra would show up in the text editor, but no. Been a while ...
Fixing gui_rpc_auth.cfg solved the connect client issue, without breaking it on the BOINCTasks side.
Didn't help with resolving machine names in remote_hosts.cfg, but since

<allow_remote_gui_rpc>1</allow_remote_gui_rpc> 

in cc_config.xml allows any host to RPC, the remote_hosts file is unneeded and I deleted it.
Guess I better clean up cc_config.xml as well, just to be sure, although it seems BOINC is reading it properly. Presumably the XML syntax makes it immune to that particular disorder.
Now, to solve the startup issue.
As always, thanks!

---

OK, finally got it to auto start properly and in the right directory on boot.
Guess I missed the part where you need to run the binstall.sh shell script from a terminal window.
Good refresher, for sure ...

---

Despite my problems with BT and the fact that I really do not like Linux, I have to say the results with the "special app" are nothing short of amazing

One of my GTX750ti's which managed around 20 minutes a task in Windows is now averaging 3.6 minutes (averaged using the first 80 tasks to validate).

That sort of increase is just plain silly ;-) 400 tasks a day as opposed to 72 !!

I have 3 spare 750ti's so I will let this one run for 24 hours, see what the RAC is then hopefully add another. (May need a better PSU)

Now I have finally "taken the plunge" with the special app, I will probably convert the machine with the 1060 as well.

As these machine are simply crunchers and I don't have to "use" Linux much I think I can live with it ;-)

Interesting times.

Despite my problems with BT and the fact that I really do not like Linux, I have to say the results with the "special app" are nothing short of amazing

Agreed.
My old Gigabyte mobo (3ghz Core2Quad Xeon w/4 gig RAM and a slow HDD) is cheerfully chewing though a VLAR or GBT every 2 minutes or a regular PFB every 1 minute, on each of 4 980's.
Of course, the down side is that my UPS test failed and now after the box lost power, boingmgr will now not load. Period.
The client starts and does its thing, run mgr and nothing happens.
Troubleshooting for another day, I guess.

---