Problems with askasync after switching to a worse cpu

[Milucide]

Hi :) I use LLamasharp with KernelMemory on a CPU. I started developing on a computer with a good GPU and CPU. My Code worked well with both (tried them seperately by switching the backend package). Now I got the task to switch to a computer with a cpu that is not as good as the one of the computer I used previously. The code is much slower (as I expected) but still runs for most commands like SearchAsync but as soon as my code hits the askasync statement I get the error: An unhandled exception was thrown by the application.
System.AggregateException: One or more errors occurred. (Unable to find an entry point named 'llama_sample_repetition_penalties' in DLL 'llama'.)

Does anyone know whether there could be a connection between the worse cpu and the error message? (The task runs for a long time beforer the errormessage. I am not sure how long exactly. It could be hours)

[dluc]

@Milucide here's two things I would try:

• Check the version of LLamaSharp you are using. If you're adding the LLamaSharp backend manually, make sure the version matches with the one used in KM.

• Consider switching to Ollama, if compatible with your environment. Since Ollama works over HTTP, it's much easier to work with.

[Milucide]

The versions are not the problem. I checked them and they are the same for llamasharp and the backend.
Thank you for the advice with ollama. I'll check it out.