| log in |
|
1)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9825)
Posted 22 Mar 2024 by Magiceye04 but it is not working again. This was before one of the many changes i should try. And I have to stop testing now. Easter holiday is starting tomorrow. |
|
2)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9823)
Posted 22 Mar 2024 by Magiceye04 The result.txt is old no factor for M758604829 from 2^73 to 2^74 [mfakto 0.15pre8 cl_barrett32_76_gs_2] after deleting and re-run the result.txt is not created again. Only stderr.txt. 22024-03-22 23:01:50 (493629): Can't open init data file - running in standalone mode 2024-03-22 23:01:50 (493629): wrapper (7.24.26018): starting 2024-03-22 23:01:50 (493629): called boinc_finish(0) |
|
3)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9821)
Posted 22 Mar 2024 by Magiceye04 [Try to set execute permissions also to wrapper file. There is no file named "wrapper" I have now set all files to exec. 2024-03-22 22:14:14 (487765): Can't open init data file - running in standalone mode 2024-03-22 22:14:14 (487765): wrapper (7.24.26018): starting 2024-03-22 22:14:14 (487765): wrapper: running ./mfakto-x64 (-d 0) 2024-03-22 22:14:14 (487765): wrapper: created child process 487769 2024-03-22 22:17:12 (487765): ./mfakto-x64 exited; CPU time 2.648441 2024-03-22 22:17:12 (487765): called boinc_finish(0) 2024-03-22 22:42:34 (491215): Can't open init data file - running in standalone mode 2024-03-22 22:42:34 (491215): wrapper (7.24.26018): starting 2024-03-22 22:42:34 (491215): called boinc_finish(0) 2024-03-22 22:50:33 (492097): Can't open init data file - running in standalone mode 2024-03-22 22:50:33 (492097): wrapper (7.24.26018): starting 2024-03-22 22:50:33 (492097): called boinc_finish(0) |
|
4)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9818)
Posted 22 Mar 2024 by Magiceye04
mfakto-x64 is executable and worktodo.txt was empty I copied it again. 2024-03-22 22:14:14 (487765): Can't open init data file - running in standalone mode 2024-03-22 22:14:14 (487765): wrapper (7.24.26018): starting 2024-03-22 22:14:14 (487765): wrapper: running ./mfakto-x64 (-d 0) 2024-03-22 22:14:14 (487765): wrapper: created child process 487769 2024-03-22 22:17:12 (487765): ./mfakto-x64 exited; CPU time 2.648441 2024-03-22 22:17:12 (487765): called boinc_finish(0) 2024-03-22 22:42:34 (491215): Can't open init data file - running in standalone mode 2024-03-22 22:42:34 (491215): wrapper (7.24.26018): starting 2024-03-22 22:42:34 (491215): called boinc_finish(0) |
|
5)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9815)
Posted 22 Mar 2024 by Magiceye04 downloaded again. stderr.txt: 2024-03-22 22:08:13 (487009): Can't open init data file - running in standalone mode 2024-03-22 22:08:13 (487009): wrapper (7.24.26018): starting 2024-03-22 22:08:13 (487009): wrapper: running ./mfakto-x64 (-device 0) 2024-03-22 22:08:13 (487009): wrapper: created child process 487011 execv() failed: : Permission denied 2024-03-22 22:08:14 (487009): ./mfakto-x64 exited; CPU time 0.000212 2024-03-22 22:08:14 (487009): app exit status: 0x6c 2024-03-22 22:08:14 (487009): called boinc_finish(195) terminal: 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 gfx906 (Advanced Micro Devices, Inc.) device (driver) version OpenCL 2.0 AMD-APP (3180.7) (3180.7 (PAL,HSAIL)) maximum threads per block 1024 maximum threads per grid 1073741824 number of multiprocessors 60 (3840 compute elements) clock rate 1304 MHz Automatic parameters threads per grid 0 optimizing kernels for GCNF Compiling kernels. GPUSievePrimes (adjusted) 82486 GPUsieve minimum exponent 1055144 Started a simple self-test ... Self-test statistics number of tests 30 successful tests 30 self-test PASSED! got assignment: exp=758604829 bit_min=73 bit_max=74 (2.52 GHz-days) Starting trial factoring M758604829 from 2^73 to 2^74 (2.52 GHz-days) Using GPU kernel "cl_barrett32_76_gs_2" Date Time | class Pct | time ETA | GHz-d/day Sieve Wait Mar 22 22:17 | 4619 100.0% | 0.182 0m00s | 1247.03 82486 0.00% no factor for M758604829 from 2^73 to 2^74 [mfakto 0.15pre8 cl_barrett32_76_gs_2] tf(): total time spent: 2m 55.770s (1239.58 GHz-days / day) ERROR: get_next_assignment(): no valid assignment found in "worktodo.txt" |
|
6)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9808)
Posted 22 Mar 2024 by Magiceye04 This is what I get as user: 2024-03-22 20:16:29 (475150): Can't open init data file - running in standalone mode 2024-03-22 20:16:29 (475150): wrapper (7.24.26018): starting 2024-03-22 20:16:29 (475150): wrapper: running ./mfakto-x64 (-d 1) 2024-03-22 20:16:29 (475150): wrapper: created child process 475154 execv() failed: : Permission denied 2024-03-22 20:16:30 (475150): ./mfakto-x64 exited; CPU time 0.000283 2024-03-22 20:16:30 (475150): app exit status: 0x6c 2024-03-22 20:16:30 (475150): called boinc_finish(195) and this as su: 2024-03-22 20:12:54 (474696): Can't open init data file - running in standalone mode 2024-03-22 20:12:54 (474696): wrapper (7.24.26018): starting 2024-03-22 20:12:54 (474696): wrapper: running ./mfakto-x64 (-d 1) 2024-03-22 20:12:54 (474696): wrapper: created child process 474698 Error -33 (Invalid device): clGetContextInfo(CL_DEVICE_NAME) 2024-03-22 20:12:55 (474696): ./mfakto-x64 exited; CPU time 0.017179 2024-03-22 20:12:55 (474696): app exit status: 0x2 2024-03-22 20:12:55 (474696): called boinc_finish(195 there is also something in the terminal: 2024-03-22 20:12:54 (474696): wrapper (7.24.26018): starting 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: ERROR: init_CL(3, 1) failed |
|
7)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9801)
Posted 21 Mar 2024 by Magiceye04 In my case it is a vega20 (radeon VII) Yes, running ~1100seconds and got 13500 credits |
|
8)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9799)
Posted 21 Mar 2024 by Magiceye04 In my case it is a vega20 (radeon VII) TF v0.17 (opencl_ati_101) was running fine last year. |
|
9)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9797)
Posted 21 Mar 2024 by Magiceye04 done. failed. ./mfakto-x64 -st ######### 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 19:45 | 1848 0.1% | 0.010 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.011s Self-test statistics number of tests 34026 successful tests 33288 no factor found 738 self-test FAILED! ERROR: self-test failed, exiting. |
|
10)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9795)
Posted 21 Mar 2024 by Magiceye04 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... |
|
11)
Message boards :
Number crunching :
Linux TF WUs on ATI 6800 cards
(Message 9789)
Posted 21 Mar 2024 by Magiceye04 The same for me on a VII. All end with error, exit code 195 |
|
12)
Message boards :
Number crunching :
Sierpinski / Riesel Base - long3 v0.27 - after 20hours and 90% back to 0 % ??
(Message 8858)
Posted 9 May 2023 by Magiceye04 The WUs were running since additional 13 hours now. I dont see any hint of a checkpoint. Are 40-50 hours normal run time for Sierpinski / Riesel Base - long3 v0.27 on a Ryzen 5950X? |
|
13)
Message boards :
Number crunching :
Sierpinski / Riesel Base - long3 v0.27 - after 20hours and 90% back to 0 % ??
(Message 8856)
Posted 8 May 2023 by Magiceye04 Thanks! Is the percentage value in the Boinc manager linear? I had 20hours=90%, which means 1%~0,22hours. After now additional 3,5hours (=+35%) I would have originally 105%. |
|
14)
Message boards :
Number crunching :
Sierpinski / Riesel Base - long3 v0.27 - after 20hours and 90% back to 0 % ??
(Message 8854)
Posted 8 May 2023 by Magiceye04 23:15:04 (1567192): wrapper (7.2.26012): starting |
|
15)
Message boards :
Number crunching :
Sierpinski / Riesel Base - long3 v0.27 - after 20hours and 90% back to 0 % ??
(Message 8852)
Posted 8 May 2023 by Magiceye04 Hello, I have some Sierpinski / Riesel Base - long3 v0.27 running. After 20 hours and about 90% the WUs were paused by the boinc manager to run other project tasks. Back to SRbase the Sierpinski / Riesel Base - long3 v0.27 started from 0%. Are the first 20 hours now lost? I have set to keep the work in memory during pause. Will this WUs running endless until deadline, because every pause will do a restart? |