klangcola @ klangcola @reddthat.com

Posts

1

Comments

159

Joined

2 yr. ago

There is one potential (small) hurdle you should be aware off: Secure Boot.

Basically some laptops came with Secure Boot locked to only allow booting Windows. These days Linux distros should still be able to boot even if the laptop was windows-only back then (thanks to the so-called shim bootloader). If you get an error about secure boot, just go in to BIOS/UEFI menu and disable secure boot for now (after installing Linux you can google the steps to enroll a key to re-enable Secure Boot).

Beyond that, just flash a USB stick with Linux Mint, boot the laptop, smash the keyboard to find the button for BIOS menu or Boot Device selection, then follow the installer. Installing Linux should take less than an hour. Way less if your computer is fast.

Haven't tried it myself, but have heard in passing that they are generally not waterproof. Might be different for different materials or print orientations though?

Or you can do some post processing, add a coating, or vapor smooth?

Nice, my HM90s have a really great cooling solution for the CPU (big silent fan, fine finned heat sink). But no cooling on the bottom side of the main board, which houses the RAM, a NVMe and two 2,5" SATA SSDs.

As usual, the arch wiki is super helpful also for non-arch distros https://wiki.archlinux.org/title/Lm_sensors#Adding_DIMM_temperature_sensors

Regarding mini PCs; Beware of RAM overheating!

I bought some Minisforum HM90 for Proxmox selfhosting, installed 64gb RAM (2x32gb DDR4 3200MHz sticks), ran memtest first to ensure the RAM was good, and all 3 mini PCs failed to various degrees.

The "best" would run for a couple of days and tens of passes before throwing multiple errors (tens of errors) then run for another few days without errors.

Turns out the RAM overheated. 85-95 C surface temperature. (There's almost no space or openings for air circulation on that side of the PC). Taking the lid off the PC, let 2/3 computers run memtest for a week with no errors, but one still gave the occasional error bursts. RAM surface temperature with the lid off was still 80-85 C.

Adding a small fan creating a small draft dropped the temperature to 55-60 C. I then left the computer running memtest for a few weeks while I was away, then another few weeks while busy with other stuff. It has now been 6 weeks of continuous memtest, so I'm fairly confident in the integrity of the RAM, as long as they're cold.

Turns out also some, but not all, RAM sticks have onboard temperature sensors. lm-sensors can read the RAM temperature, if the sticks have the sensor. So I'm making a Arduino solution to monitor the temperature with a IR sensor and also control an extra fan.

Game changing! I've never heard of Hoarder before, but will look in to it now.

LinkDing also has a REST API but I don't see the option to send attachment files

+1 for SingleFile

I recently tried LinkWarden, Linkding and Archivebox for making offline copies. They all had the same issue of running in to a Captcha or login wall for the sites I wanted to capture.
SingleFile to the rescue, as it uses your current browser session as a logged in and verified human.

Linkeding allows you to upload the singlefile html file attached to it link, but I didn't see such an option for Linkwarden.

I hadn't considered giant data sets, like Jellyfin movie library, or Immich photo library. Though for Jellyfin I'd consider only the database and config as "Jellyfin data", while the movie library is its own entity, shared to Jellyfin

How does this work? Where is additional space used for cache, server or client?

Or are you saying everything is on one host at the moment, and you use NFS from the host to the docker container (on the same host)?

This has been my thinking too.

Though after reading mbirth's comment I realised it's possible to use named volumes and explicitly tell it where on disk to store the volume:

 yaml

    
    volumes:
      - my-named-volume:/data/
volumes:
  my-named-volume:
    driver: local
    driver_opts:
      type: none
      device: "./folder-next-to-compose-yml"
      # device: "/path/to/well/known/folder"
      o: bind


  

It's a bit verbose, but at least I know which folder and partition holds the data, while keeping the benefits of named volumes.

Yeah that's fair, permission issues can be a pain to deal with. Guess I've been lucky I haven't had any significant issues with permissions and docker-containers specifically yet.

Wow thanks for this! Reading the official docker documentation I somehow missed this. Using regular well documented linux mount.

<type>

And knowing the docker container won't start unless the mount is available solves so much.
Does the container stop or freeze if the mount becomes unavailable? For example if the smb share host goes offline?

That makes sense. I've only ever used local storage on the docker-VM, but for sure it can make sense for using external storage

KDE Connect also works on Gnome, Windows and Android. I can't recommend it enough. Transfering a single image from phone to PC is instantaneous

GUIs can be very good for getting started and learning concepts though. Much more "discoverable" and can allow for quicker iteration.

Then when learning the "proper" command line tools, the process should be easier as one already knows the concepts and terminology, and can concentrate on just the tooling.

Was it "groupadd" or "addgroup"...? I can never remember xD

Which brand is this? So I never have to go near it...

I have a Samsung TV from a few years ago, never connected it to the TV, so when I turn it on it just goes to the last used input (HDMI1 in my case). The bootup isn't even that slow , maybe 5 seconds or so. Not great, but not terrible..

Agreed, but only if wages and especialy minimum wage was inflation adjusted

.... Surreal numbers?!?

The apps are Flatpak'ed, so they update independently of the system.

But yeah why did Flatpak update them when Flatpak has unsatisfied dependencies? (To be fair the apps still work, it's mostly a ergonomic and cosmetic regression)

PSA about mini PCs: They might not come with adequate cooling for RAM, leading to potential data corruption.

(I'm in the middle of troubleshooting/fixing overheating RAM causing memory errors, will post on /c/selfhosted when I have more conclusions).

TLDR: Bought 3 Minisforum HM90 mini PCs (for Proxmox), equipped them with 64gb (2x32gb) RAM, with a different brand RAM in each PC. All 3 give sporadic errors in Memtest86. The RAM overheats due to the 2 SSDs mounted in the lid blocking natural airflow. With the lid off, or an extra fan installed, there are no errors. The errors were very sporadic: 1 PC gave errors after 1-2 passes, then almost 24hours. Second PC gave errors after more than 24 hours and some cases more than 48 hours between errors. The last PC gave hundreds of errors on the first pas. To be fair, memtest is a synthetic test and the RAM is unlikely to see 100% utilisation in real life, on the other hand the two adjacent SATA SSDs and the NVMe SSD are completely idle during memtest, and will generate extra heat during production use.