Date: Tue, 28 Dec 2021 19:32:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260735] 1b33aa1f5f99e1270d526ffa5b652250ec80a7ef (amd64 UEFI loader: stop copying staging area to 2M physical) maybe not effective in some cases Message-ID: <bug-260735-227-ps2tT6d1Am@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260735-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260735-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260735 stanislso@yandex.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stanislso@yandex.com --- Comment #6 from stanislso@yandex.com --- (In reply to Graham Perrin from comment #4) I am the original poster from the forums. I want to clarify a few points. > so the install was done in CSM mode and loader.efi was copied to support = UEFI boot. Correct. If I attempted to install without CSM, I would experience an appar= ent screen freeze after the EFI framebuffer information. I had to resort to usi= ng a discreet video card to be able to enable CSM. Once the install was performed (with manual partition creation), I set up the EFI partition and removed the nVidia card from the system, thus booting the newly-installed system in UEFI mode.=20 > so stable/13 should also boot with the ASUS Prime B560-Plus=20 > in pure UEFI mode (more specifically: boot progress beyond=20 > EFI framebuffer information appearing on screen) This was, sadly, not the case. To reproduce, it is enough to boot from the memstick in non-CMS mode on that system. If need be, I can test a newer memstick or a fix candidate, to see if I man= age to go past the EFI framebuffer information screen. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260735-227-ps2tT6d1Am>