Hilmar,

On my 4000-105A (=3D3100-95) I have similar problems.
Actually I am planning to send in a bug report. Before I do so, I shall =
wait to see what comes
out of this.
Please read my remarks.

Joop

-----Original Message-----
From: Hilmar B=F6hm [mailto:Hilmar.Boehm@hiro-consult.de]
Sent: zondag 6 oktober 2002 23:36
To: port-vax@netbsd.org
Subject: Inst. NetBSD 1.6 (ISO) --> MV3100/96
Hi!

This weekend I tried to install the new 1.6 to my MV3100/96. Here a few
remarks.

-  I made a CD-ROM from the corresponding iso-file.
   This CD-ROM doesn't boot on the /96. (Same thing as with OpenBSD 3.3
CD-ROM).

>> I don't have a CD-ROM. I donwloaded the files using ftp. I installed =
them on a
>> 4000 VLC succesfully.

-  I set up a DS5000/50 (NetBSD 1.5.2) for diskless booting the /96 and =
then
to install from the 1.6-ISO-CD.
   (To setup the diskless server is not an easy job, because there is no
_single_ piece of documentation for it and to setup the diskless server =
in a
way to boot the install.ram is a little bit different.)

>> My bootserver is a Linux box. I gained some experience in setting it =
up as a
>> bootserver. The "netbooting VAX" file on the Netbsd-vax homepage =
helped me a lot.

   Is the file "boot" in /vax/installtion/netboot/ the MOPBOOT-Image =
(size:
65252)?? If yes, this one is (definitively) not an vax executable binary
file!
	# mopchk boot
	Checking: boot
	#

>> The "file" command tells you the file is in ELF format. Mopd doesn't =
support ELF.
>> Someone told me "mopcopy" in 1.6 converts an a.out or a ELF file to a =
mop format file.
>> I tried to do so and it gave me a 67 MB file!
>> Later, I discovered that the 1.5.3 boot.mop may be used as well.
  =20
	I had to use the (correspnding) "boot.mop" (size: 71168) from NetBSD
1.5.3/vax. This one gives:
	# mopchk boot.mop
	Checking: boot
	Native Image (VAX)
	Header Block Count: 1
	Image Size:         00011400
	Load Address:       00000000
	Transfer Adrress:   00000000
	#

	This one worked!

-  Sysinst:
	One thing during sysinst is not understandable for me.
	My harddisk configuration is: 2 internal hd's (in the /96 system box) =
and 3

>> The installation kernel cannot be booted on my 4000-105A. It ends up =
with some numbers
>> and an "unknown error 60". The generic kernel runs fine if netbooted.

RZ28 in an attached
	Pizza box
	>>> show dev
	SCSI Adapter A, SCSI ID 6
	-DKA0 (IBM DCAS-34330)      # not used
	-DKA100 (DEC RZ28)          # OpenBSD 3.3
	-DKA200 (DEC RZ28)          # for new NetBSD 1.6
	-DKA300 (DEC RZ26N)         # OpenVMS 7.3
	-DKA400 (DEC RRD45)
	-DKA700 (DEC RZ28)          # CCD formatted, but empty/unused)
	Ethernet Adapter
	-EZA0 (08-00-2b-...)
	>>>

	Sysinst presented only sd0, sd1, sd2 for installation. (OpenBSD sees
additionaly sd3 and sd4.)
	I installed the 1.6 on sd2, which is the DKA200.

   After installation, I tried to boot this DK200:
	>>> boot dka200
	(BOOT/R5:0 DKA200)

	  2..
	-DKA200
        1..0..

	The System seems to hang here.

>> My system behaves exactly the same way. I also prepared a boot disk =
on a 4000 VLC,
>> and connected it to the 105A. It doesn't boot.
>> If the boot process counts down to zero, control is handed to the =
boot file; that's what the
>> VAX manuals say.
>> Knowing that, the problem must be in the "boot" file.
>> VMS boots fine on this system.

	I'm a bit concerned about the fact that I can not boot the =
OpenBSD-System
(DKA100) too now. (-DKA100 | ?43 FILESTRUCT, DKA100 | ?06 HLT INST | ... =
|
Bootstrap failure.) Ok, I can repair this on later. (But: OpenVMS-disk =
is
still bootable!)
So I did the 1.6 installation a second time with the same effect that I
cannot boot (the new) NetBSD system.
Can there be anything within the VAX console system which prevents from
booting the NetBSD system?

Thanks for any hints and best regards. / Hilmar.


--------------------
Btw: The INSTALL.RAM kernel sees sd3 and sd4. It comes up with:
...
NetBSD 1.6 (INSTALL) #0: Wed Sep 11 10:16:48 UTC 2002
....
MicroVAX 3100/m{90,95}
cpu0: KA51, ucode rev 2
total memory =3D 65468 KB
....
--------------------