The AM2+ platform is about a decade old now, so I'm not surprised if your hardware is indeed on its way out. You may want to research upgrading your system to AM4, even if AM5 has launched. AM4 is relatively cheap (especially against AM5 and current gen Intel stuff) and I'd recommend a B450 mainboard, a 3000 series GPU and 2x 16GB DDR4 RAM, while reusing the GPU, case and PSU. Alternatively, obtain a R5 4600G APU and leave the GPU out, it has better video output anyway. Your existing SATA drives will still work, but the average AM4 mainboard only has 4 SATA ports, so it's wise to invest in a 1TB NVMe drive (those are now below 100USD as well as <100€) for the OS. In fact, I just purchased a 2TB NVMe drive (Chinese, of course) for just over 110€. More the adequate space for your regular desktop and you can use any HDD's from your current system for backups.

As for the logs: they repeat the same stuff several times. But you didn't include the lshw output. And store these files as text (.txt), the .log is pretty much useless (they're text files anyway, so why not designate them as such)

HTH!

Now we're getting somewhere! The last code block gave an error:

Helpful?

Not used Timeshift, so can't advise you on that, but the partitioning looks OK to me.

EFI mandates an M$ file system (FAT). They made sure (read as: paid sh#tloads of money) only FAT was specified in the EFI standard, so until the standard changes to allow non-M$ file systems, I refuse to use EFI.

But that's just me being old school I guess

Is there valuable data on that LVM partition that needs saving? If not, wipe the whole lot (i.e. delete all partitions on sda).

Partition sda as follows:

• sda1: 512MB for /boot

• sda2: 48GB for /

• sda3: 8GB for swap

• sda4: remainder for /home

Partitions sda1, sda2 and sda4 need a file system, choose one from the list: ext4, jfs or btrfs. You can mix different file systems, just ensure the appropriate tool package is installed (ie.e jfsutils, btrfs has a similar package). This allows the kernel to control and check the file system.

Modprobe is usually a symlink to kmod. See if that's the case on your system:

ls -l /sbin/modprobe

The output should look like this:

lrwxrwxrwx 1 root root 9 Jan  8  2021 /sbin/modprobe -> /bin/kmod

If it doesn't, see if kmod itself is there:

ls -l /bin/kmod

That should show this:

-rwxr-xr-x 1 root root 170168 Jan  8  2021 /bin/kmod

Note that the numbers&dates shown will differ from your system, that's not important. If you don't get the first output but do get the second one, create the required symlink so modprobe will work:

ln -s /bin/kmod /sbin/modprobe

Of course, all of the above commands as root!

However, I'm beginning to wonder if you're installing in a container, like Docker, Proxmox, Unraid or similar? If so, your network connections should be done in a whole different way.

From the aforementioned Ubuntu forum:

As root, obviously:

dmesg | grep e1000e
modprobe e1000e

What results does that yield?

Further down that thread there's a link to the Intel drivers site, try building it from scratch as per the instructions.

HTH!

Yeah, these fanatical Ukrainian SS-militia, worshiping Hitler and probably provoking a dirty war with your KGB-President Vladimir Putin are ruled by a puppet.

A
JEWISH
puppet

Yeah right... 

In case you're wondering, you're completely contradicting yourself by your statements. Never mind, I didn't expect anything less from Russian trolls.

I already do, hence my stance on Russia, in particular your spectacularly failing president and his criminal cronies, sorry (not really!) businessmen

Russia is rotten to the core and it will be a matter of time before it crumbles.

Again.

Like it did in the 1990's. Because the cause of the rot hasn't gone: greedy criminals are still in charge, the real puppet is Putin.

And that's my final word on it.

For starters, you need to install the build-essential package. It doesn't have any code itself, but its dependencies create a complete build-environment.

There's always the wayback archive

Investigate the use of the apt options --get-selections and --set-selections in the apt man page

man apt
apt --get-selections > selection.txt
apt --set-selections < selection.txt

Btw, do NOT use dd to backup your disk to an existing backup drive. Unless you don't care about the data that's already on it :-\