>Number:         18584
>Category:       install
>Synopsis:       VAX  4000-105A does not boot from disk
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 08 06:20:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Joop Braamse
>Release:        1.6
>Organization:
>Environment:
VAX 4000-105A, 128MB memory, SCSI disk RZ26,RZ28
>Description:
After installation of 1.6 the system doesnot boot from disk. This is what happens:
	>>> boot dka100
	-DKA100
         1..0..
The system hangs here
It can netboot, using the 1.5.3 mopboot file. I checked the contents of the disk, it looks OK to me. I am afraid the 4000-105A doesn't like the
/boot file.
	

>How-To-Repeat:
Install it on a 4000-105a or a 3100-95 and watch it.
>Fix:
There may be a fix, I extracted this from the vax-port mailing list:

But I know the problem and the solution to it. ;-)
The VAX4k100 / MV3100m9x does some things a bit different than
other VAXen of that type when it comes to booting. Unfortunately 
I don't have enough knowledge about this internas to describe it
closer. 
Hugh Graham from OpenBSD posted a mail about this some time ago: 
http://mail-index.netbsd.org/port-vax/2002/06/28/0005.html
I applied the patches from that mail to my source (-current
of that time) and now my MV3100m95 can boot from its own SCSI
disk. (See: http://mail-index.netbsd.org/port-vax/2002/07/01/0000.html)


>Release-Note:
>Audit-Trail:
>Unformatted: