If your problem is that the system runs slowly then start by trying to fix that *without* disabling FDE.

A few questions to start with:
What sort of system is it? (Desktop or Laptop, make model, etc?)
What CPU has it got?
How much memory has it?
What is it's display? (Could you add a GPU if it hasn't got one?)
What is running on it? (OS, desktop env, etc?)
Is it using swap space very often? (If yes then adding memory might speed it up a lot.)

Try running top and vmstat to see if they say anything interesting.

Hopefully answering that lot will point you towards a fix.

I assume both screens will be powered on before the boot. But how are they connected (are there two motherboard sockets or is one on a GPU)? And what sort of PC is it?

There *should* be a BIOS option to say which screen to use. But that probably only applies to the BIOS output.

You could try booting the system with one screen powered off and see what happens. Then try the other. (It probably won't help but costs nothing to experiment.)

The first thing I'd try is to repeat round 1, cp sums.txt sums_1.txt, repeat round 2 and diff sums_1.txt sums.txt to see if they differ.

Don't blindly assume everyone on the left is virtuous. That would place you in grave danger if you encounter a psychopathic murderer who claims to be on the left to give people a false sense of security. And a con artist doing the same thing could give you a painful lesson.

In any case trying to fit all political views onto one dimension is far to simplistic. The extreme left and extreme right are almost identical in what they actually do, the centre are much further from them than they are from each other. Remember that Nazi is short for National Socialist.

Having a quick look from outside:
$ host www.realupnow.com
www.realupnow.com has address 66.172.90.106

$ ping www.realupnow.com
PING www.realupnow.com (66.172.90.106) 56(84) bytes of data.
64 bytes from 66.172.90.106: icmp_seq=1 ttl=47 time=110 ms
64 bytes from 66.172.90.106: icmp_seq=2 ttl=47 time=109 ms

$ sudo traceroute -T www.realupnow.com
traceroute to www.realupnow.com (66.172.90.106), 30 hops max, 60 byte packets
<snip>
13  168.182.127.17 (168.182.127.17)  114.734 ms  118.489 ms  116.881 ms
14  168.182.127.1 (168.182.127.1)  110.179 ms  110.515 ms  113.517 ms
15  168.182.127.98 (168.182.127.98)  118.143 ms  116.080 ms  117.728 ms
16  66.172.90.106 (66.172.90.106)  115.229 ms  109.814 ms  111.151 ms
17  66.172.90.106 (66.172.90.106)  3117.564 ms !H  3111.648 ms !H  3109.469 ms !H

But I can't tell what 66.172.90.106 is. Could that be your router's external IP address? Or the server's external IP address?

NB. traceroute -T uses a SYN packet as it's probe, to port 80 by default.

Searching for recently changed files in /etc and your home directory might tell you what did it. It's more likely to be in /etc but might be in some subdirectory. Try the find command (read it's man page first if it's new to you).

That makes me suspect you switched to root with su so didn't get your PATH updated. Try su - and see if modprobe works then.

If it still doesn't post output from:
echo $PATH
whereis modprobe

Can you set ublock to *pretend* to allow ads, but not actually show them on your screen? It's an option I would like to have if I need to use a site that blocks access to people who are using ad blockers. The idea is that ads get downloaded but not shown, so the advertisers can't tell they are paying for nothing.

On one system I resorted to ctrl-alt-F3 and logging on as root, ready to restart the desktop if it hung (I think the system has hardware problems that cause the desktop to lock up intermittently). So if the desktop suddenly hangs I just press ctrl-alt-F3 and restart it, even if it's ignoring the keyboard. And if that fails I can reboot the system as a last resort.

man su would also be worth reading. The man pages are always worth checking if you are having probelms with a command.

And try comparing output from echo $PATH after su and su - (also output from env and set, preferably piped into less).

Try the following (WARNING - untested code- WARNING):

#!/bin/bash
FLAG=0
until [[ $FLAG = "1" ]]
do
DIR=$(date +%N)
mkdir $DIR
if  (($?>0)) ;then exit;fi
cd $DIR
if  (($?>0)) ;then exit;fi
starfish -d duration
# Tidy up anything if you want here
cd ..
if  (($?>0)) ;then exit;fi
rmdir $DIR # Optional
if  (($?>0)) ;then exit;fi
done

date +%N returns the current time in nanoseconds, so will very rarely repeat.

But I don't have starfish, so I can't test this. Use at your own risk.

That's probably why some of my systems got an error. I temporarily powered up a recently updated system (it's shut down to save power now) and it worked OK:

wget 'https://www.devuan.org/get-devuan'
--2022-11-06 12:07:55--  https://www.devuan.org/get-devuan
Resolving www.devuan.org (www.devuan.org)... 54.36.142.179, 2001:41d0:8:732b::3624:8eb3
Connecting to www.devuan.org (www.devuan.org)|54.36.142.179|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 25326 (25K) [text/html]
Saving to: ‘get-devuan’

get-devuan                              100%[============================================================================>]  24.73K  --.-KB/s    in 0.006s  

2022-11-06 12:07:56 (4.17 MB/s) - ‘get-devuan’ saved [25326/25326]

So the www.devuan.org certificate is probably OK.

I just hope being back-level doesn't start causing real problems on this system since I can't upgrade it without probably losing support for the rather old GPU.