(I've got a bad habit of saving unfinished emails in the drafts folder and
then forgetting about them. I found this one while cleaning it up and thought
it might still be informative.)
On Tuesday 12 April 2016 10:56:56 Adam Carter wrote:
>> The problem was sys-boot/grub-2.02_beta2-r9, which
On Tue, 12 Apr 2016 10:56:56 +1000, Adam Carter wrote:
> I also failed to get grub2 + UEFI working. So either;
> 1. We're both dummies
> 2. The handbook instructions are incorrect and/or inadequate
>
> Can anyone else that is familiar comment on the grub2 + UEFI doc
> quality?
ISTR getting GRUB
None of this is grub's fault, it's users are just petulant children.
It's bloated but pick a real argument.
On Mon, Apr 11, 2016 at 10:31:42PM -0400, Poison BL. wrote:
> The file 'bootx64.efi' is the default that uefi looks for when booting
> a 'disk' in a quasi-bios-style fallback (if there's not a real 'boot
> this particular thing' like the windows boot manager adds), which also
> makes the
On Mon, Apr 11, 2016 at 8:56 PM, Adam Carter wrote:
>
>> The problem was sys-boot/grub-2.02_beta2-r9, which UEFI never ran.
>>
>> The fix was to get rid of grub altogether and instead use
>> sys-boot/gummiboot.
>> Not only was it fully functional, it was a welcome relief
> The problem was sys-boot/grub-2.02_beta2-r9, which UEFI never ran.
>
> The fix was to get rid of grub altogether and instead use
> sys-boot/gummiboot.
> Not only was it fully functional, it was a welcome relief not to have to
> grapple with grub's baroque complexity and to be able to return to
On Thursday 7th April 2016 I wrote:
> I have a new box with an NVMe SSD drive attached to the PCI bus via an
> M.2 interface. The drive shows up as /dev/nvme0n1, with partitions
> /dev/nvme0n1p1, /dev/nvme0n1p2, ...
> After following the instructions in the handbook for a UEFI system, I get
>
7 matches
Mail list logo