Differences

This shows you the differences between two versions of the page.

--- linux64 [2025/06/01 08:39] – [squeezebox for music] bengt
+++ linux64 [2025/07/13 14:09] (current) – [ollama in podman for ai] bengt
@@ Line 457: / Line 457: @@
 See misc below for scanning tv channels...
-==== squeezebox for music ====
+==== squeezebox/lyrion music server ====
-I found out that there is a spotify-plugin for squeezebox and decided to try a Boom in the kitchen and after a number of years I now have 9 squeezeboxes. Nowadays they aren't manufactured anymore but it is possible to use a chromecast as a squeezebox using a plugin in the server. Squeezebox on the server is a very nice solution to get access to your music files, spotify, internet radio and more. Instructions for fedora here:\\
+I found out that there is a spotify-plugin for squeezebox and decided to try a Boom in the kitchen and after a number of years I now have 9 squeezeboxes. Nowadays they aren't manufactured anymore but it is possible to use a chromecast as a squeezebox using a plugin in the server. Squeezebox on the server is a very nice solution to get access to your music files, spotify, internet radio and more.Instructions for fedora here:\\
 http://wiki.slimdevices.com/index.php
+Note that it is called lyrionmusicserver nowadays and some instructions below may need an update...
 There was a period when the community squeeze project had a fedora repo available. This is no longer the case, but there are still some nice guys updating the server:
@@ Line 476: / Line 478: @@
   # dnf install logitechmediaserver-8.5.2-1.noarch.rpm
   # wget https://downloads.lms-community.org/LyrionMusicServer_v9.0.2/lyrionmusicserver-9.0.2-1.noarch.rpm
-  # dnf install lyrionmusicserver-9.0.2-1.noarch.rpm
+  # dnf install lyrionmusicserver-9.0.2-1.noarch.rpm # Moving config from /var/lib/squeezeboxserver to /etc/sysconfig/lyrionmusicserver and needs changes to scripts accordingly
   # ln -s /usr/lib/perl5/vendor_perl/Slim /usr/lib64/perl5/vendor_perl/Slim # Fix for 64bit OS
   # firewall-config # Open port 9000 TCP for http, 3483 TCP&UDP, 9005 TCP&UDP for spotify, 49152-49215 TCP for 3x chromecast bridge and 9090 TCP for cli. Note that cc bridge port is dynamic, tick "Use LMS interface and start from port" and set base port 49152.
@@ Line 803: / Line 805: @@
 URL Redirect Record	@ http://www.johannesson.rocks Unmasked
 (If you keep the URL redirect stuff then the ip-addresses will be combined with namecheaps. Not good.)
+==== ollama in podman for ai ====
+Using rootless podman as a separate user (starting with cpu only):
+  # dnf install
+  # useradd ollama
+  # visudo
+  ALL ALL=(ollama) NOPASSWD: /home/ollama/start.sh
+  # firewall-config # Add tcp 11434 to be able to access it from hass
+  # su - ollama
+  $ mkdir ollama
+  $ vi start.sh
+  #!/bin/bash -x
+  cd $HOME
+  loginctl enable-linger ollama
+  podman run -d --rm -v /home/ollama/ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama
+  $ chmod u+x start.sh
+Then setup a start.sh-script containing the startup command line and maybe start this using "lxterminal -t ollama -e sudo -u ollama /home/ollama/start.sh". Replace "-d" with "-it" in the podman command line to see the output if starting this way.
+Test it as the ollama user:
+  # su - ollama
+  $ podman exec -it ollama ollama run llama2
+You can add the ollama integration to home assistant. On issues check your firewall config. Be sure to have "conversation:" "assist_pipeline:" in configuration.yaml if you do not use the default config before trying to setup assist pipelines.
+TODO: GPU support. Need to use nvidia drivers first...