Network must be restarted after boot finishes

Shofs · 2005-03-14 19:53:50

Hello,
Something is messed up. I have to manually /etc/rc.d/network restart after every boot to get the network up and running. I realized that I didn't have 8139too in the modules array in rc.conf at first, then added it, but that didn't solve my problem. This is an integrated network device.

phrakture · 2005-03-14 20:55:15

hmmm you can try changing the timeout in /etc/conf.d/dhcpcd - do you have a slow network/dhcp server that would need more than 10 seconds to determine your address?
I seem to recall others having this issue, but can't recall what the solution was.

Shofs · 2005-03-14 21:01:13

I use a static address. This is going to be a new server, therefore important I can reboot it remotely and not worry.

phrakture · 2005-03-14 21:05:40

hmmm... well, maybe you'd want to move the network daemon to the end of the daemons list (and don't background it, if you're doing that)

Shofs · 2005-03-14 21:09:53

MODULES=(!usbserial !ide-scsi 8139too)

eth0="eth0 192.168.2.202 netmask 255.255.255.0 broadcast 192.168.2.255"
INTERFACES=(lo eth0)

gateway="default gw 192.168.2.1"
ROUTES=(gateway)

DAEMONS=(syslog-ng hotplug !pcmcia network @sshd @netfs @crond)

All I really could do is move crond. I guess it is worth a shot, but not a great option in case I ever have network cron job that needs to be run right away. I will try it though.

phrakture · 2005-03-14 21:12:08

yeah, best bet is to try and read through the rc.sysinit and figure out what isn't there that needs to be there.... I'm really at a loss... sorry

Shofs · 2005-03-14 21:15:27

Does anyone think hotplug may have something to do with this?

Here is some more info:

[root@stilletto ~]# lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 630 Host (rev 21)
00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 83)
00:01.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07)
00:01.3 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07)
00:02.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
00:0f.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
00:0f.1 Communication controller: C-Media Electronics Inc CM8738 (rev 20)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] SiS630 GUI Accelerator+3D (rev 21)

EDIT: MORE INFO

less /var/log/errors.log
Mar 14 13:24:59 stilletto pciehp: add_host_bridge: status 5
Mar 14 13:24:59 stilletto pciehp: Fails to gain control of native hot-plug
Mar 14 13:25:06 stilletto eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
Mar 14 13:32:35 stilletto pciehp: add_host_bridge: status 5
Mar 14 13:32:35 stilletto pciehp: Fails to gain control of native hot-plug
Mar 14 13:32:42 stilletto eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
Mar 14 13:36:31 stilletto pciehp: add_host_bridge: status 5
Mar 14 13:36:31 stilletto pciehp: Fails to gain control of native hot-plug
Mar 14 13:36:38 stilletto eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
Mar 14 13:39:20 stilletto pciehp: add_host_bridge: status 5
Mar 14 13:39:20 stilletto pciehp: Fails to gain control of native hot-plug
Mar 14 13:39:27 stilletto eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)

I don't use firewire ethernet . . . hmmm.

Shofs · 2005-03-14 21:41:35

Moving the network daemon before hotplug seems to fix the problem temporarily. I will still try to find out the root of the problem and fix it.

EDIT:

Scratch that. I can only access the box form within my network. It can't see out either.

This is from an ssh session.

[root@stilletto ~]# ping google.com
connect: Network is unreachable
[root@stilletto ~]# /etc/rc.d/network restart && exit
Network is not running.  Try 'network start'
:: Starting Network

dtw · 2005-03-15 05:23:15

mmm - i already suggested in another thread - just cos network is "not running" doesn't mean your interfaces are not up - it can bring you interfaces up fine but the daemon can still fail

Arch Linux

#1 2005-03-14 19:53:50

Network must be restarted after boot finishes

#2 2005-03-14 20:55:15

Re: Network must be restarted after boot finishes

#3 2005-03-14 21:01:13

Re: Network must be restarted after boot finishes

#4 2005-03-14 21:05:40

Re: Network must be restarted after boot finishes

#5 2005-03-14 21:09:53

Re: Network must be restarted after boot finishes

#6 2005-03-14 21:12:08

Re: Network must be restarted after boot finishes

#7 2005-03-14 21:15:27

Re: Network must be restarted after boot finishes

#8 2005-03-14 21:41:35

Re: Network must be restarted after boot finishes

#9 2005-03-15 05:23:15

Re: Network must be restarted after boot finishes

Board footer