Package Details: ollama-openmpi-git 0.3.9+5.r3417.20240902.ad3eb00b-2

Git Clone URL: https://aur.archlinux.org/ollama-nogpu-git.git (read-only, click to copy)
Package Base: ollama-nogpu-git
Description: Create, run and share large language models (LLMs). CPU optimisation with openMPI.
Upstream URL: https://github.com/jmorganca/ollama
Licenses: MIT
Conflicts: ollama
Provides: ollama, ollama-git
Submitter: dreieck
Maintainer: None
Last Packager: dreieck
Votes: 5
Popularity: 0.53
First Submitted: 2024-04-17 15:09 (UTC)
Last Updated: 2024-09-03 11:26 (UTC)

Required by (24)

Sources (5)

Latest Comments

1 2 Next › Last »

nmanarch commented on 2024-10-29 18:30 (UTC)

For @lavilao i just come to see your ask for run without avx hope you have success ? So if not you have to apply this : https://github.com/ollama/ollama/issues/2187#issuecomment-2262876198 So you have to download this ollama vulkan aur version ..change the line of code and do a new build package with the change and install this new build.

nmanarch commented on 2024-10-29 18:20 (UTC)

Hi @dreieck ! This is sad ! this is the only one i found for ollama run with vulkan. So perhaps i can take it but could you provide help if problems occurs with futur upgrade which become too hard to apply ?

dreieck commented on 2024-09-03 11:29 (UTC)

Does anyone want to take over?

I notice that I completely don't use this software, so I disown it.

Regards!

dreieck commented on 2024-09-03 11:29 (UTC)

Maybe the problem is caused by "go get" in pkgbuild, and this cause the permission of those go mod files are rrr, so when aurhelper try to delete them it crashes. I've found that people recommend "go mod download" instead of "go get" to prevent this

I now just changed go get to go mod download.

Regards!

lavilao commented on 2024-08-18 21:10 (UTC)

Hi, does anyone knows how to build this package without avx? I have added -DGGML_AVX=off, -DLLAMA_AVX=OFF -DLLAMA_AVX2=OFF -DLLAMA_AVX512=OFF -DLLAMA_AVX512_VBMI=OFF -DLLAMA_AVX512_VNNI=OFF -DLLAMA_F16C=OFF -DLLAMA_FMA=OFF yet when building llama.cpp server it still shows -DGGML_AVX=on.Am trying to build it on GitHub actions because my machine is to weak. Thanks in advice!

dreieck commented on 2024-08-03 11:36 (UTC) (edited on 2024-09-03 11:30 (UTC) by dreieck)

@beatboxchad,

Please discuss/report this with upstream.

The comments here are just for packaging issues, and yours is not a packaging issue as it seems.

@kkbs,
I am going to look into that sometime later, thanks for the information!

beatboxchad commented on 2024-08-03 04:37 (UTC)

Warm greetings,

I'm having this problem on two different laptops with Intel hardware:

Aug 02 23:14:54 myhostname ollama[1504679]: time=2024-08-02T23:14:54.987-05:00 level=INFO source=gpu.go:204 msg="looking for compatible GPUs"
Aug 02 23:14:55 myhostname ollama[1504679]: time=2024-08-02T23:14:55.043-05:00 level=INFO source=gpu.go:347 msg="no compatible GPUs were discovered"

I accidentally biked down to the coffeeshop without the other one, and my build output is obfuscated by that other issue y'all are discussing, but I've been fiddling with the build for a little while and don't see any obvious low-hanging fruit. There is one fact about the output I find peculiar, where although the Vulkan code appears to build it echos that only the CPU variant is built. I'll come back with that output soon.

Meanwhile, here's some basic diagnostic info about the machine I have:

$ lsgpu
card1                    Intel Kabylake (Gen9)             drm:/dev/dri/card1
└─renderD128                                               drm:/dev/dri/renderD128

vulkaninfo is too long to provide.

Yeaxi commented on 2024-08-03 02:33 (UTC) (edited on 2024-08-03 02:33 (UTC) by Yeaxi)

@dreieck hello dude. After viewing the pkgbuild and doing some search, I get some idea. Maybe the problem is caused by "go get" in pkgbuild, and this cause the permission of those go mod files are rrr, so when aurhelper try to delete them it crashes. I've found that people recommend "go mod download" instead of "go get" to prevent this, but I'm not pretty sure about it, maybe a pro like you can tell.btw, paru is a rust version of yay started by the same guy.

dreieck commented on 2024-07-28 09:41 (UTC)

Ahoj @kkbs,

Every time when I'm trying to upgrade this package, it shows that rm command cannot rm go pkg(permission denied), and I have to manually rm the paru cache to fix it, what could be wrong?

I do not have any idea about go specific stuff.
In the PKGBUILD there is no explicit rm.

So it seems that upstream's build script want to delete stuff.(?)

I do not understand why the build user does not have permission to delete the files that the same user has created.

What is "paru"? I do not see any reference to it in the PKGBUILD.

I have no idea, I did not encounter any such issue so far.

So maybe someone else who has an idea give a hint?

Regards!

Yeaxi commented on 2024-07-28 02:35 (UTC)

Every time when I'm trying to upgrade this package, it shows that rm command cannot rm go pkg(permission denied), and I have to manually rm the paru cache to fix it, what could be wrong?

1 2 Next › Last »