Date: Mon, 18 Dec 2017 06:16:12 -0800 (PST) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Antranig Vartanian <antranig@vartanian.am> Cc: freebsd-current@freebsd.org Subject: Re: r326820 stuck on bootloader Message-ID: <201712181416.vBIEGCKd016460@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <CALJ9-yBHzFPsD7YM=zhqDdaYNZmrtFO_Wu1BPXiYQZbjtjkfcw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Ok, > > I will install the snapshot before. but is it fixed now? since after the > installation I will do buildworld, hope it will not brick. The boot code is in a lot of flux right now, so be carefull and pay attention to commit mail. You should keep the memstick image around for repair incase you have issues. > Thanks a lot! > > -- > antranigv > https://antranigv.am/ | PGP Key ID : 0xDAB81456 > /* do one thing and do it well */ > > On Dec 18, 2017 5:35 PM, "Rodney W. Grimes" < > freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > > > > > Hey all! > > > > > > I have just downloaded > > > FreeBSD-12.0-CURRENT-amd64-20171213-r326820-memstick.img.xz and > > > decompressed it, trying to boot it on QEMU and I get "Consoles: > > > internal video/keyboard" and then it's stuck. > > > > > > I actually have no idea how to debug, any help would be appreciated. > > > > 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. > > > > > > > Thanks in advance, > > > - -- > > > antranigv > > > > -- > > Rod Grimes > > rgrimes@freebsd.org > > -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201712181416.vBIEGCKd016460>