linux64
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| linux64 [2026/05/30 16:43] – [TBS 6280 PCIe DVB-T2] bengt | linux64 [2026/07/18 21:37] (current) – [ollama in podman for ai] bengt | ||
|---|---|---|---|
| Line 78: | Line 78: | ||
| Removed a kernel and tried this instead: | Removed a kernel and tried this instead: | ||
| - | echo -e ' | + | # echo -e ' |
| - | dracut --force | + | # |
| + | Then clone again. Remove sata and boot from nvme to check that it works. This time it did. Then boot livecd again, install gparted and use this to expand /boot and move and expand / putting the swap at the end as well. Reboot | ||
| - | Then clone again. Remove sata and boot from nvme to check that it works. This time it did. | + | Also took the time to get new rescue images as my old ones were from 2016, remove old vmlinuz/ |
| - | + | # / | |
| - | Then boot livecd again, | + | |
| Line 866: | Line 866: | ||
| cd $HOME | cd $HOME | ||
| loginctl enable-linger ollama | loginctl enable-linger ollama | ||
| - | podman run -d --rm -v / | + | podman run -d --rm -v / |
| $ chmod u+x start.sh | $ chmod u+x start.sh | ||
| Then setup a start.sh-script containing the startup command line and maybe start this using " | Then setup a start.sh-script containing the startup command line and maybe start this using " | ||
| Line 872: | Line 872: | ||
| Test it as the ollama user: | Test it as the ollama user: | ||
| # su - ollama | # su - ollama | ||
| - | $ podman exec -it ollama ollama run llama2 | + | $ podman exec -it ollama |
| + | $ ollama run llama3.2 | ||
| + | |||
| + | Backup images and update: | ||
| + | # su - ollama | ||
| + | $ podman save ollama/ | ||
| + | $ podman pull ollama/ | ||
| + | Restart container... | ||
| You can add the ollama integration to home assistant. On issues check your firewall config. Be sure to have " | You can add the ollama integration to home assistant. On issues check your firewall config. Be sure to have " | ||
| - | TODO: GPU support. Need to use nvidia drivers | + | After buying a 5060 16GB ti for AI to have next to my 1660 ti super used for the console I needed to switch |
| + | # dnf update # To avoid issues below. Reboot if new kernel. | ||
| + | # dnf install -y akmod-nvidia xorg-x11-drv-nvidia-cuda | ||
| + | # akmods --force | ||
| + | Wait for akmod to complete building drivers before rebooting. Check with top? | ||
| + | Note that I lost audio after this for the new kernel that got installed at the same time. Turns out that those modules were not installed as they were not needed to compile the nvidia driver. Update and reboot before or install lacking kernel-modules and kernel-modules-extra. This should also work "dnf install kernel-$(uname -r)". | ||
| + | Configure podman: | ||
| + | # dnf install nvidia-container-toolkit | ||
| + | # nvidia-ctk cdi generate --output=/ | ||
| + | # nvidia-ctk cdi list | ||
| + | # podman run --rm --security-opt label=disable --device nvidia.com/ | ||
| + | # vi start.sh | ||
| + | Add " | ||
| + | # nvidia-smi # Check ram usage for gpus. Watch out for too large context windows spilling over as it will spread not prioritizing the 5060 ti. | ||
| + | If you run into context size problems (it got capped at 4096) you can add "-e OLLAMA_CONTEXT_LENGTH=32768" | ||
| ===== Software ===== | ===== Software ===== | ||
linux64.1780159437.txt.gz · Last modified: by bengt