lfs first boot
 

Well, I am now lfs registered user 4814 :)

It all went pretty smoothly, however, I am having network problems as I always seem to have with linux...

On bootup I get:

Bringing up the eth0 interface...
SIOCSIFADDR: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth0: unkown interface: No such device [FAILED]
setting up default dateway...
SIOCADDRT: No such device [FAILED]

You should not be reading this error message. It means that an unforseen error took place in /etc/rc.d/rc3.d/s20network,
which exited with a return value of 7

etc etc....

What have I done/forgotten or where can I look to start tracking this down :confused:

edit:

I've also had probs with lilo. When run lilo from the old (slackware) system, it works fine. But from lfs, it just hangs on system startup :P

DAMN!! I mean cool, but what did you do that I didn't? What did I screw up? See post: http://www.linuxquestions.org/questi...threadid=22741

I sent a reply to your thred, and my first prob is now sorted, but why won't lilo work for me on lfs :(

edit:

Oh never mind, twas me again. I copied lilo.conf from the old sys and forgot to update root= etc :)

so what do you have as root=

I think that may be where my problem is... My $LFS is/was /LFS on hdb1 and is / on hdb7. SO would I put root=/dev/hdb7?

Thanks

Re: lfs first boot
 

The error means the kernel has no network card driver support. If you built the network card driver as a module, you must "insmod" the module before you try to access the hardware. You can edit the network script and add the proper insmod command(s) to it before it tries to bring the devices up.

Or, you can turn on the kernel automatic module loading feature which will take care of all this for you. See the kernel documentation on how to enable and configure this option.

No you need -

root=/dev/hdb1

This is the root of where your LFS installation is contained.

lfslinux: it's odd that it did that cause I didn't build the network card drivers as a module.

I seems to have fixed itself now, I just wish I knew what it was :confused:

I will give it a try, but won't that just boot my new kernel, still putting me into my mandrake distro?