Post ATLH47UPv0qIgAaFGa by hemish@mastodon.world
(DIR) More posts by hemish@mastodon.world
(DIR) Post #ATK1oFX6YLQWWNr5PM by BrodieOnLinux@linuxrocks.online
2023-03-06T00:27:52Z
0 likes, 2 repeats
If you're dual booting Arch with a point release like Ubuntu and using it's version of grub, your system likely isn't booting right now. This is a known issue https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2009292
(DIR) Post #ATK2PipsZJjM7JVNgW by PublicLewdness@freespeechextremist.com
2023-03-06T00:34:59.716905Z
0 likes, 0 repeats
@BrodieOnLinux I've never had a great experience dual booting myself. I just use seperate systems if need be.
(DIR) Post #ATK2priUAlzDBnVriC by BrodieOnLinux@linuxrocks.online
2023-03-06T00:39:26Z
0 likes, 0 repeats
Best suggestion is stop doing that and use the version of grub from the Arch repos, which doesn't include the deprecated EFI handover protocol
(DIR) Post #ATK3xdlw09B8DEOhge by BrodieOnLinux@linuxrocks.online
2023-03-06T00:52:02Z
0 likes, 0 repeats
Update: It also effects the 3 people out there using syslinux as a bootloader, so also don't do that.
(DIR) Post #ATKYzq4ILvpzVSVuIS by aiyuh@home.social
2023-03-06T06:39:32Z
0 likes, 0 repeats
@BrodieOnLinux I don't dual boot a point release, but have Windows on a separate drive and my system broke today. Must be an unrelated error? Last thing I did was update the kernel.
(DIR) Post #ATKZ8gcyp1C6pixLRQ by BrodieOnLinux@linuxrocks.online
2023-03-06T06:40:41Z
0 likes, 0 repeats
@aiyuh That would be seperate, this specifically relates to using grub from a distro that is not Arch
(DIR) Post #ATKcQlgh31M7bL0TPE by aiyuh@home.social
2023-03-06T07:18:11Z
0 likes, 0 repeats
@BrodieOnLinux Ah yeah mine was caused by systemd, downgraded that and it is back working.
(DIR) Post #ATLH47UPv0qIgAaFGa by hemish@mastodon.world
2023-03-06T14:53:38Z
0 likes, 0 repeats
@BrodieOnLinux much better solution, just use EFIstub, become Chad by using no bootloader at all. Linux doesn't need a bootloader, it can load itself