Sheree,

	The dialog you're referring to is to chose a disklabelling scheme. This
divides the NetBSD partition into slices (a through h). I think I remember
an issue with hpcarm's sysinst and the both Standard and Standard with X,
but I'm not sure. Anyway, the easiest thing to do is to try to set up the
slices manually. The easiest way (but maybe not the best) to do is to have
slice a) contain the entire NetBSD partition. Maybe try that first. After
you get the disk slices set up, then you get to choose what sets (and what
packages) to install.

	If you need more help on disklabelling (my instructions are sparse, I know)
you can ask on the netbsd-help list. It gets a lot more traffic (and by
conincidence someone asked about a Jornada 720 earlier this month).

Jason M.

> -----Original Message-----
> From: Sheree A Hemphill [mailto:sah18@sbcglobal.net]
> Sent: Wednesday, September 15, 2004 4:06 PM
> To: jmitchel@rosstechnologygroup.com
> Cc: port-hpcarm@NetBSD.org
> Subject: Re: is anyone still working on this port?
>
>
> I'm having trouble getting the netbsd installation to complete onto a CF
> card on a Jornada 720.  I downloaded Jason's files & followed the
> instructions.  I'm able to run the bootloader to launch the
> install (though,
> it kept freezing when I chose HP Jornada 720 -- it would only run
> if I chose
> HP Jornada 720 (Japanese), for some reason).  I'm just trying to do one of
> the 2 canned installation setups -- either Standard or Standard
> with X (the
> same problem happens on both).  I let it setup the partitions for me (and
> I've tried both leaving the initial 5mb dos partition intact and also
> telling it to use the entire disk to install on).  Once the
> install begins,
> I eventually come to this error:
> ===============
> Status: Failed: command failed
> Command: /sbin/newfx /dev/rwd0f
> Press any key to continue
> - - - - - - - -
> wtfs: write error for sector 3395951: Input/Output error
> I can't continue.
> ===============
>
> I've tried:
> -- copying the 3 initial files to the My Documents folder (so
> that they are
> not on the CF card).
> -- more than one CF card (in case the card had a bad section) -- one was
> 256MB and the other was 512MB
> -- different initial boot options (not always sure I'm choosing the right
> settings here -- I'd love to hear what exact settings others are using)
> -- first I tried choosing "Standard with X", since this is what I really
> wanted, but then when the error occurred I tried instead "Standard", but
> still got the same error.
>
> Another error I received on one of my many attempts was:
> ============
> Status: Failed: command failed
> Command: /sbin/newfx /dev/rwd0a
> Press any key to continue
> ----
> newfs: /dev/rwd0a: open for read: Device not configured.
> Command  /sbin/newfx /dev/rwd0a failed.
> I can't continue
> ===============
> This above one was when I had the boot/install files still copied to that
> 5mb dos partition on the cf card -- this is when i though i might have
> better luck moving them off the card into memory.
>
> Any ideas/suggestions/step-by-steps of what has worked for you, would be
> greatly appreciated!  And I won't be offended if you mention the
> obvious, because it may not be obvious to me!
>
> Thank you for listening to my woes,
> -sheree
>
>
>
> Jason Mitchell wrote:
>
> >Hello,
> >
> >Actually, it's a bit easier than those instructions. I created an
> >installation kernel -- so all you need are three files on a dos partition
> >on a CF card.
> >
> >http://mail-index.netbsd.org/port-hpcarm/2003/01/07/0001.html
> >
> >As for whether people are still using this port -- the three files get
> >downloaded about once a week.
> >
> >Jason M.
> >
> >
> >
> >>On Sep 8, 2004, at 7:34 AM, Sheree Hemphill wrote:
> >>
> >>
> >>
> >>>One more question to add to my previous email:
> >>>In the how to use document
> >>>(again, at: http://www.netbsd.org/Ports/hpcarm/howto-use.html
> >>>
> >>>it mentions the following:
> >>>"Booting from memory card (top)
> >>>This is probably the easiest way, for now.
> >>>Connect some device to the serial port. Use 19200bps, no parity,
> >>>8bits."
> >>>
> >>>The serial port referred to is the specialize port used to sync with
> >>>the desktop computer, correct?  Why is this necessary?  And does it
> >>>really not matter what device is connected to the serial port?  Is the
> >>> connection for synchronization okay to use?
> >>>
> >>>
> >>>
> >>That's for the serial console.  Originally, there was only serial
> >>console; the display didn't work, if I remember correctly.
> >>
> >>So you can probably safely ignore that step.
> >>
> >>
> >
> >
> >
> >
> >
> >
>
>