NetBSD Problem Report #18584

Received: (qmail 17050 invoked by uid 605); 8 Oct 2002 13:19:19 -0000
Message-Id: <20021008131918.45BCF11122@narn.netbsd.org>
Date: Tue,  8 Oct 2002 06:19:18 -0700 (PDT)
From: joop.braamse@hp.com
Sender: gnats-bugs-owner@netbsd.org
Reply-To: joop.braamse@hp.com
To: gnats-bugs@gnats.netbsd.org
Subject: VAX  4000-105A does not boot from disk
X-Send-Pr-Version: www-1.0

>Number:         18584
>Category:       port-vax
>Synopsis:       VAX  4000-105A does not boot from disk
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-vax-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 08 13:20:00 +0000 2002
>Closed-Date:    Sat Mar 05 08:44:32 +0000 2016
>Last-Modified:  Sat Mar 05 08:44:32 +0000 2016
>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:
Responsible-Changed-From-To: install-manager->port-vax-maintainer
Responsible-Changed-By: tsutsui@NetBSD.org
Responsible-Changed-When: Fri, 03 Oct 2008 20:20:03 +0900
Responsible-Changed-Why:
port specific problem.


State-Changed-From-To: open->closed
State-Changed-By: ragge@NetBSD.org
State-Changed-When: Sat, 05 Mar 2016 08:44:32 +0000
State-Changed-Why:
Patch applied (as referenced in ticket) by Matt Thomas in 2004.


>Unformatted:

Home	PR Database Search