linux64
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
linux64 [2024/07/17 20:58] – [grub2 boot config] bengt | linux64 [2025/04/18 14:34] (current) – [efi partition too small] bengt | ||
---|---|---|---|
Line 128: | Line 128: | ||
# grub2-mkconfig -o / | # grub2-mkconfig -o / | ||
- | === 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, see end of chapter!) | Trying to fix full boot partition which failed to install new kernel rpm properly by: (Wrong solution, see end of chapter!) | ||
Line 142: | Line 142: | ||
Eventually I found https:// | Eventually I found https:// | ||
# mv "/ | # mv "/ | ||
+ | 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 - saved for future need === | + | ==== efi partition to fat32 ==== |
- | The following is when 256MB is not enough, from https:// | + | These instrutions were saved for possible future need if 256MB is not enough |
- | + | ||
- | There' | + | |
- | + | ||
- | Well, the next best thing to actually resizing the partition is to recreate it. Here are the detailed steps for doing this: | + | |
- | + | ||
- | If you are resizing the ESP of the disk you're booting on, ensure you have some bootable rescue media on hand that you can use to repair your system in case things go wrong. Having a backup of your data before doing any disk partitioning operations is a good idea in general. | + | |
- | + | ||
- | If you are enlarging the ESP, make room by moving or resizing any partitions directly following it, using your favorite partitioning tool (e.g. gparted). | + | |
Mount the ESP (if it's not mounted already, e.g. on /boot or /boot/efi): | Mount the ESP (if it's not mounted already, e.g. on /boot or /boot/efi): | ||
Line 665: | Line 658: | ||
If you want to be able to run with plugins you may want to look into https:// | If you want to be able to run with plugins you may want to look into https:// | ||
- | $ wget https:// | + | $ wget https:// |
$ cd minecraft/ | $ cd minecraft/ | ||
$ wget -O floodgate-spigot.jar https:// | $ wget -O floodgate-spigot.jar https:// | ||
Line 776: | Line 769: | ||
## NameCheap DynDNS | ## NameCheap DynDNS | ||
## | ## | ||
- | use=web, web=dynamicdns.park-your-domain.com/ | + | |
+ | use=web, web=http:// | ||
| | ||
protocol=namecheap | protocol=namecheap | ||
Line 1044: | 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 {} \; > | ||
+ | or | ||
+ | $ find movies/ -type f | sort | xargs -d' | ||
+ | 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 " | ||
==== Picade ===== | ==== Picade ===== | ||
Line 1200: | Line 1199: | ||
Seems ok. Had to do this later for " | Seems ok. Had to do this later for " | ||
- | ==== Upgrade Fedora ... -> 35 -> 36 -> 37 -> 38 -> 39 ==== | + | ==== Upgrade Fedora ... -> 35 -> 36 -> 37 -> 38 -> 39 -> 40 ==== |
Following the instructions on https:// | Following the instructions on https:// | ||
Line 1212: | 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. | + | |
+ | | ||
You may need the " | You may need the " | ||
Line 1220: | Line 1220: | ||
After upgrade: | After upgrade: | ||
+ | - For fedora 39 there is a bug when installing kernels fails with "No space left on device" | ||
- 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/ | - 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/ | ||
- 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 " | - 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 " | ||
- 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 / | + | - Autologin had to be reconfigured in / |
- Maybe clean up old unmaintained packages using " | - Maybe clean up old unmaintained packages using " | ||
+ | |||
linux64.1721249923.txt.gz · Last modified: 2024/07/17 20:58 by bengt