[K12OSN] Error! dhcpcd failed!

[Ray Garza]

This is how I would TS the problem.

You might have a cabling problem with the cable that goes down to the basement 
or a switch probelm. I would get the client, server and switch and two 
verified cables together on ONE table and hook it as client -> switch -> 
server and try it again. If it connects then bad cable going down to 
basement, else bad switch.

-ray

On Wednesday 08 November 2006 11:52, Shane Sammons wrote:
> Hi all I am new to this stuff, so forgive me if I am making a basic
> mistakes.
>
> I setup a server and spent some time in irc.freenode.net getting some help
> in #ltsp. Long story short got a server and a thin client working great
> with a crossover cable connecting Eth0 to Eth0 server -> client.
>
> So now I decided to move it to the basement with a switch to attach other
> systems and see how it does. I am using a dell Plug and Play switch (think
> its model 2240, i know its a 2000x series, not the managed). I have no
> touched ANY settings in this switch, it has worked in our network as a fill
> in when we lost a managed switch.
>
> I plugged my server into port 24, and my client into port 1 (neither are
> shared and I have tried others as well). When I boot the server, I get an
> error on eth1 as I have no network connection down the basement. That is
> the only error I get during boot of the server. I then run tail -f
> /var/log/messages on a terminal as root to ensure my client is getting an
> address. I then use my floppy to boot a Dell 233 GX1 with 64MB of ram. It
> starts to boot, gets its DHCP address and tail shows this. For awhile it
> was slow (I was using a normal cat5 cable at this time on  the server) then
> it would start to boot and I would receive this error:
> Error! dhcpcd failed!
> Kernel Panic - not syncing: Attempted to kill init!
>
> So, I thought perhaps it was a bad cable, replaced both on the client and
> server, same thing (still normal cat5). Next I decided to try normal on the
> client and crossover on the server (both still plugged to the switch). The
> switch is auto sensing and gave me a link light, re-booted the client and
> watched the tail. Same thing, got my address etc. Same error. Only
> difference was it was a little quicker at points most specifically
> obtaining a DHCP address.
>
> So, finally I decided to go back to the cross over direct from client to
> server. This works perfect, no error! Does anyone know what this could be
> other then a bad NIC? It is the only thing I can guess as this switch is
> known good, I have tried other ports, and the client starts to boot off the
> server and then just dies. Considering I tried other cables and they are
> manufactured not made in house there is a lesser chance they could all be
> bad.
>
> Also, just a side question, does anyone host forums for this project, cause
> I really can't stand mailing lists, they are antiquated and disorganized
> and as far as I can see unsearchable. If not, I might start a topic about
> offer to host one so we can sort and categorize topics, sticky things, and
> make common answers and guides.
>
> Thanks,
> Shane