NaibofTabr

Yeah but the current build of libvegs has some conflicts with libfruit, so if you need to use both you have to build libvegs in a different directory and then simlink it in /lib.

A long wire is an antenna that will gather electromagnetic noise from the air and turn it into random signal on the line. Shorter wires will be less responsive and therefore less noisy, and you can also mitigate the problem by grounding everything properly. It’s also possible that with the wires in that parallel ribbon, they may induce crosstalk on each other. If you want to be really careful, you could replace that big ribbon cable with an STP cable and ground the shielding jacket.

Also, a noisy/low quality power input to the Pi will produce noise in its circuits and ultimately the output. If you can, supply the power from something better than a wall wart.

Someone else has mentioned M-Disc and I want to second that. The benefit of using a storage format like this is that the actual storage media is designed to last a long time, and it is separate from the drive mechanism. This is a very important feature - the data is safe from mechanical or electrical failure because the storage is independent of the drive. If your drive dies, you can replace it with no risk to the data. Every serious form of archival data storage is the same - the storage media is separate from the reading device.

An M-Disc drive is required to write data, but any DVD or BD drive can read the data. It should be possible to acquire a replacement DVD drive to recover the data from secondary markets (eBay) for a very long time if necessary, even after they’re no longer manufactured.

PenDriveLinux or rufus or balena etcher (frequently just referred to as “etcher”) or just dd.

Maybe it’s time to start funding software infrastructure the way we fund physical infrastructure - with tax dollars.

Alternatively, Material Files (available in F-Droid) can easily create a local FTP server or connect to a NAS. It’s also a pretty good file manager app.

Yup, and it might be necessary to reproduce a lot of the answers that people used to find on reddit.

Huh… and that’s repeatable? How long could you go on Linux before the blackouts, and did you run on Windows for a similar amount of time with no issues? also, when the blackout happens does it recover after a little time, or do you have to reboot to get video back? (is it just a screen blackout, or has the system crashed?) When the screen is black, can you reboot with busier backwards?

One issue that I’ve had on Linux installs is that the system doesn’t recover properly from hibernate. I’ve seen this on laptops and desktops over more than a decade. When this happens the screen goes black and the system doesn’t respond to any keyboard or mouse input, the only way to recover is to force a reboot. Maybe check your power management profile and disable hibernation.

Otherwise there are a lot of reasons that the screen might black out:

• power issues - what is your PSU model? Linux installs are frequently not as power efficient as Windows on the same hardware, generally because Windows does a lot more throttling by default.
• overheating - Windows (and the Windows hardware drivers) might be configured to throttle the CPU and/or GPU to manage the temperature automatically without telling you, while Linux might be giving you the full unthrottled system power and overheating.
• video drivers & multimonitor - as others have said already, this could be an issue with the Linux video drivers. You should verify which driver you’re using as EccTM@lemmy.ml said. Are all your monitors the same resolution? I’ve definitely had trouble with mulitple monitors if they were mismatched.
• bad CPU core - this one’s a long shot, but Windows tends to be a lot more single-threaded while Linux is more likely to try to balance operations across all CPU cores. Maybe one of your cores has an issue, and when Linux tries to use it it triggers a system crash, while Windows just never gets around to using that particular core for anything critical (and so never triggers the crash).
• SSD/swap file issue - most Linux distros will configure a swap partition on the root hard drive by default, which is used as an extension of the RAM. Windows doesn’t use a swap file. You have plenty of RAM so there’s not really a need for it, so you should try just disabling swap.

But whether a few hours or a few days, eventually I start having issues with the displays. Monitors will black out. Not boot. Eventually the whole system just stops working in a way that I can figure out.

This sounds more like a hardware issue than software. Can you provide more detail? Have you done basic troubleshooting steps like trying different power cords and surge protector/power strip? What is the full list of hardware for your system? Have you reseated the RAM? Replaced the CMOS battery? (a dead CMOS battery will prevent system boot)

I think it’s worse when they say they found a solution and include a link which is now dead.

With Google dropping its archive I feel like dead links are going to be more and more common.

Technically the US measurement system is metric since the Mendenhall Order of 1893 reestablished all customary units as conversion factors of metric units. In 1933 the ASA redefined the inch to be exactly 25.4mm, following the lead of the British Standards Institution in 1930 (precision was increasingly important for manufacturing, and the previous value of 25.40005mm had become impractical). The international yard and pound were officially adopted by the US National Bereau of Standards (now NIST) in 1959, the Metric Conversion Act was passed in 1975, and finally EO 12770 (1991) required all agencies of the executive branch to transition to metric units.

So, from one point of view we’ve been transitioning to metric since 1893 and it’s still not done. From another, the inch is just a metric unit as its length is officially defined in millimeters (all customary units are now based on SI units), therefore the conversion is complete.