Re: Jornada 680 asks for

[Nikos Ntarmos <ntarmos%ceid.upatras.gr@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there.

On Thu, Jul 28, 2005 at 10:02:21AM -0400, Michael Wileman wrote:
> On Thu, 28 Jul 2005, tiskanto wrote:
> >- Jornada 680
> >- CF Sandisk --> !!
> >- NetBSD 2.0.2
[...]
> >Error messages:
> >couldn't find the root device

I've never tried 2.0.2 on my nada, so I can't help you with that.
However, the following should apply anyway.

> >My Question to nikos:
> >did you create a custom kernel or did you just use a GENERIC  ?

The kernel I had sent over to Michael was a custom one. However, that
doesn't seem to be the issue here -- the entries for wdc{0,1},
atabus{0,1}, and wd* were identical to those in GENERIC. I just updated
my source tree and built a GENERIC kernel:

NetBSD 3.99.7 (GENERIC) #0: Thu Jul 28 17:46:01 EEST 2005
  ntarmos@Noth:/home/ntarmos/netbsd/obj/obj/sys/arch/hpcsh/compile/GENERIC

FYI the system boots just fine. You can get this kernel image from
http://noth.ceid.upatras.gr/Misc/GENERIC if you want to try it out
(dmesg at http://noth.ceid.upatras.gr/Misc/GENERIC.dmesg).

> There is definitely a problem with the "current" binaries.

This is really disturbing... I built the above kernel (presumably) from
the exact same sources used to build the snapshot binaries, and using
vanilla conf files (i.e. standard GENERIC conf, no mk.conf or other
COPTS/CFLAGS changes, etc.) and the outcome is ok (at least for me). If
it also works for you, then this discrepancy doesn't make sense... Could
it be that the hpcsh binaries are built on some 64-bit machine and this
is an artifact of crossing the 32-64bit boundary?

\n\n
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Nikos "Nikolai" Ntarmos <ntarmos%ceid.upatras.gr@localhost>

iD8DBQFC6PgEm6J1ac+VFgoRAjgLAJ4tp1k97oeGs04G8Od5nR8o0FXn5wCfbTfZ
4En/m6zt9t3H5Ztr+IZlY18=
=1siz
-----END PGP SIGNATURE-----