log in |
Message boards : Number crunching : Linux TF WUs on ATI 6800 cards
1 · 2 · 3 · 4 · Next
Author | Message |
---|---|
Anybody running TF tasks on a RX6800/xt under Linux? | |
ID: 9785 · Rating: 0 · rate: / Reply Quote | |
The same for me on a VII. | |
ID: 9789 · Rating: 0 · rate: / Reply Quote | |
The same for me on a VII. ok, we need to investigate. | |
ID: 9790 · Rating: 0 · rate: / Reply Quote | |
more recent result that's (as of this minute) still visible: | |
ID: 9791 · Rating: 0 · rate: / Reply Quote | |
more recent result that's (as of this minute) still visible: can you try a selftest ./mfakto -st outside boinc? | |
ID: 9792 · Rating: 0 · rate: / Reply Quote | |
The same for me on a VII. Can you also be running a selftest, unfortunately most of the issues coming from linux where windows has no problems. ./mfakto -st We need to collect some datas and track down the issue. | |
ID: 9794 · Rating: 0 · rate: / Reply Quote | |
The same for me on a VII. Sure, but I need more instruction where or how to do this selftest. In the terminal the command is unknown. In the project folder there is also no mfakto file. I can offer this: <core_client_version>7.16.6</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61)</message> <stderr_txt> 2024-03-21 14:29:27 (291202): wrapper (7.24.26018): starting 2024-03-21 14:29:27 (291202): wrapper (7.24.26018): starting 2024-03-21 14:29:27 (291202): wrapper: running ./mfakto-x64 (-d 0) 2024-03-21 14:29:27 (291202): wrapper: created child process 291204 2024-03-21 14:29:28 (291202): ./mfakto-x64 exited; CPU time 0.002019 2024-03-21 14:29:28 (291202): app exit status: 0x1 2024-03-21 14:29:28 (291202): called boinc_finish(195) </stderr_txt> ]]> ./mfakto-x64 -st is also not working. Maybe the needed app was not downloaded in the project folder? There is only a mfakto-linux64-v10.zip file. Shall I upzip this? Edit: unpacked and startet. Something is running... | |
ID: 9795 · Rating: 0 · rate: / Reply Quote | |
The same for me on a VII. You only need to extract the zipfile in another folder and run the command, thats all | |
ID: 9796 · Rating: 0 · rate: / Reply Quote | |
done. failed. | |
ID: 9797 · Rating: 0 · rate: / Reply Quote | |
done. failed. thx, could be the kernel file of mfakto, vega7 and 6000er had no pretests under linux. | |
ID: 9798 · Rating: 0 · rate: / Reply Quote | |
In my case it is a vega20 (radeon VII) | |
ID: 9799 · Rating: 0 · rate: / Reply Quote | |
In my case it is a vega20 (radeon VII) and it was successful with linux? | |
ID: 9800 · Rating: 0 · rate: / Reply Quote | |
In my case it is a vega20 (radeon VII) Yes, running ~1100seconds and got 13500 credits | |
ID: 9801 · Rating: 0 · rate: / Reply Quote | |
ES7C95:/var/lib/boinc-client/projects/srbase.my-firewall.org_sr5/mfakto-test/mfakto-linux64-v10# ./mfakto-x64 -st > test.log 18.1MB test.log contents below -- Truncated. Is there a way to send you the file or do u just want the last page of it? mfakto 0.15pre8 (64-bit build)
Runtime options
INI file mfakto.ini
Verbosity 1
SieveOnGPU yes
MoreClasses yes
GPUSievePrimes 82486
GPUSieveProcessSize 24 Kib
GPUSieveSize 96 Mib
FlushInterval 8
WorkFile worktodo.txt
ResultsFile results.txt
Checkpoints enabled
CheckpointDelay 60 s
Stages enabled
StopAfterFactor class
PrintMode compact
V5UserID none
ComputerID none
TimeStampInResults no
VectorSize 2
GPUType AUTO
SmallExp no
UseBinfile mfakto_Kernels.elf
Compile-time options
Select device - Get device info:
OpenCL device info
name gfx1030 (Advanced Micro Devices, Inc.)
device (driver) version OpenCL 2.0 (3513.0 (HSA1.1,LC))
maximum threads per block 1024
maximum threads per grid 1073741824
number of multiprocessors 30 (1920 compute elements)
clock rate 2475 MHz
Automatic parameters
threads per grid 0
optimizing kernels for RDNA
Loading binary kernel file mfakto_Kernels.elf
Compiling kernels.
GPUSievePrimes (adjusted) 82486
GPUsieve minimum exponent 1055144
######### test case 1/34071 (M67094119[81-82]) #########
Starting trial factoring M67094119 from 2^81 to 2^82 (7299.20 GHz-days)
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Mar 21 16:49 | 1272 0.1% | 0.008 n.a. | n.a. 82486 0.00%
M67094119 has a factor: 2623030050785206718821057 (81.117509 bits, 857.719011 GHz-d)
found 1 factor for M67094119 from 2^81 to 2^82 [mfakto 0.15pre8 cl_barrett15_83_gs_2]
self-test for M67094119 passed (cl_barrett15_83_gs)!
tf(): total time spent: 0.008s
######### test case 2/34071 (M45448679[81-82]) #########
Starting trial factoring M45448679 from 2^81 to 2^82 (10775.53 GHz-days)
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Mar 21 16:49 | 700 0.1% | 0.007 n.a. | n.a. 82486 0.00%
M45448679 has a factor: 2758834464316013172866561 (81.190333 bits, 2050.940260 GHz-d)
found 1 factor for M45448679 from 2^81 to 2^82 [mfakto 0.15pre8 cl_barrett15_83_gs_2]
self-test for M45448679 passed (cl_barrett15_83_gs)!
tf(): total time spent: 0.007s
######### test case 3/34071 (M30568231[81-82]) #########
Starting trial factoring M30568231 from 2^81 to 2^82 (16020.99 GHz-days)
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Mar 21 16:49 | 1580 0.1% | 0.007 n.a. | n.a. 82486 0.00%
M30568231 has a factor: 3696288395636373937390841 (81.612352 bits, 9810.481914 GHz-d)
found 1 factor for M30568231 from 2^81 to 2^82 [mfakto 0.15pre8 cl_barrett15_83_gs_2]
self-test for M30568231 passed (cl_barrett15_83_gs)!
tf(): total time spent: 0.007s
######### test case 4/34071 (M71065531[81-82]) #########
Starting trial factoring M71065531 from 2^81 to 2^82 (6891.29 GHz-days)
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Mar 21 16:49 | 4116 0.1% | 0.007 n.a. | n.a. 82486 0.00%
M71065531 has a factor: 4702493985254889387181633 (81.959700 bits, 6613.577532 GHz-d)
found 1 factor for M71065531 from 2^81 to 2^82 [mfakto 0.15pre8 cl_barrett15_83_gs_2]
self-test for M71065531 passed (cl_barrett15_83_gs)!
tf(): total time spent: 0.007s
######### test case 5/34071 (M72067427[82-83]) #########
Starting trial factoring M72067427 from 2^82 to 2^83 (13590.98 GHz-days)
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Mar 21 16:49 | 4348 0.1% | 0.007 n.a. | n.a. 82486 0.00%
M72067427 has a factor: 6741341188542680773988393 (82.479310 bits, 6514.291481 GHz-d)
found 1 factor for M72067427 from 2^82 to 2^83 [mfakto 0.15pre8 cl_barrett32_87_gs_2]
self-test for M72067427 passed (cl_barrett32_87_gs)!
tf(): total time spent: 0.007s
######### test case 6/34071 (M52031087[82-83]) #########
| |
ID: 9802 · Rating: 0 · rate: / Reply Quote | |
Here's the bottom of test.log: ######### test case 34070/34071 (M332196671[91-92]) #########
Starting trial factoring M332196671 from 2^91 to 2^92 (1509608.98 GHz-days)
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Mar 21 16:50 | 484 0.1% | 0.009 n.a. | n.a. 82486 0.00%
M332196671 has a factor: 3466064070766392947648319689 (91.485357 bits, 732699.112106 GHz-d)
found 1 factor for M332196671 from 2^91 to 2^92 [mfakto 0.15pre8 cl_barrett32_92_gs_2]
self-test for M332196671 passed (cl_barrett32_92_gs)!
tf(): total time spent: 0.009s
######### test case 34071/34071 (M112404491[91-92]) #########
Starting trial factoring M112404491 from 2^91 to 2^92 (4461450.54 GHz-days)
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Mar 21 16:50 | 1848 0.1% | 0.009 n.a. | n.a. 82486 0.00%
M112404491 has a factor: 3941616367695054034124905537 (91.670846 bits, 2992945.937358 GHz-d)
found 1 factor for M112404491 from 2^91 to 2^92 [mfakto 0.15pre8 cl_barrett32_92_gs_2]
self-test for M112404491 passed (cl_barrett32_92_gs)!
tf(): total time spent: 0.009s
Self-test statistics
number of tests 34026
successful tests 34026
self-test PASSED! So, Do I have a wrapper problem? | |
ID: 9803 · Rating: 0 · rate: / Reply Quote | |
Here's the bottom of test.log: We can test with wrapper in a job.xml file, without it looks fine. | |
ID: 9804 · Rating: 0 · rate: / Reply Quote | |
Yes, but end results still the same: | |
ID: 9805 · Rating: 0 · rate: / Reply Quote | |
Yes, but end results still the same: I have created a short wrappertest 1. extract the zip. file 2. start only the wrapper file wrapper_26018_linux-u18_x86-64 outside boinc 3. check the results file | |
ID: 9807 · Rating: 0 · rate: / Reply Quote | |
This is what I get as user: | |
ID: 9808 · Rating: 0 · rate: / Reply Quote | |
ok, set the execute permissions to the wrapper file and change in job.xml -d 1 to -device 0 | |
ID: 9809 · Rating: 0 · rate: / Reply Quote | |
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards