Conversation

Notices

1. Bernie (codewiz@mstdn.io)'s status on Saturday, 03-Sep-2022 21:16:07 UTC Bernie

   Ah, the #ArchLinux #GRUB fiasco hits me too! 🤬

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 03-Sep-2022 22:04:37 UTC Bernie

     in reply to

     Oh wait, it's not that bug!

     The #GRUB menu works, and the fallback initrd boots just fine... 🤔

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 03-Sep-2022 22:05:22 UTC Bernie

     in reply to

     It has to be something with the default initrd, but I can't get any console output to debug it, even if I remove "quiet" from the kernel command line.

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 03-Sep-2022 22:15:34 UTC Bernie

     in reply to

     • Podcast Host Kaito

     @jonathan I tried #ClearLinux and I liked it, but didn't they announce that they were de-emphasizing the desktop a while ago?

   • Podcast Host Kaito (jonathan@charade.social)'s status on Saturday, 03-Sep-2022 22:15:36 UTC Podcast Host Kaito

     in reply to
     @codewiz you could always run Clear Linux on a flash drive until Arch gets around to fixing it 😋
   • Bernie (codewiz@mstdn.io)'s status on Saturday, 03-Sep-2022 22:20:01 UTC Bernie

     in reply to

     • Tagomago

     @tagomago Genuine bugs are excusable, but I read that the developers knew about the issue before releasing the update, and took a stance that #ArchLinux users should have figured out that GRUB needs to be reinstalled manually.

     (take it with a grain of salt, it comes from second-hand accounts by pissed users on r/ArchLinux and r/Fedora).

   • Tagomago (tagomago@mastodon.social)'s status on Saturday, 03-Sep-2022 22:20:02 UTC Tagomago

     in reply to

     @codewiz GRUB troubles are a PITA.

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 04-Sep-2022 01:37:53 UTC Bernie

     in reply to

     • Benoit

     @benoit systemd-bootd is too simplistic... Occasionally I also want to run firmware updates, boot Windows, the uefi shell, memtest86, multiple kernels, edit the kernel command line...

   • Benoit (benoit@toots.benpro.fr)'s status on Sunday, 04-Sep-2022 01:37:54 UTC Benoit

     in reply to

     @codewiz do you really need grub? I like the simplicity of systemd-bootd.

   • Bernie (codewiz@mstdn.io)'s status on Sunday, 04-Sep-2022 01:40:11 UTC Bernie

     in reply to

     • penguin42

     @penguin42 I couldn't figure out what went wrong, but I suspect it hung while loading the Intel microcode because my fallback initrd entry didn't have it.

     I can't reproduce it any more after running all pending updates, reinstalling grub and regenerating grub.cfg.

   • penguin42 (penguin42@mastodon.org.uk)'s status on Sunday, 04-Sep-2022 01:40:12 UTC penguin42

     in reply to

     @codewiz Hmm that's odd, normally, without quiet, a corrupt initrd leads to the kernel eventually failing with a can't-mount-rootfs, assuming you've not configured the console off somewhere odd that is.