Ok, I downloaded the latest daily builds for 1.6, laid them on top of
the original distribution, reinstalled - and Oh frabjous day!

The mouse works (and a few other things that were problems, keys, etc.)!

On to more packages!!!!

-----Original Message-----
From: Tim Underwood [mailto:tim@underwoodfamily.org] 
Sent: Saturday, August 07, 2004 2:03 PM
To: 'port-hpcmips@netbsd.org'
Subject: RE: hpcmips-current vs. hpcmips-2-0


I never used cvs.  I just downloaded the "daily" binaries from their
respective directories.

The install kernel both show 2.0G for -current and 2.0.  I was trying a
different binary build since I can't seem to get my own compiled and
linked.

-----Original Message-----
From: port-hpcmips-owner@NetBSD.org
[mailto:port-hpcmips-owner@NetBSD.org] On Behalf Of Matthew Orgass
Sent: Friday, August 06, 2004 9:32 PM
To: Tim Underwood
Cc: port-hpcmips@NetBSD.org
Subject: Re: hpcmips-current vs. hpcmips-2-0


On 2004-08-06 TimU@hightouchinc.com wrote:

> 2.0 hard-locks on mounting a CF card, and when it boots, shows "2.0G".
>
> When I try to install -current, it also boots showing "2.0G", and
> while
 > it doesn't lock up mounting a CF card, it "runs out of space on /",
and
> drops into the debugger.
>
> So - what is -current in relationship to 1.6.2 and 2.0?

  A 2.0 kernel is a cvs branch and should read 2.0_BETA at this point,
not 2.0G.  You might have tried the wrong kernel.  -current is the
current development line not part of any release (it will be branched to
form 2.1, etc.).  There is a separate CVS branch for 1.6.  Is this the
install kernel you are trying?  I think the out of space message can
appear if the md size is too small.  Your kernel hang might possibly be
related to PR 26158 (on my Clio recent 2.0 kernels and -current as of a
month or two ago hang when entering userland without the patch in the
PR).

Matthew Orgass
darkstar@city-net.com