Hi, The link light was/is on - and I forgot to mention that it works fine under windows. Having said all that - I just tried to boot the machine today and it worked :) It still fails to get an IP address during the boot process, but magically by the time the login screen is put up it has configured itself. I wonder if there is some process that `/etc/init.d/network start` is waiting for, that gets started later in the boot process - which the (backgrounded) dhcpcd then finds and works? It seems a bit unlikely that it should take longer than the 5 second default timeout to get an IP address from DHCP - and it *always* fails - irrespective of the load on the network. Any ideas? Cheers, Jon. -- Jonathan Brooks (Ph.D.) Dept of Human Anatomy & Genetics & FMRIB Centre, University of Oxford tel/fax: 01865-282675 http://www.fmrib.ox.ac.uk/~jon -----Original Message----- From: Jeffrey L. Taylor [mailto:suse@austinblues.dyndns.org] Sent: 13 October 2004 19:28 To: suse-linux-e@suse.com Subject: Re: [SLE] strange problem with SuSE 9.1 and networking Quoting Jonathan Brooks <jonathan.brooks@human-anatomy.oxford.ac.uk>: [snip]
There is one weird message in the logs, when dhcpd is trying to get an IP address for the machine I get something about a kernel module being missing: hw_random.o - but I don't know how to rectify this by hand - or even if it is relevant to the problem.
Not relevant. To get rid of the message add "hw_random" to /etc/hotplug/blacklist. Is the activity LED on the network card lit? What does "ifconfig eth0" say? Jeffrey -- Vote early and often. Apathy only encourages the bums. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com