I'm having what seems to be a strange dilemma. I installed suse 8.0 last night (I had used both redhat 7.3 and mandrake 8.2 recently and they both worked fine, I'm just experimenting). I used the FTP installation and it seemed to go well. It configured my network card (DEC 21041) with the tulip driver and dhcpcd just fine and connected and downloaded without a problem. Upon completion of the installation, the machine rebooted. When it came back up, dhcpcd timed out getting an IP address with dhcpcd (which it had done successfully during installation). For the hell of it, I rebooted with the install CD to see if it was still working there and it was. tulip.o from the install CD and the tulip.o driver installed are the same size, and thus I assume the exact same driver, but the installation did something that caused it not to work. The machine is connected to a LinkSys EtherFast Cable/DSL Router which is connected to my AT&T broadband cable modem. The other machines on the network could pull dhcp addresses fine throughout this whole ordeal.

Does anyone know what might be different about tulip and dhcpcd then there was during the installation?

try running dhcpcd -h <hostname> -i <interface> it probably did not have the correct options in the start up script.

Also run md5sum on both of the tulip modules. If the numbers match then they are the same driver.

Hi there,
I'm trying to install Suse via FTP, but I'm stuck on the ftp-ip address part...what ip address & path did you use?
Thanks!