Comment # 32 on bug 1174412 from Gary Ching-Pang Lin

Would you mind to paste the current "efibootmgr -v"?

There are two mysterious parts till now.
1. The boot entry to the wrong partition
  We could not reproduce it manually, so I don't have a clear clue yet.

2. The failure of "efibootmgr-manual"
  The boot entry looks fine to me since it points to the correct partition.
However, the firmware seems needing a full device path instead of a short one.
I'll look into efibootmgr and see if it's possible to generate a full device
path.