The efibootmgr problems mentioned above are most likely resolved already. In 13.04, there was a kernel bug where the kernel would sometimes fail to update EFI vars. I think that's partly what we were hitting here. Here's the bug, and the issue has since been fixed:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173423 If I boot to the SATA drive, update the kernel to the latest 13.04 one, add in the updated iomemory-vsl driver for that kernel and then try to add an efi entry for the fioa device via efibootmgr, it at least succeeds: efibootmgr -c -w -L FusionIO -d /dev/fioa1 -p 1 -l 'EFI\ubuntu\grubx64.efi' ...but, I'm not sure if what's added is entirely correct (see attached output from efibootmgr -v) At this point, it is indeed now every important that we test things with the latest releases, given the issue I just hit here. Brandon at FusionIO is working with his build team to see what can be done about getting a kernel module built that will work on 13.10 and higher releases. If we can get that, it'll hopefully help shake out some things that may have already been addressed. ** Attachment added: "efibootmgr.txt" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1237519/+attachment/3890232/+files/efibootmgr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237519 Title: Grub2 fails to install to non-standard device path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1237519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
