Thad wrote:Thad wrote:Then there's the question of whether I should do a fresh OS install or just stick with the one I've got. AIUI it's not that difficult to hook up the same boot drive to a new computer and have it work; since I'm going from Intel to AMD it's probably going to require booting to USB and reinstalling the bootloader, but it sounds like a pretty straightforward process.
I think I'll probably do that. While it might be useful to start fresh and without all the cruft I've accumulated over the years, I've spent a hell of a lot of time setting this thing up and I do not find the thought of having to do all that over again appealing.
It mostly worked fine but somehow now every time I do a kernel update I have to boot from a USB dongle and reinstall initramfs and GRUB.
I'm baffled as to why. It's three commands; if I execute them from my system before a reboot, I end up in a non-bootable state (trying to load the EFI partition before loading the module to read a vfat filesystem), whereas if I boot to a memory stick, mount the appropriate partitions, chroot, and then run the same three commands, everything works fine on my next reboot.
I've got it down to a workaround that takes under 10 minutes, so on the whole it's still less fucking around than if I'd done a clean install, but it's still frustrating and I'm sure there has to be a better way which I haven't quite cracked yet.
I figured out what went wrong here: when I reinstalled the bootloader after swapping out the motherboard, I didn't have my boot partition mounted, so it created a /boot directory on my root partition. So I ended up with a bootloader that expected the boot files to be on partition 3, and every time I updated my boot files they went on partition 2, and then the bootloader couldn't find the files it was supposed to be using to boot. Fortunately it was an easy enough problem to fix once I figured it out, and now I can reboot after an update with no issue.