Following the Arch wiki, I built a custom kernel for the first time ever. It was easier that I thought it’d be, probably because the Arch wiki is so thorough and because I didn’t make that many changes… I just enabled a few FireWire related options as per this guide in order to work on this project (or this).

Results/takeaways

  • The OS ran fine with the new kernel 💃
  • I learned how to manually create GRUB entries 🔧
  • I learned that I don’t even have to create new GRUB entries, since I can simply point to the new kernel image and initramfs from the bootloader menu 🪛
  • I learned that my 5800X3D runs well (compiles the new kernel blazingly fast) with all cores set to negative 30 in the UEFI
  • FireWire is dead 💀

Tiny followup on that project
That old GPU did something to the UEFI (possibly CMOS?), because even after removing all potentially incompatible hardware and reinstalling my modern GPU, I still got that same error message, saying that the system was forces to boot in CSM mode. Only by resetting the UEFI settings was I able to restore the system to a working state. I admit, I panicked.

  • eldavi@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    13 hours ago

    gentoo taught me how to recompile and it feels like arch takes that thunder sometimes. lol

    • Creat@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      12 hours ago

      In times of pre-optimized repos (like CachyOS) it seems rather redundant from a performance perspective. Other reasons remain valid though (learning or specialized optimizations or requirements).

      Alternatively, it can also be considered wasteful (electricity/compute) when everyone compiles their whole system instead of doing it once in a central server.