Re: NetBSD-current no longer boots after install

[Andreas Gustafsson <gson%gson.org@localhost>]

Izumi Tsutsui wrote:
> > Some time between CVS dates 2010.01.14.12.05.15 and 2010.01.15.01.00.46,
> 
> Why don't you check commit logs between them?

Too many commits, too little time :)

> The following one looks suspicious:
> 
> ---
> Module Name:  src
> Committed By: drochner
> Date:         Thu Jan 14 17:49:32 UTC 2010
> 
> Modified Files:
>       src/sys/arch/i386/stand/boot: boot2.c
>       src/sys/arch/i386/stand/lib: boot_params.S
>       src/sys/arch/i386/stand/pxeboot: Makefile main.c
>       src/sys/sys: bootblock.h
>       src/usr.sbin/installboot: installboot.8 installboot.c installboot.h
>       src/usr.sbin/installboot/arch: i386.c
> 
> Log Message:
> On i386/amd64, define two flag bits in the boot parameters which control
> whether modules are loaded and whether boot.cfg is evaluated, and
> set both to "off" per default in the PXE bootloader.
> Extend "installboot" to toggle the bits.
> This way, pxeboot works with existing dhcp server setups (and as
> described in the manpage) out of the box. Also, boot.cfg reading
> involves a stat() call which is horribly inefficient with the
> TFTP pseudo file system.
> ---
> 
> What happens if you replace /boot?

I replaced the /boot on my non-booting 201001150000Z system by a copy
from a 201001140000Z system, and now it boots.  So yes, the problem
does appear to be in /boot.

Looks like sysinst doesn't use installboot on i386.  Perhaps it needs
to be extended to toggle the new bits the same way installboot does?
-- 
Andreas Gustafsson, gson%gson.org@localhost