"vscode:/vscode.git/clone" did not exist on "efe90f84351e5bfae3ef92faa12f9ba8ade1ce84"
- 19 Aug, 2024 2 commits
-
-
Daniel Hiltgen authored
-
Daniel Hiltgen authored
-
- 09 Jun, 2024 1 commit
-
-
Napuh authored
* Added instructions to easily install specific versions on faq.md * Small typo * Moved instructions on how to install specific version to linux.md * Update docs/linux.md * Update docs/linux.md --------- Co-authored-by:Jeffrey Morgan <jmorganca@gmail.com>
-
- 06 May, 2024 1 commit
-
-
Mohamed A. Fouad authored
Add -e to viewing logs in order to show end of ollama logs
-
- 09 Mar, 2024 1 commit
-
-
Daniel Hiltgen authored
The recent ROCm change partially removed idempotent payloads, but the ggml-metal.metal file for mac was still idempotent. This finishes switching to always extract the payloads, and now that idempotentcy is gone, the version directory is no longer useful.
-
- 07 Mar, 2024 1 commit
-
-
Daniel Hiltgen authored
This refines where we extract the LLM libraries to by adding a new OLLAMA_HOME env var, that defaults to `~/.ollama` The logic was already idempotenent, so this should speed up startups after the first time a new release is deployed. It also cleans up after itself. We now build only a single ROCm version (latest major) on both windows and linux. Given the large size of ROCms tensor files, we split the dependency out. It's bundled into the installer on windows, and a separate download on windows. The linux install script is now smart and detects the presence of AMD GPUs and looks to see if rocm v6 is already present, and if not, then downloads our dependency tar file. For Linux discovery, we now use sysfs and check each GPU against what ROCm supports so we can degrade to CPU gracefully instead of having llama.cpp+rocm assert/crash on us. For Windows, we now use go's windows dynamic library loading logic to access the amdhip64.dll APIs to query the GPU information.
-
- 09 Feb, 2024 1 commit
-
-
Jeffrey Morgan authored
-
- 12 Jan, 2024 1 commit
-
-
Tristram Oaten authored
After executing the `userdel ollama` command, I saw this message: ```sh $ sudo userdel ollama userdel: group ollama not removed because it has other members. ``` Which reminded me that I had to remove the dangling group too. For completeness, the uninstall instructions should do this too. Thanks!
-
- 25 Oct, 2023 1 commit
-
-
Michael Yang authored
-
- 24 Oct, 2023 1 commit
-
-
Bruce MacDonald authored
-
- 15 Oct, 2023 1 commit
-
-
Jeffrey Morgan authored
-
- 01 Oct, 2023 1 commit
-
-
Jiayu Liu authored
-
- 25 Sep, 2023 5 commits
-
-
Jeffrey Morgan authored
-
Jeffrey Morgan authored
-
Jeffrey Morgan authored
-
Jeffrey Morgan authored
-
Jeffrey Morgan authored
-