Differences

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

--- linux64 [2024/10/12 08:15] – [minecraft server] bengt
+++ linux64 [2025/10/27 20:15] (current) – [squeezebox/lyrion music server] bengt
@@ Line 142: / Line 142: @@
 Eventually I found https://www.reddit.com/r/Fedora/comments/186amfb/kernels_6510_does_not_install_properly_in_fedora/ and https://discussion.fedoraproject.org/t/f39-kernels-fail-to-install-when-boot-efi-machineid-is-present/96086 which apparently was a fedora 39 problem when upgrading since forever. The solution was:
   # mv "/boot/efi/$(cat /etc/machine-id)" "/boot/efi/$(cat /etc/machine-id)_disabled"
+I deleted the _disabled folder later to get back some disk storage. Seemed to boot fine, but it was the rescue stuff that was taking disk space.
 ==== efi partition to fat32 ====
@@ Line 456: / 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 472: / Line 475: @@
   # vi /etc/group0
   squeezeboxserver:x:319:
-  # wget http://downloads-origin.slimdevices.com/nightly/8.3/lms/8e014fb139b7e75bf19d7750ce70efd6959e2d43/logitechmediaserver-8.3.1-0.1.1672158254.noarch.rpm
-  # dnf install logitechmediaserver-8.3.1-0.1.1672158254.noarch.rpm
   # wget https://downloads.lms-community.org/LogitechMediaServer_v8.5.2/logitechmediaserver-8.5.2-1.noarch.rpm
   # 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 # 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 494: / Line 497: @@
   $ sed 's#/data/music/#Y:/music/#g' Bengts.m3u > BengtsWin.m3u
+There is an issue with loosing connection with radios on modern wifis. Maybe playing a mad song when using the radio as an alarm clock. The community firmware could be the solution: https://forums.lyrion.org/forum/user-forums/3rd-party-software/1699666-how-and-why-to-install-the-community-firmware-step-by-step
 ==== samba network shares ====
@@ Line 768: / Line 772: @@
   ## NameCheap DynDNS
   ##
-  use=web, web=dynamicdns.park-your-domain.com/getip
+  #use=web, web=dynamicdns.park-your-domain.com/getip # Stopped working 20250321, got 1.1.0.1 as ip
+  use=web, web=http://ipv4.nsupdate.info/myip
   protocol=namecheap
@@ Line 801: / Line 806: @@
 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.)
+==== OpenWebRX+ for radio ====
+I buought an rtl sdr dongle that I later realized would be nice to pair with a leftover pi 4: \\
+https://fms.komkon.org/OWRX/ \\
+https://luarvique.github.io/ppa/ \\
+Use the the official raspberry image to enable and set ssh username/password: \\
+https://github.com/luarvique/openwebrx/releases/ \\
+https://www.raspberrypi.com/software/ \\
+SSH into the machine and follow the instructions to add a user: \\
+sudo openwebrx admin adduser <USERNAME>
+You may want to install extra drivers, see note on home page: \\
+sudo install-softmbe.sh
+Some comments about antenna length:
+https://www.rtl-sdr.com/using-our-new-dipole-antenna-kit/
+==== 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...
@@ Line 1036: / Line 1087: @@
   # systemctl stop firewalld.service
   # iptables --flush
+Calculate sha256 of all files in folder and store in text file that can be used to check for bit rot later or when replacing disk and checking rsync:
+  $ find movies/ -type f -exec sha256sum {} \; >checksum.txt; sort -k2 -o checksum.txt checksum.txt
+  or
+  $ find movies/ -type f | sort | xargs -d'\n' sha256sum >checksum.txt
+File checksum mismatch after copying files to a new disk can be due to memory issues. It can even vary checksumming the same file on the same disk. You can use "memtester" live in linux or reboot into memtest in the grub menu. In my case one of the two pairs/kits were faulty I eventually found out after removing/swapping pairs.
 ==== Picade =====
@@ Line 1192: / Line 1248: @@
 Seems ok. Had to do this later for "events" as well. Do not forget to remove the recovery setting and restart mariadb so that home assistant can connect. Moved away from remote mariadb hass database to the default sqlite implementation with a database on an ssd. Set up a nightly backup through an automation to to avoid all these issues. Seems quicker as well.
-==== Upgrade Fedora ... -> 35 -> 36 -> 37 -> 38 -> 39 ====
+==== Upgrade Fedora ... -> 35 -> 36 -> 37 -> 38 -> 39 -> 40 -> 41 ====
 Following the instructions on https://fedoramagazine.org/upgrading-fedora-31-to-fedora-32/ and https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
@@ Line 1204: / Line 1260: @@
   # dnf remove gnomebaker php-recode --noautoremove # For fedora 32
   # dnf remove compat-ffmpeg28 # For fedora 39
-  # dnf system-upgrade download --releasever=39 # Did not work on Saturdays due to 404 for lacking rpmfusion files, waiting for mirroring and retrying on Sunday worked.
+  # dnf remove python3-iso-639 # For fedora 40
+  # dnf remove python2-pillow # For fedora 41
+  # dnf system-upgrade download --releasever=41 # Did not work on Saturdays due to 404 for lacking rpmfusion files, waiting for mirroring and retrying on Sunday worked.
 You may need the "--allowerasing" flag or possibly force uninstall of some packages using "rpm -e --nodeps <package>" to get this to pass.
@@ Line 1217: / Line 1275: @@
   - Had to upgrade to squeezeboxserver 7.9.3 and build tbs with workarounds for kernel 5.7. Later I replaced tbs with a hauppauge dongle.
   - New samba 4.11 disables smbv1 by default which does not work with my tablet used as a photo frame. See samba section above for how to fix.
-  - Autologin had to be reconfigured in /etc/lxdm/lxdm.conf for fedora 37.
+  - Autologin had to be reconfigured in /etc/lxdm/lxdm.conf for fedora 37 AND fedora 40. Just add back the autologin line, see the .rpmsave file.
   - Maybe clean up old unmaintained packages using "remove-retired-packages 36" or similar. You may also use "dnf repoquery --unsatisfied" and "dnf repoquery --duplicates" to check for broken/duplicates. See fedora upgrade docs for more info.