boinc???

Post here if you are a new Porteus member and you're looking for some help.
Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#46 by Bogomips » 15 Sep 2015, 15:41

@wacojohn
You are getting there bit by bit. File's good. You just have a procedural problem. To copy and paste, click on SELECT ALL in 'CODE: SELECT ALL', then hit Ctl+c (^C) to copy to clipboard. At prompt in terminal hit Ctl+v (^V) to paste in. If you have some other way of copying and pasting, do that if more comfortable with that. You can practise this with

Code: Select all

lsblk | grep loop
(For my sins have given a computer appreciation class for adults. So you can rest easy)

All these remaining steps can be done as user guest, doing copy and paste! (activation requires supplying root's password):
  1. Code: Select all

    activate bcx_140915.xzm
    lsblk
    ldd /usr/bin/boinc|grep not
    
    There should be no diagnostic output from last command.
  2. If there is diagnostic output, please post all terminal output so far. Could be that xfce doesn't have gtk2, or that we have to iron out differences between your setup and mine. Anyway you will be doing testing of module for general release. :wink:
  3. If clean, need to strip Boinc of executables, placing them somewhere, where they can do no harm, before boincing:

    Code: Select all

    mkdir /tmp/bnc
    for b in  BOINC/boinc*; do ! [[ $b =~ png$ ]] && mv $b /tmp/bnc; done
    cd BOINC
    boinc --daemon
    boincmgr 
    
P.S.
wacojohn wrote: Er ... I don't know a script from a scrap .... but I think this is it:

Code: Select all

cd "/home/guest/BOINC" && exec ./boinc $@
Normally script begins with a shebang:

Code: Select all

#!/bin/bash
, but this did not, so downloaded the Berkeley Package to verify.
For your convenience:
The Berkeley Installer
...

This creates a directory called BOINC/ under the home directory containing the following files:

boinc
The BOINC core client.
boincmgr
The BOINC Manager.
boinccmd
A command line tool for controlling a running core client.
run_client
A script that cd's into the BOINC directory and runs the core client.
run_manager
A script that cd's into the BOINC directory and runs the manager.

You may want to automatically start the core client at boot time. If you do not want to auto-start BOINC and prefer a manual start method then in a terminal enter

./run_client --daemon; ./run_manager
Thanks. This helped to work out how to start boinc correctly.

P.P.S. Am here for the next few hours. Will cast a glance at Porteus now and then, so we'll be able to step you through. :)
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#47 by wacojohn » 15 Sep 2015, 19:21

typed up a comprehensive reply. Got called away from computer and somehow lost it. I pretty much did all you said. Here is the tail end of the terminal session:

Code: Select all

guest@porteus:~$ lsblk | grep loop
loop0    7:0    0    16M  0 loop /mnt/live/memory/images/000-kernel.xzm
loop1    7:1    0    46M  0 loop /mnt/live/memory/images/001-core.xzm
loop2    7:2    0     4K  0 loop /mnt/live/memory/images/001-core_alldesktops-15
loop3    7:3    0  43.7M  0 loop /mnt/live/memory/images/002-xorg.xzm
loop4    7:4    0    12K  0 loop /mnt/live/memory/images/002-xorg_alldesktops-15
loop5    7:5    0  24.6M  0 loop /mnt/live/memory/images/003-xfce.xzm
loop6    7:6    0   352K  0 loop /mnt/live/memory/images/004-xfce_fixes-150124.x
loop7    7:7    0     4K  0 loop /mnt/live/memory/images/0099-settings.xzm
loop8    7:8    0  34.4M  0 loop /mnt/live/memory/images/04-firefox.xzm
loop10   7:10   0  28.3M  0 loop /mnt/live/memory/images/wxPython-2.8.12.1-i486-
guest@porteus:~$ activate bcx_140915.xzm
gksu-run: :0.0
gksu-run: psu/|opt|porteus-scripts|activate  |home|guest|bcx_140915.xzm/2016-0-porteus_TIME0
gksu-run: 96a510f3f02693b5be45e8827c7ff574

Updating shared library links:  /sbin/ldconfig
Updating XFCE menu: update-desktop-database
guest@porteus:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
fd0      2:0    1     4K  0 disk 
sda      8:0    0   9.3G  0 disk 
├─sda1   8:1    0   7.8G  0 part /mnt/sda1
└─sda2   8:2    0   1.5G  0 part [SWAP]
sr0     11:0    1  1024M  0 rom  
loop0    7:0    0    16M  0 loop /mnt/live/memory/images/000-kernel.xzm
loop1    7:1    0    46M  0 loop /mnt/live/memory/images/001-core.xzm
loop2    7:2    0     4K  0 loop /mnt/live/memory/images/001-core_alldesktops-150124.xzm
loop3    7:3    0  43.7M  0 loop /mnt/live/memory/images/002-xorg.xzm
loop4    7:4    0    12K  0 loop /mnt/live/memory/images/002-xorg_alldesktops-150126.xzm
loop5    7:5    0  24.6M  0 loop /mnt/live/memory/images/003-xfce.xzm
loop6    7:6    0   352K  0 loop /mnt/live/memory/images/004-xfce_fixes-150124.xzm
loop7    7:7    0     4K  0 loop /mnt/live/memory/images/0099-settings.xzm
loop8    7:8    0  34.4M  0 loop /mnt/live/memory/images/04-firefox.xzm
loop9    7:9    0  11.5M  1 loop /mnt/live/memory/images/bcx_140915.xzm
loop10   7:10   0  28.3M  0 loop /mnt/live/memory/images/wxPython-2.8.12.1-i486-bundle.xzm
guest@porteus:~$ ldd /usr/bin/boinc|grep not
guest@porteus:~$ ldd /usr/bin/boinc|grep not
guest@porteus:~$ mkdir /tmp/bnc
guest@porteus:~$ for b in  BOINC/boinc*; do ! [[ $b =~ png$ ]] && mv $b /tmp/bnc; done
guest@porteus:~$ cd BOINC
guest@porteus:~/BOINC$ boinc --daemon
guest@porteus:~/BOINC$ boincmgr 
and Terminal is sitting right there right now ... at the end of that line. So, I hit the return key and got:

Code: Select all

boincmgr: error while loading shared libraries: libtiff.so.5: cannot open shared object file: No such file or directory
guest@porteus:~/BOINC$ 
and then I rebooted, and:

Code: Select all

guest@porteus:~$ boinc --daemon
bash: boinc: command not found
guest@porteus:~$ 
a file search on 'boinc' returns:

Code: Select all

/mnt/sda1/porteus/changes/tmp/bnc/boinc
/mnt/live/memory/changes/tmp/bnc/boinc
/tmp/bnc/boinc

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#48 by Bogomips » 15 Sep 2015, 20:21

@wacojohn

Looks good. boinc is ok, it's only boincmgr that has to come up to speed. Make sure you still have module in /home/guest. Then do:

Code: Select all

ls -lh BOINC
activate bcx_140915.xzm
ldd /usr/bin/boinc | grep not
ldd /usr/bin/boincmgr | grep not
Post back output. Looks like it's ironing out the difference between the KDE and the XFCE desktop that has to be done.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#49 by wacojohn » 16 Sep 2015, 02:22

Thank you. That went well.

Code: Select all

guest@porteus:~$ ls -lh BOINC
total 940K
-rw-r--r--  1 guest guest  56K Sep 15 12:31 all_projects_list.xml
-rw-r--r--  1 guest guest  219 Feb 28  2014 binstall.sh
-rw-r--r--  1 guest guest  815 Feb 28  2014 boincmgr.16x16.png
-rw-r--r--  1 guest guest 2.4K Feb 28  2014 boincmgr.32x32.png
-rw-r--r--  1 guest guest 5.5K Feb 28  2014 boincmgr.48x48.png
-rw-r--r--  1 guest guest 762K Feb 28  2014 ca-bundle.crt
-rw-r--r--  1 guest guest 2.2K Sep 15 12:31 client_state.xml
-rw-r--r--  1 guest guest 2.2K Sep 15 12:31 client_state_prev.xml
-rw-r--r--  1 guest guest  195 Sep 15 12:31 daily_xfer_history.xml
-rw-------  1 guest guest   32 Sep 13 17:39 gui_rpc_auth.cfg
drwxr-xr-x 39 guest guest 4.0K Feb 28  2014 locale/
-rw-r--r--  1 guest guest    0 Sep 13 17:39 lockfile
drwxrwx--x  2 guest guest 4.0K Sep 13 17:39 notices/
-rwxr-xr-x  1 guest guest   42 Sep 13 17:34 run_client*
-rwxr-xr-x  1 guest guest   45 Sep 13 17:34 run_manager*
drwxr-xr-x  3 guest guest 4.0K Feb 28  2014 skins/
-rw-r--r--  1 guest guest  581 Sep 15 14:28 stderrdae.txt
-rw-r--r--  1 guest guest    0 Sep 13 17:39 stderrgpudetect.txt
-rw-r--r--  1 guest guest  30K Sep 15 14:28 stdoutdae.txt
-rw-r--r--  1 guest guest   68 Sep 13 17:39 stdoutgpudetect.txt
-rw-r--r--  1 guest guest  13K Sep 15 14:28 time_stats_log
guest@porteus:~$ activate bcx_140915.xzm
Updating shared library links:  /sbin/ldconfig
Updating XFCE menu: update-desktop-database
guest@porteus:~$ ldd /usr/bin/boinc | grep not
guest@porteus:~$ ldd /usr/bin/boincmgr | grep not
	libnotify.so.4 => /usr/lib/libnotify.so.4 (0xb6973000)
	libtiff.so.5 => not found
guest@porteus:~$ 

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#50 by Bogomips » 16 Sep 2015, 19:17

@wacojohn

The good news is that the module for Nautilus FM provides libtiff.so.5 dependency. The not so good new is that this module is a bundle of several packages, and not yet been able to determine the individual package providing this. The almost good news is that the afore-mentioned module has been tested on an almost bare KDE system, which means the module first made by you with USM can probably be dispensed with.

The temporary resolution being put forward now will, it seems, almost certainly run under KDE. Remains to be seen if this is also going to be the case for xfce. The Nautilus module can temporise for the moment.
  1. Download to /home/guest
    md5sum: 02a354ccacd8fb73229402e6f4c177a8 naut_121214.xzm
  2. As before check file and md5sum
    1. Ensure bcx_140915.xzm not activated (i.e. does not appear in output of following command):

      Code: Select all

      lsblk | grep loop
    2. If activated (appears in output):

      Code: Select all

      deactivate bcx_140915.xzm
      and repeat (a) to check.
  3. Activate Modules in following order (Order is Important):

    Code: Select all

    activate p1/mods/naut_121214.xzm 
    activate p1/mods/bcx_140915.xzm 
    lsblk | grep loop
    
    Should now see both modules on loops. The order of appearance does not count.
  4. Check for missing dependencies:

    Code: Select all

    ldd /usr/bin/boinc | grep "not found"
    ldd /usr/bin/boincmgr | grep "not found"
    
  5. If nothing was 'not found':

    Code: Select all

    cd BOINC
    boinc --daemon
    boincmgr 
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#51 by wacojohn » 17 Sep 2015, 04:28

Code: Select all

guest@porteus:~$ ls
BOINC/      Downloads/  Video/                             naut_121214.xzm
Desktop/    Music/      bcx_140915.xzm
Documents/  Pictures/   boinc_7.2.42_i686-pc-linux-gnu.sh
guest@porteus:~$ file naut_121214.xzm
naut_121214.xzm: Squashfs filesystem, little endian, version 4.0, 18122686 bytes, 2756 inodes, blocksize: 262144 bytes, created: Fri Dec 12 18:46:16 2014
guest@porteus:~$ md5sum naut_121214.xzm
02a354ccacd8fb73229402e6f4c177a8  naut_121214.xzm
guest@porteus:~$ lsblk | grep loop
loop0    7:0    0    16M  0 loop /mnt/live/memory/images/000-kernel.xzm
loop1    7:1    0    46M  0 loop /mnt/live/memory/images/001-core.xzm
loop2    7:2    0     4K  0 loop /mnt/live/memory/images/001-core_alldesktops-15
loop3    7:3    0  43.7M  0 loop /mnt/live/memory/images/002-xorg.xzm
loop4    7:4    0    12K  0 loop /mnt/live/memory/images/002-xorg_alldesktops-15
loop5    7:5    0  24.6M  0 loop /mnt/live/memory/images/003-xfce.xzm
loop6    7:6    0   352K  0 loop /mnt/live/memory/images/004-xfce_fixes-150124.x
loop7    7:7    0     4K  0 loop /mnt/live/memory/images/0099-settings.xzm
loop8    7:8    0  34.4M  0 loop /mnt/live/memory/images/04-firefox.xzm
loop9    7:9    0     5M  0 loop /mnt/live/memory/images/flashplayer-plugin-11.2
loop11   7:11   0  28.3M  0 loop /mnt/live/memory/images/wxPython-2.8.12.1-i486-
guest@porteus:~$ activate p1/mods/naut_121214xzm
Usage:
/opt/porteus-scripts/activate module.xzm
/opt/porteus-scripts/activate module1.xzm module2.xzm module3.xzm
/opt/porteus-scripts/activate /folder/with_modules

To disable recursive activation of folders run activate with '-o' (one level) flag:
/opt/porteus-scripts/activate -o /folder/with_modules
guest@porteus:~$ activate p1/mods/bcx_140915.xzm
Usage:
/opt/porteus-scripts/activate module.xzm
/opt/porteus-scripts/activate module1.xzm module2.xzm module3.xzm
/opt/porteus-scripts/activate /folder/with_modules

To disable recursive activation of folders run activate with '-o' (one level) flag:
/opt/porteus-scripts/activate -o /folder/with_modules
guest@porteus:~$ lsblk | grep loop
loop0    7:0    0    16M  0 loop /mnt/live/memory/images/000-kernel.xzm
loop1    7:1    0    46M  0 loop /mnt/live/memory/images/001-core.xzm
loop2    7:2    0     4K  0 loop /mnt/live/memory/images/001-core_alldesktops-15
loop3    7:3    0  43.7M  0 loop /mnt/live/memory/images/002-xorg.xzm
loop4    7:4    0    12K  0 loop /mnt/live/memory/images/002-xorg_alldesktops-15
loop5    7:5    0  24.6M  0 loop /mnt/live/memory/images/003-xfce.xzm
loop6    7:6    0   352K  0 loop /mnt/live/memory/images/004-xfce_fixes-150124.x
loop7    7:7    0     4K  0 loop /mnt/live/memory/images/0099-settings.xzm
loop8    7:8    0  34.4M  0 loop /mnt/live/memory/images/04-firefox.xzm
loop9    7:9    0     5M  0 loop /mnt/live/memory/images/flashplayer-plugin-11.2
loop11   7:11   0  28.3M  0 loop /mnt/live/memory/images/wxPython-2.8.12.1-i486-
guest@porteus:~$ ldd /usr/bin/boinc | grep "not found"
ldd: /usr/bin/boinc: No such file or directory
guest@porteus:~$ ldd /usr/bin/boincmgr | grep "not found"
ldd: /usr/bin/boincmgr: No such file or directory
guest@porteus:~$ cd BOINC
guest@porteus:~/BOINC$ boinc --daemon
bash: boinc: command not found
guest@porteus:~/BOINC$ boincmgr
bash: boincmgr: command not found
guest@porteus:~/BOINC$ 

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#52 by Bogomips » 17 Sep 2015, 12:12

My mistake. :oops: Had flu shot couple of days ago.

Correction

Replacing Step 4. and following Steps (given in previous post)
  1. Activate Modules, after making sure both modules are in /home/guest, in following order (Order is Important):

    Code: Select all

    activate naut_121214.xzm 
    activate bcx_140915.xzm 
    lsblk | grep loop
    
    Should now see both modules on loops. The order of appearance does not count.
  2. Check for missing dependencies:

    Code: Select all

    ldd /usr/bin/boinc | grep "not found"
    ldd /usr/bin/boincmgr | grep "not found"
    
  3. If nothing was 'not found':

    Code: Select all

    cd BOINC
    boinc --daemon
    boincmgr 
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#53 by wacojohn » 17 Sep 2015, 13:56

Boinc Manager is open. I proceeded to add a project. See screen shot. There was a notice that a CHROME script was taking a long time, but I told it NOT to stop. I tried to switch to CHROME early on, but it said it would not run on my hardware. I am running Firefox. Then Manager seems to be waiting .... for something:

Image

and here is the current state of TERMINAL window:

Code: Select all

guest@porteus:~$ ls
BOINC/      Downloads/  Video/                             naut_121214.xzm
Desktop/    Music/      bcx_140915.xzm
Documents/  Pictures/   boinc_7.2.42_i686-pc-linux-gnu.sh
guest@porteus:~$ activate naut_121214.xzm
Updating shared library links:  /sbin/ldconfig
Updating MIME database:  /usr/bin/update-mime-database /usr/share/mime
Updating X font indexes:  /usr/bin/fc-cache -f
Updating glib schemas: /usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas
warning: Schema 'apps.gecko-mediaplayer.preferences' has path '/apps/gecko-mediaplayer/preferences/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'apps.gnome-mplayer.preferences' has path '/apps/gnome-mplayer/preferences/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.crypto.cache' has path '/desktop/gnome/crypto/cache/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.crypto.pgp' has path '/desktop/gnome/crypto/pgp/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.locale' has path '/system/locale/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy' has path '/system/proxy/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy.http' has path '/system/proxy/http/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy.https' has path '/system/proxy/https/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy.ftp' has path '/system/proxy/ftp/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
warning: Schema 'org.gnome.system.proxy.socks' has path '/system/proxy/socks/'.  Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
Updating XFCE menu: update-desktop-database
guest@porteus:~$ activate bcx_140915.xzm
Updating shared library links:  /sbin/ldconfig
Updating XFCE menu: update-desktop-database
guest@porteus:~$ lsblk | grep loop
loop0    7:0    0    16M  0 loop /mnt/live/memory/images/000-kernel.xzm
loop1    7:1    0    46M  0 loop /mnt/live/memory/images/001-core.xzm
loop2    7:2    0     4K  0 loop /mnt/live/memory/images/001-core_alldesktops-15
loop3    7:3    0  43.7M  0 loop /mnt/live/memory/images/002-xorg.xzm
loop4    7:4    0    12K  0 loop /mnt/live/memory/images/002-xorg_alldesktops-15
loop5    7:5    0  24.6M  0 loop /mnt/live/memory/images/003-xfce.xzm
loop6    7:6    0   352K  0 loop /mnt/live/memory/images/004-xfce_fixes-150124.x
loop7    7:7    0     4K  0 loop /mnt/live/memory/images/0099-settings.xzm
loop8    7:8    0  34.4M  0 loop /mnt/live/memory/images/04-firefox.xzm
loop9    7:9    0     5M  0 loop /mnt/live/memory/images/flashplayer-plugin-11.2
loop10   7:10   0  17.3M  1 loop /mnt/live/memory/images/naut_121214.xzm
loop11   7:11   0  28.3M  0 loop /mnt/live/memory/images/wxPython-2.8.12.1-i486-
loop12   7:12   0  11.5M  1 loop /mnt/live/memory/images/bcx_140915.xzm
guest@porteus:~$ ldd /usr/bin/boinc | grep "not found"
guest@porteus:~$ ldd /usr/bin/boincmgr | grep "not found"
guest@porteus:~$ cd BOINC
guest@porteus:~/BOINC$ boinc --daemon
guest@porteus:~/BOINC$ boincmgr
Warning: Mismatch between the program and library build versions detected.
The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1008,wx containers,compatible with 2.6),
and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,wx containers,compatible with 2.6).

