https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
dhu...@gmail.com changed:
What|Removed |Added
CC||dhu...@gmail.com
--- Comment #14
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #13 from Warner Losh ---
(In reply to Albert Valbuena from comment #12)
Yea, that lack of clarity is what needs to be updated.
We need to describe how to find the ESP. Most systems there's only one, and
it's a FAT partition of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #12 from Albert Valbuena ---
(In reply to Kyle Evans from comment #8)
Sorry for not knowing but I really need to ask this.
Quote:
"it appears that we might need to revisit how we document bootloader upgrade
procedure."
My fir
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #11 from Warner Losh ---
https://reviews.freebsd.org/D45890 (and prior reviews) have a patch chain.
It's least disruptive to bump all the versions to 3.0.
Then complain if we're < 3.0
Although I could check different symbols th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #10 from Warner Losh ---
Hmmm, 3.0. version.veriexec already uses 2.0.
And what to do about veriexec... I think in that environment, you lose since
it's all supposed to be up-to-date, but I need to socialize that I guess.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #9 from Warner Losh ---
OK. I've thought through this. We have two strategies here. This is kinda not a
bug, but also kinda a huge big rock sticking out for people to trip over that
we should do something about, since we've know
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
Kyle Evans changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #8 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #7 from di...@webweaving.org ---
And another machine coming from 14.1-RELEASE releng/14.1-n267679-10e31f0946d8
GENERIC amd64 that started its live as a 12.0 in Jan 2019 and was upgraded in
place ever since.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #6 from di...@webweaving.org ---
Also got hit by this on a 14.2-RELEASE (that was in place upgraded from at
least FreeBSD-12. This time on AMD, not intel.
Same workaround (i.e. checking for lua_path == nil; set to lua_path =
"/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
di...@webweaving.org changed:
What|Removed |Added
CC||di...@webweaving.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #4 from Albert Valbuena ---
(In reply to Kyle Evans from comment #3)
Thanks.
PS: Rebuilt the whole thing on a new box with modern EFI, first reusing the
same exact drive without a hassle. Reinstalled just for the sake of start
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
Kyle Evans changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
--- Comment #2 from Albert Valbuena ---
(In reply to Kyle Evans from comment #1)
The device has become bricked after attempting an overdue BIOS upgrade (non
related to FreeBSD). Since it does not equip a backup copy, it's now a
paperweight
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
Kyle Evans changed:
What|Removed |Added
CC||kev...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279829
Bug ID: 279829
Summary: Unable to automatically boot after upgrading to
14.1-RELEASE
Product: Base System
Version: 14.1-RELEASE
Hardware: amd64
OS: An
16 matches
Mail list logo
