LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 07-04-2005, 10:23 AM   #1
paulbutcher
LQ Newbie
 
Registered: Jul 2005
Posts: 8

Rep: Reputation: 0
Wired network works for a few seconds and then stops


I have SuSE 9.2 installed on a Dell Inspirion 9300 laptop. The wireless network works just fine. The wired network does not. The symptoms are as follows:

Immediately after enabling the wired network, I get the following console message:

Disabling IRQ #9

The network appears to initialize correctly - it successfully negotiates an IP address via DHCP and for a few seconds, it works exactly as expected. After a few seconds, however, the network fails. Pinging the gateway results in "network unreachable". After this point, nothing I've tried has any effect. ifdown followed by ifup does not successfully connect at all (not even for a few seconds).

The network card is a "Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)". YaST has (correctly, I believe) configured it to use the "b44" driver.

The system is fully updated with all the patches provided by SuSE.

Everything works just fine if I boot into Windows.

Any assistance or suggestions will be very gratefully received!

Here is a trace showing what I've just described above:

--------------------------------------------------------------------------
paul-laptop-linux:~ # ifup eth0
eth0 device: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
eth0 configuration: eth-id-00:11:43:7a:fa:67

Message from syslogd@paul-laptop-linux at Mon Jul 4 16:01:07 2005 ...
paul-laptop-linux kernel: Disabling IRQ #9
Starting DHCP Client Daemon on eth0... . IP/Netmask: 192.168.1.70 / 255.255.255.0 ('linux')

paul-laptop-linux:~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:11:43:7A:FA:67
inet addr:192.168.1.70 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:43ff:fe7a:fa67/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:7
collisions:0 txqueuelen:1000
RX bytes:12835 (12.5 Kb) TX bytes:4123 (4.0 Kb)
Interrupt:11

paul-laptop-linux:~ # ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
From 192.168.1.70: icmp_seq=10 Destination Host Unreachable
From 192.168.1.70 icmp_seq=10 Destination Host Unreachable
From 192.168.1.70 icmp_seq=11 Destination Host Unreachable
From 192.168.1.70 icmp_seq=12 Destination Host Unreachable

--- 192.168.1.254 ping statistics ---
15 packets transmitted, 0 received, +4 errors, 100% packet loss, time 13998ms
, pipe 3
 
Old 07-04-2005, 03:39 PM   #2
Half_Elf
Guru
 
Registered: Sep 2001
Location: Montreal, Canada
Distribution: Slackware; Debian; Gentoo...
Posts: 2,163

Rep: Reputation: 45
could you please post the output of "route -n" once the card "crashed" ?

your "IRQ" might be caused because you are missing PnP (plug and play) in your kernel. Some laptop need Pnp to be activated in order to use ACPI and PCMCIA... is your card a PCMCIA device?
 
Old 07-04-2005, 05:17 PM   #3
paulbutcher
LQ Newbie
 
Registered: Jul 2005
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by Half_Elf
could you please post the output of "route -n" once the card "crashed" ?
Here it is:

Code:
paul-laptop-linux:~ # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.254   0.0.0.0         UG    0      0        0 eth0
Quote:

your "IRQ" might be caused because you are missing PnP (plug and play) in your kernel. Some laptop need Pnp to be activated in order to use ACPI and PCMCIA... is your card a PCMCIA device?
Nope, not a PCMCIA device - it's a built-in network adapter (Mini-PCI, I believe).

Thanks a lot for your response - any light you can cast would be very welcome!

Paul.
 
Old 07-04-2005, 05:34 PM   #4
Half_Elf
Guru
 
Registered: Sep 2001
Location: Montreal, Canada
Distribution: Slackware; Debian; Gentoo...
Posts: 2,163

Rep: Reputation: 45
hummm okay, so except the "169.254.0.0 " line (but this should be a minor error) your routing seems fine... so it may be a bug with the drivers or something. My guess would be to make sure you do have PnP included in your kernel, even if you don't use PCMCIA, it may be related. You might want to recompile your kernel to make sure you have it (eeh, good time to learn recompiling kernel, isn't it? )

Out of that... try searching google about this network card... maybe someone got the same bug and fixed it already. Trying an older/newer kernel may be a good gues too. Sorry I'm running out of idea
 
Old 07-04-2005, 06:02 PM   #5
paulbutcher
LQ Newbie
 