(process:7137): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed

(boincmgr:7106): Gtk-CRITICAL **: IA__gtk_window_set_modal: assertion `GTK_IS_WINDOW (window)' failed

(boincmgr:7106): Gtk-CRITICAL **: IA__gtk_window_set_modal: assertion `GTK_IS_WINDOW (window)' failed

(boincmgr:7106): Gtk-CRITICAL **: IA__gtk_window_set_modal: assertion `GTK_IS_WINDOW (window)' failed

I think I MIGHT be damn near out of memory (or not). I opened one more tab in FF and disk drive went into a psychotic episode .. and I had to wait oh ...12 minutes or so before I could continue.

At the moment, Manager etc are in wait states though and drive and access have stabilized..

I am terribly sorry you are bearing my weight when you do not feel well. I hope you are much better today.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#54 by Bogomips » 17 Sep 2015, 14:36

@wacojohn

It says click Finish to close. :)

Did you try clicking Cancel on top window, and then Finish to close?
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#55 by wacojohn » 17 Sep 2015, 20:59

The small window that says 'communicating with BOINC MANAGER' is seemingly in a wait state ... and I did not want to force close until I notified you. I went ahead and cancelled .. and everything seems to be working fine. I even added one more project.

I don't know if we are finished. Is makemenu involved at any point? I plan to run this BOINC 24/7 .. but the day will come (power outage etc) that I will need to start it.

You are amazing. I don't know what all we did, ... but if this is what it takes to install an app/pkg/sw product ... this will be it. I think childbirth must be simpler.

Thank you immensely. This old machine had NO purpose until now. Cannot thank you enough. As for a tutorial ... WAY too much lack of knowledge on what was done.

Thank you and the others ... you are either all geniuses or sorcerers ... either way (so patient and friendly) ....thank you.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#56 by Bogomips » 18 Sep 2015, 23:46

While everything is fresh in mind, as a memo to self, and for you to tackle when you feel up to it, jotting down the steps which have to come next, as it's all makeshift at the moment and not the way you wanted it yet. Over the next period of time I shall be appending to this post as and when a thought comes to me. :)

Checklist & Memo
  • boincmgr
    View > Advanced View; File > Exit BOINC Manager; OK (without checking any boxes)
    At next boot up, after starting boinc client, projects seem to resume where they left off. At least this is what the manager will show.
  • Changes=exit or just =ro?
  • /proc/cmdline
  • ls -1 /mnt/live/memory/images
  • cliexec
  • menu item amendment
Agenda
  1. As Superuser:
    1. Code: Select all

      mkdir /mnt/sda1/porteus/optional/boinc
      mv /mnt/sda1/porteus/modules/wxPython-2.8.12.1-i486-bundle.xzm   /mnt/sda1/porteus/optional/boinc
      cp  naut_121214.xzm    /mnt/sda1/porteus/modules
      cp  bcx_140915.xzm   /mnt/sda1/porteus/optional/boinc
      
      • Used 'disk' as directory name here, but use whatever you prefer.

        Code: Select all

        mkdir /mnt/sda1/disk
        chmod a+rw /mnt/sda1/disk
      • Need to suspend processing first. Maybe:
        View > Advanced View; File > Exit BOINC Manager; OK (after checking box Stop running tasks ...), then

        Code: Select all

        cp -a BOINC /mnt/sda1/disk
        This transfers the BOINC directory from a 'live' filesystem to a 'real' filesystem, thereby allowing boinc to utilise the remainder of the hard disk.
  2. Reboot using Kernel Parameter (cheatcode) load=1409
    Continuing on as guest
    1. Verify parameters:

      Code: Select all

      cat /proc/cmdline
    2. Both modules naut_121214.xzm and bcx_140915.xzm should have been activated and appear in output of following:

      Code: Select all

      ls -1 /mnt/live/memory/images
    3. If both modules activated, check for missing dependencies:

      Code: Select all

          ldd /usr/bin/boinc | grep "not found"
          ldd /usr/bin/boincmgr | grep "not found"
      
    4. Boinc on:

      Code: Select all

      boinc --dir /mnt/sda1/disk/BOINC --daemon
      cd /mnt/sda1/disk/BOINC; boincmgr
  3. Module for general release, cliexec, guiexec, boinc_mgr, changes on exit
    libgnome-desktop-3-2-3.4.2-i386 needed for this module
  4. menu amendment (to be done), installpkg (for consideration)
  5. To be continued
Heat and energy considerations

When BOINC applications are running on a computer, its CPU chip produces more heat than when it is idle. The computer's heat sinks and fans are normally able to dissipate this heat sufficiently. However, if the fans become clogged with dust, they may not be able to cool the CPU adequately, and this can lead to premature failure of the CPU or motherboard.

To deal with this problem, we recommend that you:

Clean your computer's fans and heat sinks periodically.
Install a utility that monitors CPU temperature, such as Motherboard Monitor or i8kfan (for Dell laptops).
If needed, set your preferences to throttle CPU usage.
Last edited by Bogomips on 27 Sep 2015, 20:00, edited 1 time in total.
Reason: Update
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: boinc???

Post#57 by francois » 19 Sep 2015, 00:03

@wacojohn:
but if this is what it takes to install an app/pkg/sw product ... this will be it. I think childbirth must be simpler.

No it is not usually this complicated. It depends on the package. :twisted:

You will see at your next demand. Unless you always ask for things more complicated than simple package installation. Do you need gimp, abiword, photoprint, fotoxx?

Please appreciate bogomips special care. He used to write that I was taking great care of newcomers, but this thread is making him champion of caretakers. :oops:
Voltaire: Le mieux est l'ennemi du bien.

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#58 by wacojohn » 19 Sep 2015, 03:06

francois wrote:@wacojohn:
but if this is what it takes to install an app/pkg/sw product ... this will be it. I think childbirth must be simpler.

No it is not usually this complicated. It depends on the package. :twisted:

You will see at your next demand. Unless you always ask for things more complicated than simple package installation. Do you need gimp, abiword, photoprint, fotoxx?
I see. This machine is so minimal, I don't think I will be running anything else on it. With all the help I received, I have achieved my goal.
Please appreciate bogomips special care. He used to write that I was taking great care of newcomers, but this thread is making him champion of caretakers. :oops:
I cannot thank him enough. He is phenomenal ... as I mentioned, patient and friendly ... and most of all talented.

Thank you also, ... and the others who have stepped in. Fantastic team.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc??? SOLVED

Post#59 by Bogomips » 19 Sep 2015, 12:42

^ Accolades :beer:
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#60 by wacojohn » 13 Oct 2015, 20:01

Bogomips wrote:While everything is fresh in mind, as a memo to self, and for you to tackle when you feel up to it, jotting down the steps which have to come next, as it's all makeshift at the moment and not the way you wanted it yet. Over the next period of time I shall be appending to this post as and when a thought comes to me. :)

Checklist & Memo
  • boincmgr
    View > Advanced View; File > Exit BOINC Manager; OK (without checking any boxes)
    At next boot up, after starting boinc client, projects seem to resume where they left off. At least this is what the manager will show.
  • Changes=exit or just =ro?
  • /proc/cmdline
  • ls -1 /mnt/live/memory/images
  • cliexec
  • menu item amendment
Agenda
  1. As Superuser:
    1. Code: Select all

      mkdir /mnt/sda1/porteus/optional/boinc
      mv /mnt/sda1/porteus/modules/wxPython-2.8.12.1-i486-bundle.xzm   /mnt/sda1/porteus/optional/boinc
      cp  naut_121214.xzm    /mnt/sda1/porteus/modules
      cp  bcx_140915.xzm   /mnt/sda1/porteus/optional/boinc
      
      • Used 'disk' as directory name here, but use whatever you prefer.

        Code: Select all

        mkdir /mnt/sda1/disk
        chmod a+rw /mnt/sda1/disk
      • Need to suspend processing first. Maybe:
        View > Advanced View; File > Exit BOINC Manager; OK (after checking box Stop running tasks ...), then

        Code: Select all

        cp -a BOINC /mnt/sda1/disk
        This transfers the BOINC directory from a 'live' filesystem to a 'real' filesystem, thereby allowing boinc to utilise the remainder of the hard disk.
  2. Reboot using Kernel Parameter (cheatcode) load=1409
    Continuing on as guest
    1. Verify parameters:

      Code: Select all

      cat /proc/cmdline
    2. Both modules naut_121214.xzm and bcx_140915.xzm should have been activated and appear in output of following:

      Code: Select all

      ls -1 /mnt/live/memory/images
    3. If both modules activated, check for missing dependencies:

      Code: Select all

          ldd /usr/bin/boinc | grep "not found"
          ldd /usr/bin/boincmgr | grep "not found"
      
    4. Boinc on:

      Code: Select all

      boinc --dir /mnt/sda1/disk/BOINC --daemon
      cd /mnt/sda1/disk/BOINC; boincmgr
  3. Module for general release, cliexec, guiexec, boinc_mgr, changes on exit
    libgnome-desktop-3-2-3.4.2-i386 needed for this module
  4. menu amendment (to be done), installpkg (for consideration)
  5. To be continued
Heat and energy considerations

When BOINC applications are running on a computer, its CPU chip produces more heat than when it is idle. The computer's heat sinks and fans are normally able to dissipate this heat sufficiently. However, if the fans become clogged with dust, they may not be able to cool the CPU adequately, and this can lead to premature failure of the CPU or motherboard.

To deal with this problem, we recommend that you:

Clean your computer's fans and heat sinks periodically.
Install a utility that monitors CPU temperature, such as Motherboard Monitor or i8kfan (for Dell laptops).
If needed, set your preferences to throttle CPU usage.
I have foolishly not paid attention to the above. Somehow, I assumed we were done. I don't know how I missed the point of 'above', but I did. As is the case, I am having a number of problems. I am assuming that when you (Bogomips) 'finish this up', I COULD install Porteus anew ... because I am not convinced I did it right in the first place, ... THEN, install a BOINC 'module' good and proper. If that is the case, I would be so grateful to your helping me do that.

I am terribly confused with installing Porteus from a CD. Copy to RAM? ... I don't think so ... only 512MB of RAM. Boot from CD? I don't think so ... but maybe. Boot from HD? Why not? ... every computer I ever used that HAD a HD booted from it. Live system ..? I guess ... whatever. FRUGAL install?? Installation page says:
Porteus can be installed to hard drives, but it should be left in its compressed state (otherwise known as a 'Frugal' installation). Installing extracted files to a hard drive is not supported; it is suggested that you install Slackware Linux instead if you wish to have an Operating System installed to your system natively.

Creating a 'Frugal' installation is very similar to installing on a USB drive. Porteus can be installed on it's own partition, or it can be installed side by side with Windows or another Linux OS on the same partition.

If Porteus is the only Operating System that you are installing to a device (internal or external), follow the instructions given above for burning the ISO to a CD and booting from it, and then run the 'Porteus Installer' program, which can be found in the KDE, LXDE, Razor or Xfce menu under the 'System' heading.
I THINK this is how I did it last time ... but if we follow my request, would prefer to start from a newly partitioned HD. Just need to know how to partition the drive ... ext ??? It's an 8GB Drive .. dedicated to PORTEUS.

The point is, I would like to boot up this computer and run BOINC. I would like to be able to update the OS ... I would think. To reach these goals, I think I need you to resume your support and development of the 'module', then instruct on Porteus installation and BOINC execution.

I would not blame you if you said 'Get out of my life' .... and I feel terrible that I missed the point ... that we are not 'finished' ....but I can't run this the way it is at this point

I hope you will be willing to finish this up. Thank you in advance.

Locked