[SOLVED] rpcbind: cannot create socket for udp6 and tcp6

[Leonard]

I don't think the problem has to do with IP6. Only that this is the last message I see on the conneced monitor before the system seems to get to a halt.
When starting from a live CD the system I get the same message but the system will keep on booting after that. The next message I get normally is "* Starting early crypto disks"
So I think the problem must be somewhere between these two steps.

I am not able to access the system via the web UI or telnet

Seems there is a problem somewhere. But not sure what it is just yet. Can you give me a full list of your hardware specs?
 

Tried installing the 32 bit and 64 bit versions without succes. Also tried installing it on SSD and HD and different BIOS settings made no difference.
Is it related to the BIOS? What BIOS version and settings are you using for this NF9C board?

Here's my BIOS setting for NF9C. The only thing that needs to be set really is to make sure your SATA is set to AHCI. For best results, reset your BIOS to the default first and then make the changes.

When booting from the SSD, can you see if your network link LED is lit or not?

I have updated the BIOS to the latest version. The network link LED is indeed blinking. Can it be the case that it has to do with not getting a proper IP address?
I have now finally managed to install the 64 bit version on the Atom board and get to work. However I had to use a screen and keyboard to login to the prompt and set my ipaddress manually (sudo ifconfig eth0 ....)

Using the 32-bit version I don't see a chance to login as the boot process seems to get stuck.