Hi!

This System boots now from its local harddisk - with a big "Dankeschön" to
Jochen!  - and his Kernel and bootstrap loader package (s.b.).

Can we expect, that  those modifications go its way into the distribution?
If I can do anything for this happening, let me know.

Thanks again and best regards. / Hilmar.

------------------
Here the dmesg output:
------------------
NetBSD 1.6B (MrPomeroy) #0: Sun Jun 30 21:48:50 CEST 2002
    jkunz@MrPomeroy:/usr/src/src/sys/arch/vax/compile/MrPomeroy

MicroVAX 3100/m{90,95}
cpu0: KA51, ucode rev 2
total memory = 65468 KB
avail memory = 55136 KB
using 844 buffers containing 3376 KB of memory
mainbus0 (root)
ibus0 at mainbus0
ze0 at ibus0
ze0: hardware address 08:00:2b:9b:8b:d8
uba0 at ibus0: Q22
vsbus0 at mainbus0
vsbus0: 8K entry DMA SGMAP at PA 0x27000000 (VA 0x9d039000)
vsbus0: interrupt mask 0
dz0 at vsbus0 csr 0x25000000 vec 524 ipl 15 maskbit 3
dz0: 4 lines
asc0 at vsbus0 csr 0x26000080 vec 510 ipl 15 maskbit 1
asc0: NCR53C94, 25MHz, SCSI ID 6
asc0: SCSI bus reset
scsibus0 at asc0: 8 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0: <IBM, DCAS-34330, S65A> SCSI2 0/direct fixed
sd0: 4134 MB, 8205 cyl, 6 head, 171 sec, 512 bytes/sect x 8467200 sectors
stray interrupt: vector 0x0, ipl 21
sd0: sync (160.0ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
sd1 at scsibus0 target 1 lun 0: <DEC, RZ28     (C) DEC, 442D> SCSI2 0/direct
fixed
sd1: 2007 MB, 3045 cyl, 16 head, 84 sec, 512 bytes/sect x 4110480 sectors
stray interrupt: vector 0x0, ipl 21
sd1: sync (160.0ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
sd2 at scsibus0 target 2 lun 0: <DEC, RZ28     (C) DEC, 442D> SCSI2 0/direct
fixed
sd2: 2007 MB, 3045 cyl, 16 head, 84 sec, 512 bytes/sect x 4110480 sectors
stray interrupt: vector 0x0, ipl 21
sd2: sync (160.0ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
sd3 at scsibus0 target 3 lun 0: <DEC, RZ26N    (C) DEC, 0568> SCSI2 0/direct
fixed
sd3: 1001 MB, 3117 cyl, 8 head, 82 sec, 512 bytes/sect x 2050860 sectors
stray interrupt: vector 0x0, ipl 21
sd3: sync (160.0ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
cd0 at scsibus0 target 4 lun 0: <DEC, RRD45   (C) DEC, 1645> SCSI2 5/cdrom
removable
cd0: sync (240.0ns offset 15), 8-bit (4.166MB/s) transfers
sd4 at scsibus0 target 7 lun 0: <DEC, RZ28     (C) DEC, 442D> SCSI2 0/direct
fixed
sd4: stray interrupt: vector 0x0, ipl 21
2007 MB, 3045 cyl, 16 head, 84 sec, 512 bytes/sect x 4110480 sectors
stray interrupt: vector 0x0, ipl 21
sd4: sync (160.0ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
boot device: sd2
root on sd2a dumps on sd2b
root file system type: ffs
---------------------------------------


-----Ursprüngliche Nachricht-----
Von: port-vax-owner@netbsd.org [mailto:port-vax-owner@netbsd.org]Im
Auftrag von Jochen Kunz
Gesendet: Mittwoch, 9. Oktober 2002 21:37
An: port-vax@netbsd.org
Betreff: MV3100m9x boot stuff


Hi.

As requested some days ago:
http://www.unixag-kl.fh-kl.de/~jkunz/tmp/mv3100_kern_boot.tar.gz
This contains a 1.6B kernel (netbsd) from my MV3100m95, first stage
booter (xxboot) and second stage booter (boot) as well as a MD5 checksum
file (MD5). Make a backup copy of your existing files! Copy netbsd and
boot to the / directory and install the first stage bootloader with
installboot(8). All MV3100m9x and VAX4k1xx (VAX53 type machines) should
be able to autoboot with this stuff. Additionally the VS4k90 (VAX49) is
supported. Kernel config file is included:
tar xOzf mv3100_kern_boot.tar.gz netbsd | strings | sed -n 's/^_CFG_//p'
| unvis

Please report (un)success with this stuff. Maybe the changes needed to
get the VAX53 to autoboot will find there way into the NetBSD source if
it works.
--



tschüß,
         Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/