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...
Ah ok, I tried GCN now and it seems to be okay too.
/ 
Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
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 parsefor option \"--device\"\n");
return ERR_PARAM;
}
}
i++;
}[/url]
This app is now up.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
Thanks, now I get a new error:
process exited with code 195
This is an error from BOINC (wrapper)
195 is CHILD_FAILED,
Which means the wrapper failed to start the worker app.
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
Thanks, now I get a new error:
process exited with code 195
This is an error from BOINC (wrapper)
195 is CHILD_FAILED,
Which means the wrapper failed to start the worker app.
I have tried it on the server (ubuntu) and the wrapper is starting the app (CPU), selftest was ok.
Did you use the same wrapper?
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
All my "standalone tests" are okay too. I think the problem ist that mfakto-x86_64 starts a child process to compile the mfakto_Kernels.elf file.
I seems that this forces the CHILD_FAILED error.
Can you include this file:
https://p-numbers.net/mfakto_Kernels.elf
in the ZIP?
(Just for a test)
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
All my "standalone tests" are okay too. I think the problem ist that mfakto-x86_64 starts a child process to compile the mfakto_Kernels.elf file.
I seems that this forces the CHILD_FAILED error.
Can you include this file:
https://p-numbers.net/mfakto_Kernels.elf
in the ZIP?
(Just for a test)
I hope you will not get an error, I put this in v5 zip.
Update
I have seen the error which I have expected, v7 is available.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
I get an error (two):
A new attached PC: Download error (checksum fail)
Previously attached: The old ZIP (without elf-file) remains, if you replace the file manually the file is deleted (zip error).
It seems you have to create a new version, sorry.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
On both of my PC with AMD GPU: error 195 from wrapper, with or without elf-file?!
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
On both of my PC with AMD GPU: error 195 from wrapper, with or without elf-file?!
with the .elf file
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
Yes with elf-file.
But in the tests before (zip without elf-file) was the same error.
Standalone test with wrapper and job.xml succeeded. So I don't know what the problem is. Sofware is o.k., but if the wrapper is started inside BOINC it fails.
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
Yes with elf-file.
But in the tests before (zip without elf-file) was the same error.
If the old wrapper was currently working in standalone then it must also be running in BOINC, this is odd, do you have a chance to compile the linux wrapper from the latest BOINC code? So we could trying if the latest wrapper is running.
https://github.com/BOINC/boinc (in samples folder)
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
You can download here:
https://p-numbers.net/wrapper
Version information:
wolfgang@i920:~/Downloads/boinc-client_release-7-7.16/samples/wrapper> ./wrapper --version
11:22:17 (26004): wrapper (7.16.26016): starting
7.16.6
11:22:17 (26004): called boinc_finish(0)
If you need a verion from trunk, I can compile it too. It shouldn't differ from this version here.
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
You can download here:
https://p-numbers.net/wrapper
Version information:
wolfgang@i920:~/Downloads/boinc-client_release-7-7.16/samples/wrapper> ./wrapper --version
11:22:17 (26004): wrapper (7.16.26016): starting
7.16.6
11:22:17 (26004): called boinc_finish(0)
If you need a verion from trunk, I can compile it too. It shouldn't differ from this version here.
v8 app is up with new wrapper
Update:
damnit, the execute bit was not set for wrapper. v9 is up
Looks like its running? But there are no checkpoints, if you are able to put the checkpoint code into the new wrapper code that would be great, I think the Mac app should be running too with the new wrapper.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
No doesn't work:
version `GLIBC_2.29' not found
The PC where I took the wrapper from has a very new linux and this dependency is awful.
I compiled BOINC on Ubuntu 18.04, and this wrapper should be o.k.:
https://p-numbers.net/wrapper_26016
For Linux it's a hard way to deploy software.....
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
No doesn't work:
version `GLIBC_2.29' not found
The PC where I took the wrapper from has a very new linux and this dependency is awful.
I compiled BOINC on Ubuntu 18.04, and this wrapper should be o.k.:
https://p-numbers.net/wrapper_26016
For Linux it's a hard way to deploy software.....
Linux shows me as shared lib not as executable file. I need a corrected file, cannot change it in config.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
Oops,
can you try this one:
https://p-numbers.net/wrapper_26016_7.16
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
Oops,
can you try this one:
https://p-numbers.net/wrapper_26016_7.16
is up, I have tried to compile it on the old ubuntu, no chance, I think the code isnt working anymore with older OS.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
And it's running!
stderr:
19:07:26 (16398): wrapper (7.16.26016): starting
19:07:26 (16398): wrapper (7.16.26016): starting
19:07:26 (16398): wrapper: running ./mfakto-x64 ()
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0
After one minute it jumped to 100% ?!
The first checkpoint was generated after 300 s.
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,717,239
RAC: 43,973
And it's running!
stderr:
19:07:26 (16398): wrapper (7.16.26016): starting
19:07:26 (16398): wrapper (7.16.26016): starting
19:07:26 (16398): wrapper: running ./mfakto-x64 ()
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0
After one minute it jumped to 100% ?!
The first checkpoint was generated after 300 s.
ok but there is no checkpointing in the wrapper code.
/ Reply
Quote
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,221
The checkpoint is generated from mfakto with the name: M97983883.ckp
/ Reply
Quote