systemconfigurator, when called with --runboot, runs
efibootmgr in a way that creates bad entries that won't
boot, at least on my one test machine.
I was looking at how to fix it but I'm a bit confused
about what the efibootmgr command that is run is trying
to do. I don't want to break anything.
The following command, for example, works fine for me
and is what I'll do manually for now in the
systemimager autoinstall scripts.
efibootmgr -c -L "erikj-SuSE" -d /dev/sdb -p 1 -l
In this case, I wanted to add an entry for elilo on the
2nd root drive, first partition.
If you'd like me to investigate a fix and can explain a
bit why the efibootmgr command that was produced is
used, I'd be happy to look in to this.