You are not logged in.

#1 2009-08-17 11:46:12

NoOrdinary
Member
Registered: 2008-08-08
Posts: 6

[SOLVED] network randomly doesn't work after reboot (e100)

Hi
Lately I have some weird issues with network. I shutdown computer during night, so basicly I reboot it at least once per day and every now and then without any pattern network doesn't work at all and so far only solution I have found is to reboot (again).
Before anything else I'm sure it's not hardware problem, since other OS on same computer don't have any issues, neither is router since other devices in network from laptops to mobile phones work flawless.
Relevant info and what I have found so far (not everything is copy/pasted so there may be some typos):

$less rc.conf (network part)
eth1="eth1 192.168.1.242 netmask 255.255.255.0 broadcast 192.168.1.255
INTERFACES=(eth1)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)

$ifconfig
eth1      Link encap:Ethernet  HWaddr 00:D0:B7:5A:7A:A9  
          inet addr:192.168.1.242  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:380 errors:0 dropped:0 overruns:0 frame:0
          TX packets:380 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:36154 (35.3 Kb)  TX bytes:36154 (35.3 Kb)

$route
Kernel IP routing table
Destination     Gateway         Genmask           Flags Metric Ref      Use Iface
192.168.1.0    *                    255.255.255.0    U      0        0            0 eth1
default           192.168.1.1     0.0.0.0               UG    0        0            0 eth1

$ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data
From 192.168.1.242 icmp_seq=2 Destination Host Unreachable
...

So basicly network is dead, can't even ping router, cable connection is detected tho (lights are on). I have tried to restart newtork with /etc/rc.d/network stop/start, nothing. Only clue is dmesg.

$dmesg
Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
...
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
e100 0000:03:07.0: PME# disabled
e100: eth1: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
e100 0000:03:07.0: firmware: requesting e100/d101m_ucode.bin
ADDRCONF(NETDEV_UP): eth1: link is not ready

modrope -r e100 and then reloading it doesn't help either, but reboot does (once I had to reboot twice tho).
Anyone with more clue and ideas then me, it's getting really annoying, it also kill whole KDE plasma-desktop for couple of minutes before plasmoids find out network is really down and I'm not really fan of morning "gamble". I can't pinpoint some hard date/update when this started to happening because like I said it's random but last couple of months should be quite accurate. Thanks in advance.

EDIT: dmesg when network works:

tilen@pikmin ~]$ dmesg | grep e100
pci 0000:03:07.0: Firmware left e100 interrupts enabled; disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
e100 0000:03:07.0: PME# disabled
e100: eth0: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9

Last edited by NoOrdinary (2009-09-05 09:47:20)

Offline

#2 2009-08-26 21:14:04

neddie_seagoon
Member
Registered: 2009-08-23
Posts: 121

Re: [SOLVED] network randomly doesn't work after reboot (e100)

ADDRCONF(NETDEV_UP): eth1: link is not ready

Maybe you have already tried this, but when the network is off and the above message is in dmesg, have you tried unplugging and plugging in the network cable? Maybe it is just not detecting that it is actually plugged in.

Offline

#3 2009-08-27 02:24:33

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [SOLVED] network randomly doesn't work after reboot (e100)

actually, if the "other OS" is windows, this in some curcumstances is "normal" and related to the way how windows handles some devices (including net cards) at restart/shutdown. This is particularly prominent for some mobos (check web)
It is possible then that the spcific way of handling network devices by other OS is causing problems.

Offline

#4 2009-08-27 15:50:26

fowler
Member
Registered: 2009-01-26
Posts: 152

Re: [SOLVED] network randomly doesn't work after reboot (e100)

I have this same issue.

Offline

#5 2009-08-29 19:24:51

NoOrdinary
Member
Registered: 2008-08-08
Posts: 6

Re: [SOLVED] network randomly doesn't work after reboot (e100)

The other OS is Windows 7 RC, but I don't log into them sometimes for weeks so this can happen straight from arch shutdown-boot cycle. I have tried trick with cable, no success, also tried to reboot router and other such stuff.
I didn't encounter this problem since the latest kernel upgrade tho, but I noticed this warning in windows (MS windows smile ) event viewer: "Adapter Intel(R) PRO/100+ Management Adapter: Adapter Link Down" that repeat daily, so maybe it's hardware related. Weird is just that connection stay online all the time in win (well also in arch once it works it's rock stable).
I'm a bit occupied with work at the moment but I'll update if I find anything, in the meantime I'm still open for all suggestions and thanks for all the help so far.

Offline

#6 2009-09-02 07:43:49

mandog
Member
From: Peru
Registered: 2008-09-17
Posts: 218

Re: [SOLVED] network randomly doesn't work after reboot (e100)

How have you got your router set up if your is set up with your password and ip + mac details you don't need all that info in your r.c conf file this is mine

# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="xxxx"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth1="dhcp")
# Wireless: See network profiles below
#
eth1="dhcp"
INTERFACES=(eth1)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(gateway)

That is it set to auto config I have XP, WIN7, BSD, and a couple of other distros all setup this way.


I'm dyslexic Please do not complain about puntuation or spelling and remember most dyslexic people have above average iq.

Offline

#7 2009-09-02 09:50:20

NoOrdinary
Member
Registered: 2008-08-08
Posts: 6

Re: [SOLVED] network randomly doesn't work after reboot (e100)

I don't have anything special set at router but I doubt rc.conf play any role. I will try to set it up with dhcp (but I think I have tried that already) if there is any change.
This morning I had to reboot twice, so new kernel didn't help. Fowler, what network card are you using, also e100 (well or some intel)? I dunno, should this be handed to the kernel team? If it will piss me enough one morning I'll just go and buy a new network card, just wanna be sure that will really solve the problem.

UPDATE: OK, this is just silly. I remebered I have acctualy onboard LAN so I edited rc.conf and dived into the dust under my desk to move cable and there I found out it was acctual onboard in use all the time neutral Now this dosen't make much sense to me anymore, when I can't get net up all the stuff in dmesg is e100 related. Anyway, I connected network to e100 and rebooted, suprise, same story. Dmesg reported again link was not ready. I edited rc.conf to

INTERFACES=(eth0 !eth1)

in case this has anything to do with proper timing at assigning whatever needs to be assigned to network cards at boot so I'm sure just 1 card with all info provided get's kicked in at boot. First reboot after that works, it dosen't prove anything yet but at leat it's some kind of progress in recognising proper cause.

UPDATE 2: Nah, still happens. Googling for "no link during initialization" show a lot of familiar problems, almost all on nforce motherboards and mine is nforce too. I just don't get it why this mess seperate PCI network card. In any case it's extremely annoying.

Last edited by NoOrdinary (2009-09-02 11:46:27)

Offline

#8 2009-09-05 09:54:26

NoOrdinary
Member
Registered: 2008-08-08
Posts: 6

Re: [SOLVED] network randomly doesn't work after reboot (e100)

I'm still not 100% sure but I think physicaly removing the intel network card from the box eliminate the problem. So now just onboard LAN is present.
My motherboard is Asus P5N-E SLI with nvidia chipset, "problematic" network card was Intel e100, router is Linksys WRT54GL with original firmware (some were reporting chanign router helped in similar problems) if anyone will encounter same problem.

Offline

Board footer

Powered by FluxBB