Kazuki Sakamoto wrote:

>  >   Boot: Loading in()
>  >   1580436+1528 [94+85072+71240]=0x1a88e8
>  >   start=0x3100

> -current kernel of bebox may be bad...

I did not use netbsd-current but NetBSD 1.5 to avoid possible problems
with unstable source code.

> Please try to use the following filter to fix length of bss section.
> I think "1528" is too short.

That did the trick.

I have to admit, I didn't mention this output

  /usr/pkg/cross/bin/powerpc-netbsd-strip --strip-debug -o netbsd netbsd.gdb
  BFD: netbsd: warning: allocated section `.bss' not in segment

in my last e-mails. Is this a problem with the cross-compiler?


Now, the kernel starts and boots the system over nfs.

  nfs_boot: trying RARP (and RPC/bootparam)
  nfs_boot: client_addr=x.x.x.196 (RARP from x.x.x.70)
  nfs_boot: server_addr=x.x.x.30
  nfs_boot: hostname=bluebox
  nfs_boot: timeout...
  nfs_boot: timeout...
  nfs_boot: timeout...
  root on x.x.x.78:/usr/bebox/root
  root time: 0x3a6afe61
  root file system type: nfs
  init: copying out path `/sbin/init' 11
  ne0: device timeout
  ne0: device timeout
  ne0: device timeout
  ne0: device timeout
  ne0: device timeout
  /etc/rc: Can't open /etc/rc
  Jan 17 10:06:18 init: /etc/pwd.db: No such file or directory
  Enter pathname of shell or RETURN for sh: 
  #

I'm getting a lot of device timeouts from ne0. In fact, after the shell prompt
above, the system is not really usable due to those timeouts.

The network interface card is a simple ne2000 clone:

  ne0 at isa0 port 0x300-0x31f irq 5
  ne0: NE2000 (RTL8019) Ethernet
  ne0: 10base2, 10baseT, 10baseT-FDX, auto, default [0x00 0x30] auto

and I had no problems with it in BeOS. I guess, I will try a different
ISA network card (3com Etherlink III) and a new config file and kernel.


ciao
     Klaus