User Tools

Site Tools


linux64

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
linux64 [2024/07/17 20:55] – [grub2 boot config] bengtlinux64 [2025/04/18 14:34] (current) – [efi partition too small] bengt
Line 128: Line 128:
   # grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg # Update kernel boot list   # grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg # Update kernel boot list
    
-=== efi partition too small ===+==== efi partition too small ====
  
-Trying to fix full boot partition which failed to install new kernel rpm properly by: (Wrong solution!)+Trying to fix full boot partition which failed to install new kernel rpm properly by: (Wrong solution, see end of chapter!)
   - Creating bootable fedora live usb and booting from it.   - Creating bootable fedora live usb and booting from it.
   - You MUST disable automatic suspension in "Settings --> Power --> Automatic Suspend". Hangs on resume which you don't want for disk operations. See https://forums.fedoraforum.org/showthread.php?330586-Fedora-38-change-Systems-with-Gnome-suspend-after-15-minutes-even-when-plugged-in   - You MUST disable automatic suspension in "Settings --> Power --> Automatic Suspend". Hangs on resume which you don't want for disk operations. See https://forums.fedoraforum.org/showthread.php?330586-Fedora-38-change-Systems-with-Gnome-suspend-after-15-minutes-even-when-plugged-in
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: 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"   # 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 ====
 +
 +These instrutions were saved for possible future need if 256MB is not enough for /boot/efi, from https://superuser.com/questions/1230741/how-to-resize-the-efi-system-partition
 +
 +Mount the ESP (if it's not mounted already, e.g. on /boot or /boot/efi):
 +  # mount /dev/sdx1 /mnt # replace sdx1 with ESP
 +Make a backup of its contents:
 +  # mkdir ~/esp
 +  # rsync -av /mnt/ ~/esp/
 +
 +Unmount the ESP:
 +  # umount /mnt
 +
 +Delete and recreate the ESP:
 +  # gdisk /dev/sdx # replace sdx with disk containing ESP
 +  p (list partitions)
 +  (ensure the ESP is the first partition)
 +  d (delete partition)
 +  1 (select first partition)
 +  n (create partition)
 +  Enter (use default partition number, should be 1)
 +  Enter (use default first sector, should be 2048)
 +  Enter (use default last sector, should be all available space)
 +  EF00 (hex code for EFI system partition)
 +  w (write changes to disk and exit)
 +
 +Format the ESP:
 +  # partprobe /dev/sdx
 +  # mkfs.fat -F32 /dev/sdx1
 +
 +Restore the ESP's contents:
 +  # mount /dev/sdx1 /mnt
 +  # rsync -av ~/esp/ /mnt
 +
 +Update EFI entry in /etc/fstab
 +  # blkid | grep EFI
 +  # nano /etc/fstab
 +  UUID=XXXX-XXXX /boot vfat umask=0077 0 2 # Replace with UUID from blkid
 +If you use GRUB, you may need to update or regenerate its configuration file (/boot/grub/grub.cfg), e.g. by running update-grub.
  
 ==== nvidia  [old] ==== ==== nvidia  [old] ====
Line 617: Line 658:
  
 If you want to be able to run with plugins you may want to look into https://papermc.io/software/paper and https://hangar.papermc.io/ fo the actual plugins. For example if you want to be able to use bedrock clients you can use GeyserMC https://hangar.papermc.io/GeyserMC with floodgate. https://www.youtube.com/watch?v=nJWIo9LgQzA If you want to be able to run with plugins you may want to look into https://papermc.io/software/paper and https://hangar.papermc.io/ fo the actual plugins. For example if you want to be able to use bedrock clients you can use GeyserMC https://hangar.papermc.io/GeyserMC with floodgate. https://www.youtube.com/watch?v=nJWIo9LgQzA
-  $ wget https://api.papermc.io/v2/projects/paper/versions/1.20.1/builds/196/downloads/paper-1.20.1-196.jar+  $ wget https://api.papermc.io/v2/projects/paper/versions/1.21.1/builds/120/downloads/paper-1.21.1-120.jar
   $ cd minecraft/plugins   $ cd minecraft/plugins
   $ wget -O floodgate-spigot.jar https://download.geysermc.org/v2/projects/floodgate/versions/latest/builds/latest/downloads/spigot   $ wget -O floodgate-spigot.jar https://download.geysermc.org/v2/projects/floodgate/versions/latest/builds/latest/downloads/spigot
Line 728: Line 769:
   ## NameCheap DynDNS   ## 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   protocol=namecheap
Line 996: Line 1038:
   # systemctl stop firewalld.service   # systemctl stop firewalld.service
   # iptables --flush   # 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 ===== ==== Picade =====
  
Line 1152: Line 1199:
 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. 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 ====
  
 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/ 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 1164: Line 1211:
   # dnf remove gnomebaker php-recode --noautoremove # For fedora 32   # dnf remove gnomebaker php-recode --noautoremove # For fedora 32
   # dnf remove compat-ffmpeg28 # For fedora 39   # 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 system-upgrade download --releasever=40 # 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. You may need the "--allowerasing" flag or possibly force uninstall of some packages using "rpm -e --nodeps <package>" to get this to pass.
  
Line 1172: Line 1220:
  
 After upgrade: After upgrade:
 +  - For fedora 39 there is a bug when installing kernels fails with "No space left on device" if you have upgraded since really old fedora versions. There is a file/folder in /boot that triggers this issue. See end of "efi partition too small" chapter.
   - It hangs during first boot waiting for lvm2 mirrors. I had to disable Intel RST and use AHCI in BIOS to get it to boot. Then I disabled/masked the lvm2 service using "systemctl mask lvm2-monitor.service" and switched back to RST in the next boot.   - It hangs during first boot waiting for lvm2 mirrors. I had to disable Intel RST and use AHCI in BIOS to get it to boot. Then I disabled/masked the lvm2 service using "systemctl mask lvm2-monitor.service" and switched back to RST in the next boot.
   - Old, not be needed anymore: It is running cgroups v2 which was incompatible with docker. Either switch to v1 using kernel command line options or use podman instead of docker. Add "systemd.unified_cgroup_hierarchy=0" to GRUB_CMDLINE_LINUX in /etc/default/grub and run "grub2-mkconfig" to start using v1 again. You will probably want to upgrade to podman later though and start using new cgroups.   - Old, not be needed anymore: It is running cgroups v2 which was incompatible with docker. Either switch to v1 using kernel command line options or use podman instead of docker. Add "systemd.unified_cgroup_hierarchy=0" to GRUB_CMDLINE_LINUX in /etc/default/grub and run "grub2-mkconfig" to start using v1 again. You will probably want to upgrade to podman later though and start using new cgroups.
   - 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.    - 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.   - 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.   - 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.
 +
  
linux64.1721249749.txt.gz · Last modified: 2024/07/17 20:55 by bengt

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki