Date: Wed, 11 Apr 2018 09:49:08 -0500 From: Kyle Evans <kevans@freebsd.org> To: Zaphod Beeblebrox <zbeeble@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Call for Testing: UEFI Changes Message-ID: <CACNAnaH1PQWTZTUNwDTGmvA8st%2B%2Bh-MMY-_L1w5m=Ttu34Q4aw@mail.gmail.com> In-Reply-To: <CACpH0MeiLZoZv8wwt_3GL%2B44pPeD224pNkUJZVxJOsut5E_V2Q@mail.gmail.com> References: <CACNAnaFmu2rFF1w4ar4xHUbN5vHitTLi0Ui6aCjL1MuTj3iJsQ@mail.gmail.com> <CACNAnaEER9qPr7MmhxkiG_fSsZL9VGFH98kG6HoK0%2BxPkGBD9A@mail.gmail.com> <CACpH0MeiLZoZv8wwt_3GL%2B44pPeD224pNkUJZVxJOsut5E_V2Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 5, 2018 at 7:23 PM, Zaphod Beeblebrox <zbeeble@gmail.com> wrote: > As I said I would, I put the contents of /boot onto the FAT-formated EFI > partition. This is suboptimal. The default is to use "kernel.old" ... etc > ... which cannot be done on a FAT partition... at least not with our > filesystem driver ... > > ... but with all of /boot on the EFI partition, simply starting loader.efi > works. > Hi, Can you try a standard setup with the patch at [1] applied to your boot1.efi? Standard setup being /boot/loader.efi in place and boot1.efi copied over to your ESP. I *think* this might help your situation, but I've no real idea. If I know what I'm doing (which I don't), then this patch should (maybe?) force your screen down into a lower resolution prior to drawing the menu then reset it once more before it prints resolution information and executes the kernel. Maybe it'll fix it? Thanks, Kyle Evans [1] https://people.freebsd.org/~kevans/loader.diff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaH1PQWTZTUNwDTGmvA8st%2B%2Bh-MMY-_L1w5m=Ttu34Q4aw>