Arch Linux

jvicory

Member

Registered: 2008-11-01

Posts: 8

[solved] network dies after 30 seconds

I just made a fresh install on an old Dell P4 I just inherited and I'm running into the most bizarre problem I think I've ever seen (then again, I've been awake for about 24 hours, so I'm probably missing something obvious).  When the system boots, the internet connection works fine.  If, immediately after logging in, I start a ping www.google.com, it gets up to between 25-30 for the sequence number before the network becomes non-responsive.  Nothing I've done will make it reconnect, not ifconfig down/up, dhcpcd detects nothing, etc.  If I unplug the network cable from the router and plug it back in, it will once again connect for the ~30 seconds as before, and then crap out again.

I just booted into a Xubuntu live cd and had no issues, so its not the hardware.  My rc.conf is standard stuff:

eth0="dhcp"
INTERFACES=(eth0)
ROUTES=(!gateway)

It should be working fine, as I have another Arch system on the same network using the same options with no problems.  Any ideas?

Last edited by jvicory (2009-07-22 19:53:30)

alienman

Member

From: Mexico

Registered: 2008-07-08

Posts: 106

Re: [solved] network dies after 30 seconds

Could you show us your daemons array in the rc.conf?
Maybe there's something wrong over there

---

ISC - Ignacio Marmolejo
ArchLinux & GNOME User.

jvicory

Member

Registered: 2008-11-01

Posts: 8

Re: [solved] network dies after 30 seconds

DAEMONS=(syslog-ng network netfs crond)

Just the default array.  The only things I've done on this system are go through the installer (had to use the CD since http/ftp wasn't working) then try to fix this problem.  Nothing except base, base-dev, and dhclient are installed (dhclient fared no better than dhcpcd did).

Vipes

Member

From: Okinawa, Japan

Registered: 2008-06-06

Posts: 14

Re: [solved] network dies after 30 seconds

Step down in your package of dhcpcd. I had the same problem but the network would die immediately after gaining an IP address. Stepping down to dhcpcd 5.0.4 fixed the issue.

---

Main Box: AMD Athlon 64 X2 Dual Core 6400+ @ 3.2Ghz, 4GB Kingston HyperX DDR2 PC6400 @ 4-4-4-12, eVGA NVidia 8800GTX w/ 768MB DDR3, Arch64 and Windows 7 64-bit on Dual boot
Laptops: Sony VPCF1 Arch64/Win7, Dell Inspiron E1705 Arch32.

jvicory

Member

Registered: 2008-11-01

Posts: 8

Re: [solved] network dies after 30 seconds

I was using the dhcpcd version included on the 2009.02 cd (4.0.10 I believe).  Since dhclient doesn't work either, I don't think its a dhcpcd issue.  Manually configuring the network like so:

eth0="eth0 192.168.1.104 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(eth0)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)

leads to the same problem.

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: [solved] network dies after 30 seconds

I guess you have done it already but did you take a look at the output of dmesg for any indication of the cause of the problem?

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

jvicory

Member

Registered: 2008-11-01

Posts: 8

Re: [solved] network dies after 30 seconds

I think I found the problem.  Turns out two modules were loading for my ethernet card, specifically the dmfe and tulip modules.  I changed rc.conf like so:

MODULES=(dmfe !tulip)

and have had a connection for 3 whole minutes now.  Apparently this isn't an unknown issue, as I searched google after I fixed the problem and saw a similar discussion and solution on a Debian mailing list.  If anyone is interested, the lscpi output for the card is:

Ethernet controller: Davicom Semiconductor, Inc.  21x4x DEC-Tulip compatible 10/100 Ethernet (rev 31)

Thanks for the help.