<div>
During startup, I see:<br />
Using DHCP for eth0...<br />
modprobe: no dependency information for module: &quot;/etc/sysco&quot;<br />
modprobe: no dependency information for module: &quot;/etc/sysco&quot;<br />
DHCP wait expired<br />
..<br />
It's like this /etc/sysco is getting cut off from a script or something. <br />
We are talking about dhcp client and not dhcp server, right?<br />

</div>


During startup, I see:
Using DHCP for eth0...
modprobe: no dependency information for module: "/etc/sysco"
modprobe: no dependency information for module: "/etc/sysco"
DHCP wait expired
..
It's like this /etc/sysco is getting cut off from a script or something.
We are talking about dhcp client and not dhcp server, right?


<div>
<div class="content wysiwyg-content">
I'm running RedHat 5.2 out of the box, a Kingston 10/100 nic(tulip driver, connecting to the Internet with a cable modem (@home). &nbsp;At boot, the DHCP client fails to get an ip address from my isp, but I can run &nbsp;my '/etc/rc.d/rc3.d/S10networ<wbr />k start' after I login as root and DHCP client gets the address. &nbsp;How can I fix this startup problem? &nbsp;tia<br />

</div>
</div>


I'm running RedHat 5.2 out of the box, a Kingston 10/100 nic(tulip driver, connecting to the Internet with a cable modem (@home).  At boot, the DHCP client fails to get an ip address from my isp, but I can run  my '/etc/rc.d/rc3.d/S10network start' after I login as root and DHCP client gets the address.  How can I fix this startup problem?  tia


DHCP client during boot fails.

The variety of Linux distributions creates myriad issues relating to configuration and operations when computers are networked, not the least of which is the use of various network management applications, some of which are included with specific distributions, while others are standalone applications.