(Written March 13th at 2am.)

This morning (yesterday), my computer decided not to boot again: it halts on "cannot find firmware rtl-whatever" every time. (it has booted just fine several times since removing the firmware.) I've had quite the ordeal today trying to fix it, and every freaking step along the way has thrown errors and/or required workarounds and a lot of research.

Let's make a list of everything that went wrong!

1) Live CD: 2yo had been playing with it, and lost it. Not easy to find, and super smudgy.

2) Unencrypt volume: Dolphin reports errors when decrypting the volume. Research reveals the Live CD doesn't incude the cryptsetup packages. First attempts at installing them mysteriously fail.

3) Break for Lunch: automatic powersaving features turned off the displays, and also killed my session.

4) Live CD redux: 25min phonecall from work! yay, more things added to my six-month backlog.

5) Mount encrypted volume: Dolphin doesn't know how, and neither do I. Research ensues. Missing LVM2 package; lvmetad connection failure ad nauseam; had to look up commands to unlock, clone, open, and mount encrypted Luks volume, and how to perform these actions on Debian instead of Ubuntu/Kali. This group of steps took four hours.

6) Chroot into mounted volume group: No DNS! Research reveals how to share the host's resolv with the chroot.

7) `# apt install firmware-realtek`: /boot/initrd.img does not exist. Cannot update.

8) Find and mount /boot, then reinstall firmware: Apt cannot write to its log (minor), listed three install warnings, and initially refused to write to /boot/initrd.img-[...]

9) Reboot!: Volume group not found. Cannot process volume group. Dropping to a shell! oh no..

(Not listed: much research, many repeated attempts with various changes.)

At this point it's been 9 hours. I'm exhausted and frustrated and running out of ideas, so I ask @perfectasshole for help.
He walks me through some debugging steps (most of which i've already done), and we both get frustrated because everything looks correct but isn't working.

10) Thirteenth coming of the Live CD: `update-initramfs -u` within chroot throws warnings about /etc/crypttab and fsck, but everything looks fine with both. Still won't boot. Editing grub config manually to use the new volume group name likewise produces no boots. Nothing is making sense.

11) Rename volume group: doubles -'s for whatever reason; Rebooting gives the same dreaded "dropping to a shell" result.

A huge thank-you to @perfectasshole for spending three hours fighting with this issue with me! I finally fixed it about half an hour after he went to bed.

After renaming the volume group to what it was originally, one of the three recovery modes managed to actually boot and load the volume. From there I was able to run `update-initramfs -u` from the system proper (which completed without issue) and was able to boot normally thereafter.

I've run updates and rebooted twice now.
After twelve+ hours... yay, I have my Debian back!

oof.

Linux:
The operating sistem that wants you to be a pro right from start.
But stuck because grub doesn't install.
Following tutorials on the cellphone but still stuck. At boot I'll get stuck in initramfs...
I really want mint... But I'm not gonna reinstall windows just to get other distro.
Why da FUCK?
Even formated C to ext4 to help

Lovely... About a week ago I moved my manjaro installation from bios to UEFI.
I ran a system update last night... and, well, my boot broke, cause mkinitcpio failed to build my initramfs. I was up till twelve cause now my system wouldn't mount a fat32 partition, so till I had my esp mounted and finaly fixed, it was 12. (And I wanted to go to sleep early that night)

Okay, so just now I literally had to force-reboot a laptop because I could not exit vim.

damn.. It really IS a trap.

A friend of mine who wants to learn about Linux has a stronger will than me, as I think installing Linux in 2020 is gonna break me but he's still stoked as shit. I'm fucking serious. He asked me to install several distros, in order of interest (because they all fucking failed, because of fucking course they did) on a USB HDD he was using just for this.

We tried, in order:

Arch: initramfs wiped his Windows HDD when it crashed. IDFK how, but it zeroed the top 32KB of the drive. It wasn't even the right HDD...

Linux Mint: nvidia drivers refused to see his GPU after install. No matter what we did. Live media saw it fine until it was installed on the external drive, too.

Debian: Installer couldn't see the external HDD, ever. No matter what we did. It had a /dev entry, lsblk and fdisk saw it, I could format and mount it, but the installer crashed when it refreshed the device list when it was present. Every goddamn time.

Fedora: Installer broke halfway through as an executable (or 70) were corrupted, but the disc matched the ISO and the ISO sums correctly, so this is apparently how it was packed and shipped.

CentOS: Refused to boot. Just entirely. GRUB would go to load the kernel and it'd hang.

All ISOs and discs were verified as matching provided sums using MD5 and SHA256. How the fuck is Linux so fucking hard to get working on older hardware in 2020? Worked great in 2008, worked great in 2018, why is 2020 such a goddamn issue?

For fucks sake!
Why does every god damn distro have their own tool to generate initramfs?!
I just spend over an hour to find out that Void-Linux uses dracut and to find documentation, on how to use luks with a dracut-generated initramfs.
Seriously,Arch has mkinitcpio,
Fedora has dracut,
Gentoo has genkernel and I suppose the other big distros also have their own tools.
Why can't we standardize that shit on one of them?

Opened my beloved laptop after a week of sickness.

ACPI error...

Spent the evening taking a backup from initramfs. Then installing Ubuntu 17.10

Now, I love me some penguin but that shit gets too crazy too often.

Not that I didn't enjoy spending the day setting up the system, there is some stability I always miss from a Win/Mac environment

Recent VM/Emulation Adventures:

The goal was to get TCP/IP and SSH running on whatever weird VM/emulated machine, and connect to the chatroom at chat.tcp.direct successfully.

Longhorn, somewhere late pre-reset: Crashes right after installer begins "Starting Windows", 0x7b from sum-match ISO. Fail.

TempleOS (well, Shrine, but y'know): Dear god. No. No, I am not writing SSH in HolyC myself *fuck that,* fail.

Slackware: oh ffs i gotta use fdisk to partition this damn thing? and it's not even the good fdisk? Oh, wait... it hangs. Fail.

WinME: shockingly, was *fairly* stable... until it hung up WASAPI and the hypervisor two frames into desktop rendering. Fail.

Mac OS 7: First-boot after install, immediate unknown trap. Just works, eh? Fail.

Amiga: After about 85 resets and 7 hours of constant fighting with WinUAE, I finally got TCP/IP working. (Required 10MB of total RAM and an FPU to connect.) Success!

Win98FE: just... PuTTY and done. Easy. (This was the warmup.) Success...

Other people's achievements so far:

- Minecraft using the new QEMU interface mod thing.
- Hacked smart fridge.
- iPhone, from custom initramfs.

I think I finally reached a point where I Have to completely reinstall my RPi.

Running Raspbian, I was under the impression their kernel releases worked the same way a pure Debian release worked - That the kernel was somewhere in the system repository.

Turns out it was, but in a different pool. And also turns out the new kernel and initramfs won't fit into my /boot as, for some reason, it is under 50 MBs in size. I dunno why, but I don't have any unallocated space left to grow the partition...

I have no idea why the boot is so small (Probably because, when I was setting the system up, I wasn't really that good with Linux yet, and just went with defaults).

What do you guys think - Is it better to run the native Raspbian system (Formerly RaspberryPi OS), or go with a pureblood Debian for Arm? (Yes, I already checked, my HW revision [3B+] is already compatible])