No, It's not work. Did someone here has a problem and remember what he did and what moduls are missing?
Thanks Nadav On 10/20/06, nadav vinik <[EMAIL PROTECTED]> wrote:
oops sorry. The only thing which I didn't do, is to check if I need modules to the kernel. After the first time that I compile the kernel, The LFS boot, so I didn't fink that I have missing modules. How do I know which module I need? I access to Networking->networking support I try know the "Generic IEEE 802.11 Networking Stack " Is it what I need? Does there more modules in somewhere else? Thanks for your help Nadav On 8/11/06, jeeva suresh <[EMAIL PROTECTED]> wrote: > > Interface eth0 doesn't exist. > > I am at work ATM, but this line is the exact line which I got while > trying to configure my DHCP interface. > > I have notes at home, but from memory, this was a problem with my > kernel, as in I didn't compile in the right drivers for my network > card. > > Also, if you did choose the right driver, change it from a module to a > built-in, this can also cause this error. > > Double check this, and if it is still not working email me back and I > will check my notes for you > > Cheers > Jeeva. > > On 8/10/06, rblythe <[EMAIL PROTECTED]> wrote: > > nadav vinik wrote: > > > I uncomment these line and set to: > > > ---------------- > > > DHCP_START="" > > > DHCP_STOP="-k" > > > ---------------------- > > > > > > but I get the same error and warning > > > --------------------------------------------------------------------- > > > Unable to process /etc/sysconfig/network-devices/ifconfig.eth0/dhcpcd. > > > Either > > > the SERVICE variable was not set, > > > or the specified service cannot be executed. [ > > > FAIL ] > > > > > > Interface eth0 doesn't exist. > > > ---------------------------------------------------------------------------- > > > > > > > > > On 8/9/06, Dan Nicholson <[EMAIL PROTECTED]> wrote: > > >> On 8/9/06, nadav vinik <[EMAIL PROTECTED]> wrote: > > >> > > > >> > the dhcpd file is: > > >> > ------------------------------------------------ > > >> > ONBOOT="yes" > > >> > SERVICE="dhcpcd" > > >> > #DHCP_START="<insert appropriate start options here>" > > >> > #DHCP_STOP="-k <insert additional stop options here>" > > >> > > > >> > # Set PRINTIP="yes" to have the script print > > >> > # the DHCP assigned IP address > > >> > PRINTIP="no" > > >> > > > >> > # Set PRINTALL="yes" to print the DHCP assigned values for > > >> > # IP, SM, DG, and 1st NS. This requires PRINTIP="yes". > > >> > PRINTALL="no" > > >> > > > >> -------------------------------------------------------------------------------- > > >> > > >> > > > >> > I didn't found in the man dhcpcd what to set the DHCP_START and > > >> DHCP_STOP. > > >> > > >> Try `man dhcpcd' and see what options are interesting to you. > > >> Generally, though, you can just have > > >> > > >> DHCP_START="" > > >> DHCP_STOP="-k" > > >> > > >> But you can't comment out those variables. > > >> > > >> -- > > >> Dan > > >> -- > > >> http://linuxfromscratch.org/mailman/listinfo/blfs-support > > >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html > > >> Unsubscribe: See the above information page > > >> > > > > You might have to try (in your dhcpcd file) - make a back-up first: > > ONBOOT="yes" > > SERVICE="dhcpcd" > > DHCP_START="eth0 -t 20" # See man dhcpcd for definition of -t and the > > reason for eth0 spec > > DHCP_STOP="-k " > > > > # Set PRINTIP="yes" to have the script print > > # the DHCP assigned IP address > > PRINTIP="no" > > > > # Set PRINTALL="yes" to print the DHCP assigned values for > > # IP, SM, DG, and 1st NS. This requires PRINTIP="yes" > > PRINTALL="no" > > > > > > > > And for your ipv4 file: (make a back-up first) > > place comment (#) symbol in front of everything except SERVICE. > > change SERVICE variable to SERVICE="dhcpcd" > > > > I know this appears to be redundant, but even though I use a wireless > > connection (my file has ra0 instead of eth0), it connects without > > problem every time. > > > > Also, what does your /etc/resolv.conf look like? If dhcpcd is working > > correctly, it should have created a back-up named > > /etc/resolv.conf-eth0.sv or something similar (also in the man page). > > > > Last thing: Was you eth0 working before you tried dhcpcd? Did you name > > it something different when you set it up in LFS (using the udev rules > > as outlined in the LFS instructions)? If you named it something else, > > then technically eth0 no longer exists and the new name of your > > interface does. You would then need to change your information > > accordingly when setting up dhcpcd in BLFS. > > > > rblythe > > -- > > http://linuxfromscratch.org/mailman/listinfo/blfs-support > > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > > Unsubscribe: See the above information page > > > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page >
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
