RE: Has kernel in 1.4.1 distribution been fixed with regard to BB-Clock?

["Job Hanssen" <hanssen%dds.nl@localhost>]

> -----Original Message-----
> From: Lars Hecking [mailto:lhecking%nmrc.ucc.ie@localhost]
> Sent: maandag 31 januari 2000 18:26
>
> > I'm using gobsd to boot into NetBSD. The system starts to
> > boot, but doesn't make it all the way...
>
>  Sorry, I am not familiar with gobsd at all :-( Is it
>  something specific for 060 machines? Can you run loadbsd at all?

I don't know really, but I used to use loadbsd, but that stopped doing its
job at some time. I don't recall why, but it might have had to do with the
larger amount of fastmem I put in (96Mb).

> > >  I had a similar problem over the weekend with OpenBSD, so I reset
> > >  the clock under AmigaOS, booted into OpenBSD and set the current
> >
> > I'm not sure what you mean by 'reset the clock'. Do you
> > mean setting it to *any* date prior to 1-1-2000?
>
>  That's what I meant, yes.
>
> > Ok, what happens is this:
> [...]
>
>  No idea :( But it's hard to believe that the clock is causing this.
>  In my experience, *BSD normally continues to boot regardless of this
>  message.

Well, I don't know what else can be wrong... Last time I hooked up these
scsi-drives and booted NetBSD, everything just worked as expected. (This was
somewhere in October). After that, the drives have not been in use by *any*
system, so there's really nothing changed on them.

Regards,

   Job