I am sorry for this vague bug report, but I thought this was
important to report, with the upcoming 1.1 release in mind.

I installed new boot blocks on a NetBSD-current system using:

	disklabel -B sd0

After this, the system refused to boot, it just hung when the "boot
prompt" should come, it didn't write anything at all. This is a
NetBSD-only system, no OS-BS or DOS partitions.

Putting the disk in another machine, I could verify that the disklabel
and all partitions still were intact. Reinstalling NetBSD-1.0
bootblocks with:

	disklabel -B -b ~/sdboot-1.0 -s ~/bootsd-1.0 sd1

made the disk bootable again, and now everything works just fine (the
1.0 boot blocks reports version 1.21.2.2). After I got it working I
once again tried the current bootblocks, trying all possible
combinations of arguments to disklabel, but nothing worked. Reverting
to the 1.0 boot blocks made it work immediately again.

The disk is a Micropolis 4110:

ncr0 targ 0 lun 0: <MICROP, 4110-09NB_Nov18F, TN0F> SCSI2 0/direct fixed
sd0 at scsibus0sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
: 1002MB, 2428 cyl, 9 head, 93 sec, 512 bytes/sec

The same geometry is used in the disklabel.

The original system, that hangs with current boot blocks, is:

	ASUS P55TP4XE with P75, triton chipset, Award BIOS
	NCR 53c810 SCSI controller (the one ASUS calls SC200)

Another system reboots before showing any boot prompt:

	NoName P60, Intel Mercury chipset, Award BIOS,
	onboard NCR 53c810

Both systems work with the 1.0 boot blocks on the disk.

Has anyone else had boot block problems lately?

	-- Urban

--
South Africa BATF Peking Marxist kibo nuclear [Hello to all my fans in
domestic surveillance] jihad Delta Force plutonium FSF Qaddafi
security Khaddafi Rule Psix