On 11/14/2016 05:04 PM, Tianon Gravi wrote: > On 4 November 2016 at 02:34, Bjørn Mork <bj...@mork.no> wrote: >> + /bin/efibootmgr -c -l '\EFI\refind\refind_x64.efi' -L 'rEFInd Boot >> Manager' -d /dev/nvme0n1 -p 1 > > I just tested this on a friend's machine which has NVMe and uses > rEFInd and we had to change the "-d" value to be "/dev/nvme0n1p1" > (full path to the partition itself) for the entry to be created > correctly (otherwise "efibootmgr -v" afterwards shows > "HD(1,0,000...000,0x0,0x0)/File(...)" instead of the correct > "HD(1,GPT,xxx...xxx,0x800,0x200000)/File(...)", which we got after > adjusting the "-d" path). > > Rod, any ideas for why that might be the case (and how it might be > handled properly in "refind-install")? :/
This is starting to sound like a bug in efibootmgr to me, but I haven't yet had a chance to look into it further. -- Rod Smith Server and Cloud Certification Engineer rod.sm...@canonical.com
signature.asc
Description: OpenPGP digital signature