Registered: Jul 2005
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by Half_Elf
hummm okay, so except the "169.254.0.0 " line (but this should be a minor error) your routing seems fine... so it may be a bug with the drivers or something. My guess would be to make sure you do have PnP included in your kernel, even if you don't use PCMCIA, it may be related. You might want to recompile your kernel to make sure you have it (eeh, good time to learn recompiling kernel, isn't it? )
I'm pretty sure that the kernel does have PnP compiled in (can't imagine that SuSE wouldn't?). Although I'm not sure how I would go about finding out for sure?

And no, you're right, learning how to recompile the kernel isn't top of my things to do right now :-)

Quote:

Out of that... try searching google about this network card... maybe someone got the same bug and fixed it already. Trying an older/newer kernel may be a good gues too. Sorry I'm running out of idea
I've done the Google thing - and everything that I can find suggests that things should work (assuming that I've got the latest patches from SuSE). For example http://linux-laptop.net/hosted/dell-inspiron-9300.html.

I'm kinda suspicious that the problem is power management related - the fact that everything works to start off with and then stops suggests to me that something's being powered down which shouldn't be, and isn't IRQ #9 the ACPI interrupt? I'm not a Linux config expert though, so I'm kinda at a loss to work out how to pursue this hunch. Is there some kind of global "switch of power management" that I could do to test this, for example?

Thanks for your help so far!
 
Old 07-04-2005, 10:46 PM   #6
Half_Elf
Guru
 
Registered: Sep 2001
Location: Montreal, Canada
Distribution: Slackware; Debian; Gentoo...
Posts: 2,163

Rep: Reputation: 45
yup I'm pretty sure it has something to do about power management too, or ACPI, as it is called on laptop
SUSE probably have PnP compiled as module... you might try to just load the module, I'm not on a linux computer right now but I'll take a look on my ystem later to give you the module name. But I'm pretty sure that kind of thing should be loaded at boot so it has to be in initrd (assuming Suse use initrd... initrd is a way to load module "driver" just "before" the system bootup, so you can have essential drivers compiled as optionnal module). I can't tell you for sure right now... post me the output of "dmesg" just after the boot (it's the kernel logging... lot of stuff, I warn you) and I could maybe tell you, by comparing the output with my own.
 
Old 07-05-2005, 04:12 AM   #7
paulbutcher
LQ Newbie
 
Registered: Jul 2005
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by Half_Elf
yup I'm pretty sure it has something to do about power management too, or ACPI, as it is called on laptop
SUSE probably have PnP compiled as module... you might try to just load the module, I'm not on a linux computer right now but I'll take a look on my ystem later to give you the module name. But I'm pretty sure that kind of thing should be loaded at boot so it has to be in initrd (assuming Suse use initrd... initrd is a way to load module "driver" just "before" the system bootup, so you can have essential drivers compiled as optionnal module). I can't tell you for sure right now... post me the output of "dmesg" just after the boot (it's the kernel logging... lot of stuff, I warn you) and I could maybe tell you, by comparing the output with my own.
Yup - PnP is definitely there - lots of PnP-related messages in the log.

I've made some more progress - the issue is definitely ACPI-related. If I boot with "pci=noacpi", then everything works just fine. What I'm not sure about is what bad things may occur as a result of booting this way. I will post a question to that effect on the laptop forum, I think!

Very many thanks for all your assistance.
 
Old 07-05-2005, 07:54 AM   #8
Half_Elf
Guru
 
Registered: Sep 2001
Location: Montreal, Canada
Distribution: Slackware; Debian; Gentoo...
Posts: 2,163

Rep: Reputation: 45
Hmmm maybe I have it wrong since the beginning... maybe you should disable PnP? Back in old time, a lot of PCI device were having troubles with PnP, you often had to disable it. But these days, it should be pretty stable.

Giving "pci=noacpi" isn't a real problem, it shouldn't cause problem except maybe about hardwares able to suspend or to use power management, that you won't be able to use (might cause some bugs too I guess but I can't really tell you). If it works fine for you, it could be a possible fix I guess.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Bridging a wired network to a wifi network bobmcobob Linux - Wireless Networking 2 07-18-2008 06:36 PM
Totem-Xine only plays the first few seconds of a video in Firefox, then stops DaneM Ubuntu 1 10-20-2005 06:49 AM
ATI - fglrx - X runs 3 seconds then stops GuidoS Linux - Hardware 2 09-06-2004 12:37 PM
VNC Works then stops! Reboot fixes but then it stops again! Leethal Linux - Software 1 02-26-2004 07:57 AM
Multiple-OS-supported PCMCIA NIC works for a few seconds, then quits onu Linux - Laptop and Netbook 6 02-05-2004 12:55 PM


All times are GMT -5. The time now is 02:00 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration