On 5/6/22 2:30 PM, Nick Holland wrote:
On 5/6/22 12:48 PM, Theo de Raadt wrote:
Florian Obser <flor...@openbsd.org> wrote:
So, if you end up with a /bsd.upgrade on the running system that is
still mode 0700, your bootloader is on the fritz.
If you have a /bsd.upgrade that's 0600 your bootloader found the kernel
and tried to boot it, but the installer didn't get very far.
If there is no /bsd.upgrade after a reboot and no email to root the
installer got rebooted by a watchdog process, otherwise you got an email
to root detailing the upgrade process.
A very nice 3-way split.
Brilliant, even.
Then once you figure out which one of those 3 is happening, it is easy
to reason about how to create further differentiations and see which is
happening.
I was very much guessing it was /boot, but no.
-rw------- 1 root wheel 4609699 May 6 13:13 bsd.upgrade
So ... it's booting bsd.upgrade and failing, which explains why copying
bsd.upgrade (aka bsd.rd) to /bsd tossed it into a lala-loop.
Unfortunately, this machine doesn't retain dmesg buffer between boots.
so ... booted bsd.rd with a monitor attached, and grabbed the dmesg below.
I'm looking at this:
efifb0 at mainbus0: 1920x1080, 32bpp
If the system is booted (bsd) without a monitor attached, that says:
efifb at mainbus0 not configured
Getting to the boot> prompt, typing "boot bsd.rd", unplugging the monitor
and hitting "ENTER" resulted in a successful boot of the bsd.rd kernel (and
efifb is showing the monitor as connected).
I tried bsd.rd renamed "bsd" so it would only boot bsd.rd, and then firing
the machine up and plugged the monitor in AFTER the boot process (probably)
started hoping to see some indication on the screen of the crash. Result:
no display until the kernel crashes and the system reboots.
Nick.
Got contacted by someone off-list who told me they "fixed" this problem
on their machine by switching to a serial console, which is cool, but my
machine doesn't have a serial console. (set tty com0 resulted in a hang,
as it was probably waiting for the UART to say, "Sent that first character"
and it never does).
Is it possible that bsd.rd *must* have some kind of output device?
efifb fails to configure without a monitor attached, so no console output?
For giggles, I did a "gop" and a "video" at the boot> prompt, and both came
back with no response, just another boot> prompt.
Nick.
