Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Apr 2015 16:55:00 -0700
From:      Devin Teske <dteske@FreeBSD.org>
To:        Shawn Webb <shawn.webb@hardenedbsd.org>
Cc:        freebsd-current@freebsd.org, Devin Teske <dteske@vicor.com>, Rui Paulo <rpaulo@me.com>
Subject:   Re: Nothing can boot anymore - video issues
Message-ID:  <6D9FB562-9899-4180-A07A-232EEE2A09DB@FreeBSD.org>
In-Reply-To: <1428352517.6806.10.camel@hardenedbsd.org>
References:  <CAExMvskLeBVN1fh7kiiHdNWbOMDNnhNVUGZX0K9uk5VB7EK56A@mail.gmail.com> <369848B3-73AB-4A71-9597-9ED098C7EF64@me.com> <1428343182.6806.3.camel@hardenedbsd.org> <1428352517.6806.10.camel@hardenedbsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

> On Apr 6, 2015, at 1:35 PM, Shawn Webb <shawn.webb@hardenedbsd.org> =
wrote:
>=20
> On Mon, 2015-04-06 at 13:59 -0400, Shawn Webb wrote:
>> On Sun, 2015-04-05 at 12:07 -0700, Rui Paulo wrote:
>>> On Apr 5, 2015, at 09:11, Shawn Webb <shawn.webb@hardenedbsd.org> =
wrote:
>>>>=20
>>>> So I just updated my laptop and desktop to a recent HEAD. Both =
machines
>>>> boot using gptzfsboot. The boot spinner shows, then when it's =
supposed to
>>>> transition to the Beastie logo screen, the monitor funks out. =
Booting never
>>>> finishes. Below is a link to a picture of my laptop.
>>>>=20
>>>> http://imgur.com/l3mLDBX
>>>=20
>>> Try reverting the Forth changes.  That's all that comes to mind.
>>>=20
>>> --
>>> Rui Paulo
>>=20
>> I'm going through commit-by-commit from April 3rd to March 31st, =
which
>> will take a big chunk of time. It's really weird that no one else has
>> reported this since even my VirtualBox VMs have this same issue.
>>=20
>> Thanks,
>>=20
>> Shawn
>=20
> I've figured out the commit that caused the breakage. Looks like the
> boot Forth changes are pretty bad. The commit that caused the =
breakage,
> as far as I can tell is, r280974. Reverting that and the two commits
> above that revision regarding sys/boot/forth allowed me to boot again.
>=20
> Now the boot screen looks like this: http://imgur.com/I9SVHfT
>=20
> I can now boot, but as you see, the boot screen's messed up.
>=20

Why the screen looks that way (no brand and no logo):
You were caught in a small window of broken-ness.

Window was between:
https://svnweb.freebsd.org/base?view=3Drevision&revision=3D280933 =
<https://svnweb.freebsd.org/base?view=3Drevision&revision=3D280933>;
and
https://svnweb.freebsd.org/base?view=3Drevision&revision=3D281002 =
<https://svnweb.freebsd.org/base?view=3Drevision&revision=3D281002>;

A window of approximately 2 days.

As for why the screen got wonky =E2=80=A6 well=E2=80=A6 your comp and my
comp don=E2=80=99t agree on ANSI sequences. I=E2=80=99ve reverted the =
offending
changes so that we may once-again agree on ANSI codes. ;D
=E2=80=94=20
Cheers,
Devin=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6D9FB562-9899-4180-A07A-232EEE2A09DB>