=?iso-8859-1?Q?H=E5kan=20Th=F6rngren?= <hth@update.uu.se> wrote:
>So I put the network card back and this time it was recognized as ne0.
>I do not know why it did not work before, dirty connectors perhaps,
>ugh.

>Strangely, the ethernet address is 00:00:00:00:e8:e8

>At least it starts to boot now, finds the kernel but hangs during
>boot.  After the long talk about all devices it comes to a stop with
>boot device: <unknown>
>root device: 

>And a blinking cursor after "root device: ".
>I am allowed to choose one of: ne0 ddb halt reboot

>Should it not automatically find the nfs root file system?
>I have it exported on the server, but the client does not seem to
>request it (at least not according to syslog).

What happens if you type in a valid root path at this point ?

>Here is the relevant parts of my current dhpcd.conf:
>
>subnet 192.168.106.0 netmask 255.255.255.0 
>{ 
>  option routers 192.168.106.254;
>
>  host gestur
>    {
>       hardware ethernet 00:00:00:00:E8:E8;
>       fixed-address 192.168.106.12;
>       server-name "skyfari";
>       option root-path "skyfari/export/diskless/root/gestur";
>       option tftp-server-name "skyfari";
>       option host-name "gestur";
>       filename "netbsd.aout-GENERIC";
>    }
>}

Your root-path doesn't look right to me. I would delete the leading 'skyfari'.

Robert Swindells