Hi Kevin, Thanks for your help. Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make LOADER_DEFAULT_INTERP=4th installkernel"? I had also previously tried " make clean all install WITHOUT_LUA_LOADER=yes" in /usr/src/stand which did not help. Thanks! -Brett On 8/20/2018 6:31 PM, Kevin Oberman wrote: > Check the archive of this list for the past 24 hours. The default bot > was just converted to the lua boot today and there have been some > issues. The "one liner" to switch back to the FORTH boot was posted to > use to work around this and I believe that the change will be rolled > back until the "corner cases" can be fixed. > http://lists.freebsd.org/pipermail/freebsd-current/ > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman_at_gmail.com <mailto:rkoberman_at_gmail.com> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > On Mon, Aug 20, 2018 at 2:28 PM Brett Gmoser > <freebsdcurrent_at_codexterous.com > <mailto:freebsdcurrent_at_codexterous.com>> wrote: > > Hi there, > > I was told to e-mail these addresses with this. > > I did an `svn update` on /usr/src last night, build world and > kernel as > usual. This morning I installed the kernel, booted into single user, > installed world and did mergemaster -Ui as usual. The new kernel had > booted fine. Upon reboot, the machine will no longer boot: > > Startup error in /boot/lua/loader.lua: > LUA ERROR: cannot open /boot/lua/loader.lua: no such file or > directory > > can't load 'kernel' > > Many things in the bootloader do not work, including "boot > kernel.old", > "ls /boot", and various other things (most if not all just result in > "Command failed"). Interestingly, "ls /mnt" works, other > directories do > not. That's the only clue I have. > > I'm able to reboot in an installer image and mount the drive just > fine. > Everything is there and is as expected, including > /boot/lua/loader.lua. > > I re-installed everything in /usr/src/stand (chroot'd on the > installer > image, and "cd /usr/src/stand && make clean all install"). This > did not > fix the problem. > > Does anybody happen to have any ideas? > > Thanks, > > -Brett > > _______________________________________________ > freebsd-current_at_freebsd.org <mailto:freebsd-current_at_freebsd.org> > mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe_at_freebsd.org > <mailto:freebsd-current-unsubscribe_at_freebsd.org>" >Received on Mon Aug 20 2018 - 20:50:32 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:17 UTC