strange problem with SuSE 9.1 and networking

Jonathan Brooks

13 Oct 2004 13 Oct '04

18:10

Hi, I recently installed SuSE 9.1 on a Samsung P30 laptop. Initially everything worked fine, I was able to run YOU, browse the web etc. However, In the process of installing one of the patches (?kernel patch), support for the centrino wireless networking, etc, the normal LAN networking has stopped working. I can't say which one caused the problem, but I'm in a Catch22 now - I can't get on the network to see whether there are updates to the kernel or network card support, to fix this problem. The laptop's LAN chip is a realtek 8139, and is correctly identified by Yast, but neither auto config using DHCP or manual config with static IP address will bring up the network. I have tried removing then re-adding the network card with Yast, no joy. Removing the WLAN card doesn't help either. I even removed the module that was installed for the centrino wireless card (ipw2100.o). On the advice of a friend I tried adding pci=noacpi and noapic to the linux boot line, no joy. 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. Has anyone got any suggestions? This is driving me crazy.....! >:( 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

Show replies by date

Jeffrey L. Taylor

13 Oct 13 Oct

18:27

New subject: [SLE] strange problem with SuSE 9.1 and networking

Quoting Jonathan Brooks : [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.

Jonathan Brooks

19:11

New subject: [SLE] strange problem with SuSE 9.1 and networking

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 : [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

Jeffrey L. Taylor

19:30

New subject: [SLE] strange problem with SuSE 9.1 and networking

Quoting Jonathan Brooks :

...

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?

Is it getting the same IP address everytime? Switching back and forth between Windows and Linux will mess w/ DHCP. Only one will have the lease info and the other will try and grab it, fail, then get a new address. In environments like this, static IPs work better. On Linux, look for the scpm profile manager. This will allow you to have different profiles for different environments, i.e., one for wireless, one for DHCP, one for static IP, etc. I have the following four profiles: Home: static IP on 10/100/1000Base-T Ethernet interface. Central time. Central: wireless w/ DHCP and/or dialup on Central time. Pacific: wireless w/ DHCP and/or dialup on Pacific time. DHCP: DHCP on 10/100/1000Base-T Ethernet. Central time. So far, these four cover it. Also, when it boots, F4 (IIRC) will allow you to change the active profile. HTH, Jeffrey -- Vote early and often. Apathy only encourages the bums.

Leendert Meyer

19:51

New subject: [SLE] strange problem with SuSE 9.1 and networking

On Wednesday 13 October 2004 21:30, Jeffrey L. Taylor wrote:

...

Quoting Jonathan Brooks :

...
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?

Is it getting the same IP address everytime? Switching back and forth between Windows and Linux will mess w/ DHCP. Only one will have the lease info and the other will try and grab it, fail, then get a new address.

Jonathan Brooks

14 Oct 14 Oct

11:27

New subject: [SLE] strange problem with SuSE 9.1 and networking

Hi, Thanks!! I think that may be the problem here - by default the lease request time is set to infinite in /etc/sysconfig/network/dhcp; at the very most it should be set to 3600 seconds. Also, I have set the machine to relinquish it's IP address on shutdown as you suggested. So far, so good :) Thanks for everyone's suggestions. 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: Leendert Meyer [mailto:leen.meyer@home.nl] Sent: 13 October 2004 20:52 To: suse-linux-e@suse.com Subject: Re: [SLE] strange problem with SuSE 9.1 and networking On Wednesday 13 October 2004 21:30, Jeffrey L. Taylor wrote:

...

Quoting Jonathan Brooks :

...
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?

Is it getting the same IP address everytime? Switching back and forth between Windows and Linux will mess w/ DHCP. Only one will have the lease info and the other will try and grab it, fail, then get a new address.

Possible solution: release the lease upon disconnection from the network. Edit /etc/sysconfig/network/dhcp, and set: DHCLIENT_RELEASE_BEFORE_QUIT="yes" On Windows you'll also have to release the lease before/upon shutting down. Cheers, Leen -- 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

7135

Age (days ago)

7136

Last active (days ago)

List overview

Download

5 comments

3 participants

participants (3)

Jeffrey L. Taylor
Jonathan Brooks
Leendert Meyer