On 01-Apr-98, Ignatios Souvatzis wrote:
> > *** Forwarded message, originally written by B. Bogart on 27-Mar-98 ***
> > On 27-Mar-98, Ignatios Souvatzis wrote:
> > 
> > > My guess is the 8meg expansion board is the culprit. Can you please find
> out
> > > where the kernel is initially loaded to? (loadbsd -t tells you that).
> > 
> > loadbsd -t output:
> > 
> > Translated 07c00020 sz 003fffe0 to 07c00020 sz 003fffe0
> > Translated 00200020 sz 007fffe0 to 00200020 sz 007fffe0
> > Translated 00001000 sz 001ff000 to 00001000 sz 001ff000
> > mem segment 1: start=07c00000 size=00400000 attribute=0105 pri=30
> > mem segment 2: start=00200000 size=00800000 attribute=0205 pri=0
> > mem segment 3: start=00000000 size=00200000 attribute=0303 pri=-10

> wait. your 8Meg Z2 board is included in the 12 Meg Fastmem you reported? oh.

> I guess you can try to boot with

> loadbsd -p

> which will prefer high-priority memory segments over big ones, and find
> out wether this works with -n2 or not.

> Regards,
> Ignatios

success!

Loadbsd -bpn2 -Z netbsd

did do the trick, except netbsd hangs at this point in the startup:

root device> [sd0*]
preserved ... blocks of miniroot...
enter pathname of shell.. enter for sh: [enter]
erase ^?, werase ^W, kill ^U, intr ^C

[Hangs here]

if these questions could be better answered by another address please let me
know.

Ben

Oh and I do have a problem with my HD, bad blocks are starting to com up, the
front end of the drive is fo far unaffected but im not sure how many bad
blocks are in the netbsd partitions. how is the bad block handling in netbsd?
What problems can i expect from this?