Post ANCWO9Z0mPCYod5Qjg by codewiz@mstdn.io
(DIR) More posts by codewiz@mstdn.io
(DIR) Post #ANCQaOmxOs7Fmj47GK by codewiz@mstdn.io
2022-09-03T21:15:30Z
0 likes, 0 repeats
Ah, the #ArchLinux #GRUB fiasco hits me too! 🤬
(DIR) Post #ANCTdCpsb3xDReSk1A by tagomago@mastodon.social
2022-09-03T21:49:37Z
0 likes, 0 repeats
@codewiz GRUB troubles are a PITA.
(DIR) Post #ANCUuLSTtJtJ44FqJE by codewiz@mstdn.io
2022-09-03T22:03:56Z
0 likes, 0 repeats
Oh wait, it's not that bug!The #GRUB menu works, and the fallback initrd boots just fine... 🤔
(DIR) Post #ANCUzte4DFYcXcJx7w by codewiz@mstdn.io
2022-09-03T22:04:57Z
0 likes, 0 repeats
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.
(DIR) Post #ANCVu2N4xNJloy92Qq by jonathan@charade.social
2022-09-03T21:22:37.227446Z
0 likes, 0 repeats
@codewiz you could always run Clear Linux on a flash drive until Arch gets around to fixing it 😋
(DIR) Post #ANCVu2rZ81hjLWPNx2 by codewiz@mstdn.io
2022-09-03T22:15:05Z
0 likes, 0 repeats
@jonathan I tried #ClearLinux and I liked it, but didn't they announce that they were de-emphasizing the desktop a while ago?
(DIR) Post #ANCWO9Z0mPCYod5Qjg by codewiz@mstdn.io
2022-09-03T22:19:51Z
0 likes, 0 repeats
@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).
(DIR) Post #ANCXrlLFV79KKmKdrk by janci@mstdn.io
2022-09-03T22:37:04Z
0 likes, 0 repeats
@codewiz I am not sure, but can be same problem as I havehttps://bbs.archlinux.org/viewtopic.php?id=278895also some othershttps://bbs.archlinux.org/viewtopic.php?id=278856Workaround was to downgrade kernel so I did install LTS one. But maybe newest one could work ...
(DIR) Post #ANCY4i6opbje4YkxMG by penguin42@mastodon.org.uk
2022-09-03T22:39:25Z
0 likes, 0 repeats
@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.
(DIR) Post #ANCZnxKBCu8sFR90nQ by tagomago@mastodon.social
2022-09-03T22:58:47Z
0 likes, 0 repeats
@codewiz That would be unacceptable imo...
(DIR) Post #ANCdaSAI963Hf1KuP2 by benoit@toots.benpro.fr
2022-09-03T23:41:07Z
0 likes, 0 repeats
@codewiz do you really need grub? I like the simplicity of systemd-bootd.
(DIR) Post #ANCnxdZEuvDvE6hP6W by codewiz@mstdn.io
2022-09-04T01:37:24Z
0 likes, 0 repeats
@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...
(DIR) Post #ANCo9nMuIpN96CjCYy by codewiz@mstdn.io
2022-09-04T01:39:37Z
0 likes, 0 repeats
@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.