LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-03-2014, 03:49 PM   #31
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, exMandriva
Posts: 377

Original Poster
Rep: Reputation: 30

Quote:
Originally Posted by j_v View Post
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?
ok, thank you.
not, there no .xsession* files in home directory. i also see at /var/adm in logfiles for something interesent in that regard, and not found.
looks like any communication with xorg loaded driver problem, if boinc not run from session opened by kde ( window manager)?
try also do xhost +local:
also from root account in physical console. also try to run ./boinc in physical console from root account - always the same result - boinc stuck at gpu detection and not see gpu. when i run boinc from terminal session from kde - all be beautiful - detection is fast, and all found.
boinc is programm, who compute tasks on computer, also using for that a videocard ( GPU), if found any. looks like, ati videocards require x org running and x org videodriver loaded, then boinc can communicate with that driver and use it. Nvidia videocards \ drivers looks like better in that way - there is requiring to install kernel drivers, then you can log in in console (CLI) and boinc can use and detect Nvidia card without any X-es and another struggles...
sadly, but i need to get work ati videocard ( radeon 4350, catalyst 13.1 driver, amd SDK 2.9 for OpenCL, slackware64 14.0 )...and to work from console, not from terminal on WindowManager ( where it works ok)...
 
Old 02-03-2014, 04:03 PM   #32
j_v
Member
 
Registered: Oct 2011
Distribution: Slackware64, LFS, Crux
Posts: 194

Rep: Reputation: 25
Others probably have more useful help, but I wonder if when starting boinc (after starting the dummy-wm), maybe use 'xterm -e sh /path/to/rc.boinc'?
 
Old 02-03-2014, 04:21 PM   #33
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,469

