Volunteer developer
Volunteer tester
Send message
Joined: 7 Aug 19
Posts: 19
Credit: 10,641,118
RAC: 0
Also- if anyone is trying to debug mfakto errors make sure to set Verbosity to 3 in the ini to show everything.
/ 
Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Do you mean it's not recognized or it does not run?
Because even though my vega 8 isn't recognized it still runs.
The device is recognized and calculation starts but fails.
To test if this is a driver issue I have replaced the Radeon 5500XT with an R9 380 and now the selftest is completed with success.
But now I can't get new work to test if "AMD with Linux x86_64" is running or not?!
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
I have managed to install the AMD 20.10 driver for linux and the Radeon 5500XT now passes the selftest without errors.
Can you please allow new work for linux boxes with AMD GPU?
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,041
RAC: 41,978
I have managed to install the AMD 20.10 driver for linux and the Radeon 5500XT now passes the selftest without errors.
Can you please allow new work for linux boxes with AMD GPU?
done.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Thanks.
results are failing:
13:20:23 (13094): wrapper: running ./mfakto-x64 ( -d 11 --device 0)
app_config.xml tells -d 11 but the argument --device 0 ist still there...
How can we deal with this?
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,041
RAC: 41,978
Thanks.
results are failing:
13:20:23 (13094): wrapper: running ./mfakto-x64 ( -d 11 --device 0)
app_config.xml tells -d 11 but the argument --device 0 ist still there...
How can we deal with this?
could be the wrapper app. Can you test it standalone?
copy the zip folder somewhere, create a worktodo.txt file, put this into the file
Factor=78467119,70,71
run the app, if this is working then the boinc wrapper need a change.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
I can do this around 18:00 UTC+2. Now it's time to visit the 80+ generation for Easter. (Corona social task force)
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,041
RAC: 41,978
I can do this around 18:00 UTC+2. Now it's time to visit the 80+ generation for Easter. (Corona social task force)
yes, do this as long as you can, my grandmother died on Friday but no Corona.
/ Reply
Quote
yes, do this as long as you can, my grandmother died on Friday but no Corona.
I'm sorry to hear that, really hope that you got the best of your time with her :)
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
@Rebirther: I am sorry to read that.
Tests with worktodo.txt:
In the self compiled stuff: o.k. runtime about 8 min.
In the unpacked ZIP: Failure.
In the ZIP is contained: mfakto_Kernels.elf
This will work only for the specific hardware and Linux for what this file was compiled for. This file has to be deleted ... it will be compiled during runtime in the target system.
After deletion of mfakto_Kernels.elf the test is also running for the ZIP content.
I have made my own app_info.xml.....but project doesn't accept this.
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,041
RAC: 41,978
@Rebirther: I am sorry to read that.
Tests with worktodo.txt:
In the self compiled stuff: o.k. runtime about 8 min.
In the unpacked ZIP: Failure.
In the ZIP is contained: mfakto_Kernels.elf
This will work only for the specific hardware and Linux for what this file was compiled for. This file has to be deleted ... it will be compiled during runtime in the target system.
After deletion of mfakto_Kernels.elf the test is also running for the ZIP content.
I have made my own app_info.xml.....but project doesn't accept this.
ok, noticed, the app is deprecated again, you dont need to full run, for the wrapper test, rename the job.xxx.xml file to job.xml, put the factor again in the worktodo.txt and run the wrapper, if this is working we have tracked down the issue.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
It's running:
wolfgang@9600k:~/BOINC/projects/srbase.my-firewall.org_sr5$ ./wrapper_26012-v2_x86_64-pc-linux-gnu
mfakto 0.15pre6 (64bit build)
Runtime options
Inifile 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 300 s
Stages enabled
StopAfterFactor class
PrintMode compact
V5UserID none
ComputerID none
TimeStampInResults no
VectorSize 2
GPUType AUTO
SmallExp no
UseBinfile mfakto_Kernels.elf
Compiletime options
Select device - Get device info:
WARNING: Unknown GPU name, assuming GCN. Please post the device name "gfx1012 (Advanced Micro Devices, Inc.)" to http://www.mersenneforum.org/showthread.php?t=15646 to have it added to mfakto. Set GPUType in mfakto.ini to select a GPU type yourself to avoid this warning.
OpenCL device info
name gfx1012 (Advanced Micro Devices, Inc.)
device (driver) version OpenCL 2.0 AMD-APP (3075.9) (3075.9 (PAL,LC))
maximum threads per block 1024
maximum threads per grid 1073741824
number of multiprocessors 11 (704 compute elements)
clock rate 1855 MHz
Automatic parameters
threads per grid 0
optimizing kernels for GCN
Compiling kernels.
GPUSievePrimes (adjusted) 82486
GPUsieve minimum exponent 1055144
Started a simple selftest ...
Selftest statistics
number of tests 30
successful tests 30
selftest PASSED!
got assignment: exp=78467119 bit_min=70 bit_max=71 (3.05 GHz-days)
Starting trial factoring M78467119 from 2^70 to 2^71 (3.05GHz-days)
Using GPU kernel "cl_barrett15_73_gs_2"
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Apr 12 19:43 | 116 2.4% | 0.553 8m38s | 495.97 82486 0.00%
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,041
RAC: 41,978
Thats great, nice finding, I will add a new updated app.
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,041
RAC: 41,978
New linux opencl app is up.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
ERROR: unknown option '--device'
The application mfakto doesn't know the option --device
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,041
RAC: 41,978
ERROR: unknown option '--device'
The application mfakto doesn't know the option --device
The same config as in test? We need to check both folders, your new compiled version with the current used.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
I have extended the parameter list for mfakto. (and compiled)
You can download it frome here:
https://p-numbers.net/mfakto_linux_x86_64_device.zip
HTH
the new code snippet:
else if(!strcmp((char*)"--device", argv[i]))
{
if(i+1 >= argc)
{
printf("ERROR: no device number specified for option \"--device\"\n");
return ERR_PARAM;
}
else if (argv[i+1][0] == '0') // parse to 00
{
devicenumber = strtol("00",&ptr,10);
if(*ptr || errno || devicenumber != strtol("00",&ptr,10) )
{
printf("ERROR: can't parse <device number> for option \"--device\"\n");
return ERR_PARAM;
}
}
i++;
}[/url]
/ Reply
Quote
I have extended the parameter list for mfakto. (and compiled)
Are you sure that you have taken into account all possible combinations of these parameters?
- numbering platform / device (from one) and just a device (from zero).
- "ingenious" user config and trivial "-device 0" from wrapper
- or a simple conflict in the numbers of these parameters
a couple of examples for a logic test
( -d 11 --device 0)
( -d g --device 0)
( -d c --device 0)
can simply ignore (delete when analyzing arguments) the --device parameter in the presence of the -d parameter?
/ Reply
Quote
I can do this around 18:00 UTC+2. Now it's time to visit the 80+ generation for Easter. (Corona social task force)
yes, do this as long as you can, my grandmother died on Friday but no Corona.
I'm really sorry to hear that.
Also, my device isn't recognized when mfakto is collecting device data unless I specify APU.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 7 Aug 19
Posts: 19
Credit: 10,641,118
RAC: 0
Even though your APU is not recognized, I think selecting APU will be slower than "AUTO" - kernels used on the APU settings were tested on much older, different APU's (if i recall correctly, that was tuned for A8-3850... released 2011.)
I'm hoping I can test the IGP of the Ryzen 2400g that I get occasional access to...
/ Reply
Quote