Date: Mon, 23 Sep 2019 23:55:36 +0300 From: Andrey Fesenko <f0andrey@gmail.com> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Warner Losh <imp@bsdimp.com>, lausts@acm.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Booting anything after r352057 kills console Message-ID: <CA%2BK5SrNWfznScAFbmD39RV23xzLsJWVwS74aPP1%2B4DXO6J6DcQ@mail.gmail.com> In-Reply-To: <18606.1569271853@critter.freebsd.dk> References: <11db909b-57ee-b452-6a17-90ec2765c36e@acm.org> <18332.1569268545@critter.freebsd.dk> <CANCZdfr5TPUX9uvmbm7oFPBTO7rgBGg-Rb0PcOjt-1-gL8et=g@mail.gmail.com> <18606.1569271853@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 23, 2019 at 11:51 PM Poul-Henning Kamp <phk@phk.freebsd.dk> wrote: > > -------- > In message <CANCZdfr5TPUX9uvmbm7oFPBTO7rgBGg-Rb0PcOjt-1-gL8et=g@mail.gmail.com> > , Warner Losh writes: > > >We are working on making drm ports less problematic on upgrade... > > Yes, I know. > > But when you track current, it seems that it takes a port-reinstall > to get on that wagon... > beadm/bectl rules 1) make world/kernel 2) install in new BE 3) make new pkg drm 4) install it in new BE too 5) activate 6) reboot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BK5SrNWfznScAFbmD39RV23xzLsJWVwS74aPP1%2B4DXO6J6DcQ>