Rep: Reputation: 411Reputation: 411Reputation: 411Reputation: 411Reputation: 411
Your kde log has
Code:
[   378.287] (II) fglrx(0): EDID vendor "ACI", prod id 8871
[   378.288] (II) fglrx(0): Using EDID range info for horizontal sync
[   378.288] (II) fglrx(0): Using EDID range info for vertical refresh
[   378.288] (II) fglrx(0): Printing DDC gathered Modelines:
[   378.288] (II) fglrx(0): Modeline "1680x1050"x0.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz eP)
[   378.288] (II) fglrx(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   378.288] (II) fglrx(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[   378.288] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[   378.288] (II) fglrx(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[   378.288] (II) fglrx(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[   378.288] (II) fglrx(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   378.288] (II) fglrx(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   378.288] (II) fglrx(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[   378.288] (II) fglrx(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[   378.288] (II) fglrx(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[   378.288] (II) fglrx(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   378.288] (II) fglrx(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[   378.288] (II) fglrx(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[   378.288] (II) fglrx(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[   378.288] (II) fglrx(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   378.288] (II) fglrx(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[   378.288] (II) fglrx(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   378.288] (II) fglrx(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[   378.288] (II) fglrx(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[   379.987] (II) AIGLX: Suspending AIGLX clients for VT switch
[   379.987] (II) fglrx(0): Backup framebuffer data.
[   380.020] (II) fglrx(0): Backup complete.
[   490.973] (II) AIGLX: Resuming AIGLX clients after VT switch
[   516.727] (II) AIGLX: Suspending AIGLX clients for VT switch
[   516.728] (II) fglrx(0): Backup framebuffer data.
[   516.770] (II) fglrx(0): Backup complete.
[   538.829] (II) AIGLX: Resuming AIGLX clients after VT switch
[  1208.395] (II) AIGLX: Suspending AIGLX clients for VT switch
[  1208.397] (II) fglrx(0): Backup framebuffer data.
[  1208.518] (II) fglrx(0): Backup complete.
[  1226.757] (II) AIGLX: Resuming AIGLX clients after VT switch
[  1873.860] (II) AIGLX: Suspending AIGLX clients for VT switch
[  1873.862] (II) fglrx(0): Backup framebuffer data.
[  1873.996] (II) fglrx(0): Backup complete.
[  2019.462] (II) AIGLX: Resuming AIGLX clients after VT switch
[  3138.220] (II) AIGLX: Suspending AIGLX clients for VT switch
[  3138.222] (II) fglrx(0): Backup framebuffer data.
[  3138.292] (II) fglrx(0): Backup complete.
[  3213.398] (II) AIGLX: Resuming AIGLX clients after VT switch
[  3307.350] (II) AIGLX: Suspending AIGLX clients for VT switch
[  3307.352] (II) fglrx(0): Backup framebuffer data.
[  3307.497] (II) fglrx(0): Backup complete.
[  3404.382] (II) AIGLX: Resuming AIGLX clients after VT switch
[  4092.366] (II) AIGLX: Suspending AIGLX clients for VT switch
[  4092.368] (II) fglrx(0): Backup framebuffer data.
[  4092.491] (II) fglrx(0): Backup complete.
[  4097.766] (II) AIGLX: Resuming AIGLX clients after VT switch
[  5148.478] (II) AIGLX: Suspending AIGLX clients for VT switch
[  5148.482] (II) fglrx(0): Backup framebuffer data.
[  5148.643] (II) fglrx(0): Backup complete.
[  5190.838] (II) AIGLX: Resuming AIGLX clients after VT switch
[  5221.544] (II) AIGLX: Suspending AIGLX clients for VT switch
[  5221.547] (II) fglrx(0): Backup framebuffer data.
[  5221.711] (II) fglrx(0): Backup complete.
[  5292.622] (II) AIGLX: Resuming AIGLX clients after VT switch
[  5315.728] (II) AIGLX: Suspending AIGLX clients for VT switch
[  5315.730] (II) fglrx(0): Backup framebuffer data.
[  5315.855] (II) fglrx(0): Backup complete.
[  5359.766] (II) AIGLX: Resuming AIGLX clients after VT switch
[  5407.364] (II) AIGLX: Suspending AIGLX clients for VT switch
[  5407.366] (II) fglrx(0): Backup framebuffer data.
[  5407.484] (II) fglrx(0): Backup complete.
[  5463.711] (II) AIGLX: Resuming AIGLX clients after VT switch
[  5508.193] (II) AIGLX: Suspending AIGLX clients for VT switch
[  5508.195] (II) fglrx(0): Backup framebuffer data.
[  5508.365] (II) fglrx(0): Backup complete.
[  5683.527] (II) AIGLX: Resuming AIGLX clients after VT switch
[  5729.111] (II) AIGLX: Suspending AIGLX clients for VT switch
[  5729.113] (II) fglrx(0): Backup framebuffer data.
[  5729.172] (II) fglrx(0): Backup complete.
[  5848.151] (II) AIGLX: Resuming AIGLX clients after VT switch
[  6603.310] (II) AIGLX: Suspending AIGLX clients for VT switch
[  6603.312] (II) fglrx(0): Backup framebuffer data.
[  6603.584] (II) fglrx(0): Backup complete.
[  6620.415] (II) AIGLX: Resuming AIGLX clients after VT switch
[  7058.014] (II) AIGLX: Suspending AIGLX clients for VT switch
[  7058.016] (II) fglrx(0): Backup framebuffer data.
[  7058.390] (II) fglrx(0): Backup complete.
[  7071.983] (II) AIGLX: Resuming AIGLX clients after VT switch
...which the other log file doesn't.

I don't know if that's relevant or not. I'm afraid that I won't be of much help. Sorry.
 
Old 02-03-2014, 04:42 PM   #34
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,504
Blog Entries: 2

Rep: Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018
Quote:
Originally Posted by j_v View Post
Others probably have more useful help, but I wonder if when starting boinc (after starting the dummy-wm), maybe use 'xterm -e sh /path/to/rc.boinc'?
If you start xterm anyways to start boinc, you don't need the dummy WM, just use xterm as WM. In fact, any program can act as a WM in this way, possibly just starting BOINC instead of the dummy WM will work (as suggested already by business_kid).
 
Old 02-04-2014, 02:14 AM   #35
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, exMandriva
Posts: 377

Original Poster
Rep: Reputation: 30
Quote:
Originally Posted by TobiSGD View Post
If you start xterm anyways to start boinc, you don't need the dummy WM, just use xterm as WM. In fact, any program can act as a WM in this way, possibly just starting BOINC instead of the dummy WM will work (as suggested already by business_kid).

xm, today at morning before get to job i try that ->

#!/bin/sh
xterm -e sh /Install/BOINC/boinc


into file dummy_wm_boinc
make it executable and do
xinit /Install/BOINC/dummy_wm_boinc

looks like X start, and then quit.
in logfile is a strange for me lines like "ctrl-alt-del pressed" or so on. put that log in evening, when got to home....
i be more and more not like ATI.
Nvidia looks like far better in driver quality and linux support than ati.
i have nvidia 210 videocard at work, and boinc work with it very fine - even without any Xes - computer started at runlevel 3, i log in as user, run ./boinc - and all detected, and running. with that ati i struggling more than week for now, and do not see a light at the end of the tunnel....
 
Old 02-04-2014, 09:46 AM   #36
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, exMandriva
Posts: 377

Original Poster
Rep: Reputation: 30
log file for try running


#!/bin/sh
xterm -e sh /Install/BOINC/boinc


into file dummy_wm_boinc
make it executable and do
xinit /Install/BOINC/dummy_wm_boinc
in attach:
Attached Files
File Type: txt xorg_dummy_boinc.txt (35.6 KB, 3 views)
 
Old 02-04-2014, 12:00 PM   #37
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,504
Blog Entries: 2

Rep: Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018Reputation: 4018
There is no indication for an error in that log. It may be possible that BOINC has detached itself from the terminal, which would have closed the terminal automatically and therefore shutdown the X server. What happens when you start BOINC directly as WM, without using Xterm?
 
Old 02-04-2014, 12:43 PM   #38
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, exMandriva
Posts: 377

Original Poster
Rep: Reputation: 30
Quote:
Originally Posted by TobiSGD View Post
There is no indication for an error in that log. It may be possible that BOINC has detached itself from the terminal, which would have closed the terminal automatically and therefore shutdown the X server. What happens when you start BOINC directly as WM, without using Xterm?
Woow!
i change dummy wm script to:
dummy_wm_boinc file, file perm 100755:

#!/bin/sh
##xterm -e sh /Install/BOINC/boinc --dir /Install/BOINC/
## > dumlog.txt
/Install/BOINC/boinc --dir /Install/BOINC >boinc.log 2>berror.log

then
xinit /Install/BOINC/dummy_wm_boinc

and there is boinc.log:

04-Feb-2014 18:35:24 [---] cc_config.xml not found - using defaults
04-Feb-2014 18:35:24 [---] Starting BOINC client version 7.2.33 for x86_64-pc-linux-gnu
04-Feb-2014 18:35:24 [---] log flags: file_xfer, sched_ops, task
04-Feb-2014 18:35:24 [---] Libraries: libcurl/7.27.0 OpenSSL/1.0.1c zlib/1.2.6 libidn/1.25
04-Feb-2014 18:35:24 [---] Data directory: /Install/BOINC
04-Feb-2014 18:35:24 [---] CAL: ATI GPU 0: ATI Radeon HD 4350/4550 (R710) (CAL version 1.4.1734, 512MB, 384MB available, 192 GFLOPS peak)
04-Feb-2014 18:35:24 [---] 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, 384MB available, 192 GFLOPS peak)
04-Feb-2014 18:35:24 [---] 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))
04-Feb-2014 18:35:24 [---] Host name: TESTslk64_14
04-Feb-2014 18:35:24 [---] Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz [Family 6 Model 15 Stepping 13]
04-Feb-2014 18:35:24 [---] 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
04-Feb-2014 18:35:24 [---] OS: Linux: 3.2.29
04-Feb-2014 18:35:24 [---] Memory: 3.79 GB physical, 1.91 GB virtual
04-Feb-2014 18:35:24 [---] Disk: 36.67 GB total, 16.75 GB free
04-Feb-2014 18:35:24 [---] Local time is UTC +2 hours
04-Feb-2014 18:35:24 [---] No general preferences found - using defaults
04-Feb-2014 18:35:24 [---] Preferences:
04-Feb-2014 18:35:24 [---] max memory usage when active: 1938.85MB
04-Feb-2014 18:35:24 [---] max memory usage when idle: 3489.92MB
04-Feb-2014 18:35:24 [---] max disk usage: 16.66GB
04-Feb-2014 18:35:24 [---] don't use GPU while active
04-Feb-2014 18:35:24 [---] suspend work if non-BOINC CPU load exceeds 25%
04-Feb-2014 18:35:24 [---] (to change preferences, visit a project web site or select Preferences in the Manager)
04-Feb-2014 18:35:24 [---] GUI RPC bind to port 31416 failed: 98

i e at least, looks boinc be started, and see a GPU. it is very great result. ill be try to test all this in this week.
also think about make a startup script for this, for can be start it from console, and that task remain running after console was closed...

thank you very much, and all another folks, who post there and help me.
 
  


Reply

Tags
ati, boinc, x server


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] how to start window-manager with beryl lord_didger Linux - Desktop 3 01-26-2008 11:01 PM
PROBLEM: window manager won't start linux4real Linux - Newbie 4 05-03-2006 01:17 AM
Window manager doesn't start ka7znm Fedora 1 10-03-2004 08:54 AM
How do I get the window manager to start straight away? neocookie Slackware - Installation 4 04-27-2004 02:48 AM
start X without a window manager BTseapig Programming 1 03-14-2002 04:58 AM


All times are GMT -5. The time now is 11:35 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration