Something failing on boot, but still works!

Upon boot I get a fail. Its reads....

Code:

Bringing up the loop back interface
Cannot open netlink socket: function not implemented
Cannot create control socket: function not implemented  FAIL

I think its something to do with the way Ive compiled the kernel (2.6.11.12) but I dont know which part. I reckon its to do with networking but thats just a hunch. It doesnt prevent the OS from booting, it seems to work fine.
I will never need networking on that computer but it will be nice to have the option there just in case. Im going to play with some bootscripts just to see what happens.

Can anyone help resolve this?

 

Stating the obvious -
Have you checked the forums of your chosen distro?

 

If you think you've accidentally compiled out a networking feature, then just reuse your .config file when you configured the kernel and recompile. The loopback interface should not be failing.

 

Ive tried recompiling with networking support and I get

Code:

RTNETLINK answers: invalid argument
cannot create control socket:address family not supported by protocol  fail

When I first enter make menuconfig there are certain settings selected, does anyone know how I can get back to these "default settings"?
Ive tried running make mrproper from a new kernel source directory but I get the same settings as I did in the first place.
I suppose I could wade through a kernel I know is good on another computer and write it all down. Thats gonna take time though!

 

Try getting the latest stable version of the kernel from The Linux Kernel Archives

The vanilla kernel has all the options required for most users selected by default.

 

It sounds like you opted out of compiling a crucial part of the kernel -- the loopback interface -- which is part of the networking subsystem of the kernel.

 

Im still trying to find out if it will be safe for me to update the kernel to the newest version.
I think I might just backup my partition and do it anyway.

 

There shouldn't be any problems updating the kernel, especially a small update from two 2.6 kernels.

 

Just make sure you keep a known working kernel around as a safety net.

 

I stuck with the 2.6.11.12 kernel and transferred some options from within the networking support section I got off a livecd of the same flavour.
It worked and I get a long list of OKs with no Fails!

Next job is X

Many Thanks for your help guys