Date: Mon, 18 Dec 2017 08:49:03 -0800 From: "Chris H" <bsd-lists@BSDforge.com> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> Cc: <freebsd-current@freebsd.org>, "antranigv" <antranig@vartanian.am> Subject: Re: r326820 stuck on bootloader Message-ID: <0cc30f3ae9bbac71deb1f4c132d8d795@udns.ultimatedns.net> In-Reply-To: <201712181335.vBIDZXNb016145@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Dec 2017 05:35:33 -0800 (PST) "Rodney W=2E Grimes" <freebsd-rwg@pd= x=2Erh=2ECN85=2Ednsmgr=2Enet> said > > Hey all! > >=20 > > I have just downloaded > > FreeBSD-12=2E0-CURRENT-amd64-20171213-r326820-memstick=2Eimg=2Exz and > > decompressed it, trying to boot it on QEMU and I get "Consoles: > > internal video/keyboard" and then it's stuck=2E > >=20 > > I actually have no idea how to debug, any help would be appreciated=2E >=20 > This snapshot may have broken boot code in it, I had problems > installing it to a zfs system and had to post install replace > my zfs boot blocks from those of 20171206=2E Like I said; I can confirm r326056 (2017-11-21) doesn't contain the boot regression=2E Warner advised me to try an earlier version when I indicated I had the problem you also described in this message=2E Yesterday, Warner indicated he believes he has corrected this regression, as well as add some other goodies=2E So it should be safe to svn up to the latest revision, after your initial install, and build from there=2E --Chris >=20 >=20 > > Thanks in advance, > > - --=20 > > antranigv >=20 > --=20 > Rod Grimes =20 > rgrimes@freebsd=2Eorg > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0cc30f3ae9bbac71deb1f4c132d8d795>