Date: Tue, 04 Sep 2018 14:42:15 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 215143] FreeBSD 11 install cd does not boot on macpro1,1 (32-bit efi) Message-ID: <bug-215143-227-KQ9iPrSjwi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215143-227@https.bugs.freebsd.org/bugzilla/> References: <bug-215143-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=3D215143 --- Comment #13 from Jason W. Bacon <jwb@freebsd.org> --- Finally got around to fully testing this. I did a full install with my cus= tom ISO on a MacBook Pro 2,2. I'm using it right now to send this update. I then did a freebsd-update fetch install which updated the kernel and it did not cause any problems. Clearly from previous posts, "freebsd-update upgrade" can render the system unbootable, but I'm not sure what other conditions could cause problems. I don't understand the details of the boot process well enough. Might it be possible to patch the generic ISO to prevent the EFI boot path = from being used on 32-bit EFI systems? Is there an easy way to fix an installation following "freebsd-update upgra= de"? I'm not so concerned about this one as I prefer to do fresh installs when I upgrade. ( A little OCD about bit rot and keeping my installations pristin= e. ) --=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-215143-227-KQ9iPrSjwi>