Port-vax archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: VS2000 + NetBSD
Mark Pizzolato wrote:
> Unless you guys have written a new boot ROM for the VS2000 that he's
> trying to boot, as I recall, the native ROM could only boot from: 1) MFM
> disk, 2) Ethernet, 3) TK50 tape which may have been connected via an early
> SCSI or a real SCSI interface. No native SCSI disk access from the ROM.
Good Morning!
Do you had a good sleep?
> Maybe there could be after boot access to a SCSI disk via a NetBSD driver,
> but DEC never provided SCSI access in Ultrix or VMS via what might have
> been to the SCSI connection for the tape.
> - Mark
Not DEC but:
http://home.iae.nl/users/pb0aia/vax/vs-scsi.html
Have you read anything from that thread here before your Post?
Regards,
Holm
> On Apr 13, 2018 1:03 AM, Anders Magnusson <ragge%ludd.ltu.se@localhost> wrote:
>
> Den 2018-04-13 kl. 09:54, skrev Lukas Kaminski:
> >
> >
> > On 13.04.2018 08:53, Holm Tiffe wrote:
> >> Holm Tiffe wrote:
> >> [..]
> >>>
> >>> Ok, I think I'm giving up now.
> >>
> >> .. since I have to move the Vax back to the owner tomorrow..
> >> but I think the owner is still interested booting that thing
> >> from the disk.
> >>
> >>> I've done several experiments now, begun to install 1.6.2 but the
> >>> kernel
> >>> panics every time when one tries to copy some things over nfs on
> both
> >>> the netbooted VS2000 and the VS3100 M76.
> >>> Switched to 1.6.1, that's stable so far. I was able to create a
> >>> disklabel, make filesystems, copy base.tgz and etc.tgz to the disk.
> >>> Next I've installed the sdboot with installboot ...doesn't work at
> all.
> >>> Cleaned the first 16 sectors, reinstalled the label and used
> disklabel
> >>> -B this time.
> >>> The disk is now booting with the VS3100 M76, but not on the VS2000.
> >>>
> >>> KA410-W V2.3
> >>>
> >>> F...E...D...C...B...A...9...8...7...6...5?..4...3_..2_..1...
> >>>
> >>>
> >>> ? C 0080 0000.4001
> >>> ?? 5 0001 0000.0002
> >>>
> >>>>>> b dka2
> >>>
> >>>
> >>> -DKA2
> >>>
> >>>>> NetBSD/vax boot [1.11 Wed Apr 9 05:16:34 UTC 2003] <<
> >>>>> Press any key to abort autoboot 0
> >>> open netbsd.vax: Unknown error: code 3149680
> >>>> boot netbsd
> >>> open netbsd: Unknown error: code 3149680
> >>> netbsd: boot failed: Unknown error: code 3149680
> >>>> boot netbsd.gz
> >>> open netbsd.gz: Unknown error: code 3149680
> >>> netbsd.gz: boot failed: Unknown error: code 3149680
> >>>> boot netbsd.old
> >>> open netbsd.old: Unknown error: code 3149680
> >>> netbsd.old: boot failed: Unknown error: code 3149680
> >>>> boot gennetbsd
> >>> open gennetbsd: Unknown error: code 3149680
> >>> gennetbsd: boot failed: Unknown error: code 3149680
> >>>>
> >>> It seems that the 2nd bootstrap is not seeing any files from the
> disk.
> >>
> >> It is possible that the KA410 config in
> /usr/src/sys/arch/vax/boot/boot
> >> simply doesn't contain the "possibility" to boot from SCSI and
> therefore
> >> the bootstrap doesn't even try to find the filesystem with the
> kernel?
> >> Maybe I have to dig out where this definition is?
> >> Ragge you digged in the bootloader lately..??
> >>
> >> Regards,
> >>
> >> Holm
> >>
> >>
> >
> > Now i remembering that i had troubles to boot from an MFM disk years
> > ago. I blamed the disk or my disability to use the test50 (?) format
> > tool properly, since it wasn't a DEC-MFM disk. But maybe our bootcode
> > for the VS2000 has troubles booting from disk at all?
> >
> > I planned to use a small 10MB MFM disk for the boot/kernel and a 1GB
> > SCSI-flash-disk as root.
> MFM disks may not work, since they are CHS addressed and the prom boot
> code
> must know the exact geometry of the disk.
>
> -- Ragge
--
Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe,
Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
info%tsht.de@localhost Fax +49 3731 74200 Tel +49 3731 74222 Mobil: 0172 8790 741
Home |
Main Index |
Thread Index |
Old Index