Re: VS3100M76 - current

[Holm Tiffe <holm%freibergnet.de@localhost>]

Johnny Billquist wrote:

> On 2014-05-22 16:28, Holm Tiffe wrote:
> >Johnny Billquist wrote:
> >
> >>On 2014-05-22 15:54, Holm Tiffe wrote:
> >>>Next thing would be NEtbooting and teht the folowing available releases
> >>>and to find out where it stops.
> >>>Anyone knows what the kernel tries next after putting out this "root file
> >>>system is ffs" (or so?). That is where 1.6.2 simply halts...
> >>
> >>I seem to remember that the main reason if it stops there is if you do
> >>not have /dev populated.
> >>
> >>    Johnny
> >
> >Hmm, it halts wenn booting from the vax.iso from NetBSD.org. Not sure if
> >/dev is populated properly there :-))
> 
> Oh. I thought it halted when booting your disk.
> I would expect the CD to have /dev populated.
> 
> More recent versions will setup a /dev on the fly if it don't exist, but 
> it takes a hell of a long time on a VAX, I can tell...
> But I have no memory of that ability being in 1.5.3.
> 
>       Johnny

Hmm.. that wasn't there as I've experimented last time with taht rtVAX and
netbooting.. but I'll look for, just in case ...

Another thing:

It is curious, but I can't get the M38 boot from sd0 (dka300).
I've reinstalled the label with 1.5.2 and uses disklabel and 
usr/mdec/installboot to install the sdboot on the disk.
I've even enabled the writing of the label with disklabel -W.

still getting this:

>>> b dka300


-DKA300
 85 RESTART SYS
 84 FAIL

 83 BOOT SYS
?41 DEVASSIGN, 0
 84 FAIL

I'm remembering that I've read something that boot wasn't supported from
VaxStations sometimes. Is 1.5.3 old enoug for that to be true or should it
work?

So far as I know the sdboot should load boot from the rootfs which then
loads the kernel... I had no problem with that while experimenting mit 6.x

The disklabel is as follows:

# disklabel sd0|less
# /dev/rsd0c:
type: SCSI
disk: FIREBALL_TM2110S
label: fictitious
flags:
bytes/sector: 512
sectors/track: 151
tracks/cylinder: 4
sectors/cylinder: 604
cylinders: 6810
total sectors: 4124736
rpm: 4500
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0 

6 partitions:
#        size   offset     fstype   [fsize bsize cpg/sgs]
  a:   262144       16     4.2BSD     1024  8192    16   # (Cyl.    0*- 434*)
  b:   262144   262160       swap                        # (Cyl.  434*- 868*)
  c:  4124736        0     unused        0     0         # (Cyl.    0 - 6829*)
  d:   131072   524304     4.2BSD     1024  8192    16   # (Cyl.  868*- 1085*)
  e:  1024000   655376     4.2BSD     1024  8192    16   # (Cyl. 1085*- 2780*)
  f:  2445360  1679376     4.2BSD     1024  8192    16   # (Cyl. 2780*- 6829*)


what about the 16 blocks offset from the rootfs to the beginning of the
disk? I know that in the past the offset was set to 0 normally and the fs
reserved place if it was the rootfs. Later the Offset 16 or 64 was introduced
on FreeBSD.. how is this handled here?

Regards,

Holm


-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
  www.tsht.de, info%tsht.de@localhost, Fax +49 3731 74200, Mobil: 0172 8790 741