I mean speaking from experience, its resurrected a couple problematic CPUs for me. CPU pins no, pads on an LGA style CPU, sure.
I mean speaking from experience, its resurrected a couple problematic CPUs for me. CPU pins no, pads on an LGA style CPU, sure.
I’m with catloaf. Consistent CPU soft locks point to a possible bad memory module or CPU.
Clear CMOS.
Try removing one memory module at a time.
See if there is an option to disable hyperthreading in bios.
Another thing to try is to remove the CPU, careful not to damage the LGA pins on the motherboard, and clean the CPU contacts with alcohol. Take care to ground yourself out and the case before handling the CPU out of socket.
See my other comment on this thread. Basically I have a shared mount point for the two containers and TubeSync writes video metadata to NFO files.
TubeSync has an option to write metadata to NFO files. Then you just tell Jellyfin to not run any scrapper and just use said NFO files. It’s not perfect but it gets you a title and description for the video.
I use TubeSync to do the downloading and then have Jellyfin as a frontend player. Seems to work pretty good for me and was pretty quick to stand up in docker.
I’ve been using fedora on a small intel 6th gen or newer mini pc. I then cook up some custom launch scripts that cause JMP to run at login. I use cockpit and a CMK agent for remote monitoring and management.
I got sick of the lack certificate management on Android TV and how much you need to do to make it reasonably private.
If you are on the latest mesa drivers (hence fedora over a more LTS release), and you install Jellfin Media Player via flatpak, everything should just work with hardware decoding.
You can self-host the kiwix server in docker and grab .zim files for whatever wiki you want to host. Wikipedia is one of those files.
I can also vouch that Android Auto works in a work profile.
I would cd into the user folder that you want to add / remove files from and see what the ownership is to begin with and simply replicate ownership to match what’s already there.
Generally, in my experience, modifying the backing storage for a nextcloud instance is more of a PITA than its worth. I would just mount the webDAV in your file manager. This way the nextcloud db stays in sync with the backing storage.
If you are going to be making direct modifications to the backing storage, check this form post on modifying the nextcloud config to have it look for changes on the filesystem.
As for the permission side of things, run ls -lh in the folder that you want to make changes and see what the user:group is for ownership of the existing files and make sure your new files match. Chmod and chown will be your friends here and chmod has a --reference option that let’s you mirror permissions from an existing file, a real time saver.
Hopefully this helps!
BTW you CAN do DNS in a unifi gateway. It just requires making dnsmasq entries through shell. Perfect solution? No. But it gets you there with no additional hardware.