SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
probably doesn't have permission to get input
my bad
bdw you can use "sleep 100d" to sleep for a 100 days, if you don't want to load ruby
100 days not my target. i want to insert that x server up and down in rc.boinc script:
#!/bin/sh
# rc.boinc - BOINC startup/control script for Slackware Linux
#
# Licence:
# Copyright (c) 2005, 2008, Mark Hill <http://markhill.me.uk/>
#
# Permission to use, copy, modify, and/or distribute this software for any
# purpose with or without fee is hereby granted, provided that the above
# copyright notice and this permission notice appear in all copies.
#
# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
#
#######################################################################
# Program: /etc/rc.d/rc.boinc
# Purpose: A startup and control script for Slackware Linux.
# Installation:
# 1. Rename this file to rc.boinc and remove any possible DOS line endings. I.E:
# $ tr -d '\r' <thisfile >rc.boinc
# 2. Edit the variables below to suit your BOINC setup.
# 3. Place this file in /etc/rc.d/ and make the file executable.
# 4. Change ownerships of the file as appropriate
# 5. Add the following code to /etc/rc.d/rc.local:
#
# if [ -x /etc/rc.d/rc.boinc ]; then
# /etc/rc.d/rc.boinc start
# fi
#
# 6. Test the script - Run the script as root using 'sh /etc/rc.d/rc.boinc' or
# similar. You should see a list of options.
# 7. Check for any current running boinc process be running the script like
# so as root: 'sh /etc/rc.d/rc.boinc status'
# 8. If no boinc process running, run as root: 'sh /etc/rc.d/rc.boinc start'
# 9. Installation complete! - rc.boinc should start boinc on each boot. You may
# want to use an 'rc.boinc stop' command to a shutdown script, although this
# isn't strictly necessary.
#######################################################################
# Author: Mark Hill <http://markhill.me.uk/contact/>
# URL: <http://markhill.me.uk/articles/boinc_slackware/>
# Version: 2008-09-22 - Removed previous change to boinc_status. Rewrote
# function as grep would sometimes find itself from the ps output
#######################################################################
# Usage: rc.boinc start|stop|restart|reload|force-reload|status
#######################################################################
# Begin user configuration
BOINC_DIR=/home/mark/BOINC/ # directory of boinc files - MUST have trailing /
BOINC_BIN=boinc # name of the boinc binary
BOINC_USER=root # user that will run boinc process
BOINC_OPTIONS= # E.G "-return_results_immediately"
BOINC_LOGFILE=/home/mark/boinc-log # will be created if it does not exist
BOINC_ERRORFILE=/home/mark/boinc-errors # as above
# End of user configuration
#######################################################################
boinc_status() {
if ( ps -ef | grep "$BOINC_DIR$BOINC_BIN$" > /dev/null 2>&1 ); then
return 0
else
return 3
fi
}
boinc_start() {
boinc_status;
if [ $? = 0 ]; then
echo "BOINC is already running"
exit 1;
fi
if [ ! -d $BOINC_DIR ]; then
echo "ERROR: $BOINC_DIR does not exist"
exit 1;
elif [ ! -x $BOINC_DIR$BOINC_BIN ]; then
echo "ERROR: $BOINC_DIR$BOINC_BIN does not exist or not executable"
exit 1;
fi
echo "Starting BOINC client"
su - $BOINC_USER -c "
cd $BOINC_DIR;
exec $BOINC_DIR$BOINC_BIN \
$BOINC_OPTIONS \
>$BOINC_LOGFILE 2>$BOINC_ERRORFILE" &
ok, x startt with ruby sleep script works, but in window from where i do it, last message is
fglrx: no instance found
and boinc anyway not found GPU. when i do startx and start kde, and then run boinc, it found GPU.
strange, theoretically all drivers is loaded by X server, and window manager in that aspect do not change anything, no?
Have you considered using a really small window manager, like http://incise.org/tinywm.html? I've messed about with it in the past and found it to work in a very minimal manner. It is just functional enough, while remaining super small, to be of help to you.
Have you considered using a really small window manager, like http://incise.org/tinywm.html? I've messed about with it in the past and found it to work in a very minimal manner. It is just functional enough, while remaining super small, to be of help to you.
yes, i start to consider it, but i found, a tinywm not in slackware 14.0, and also cannot find an slackware package for tinywm.
it is possible, sure, to compile it myself, but i plan to put it on the server, and want to minimalize possibility of break down it.\i see slackware offers blackbox, fluxbox, fvwm2, twm, wmaker, and xfce in default. which of that is smallest and minimal resources eating?
a new input!
things got more and more strange!
that message from i found on the console screen, whom i run dummy x server is be a
(WW) fglrx: no matching Device section for instance (BusID PCI:0@1:0:1) found.
when i run ./boinc from next console (tty) (alt+ctrl+f2) from the same user, wrom who i run x server - boinc started and got until that place, where it can give "GPU found" lines on console, and stuck, as earlier. when i do ctrl+c it do "receiving signal 2, exiting, and "GPU not found" - exactly as earlier.
then i do ctrl+c from first console to stop my dummy X server, and it stopped. then i do "startx" and run my KDE.
after that i try again in console 2 ( ctrl+alt+f2) run ./boinc and get exactly the same result as previous - stuck, and "no GPU"!i try to log off from console 2, and log in again, and again ./boinc - the same!
then i go on kde ( ctrl+alt+f7), and as earlier, open there new terminal session, and run ./boinc from there, and all works!
strange.
i be reading there may be a problem, who need to be enter "xhost local:boinc" in console before run boinc client, for that client see a GPU - got to alt+ctrl+f2, enter "xhost local:boinc", but got only
xhost: unable to open display ""
very stucked here. seems there is some difference in environment of terminal, but what, and why i can do?
user, from who i run startx and ./boinc in console 2 is the same...
Losing track here. have tried using boinc as your dummy WM? You might even be able to script it so thar if you ran this command
startx /somewhere/boinc
in ~xinitrc, $1 would be boinc, and you would have something looking for the GPU at the time it became available.
But you shouldn't have to figure this out. Doesn't boinc have any instructions on how to run it?
no-no-no.
i start run dummy wm on script provided in first page of this epopey: a ruby script.
then i figured out, there are another problem: ,y ./boinc programm, if runned from "physical tty" ( ctrl+alt+Fx) in any way do not seem GPU. when the same ./boinc programm is runned from terminal session inside of window manager (KDE in my case) - it detects GPU good.
i try to make "xhost local:boinc" where boinc is user from what i run x server, and also a ./boinc programm, but when i run it from "physical tty", i get that error message ( xhost: unable to open display "" ).
there i stucked. i need to grant access programm running from "physical tty" from the same user, to videodriver in X ?
update: i do that:
user login in "physical tty" ( ctrl+alt+Fx)
DISPLAY=:0
export DISPLAY
xhost local:boinc
non-network local connections being added to access control lists
./boinc -> stuck before "GPU found / not found".
can not imagine, where else is problem.
if i run ./boinc from terminal programm open on KDE all was fine - ./boinc see ATI GPU:
bash-4.2$ ./boinc
./boinc: /lib64/libssl.so.1.0.0: no version information available (required by ./boinc)
./boinc: /usr/lib64/libcurl.so.4: no version information available (required by ./boinc)
./boinc: /lib64/libcrypto.so.1.0.0: no version information available (required by ./boinc)
03-Feb-2014 17:31:22 [---] cc_config.xml not found - using defaults
03-Feb-2014 17:31:22 [---] Starting BOINC client version 7.2.33 for x86_64-pc-linux-gnu
03-Feb-2014 17:31:22 [---] log flags: file_xfer, sched_ops, task
03-Feb-2014 17:31:22 [---] Libraries: libcurl/7.27.0 OpenSSL/1.0.1c zlib/1.2.6 libidn/1.25
03-Feb-2014 17:31:22 [---] Data directory: /home/boinc/BOINC
boinc: /lib64/libssl.so.1.0.0: no version information available (required by boinc)
boinc: /usr/lib64/libcurl.so.4: no version information available (required by boinc)
boinc: /lib64/libcrypto.so.1.0.0: no version information available (required by boinc)
03-Feb-2014 17:31:22 [---] CAL: ATI GPU 0: ATI Radeon HD 4350/4550 (R710) (CAL version 1.4.1734, 512MB, 394MB available, 192 GFLOPS peak)
03-Feb-2014 17:31:22 [---] OpenCL: AMD/ATI GPU 0: ATI Radeon HD 4350/4550 (R710) (driver version CAL 1.4.1734, device version OpenCL 1.0 AMD-APP (937.2), 512MB, 394MB available, 192 GFLOPS peak)
03-Feb-2014 17:31:22 [---] OpenCL CPU: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 2.0 (sse2), device version OpenCL 1.2 AMD-APP (937.2))
03-Feb-2014 17:31:22 [SETI@home] Found app_info.xml; using anonymous platform
03-Feb-2014 17:31:22 [---] Host name: TESTslk64_14
03-Feb-2014 17:31:22 [---] Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz [Family 6 Model 15 Stepping 13]
03-Feb-2014 17:31:22 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm
03-Feb-2014 17:31:22 [---] OS: Linux: 3.2.29
03-Feb-2014 17:31:22 [---] Memory: 3.79 GB physical, 1.91 GB virtual
03-Feb-2014 17:31:22 [---] Disk: 36.67 GB total, 16.73 GB free
03-Feb-2014 17:31:22 [---] Local time is UTC +2 hours
03-Feb-2014 17:31:22 [rosetta@home] URL http://boinc.bakerlab.org/rosetta/; Computer ID 1716837; resource share 100
03-Feb-2014 17:31:22 [Milkyway@Home] URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 559365; resource share 100
03-Feb-2014 17:31:22 [Einstein@Home] URL http://einstein.phys.uwm.edu/; Computer ID 10283457; resource share 100
03-Feb-2014 17:31:22 [Poem@Home] URL http://boinc.fzk.de/poem/; Computer ID 195468; resource share 100
03-Feb-2014 17:31:22 [SETI@home] URL http://setiathome.berkeley.edu/; Computer ID 7203016; resource share 100
03-Feb-2014 17:31:22 [---] General prefs: from http://www.worldcommunitygrid.org/ (last modified 01-Jan-1970 03:00:01)
03-Feb-2014 17:31:22 [---] Host location: none
03-Feb-2014 17:31:22 [---] General prefs: using your defaults
03-Feb-2014 17:31:22 [---] Reading preferences override file
03-Feb-2014 17:31:22 [---] Preferences:
03-Feb-2014 17:31:22 [---] max memory usage when active: 1163.31MB
03-Feb-2014 17:31:22 [---] max memory usage when idle: 1744.96MB
03-Feb-2014 17:31:22 [---] max disk usage: 2.00GB
03-Feb-2014 17:31:22 [---] max CPUs used: 1
03-Feb-2014 17:31:22 [---] suspend work if non-BOINC CPU load exceeds 50%
03-Feb-2014 17:31:22 [---] (to change preferences, visit a project web site or select Preferences in the Manager)
03-Feb-2014 17:31:22 [---] Not using a proxy
03-Feb-2014 17:31:22 Initialization completed
03-Feb-2014 17:31:22 [SETI@home] Restarting task ap_29oc13aa_B4_P0_00223_20140108_17005.wu_3 using astropulse_v6 version 607 (ati_opencl_100) in slot 1
03-Feb-2014 17:31:22 [Poem@Home] Restarting task poempp_fastfoldinga3d_1391081589_567503941_0 using poempp version 106 in slot 3
Logs from "dummy script" and from kde staret also is attached - cannot put it there, because any of it is larger than 30 000 lines....
That is from "dummy wm script" logs. but i cannot understand, why it is relevant, because as i say,
i found ./boinc not see GPU if started from "physical" console - no matter there is running "dummy wm"
or fully KDE at that time. there is some strange differencies between user login in physical console,
and open a console from KDE - when i start boinc in console from KDE all works, when i do the same from physical console - programm ( boinc) cannot see GPU...
yes, i start to consider it, but i found, a tinywm not in slackware 14.0, and also cannot find an slackware package for tinywm.
it is possible, sure, to compile it myself, but i plan to put it on the server, and want to minimalize possibility of break down it.\i see slackware offers blackbox, fluxbox, fvwm2, twm, wmaker, and xfce in default. which of that is smallest and minimal resources eating?
I understand about tinywm perhaps unstable for server, was just idea. For memory footprint, the smallest and, I think most stable, is twm, though blackbox is close after twm for memory usage.
Is there an ~/.xsession-errors file that might contain the errors from boinc?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.