Search found 30 matches
- Mon Jan 30, 2023 5:44 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
This issue has been resolved.
- Mon Jan 30, 2023 12:07 am
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
Judging by the reply, it seems that there are fewer core options in the v8 beta and hence my older CPU is not supported in v8 while it is in v7. It also appears that this is something configured by FAH server. Is that correct?
TY!
TY!
- Sun Jan 29, 2023 10:18 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
Update, this was just populated in the log. Here is the entry.
Code: Select all
21:38:57:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/cores.foldingathome.org/lin/64bit-sse2/a8-0.0.12/Core_a8.fah/FahCore_a8 -dir 00 -suffix 01 -version 704 -lifeline 1845 -checkpoint 15
- Sun Jan 29, 2023 9:42 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
I just looked at this and cannot find the entry in the log mentioned above. Maybe because verbosity was set at 1? I upped it to 5 and restarted the service and still don't see where I can find the core. Is it somewhere else? The system is still folding away....
- Sun Jan 29, 2023 5:40 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
Update: I installed v7 on the SAME client that is given the "No cores found" error in v8, and it is happily folding away. I will open a Github ticket as this is definitely a v8 bug. For future reference is here a direct link to the GitHub ticket: https://github.com/FoldingAtHome/fah-client...
- Sun Jan 29, 2023 5:21 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
Thank you for the clarification and history. A couple of questions to consider: Where is the core download request attribute in the beta build? It would appear to be missing if it is not in the debug build with verbosity 10. Could the issue I am seeing be related to a bug? Out of curiousity, I am go...
- Sun Jan 29, 2023 3:22 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
I moved to the debug version and do not see that. I then upped the debug verbosity to 10. I let a few WU searches happen and grep'd the resulting log for "avx" or "sse" and found nothing. For good measure, I also searched for "a8" and "a9" and neither of those...
- Sun Jan 29, 2023 2:53 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
Thank you for the clarification. I will install the debug version of v8 client and switch to verbosity 3 and see if I can find and post that information.
- Sun Jan 29, 2023 12:47 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Re: Error: No Matching Core on v8.1.11 client
I don't know what the released A9 supports, but future builds currently are for sse4_1, avx_256, avx2_256. There is also the matter of which cores have been validated and deployed for v8 use. Does this mean that to use A9 a CPU must have one of these things or all of them? This raises a bigger ques...
- Sat Jan 28, 2023 7:25 pm
- Forum: V8.1.xx Open Beta
- Topic: Error: No Matching Core on v8.1.11 client
- Replies: 20
- Views: 12123
Error: No Matching Core on v8.1.11 client
I am using the beta and just installed it on a second machine which worked fine. The first two units are reasonably powerful (11th gen i5), and now I am considering running on FAH other systems. Specifically the following: Celeron J3160 Celeron 3215U Celeron N3450 I have installed the 8.1.11 client ...
- Fri Jan 27, 2023 11:24 pm
- Forum: V8.1.xx Open Beta
- Topic: Summarizing headless beta learnings
- Replies: 3
- Views: 1375
Re: Summarizing headless beta learnings
Awesome, thanks for driving this!
- Fri Jan 27, 2023 11:18 pm
- Forum: V8.1.xx Open Beta
- Topic: Not getting WUs in 8.1.11 Beta
- Replies: 28
- Views: 3994
Re: Not getting WUs in 8.1.11 Beta
Thank you for the log details and CPU clarification.
If 1 CPU will rarely work, should the client even allow that as an option? Is there some other limit that? At a minimum, it should be documented.
If 1 CPU will rarely work, should the client even allow that as an option? Is there some other limit that? At a minimum, it should be documented.
- Fri Jan 27, 2023 5:16 pm
- Forum: V8.1.xx Open Beta
- Topic: Not getting WUs in 8.1.11 Beta
- Replies: 28
- Views: 3994
Re: Not getting WUs in 8.1.11 Beta
Unexpected update -- The cause list just populated! I have no idea why as I have done nothing except early today when I changed the CPU 2.
- Fri Jan 27, 2023 1:43 pm
- Forum: V8.1.xx Open Beta
- Topic: Summarizing headless beta learnings
- Replies: 3
- Views: 1375
Summarizing headless beta learnings
First let me start by recognizing @calxalot for his help through this process. As an appreciation for all the efforts, I wanted to summarize the findings in one post in the hopes that it can help the dev team as we go through the beta process. Please note, that all is not well as I still have the AP...
- Fri Jan 27, 2023 1:01 pm
- Forum: V8.1.xx Open Beta
- Topic: Not getting WUs in 8.1.11 Beta
- Replies: 28
- Views: 3994
Re: Not getting WUs in 8.1.11 Beta
Wow so adding a second CPU in the GUI seemed to solve the "No WU" problem as it found one and started working. Great! I am curious why. I still don't see any entries in the "cause" box and so would still love to figure out how to resolve that. Oh and removing the log entries from...