Also- if anyone is trying to debug mfakto errors make sure to set Verbosity to 3 in the ini to show everything.

Do you mean it's not recognized or it does not run?
Because even though my vega 8 isn't recognized it still runs.

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?

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?

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?

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?

I can do this around 18:00 UTC+2. Now it's time to visit the 80+ generation for Easter. (Corona social task force)

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.

@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.

@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.

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%

Thats great, nice finding, I will add a new updated app.

New linux opencl app is up.

ERROR: unknown option '--device'

The application mfakto doesn't know the option --device

ERROR: unknown option '--device'

The application mfakto doesn't know the option --device

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]

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...