You are not logged in.
- Topics: Active | Unanswered
#1 2005-07-14 02:36:09
- tdphys
- Member
- From: Lower Mainland
- Registered: 2005-06-14
- Posts: 50
rc wierdness with network
So when the network daemon is started during init, it fails, whether I have it in the rc.conf, or even just called at the end of rc.local. But after a log in as root and run it, it works...
What gives?
I have two cards, using eth1.
rc.conf network stuff:
lo="lo 127.0.0.1"
#eth0=""
eth1="dhcp"
INTERFACES=(lo !eth0 eth1)Offline
#2 2005-07-14 03:25:24
- phrakture
- Arch Overlord
- From: behind you
- Registered: 2003-10-29
- Posts: 7,879
- Website
Re: rc wierdness with network
if your network module available when that get's called (are you using hotplug?) - please post both your DAEMONS and MODULES arrays from rc.conf
Offline
#3 2005-07-16 16:03:56
- tdphys
- Member
- From: Lower Mainland
- Registered: 2005-06-14
- Posts: 50
Re: rc wierdness with network
Okay, here they are
MODULES=(!usbserial !ide-scsi)
DAEMONS=(syslog-ng hotplug !pcmcia netfs crond !network !gdm cups)I don't have much in the MODULES, but shouldn't hotplug be loading the appropriate ones anyway?
network and gdm are both commented out because they were giving me problems. I load gdm at the end of rc.local, and now it works, but that hack doesn't work for the network daemon
Offline
#4 2005-07-16 21:16:09
- CyberTron
- Member
- From: Gotland ,Sweden
- Registered: 2005-03-17
- Posts: 645
- Website
Re: rc wierdness with network
for once, you have commented out network !!
*my 50 cents*
http://www.linuxportalen.com -> Linux Help portal for Linux and ArchLinux (in swedish)
Dell Inspiron 8500
Kernel 2.6.14-archck1 (selfcompiled)
Enlightenment 17
Offline
#5 2005-07-16 21:33:58
- Snowman
- Developer/Forum Fellow
- From: Montreal, Canada
- Registered: 2004-08-20
- Posts: 5,212
Re: rc wierdness with network
It won't solve your network problem, but netfs should be listed after network.
Offline
#6 2005-07-16 21:46:57
- sudman1
- Member
- From: Huntingdon, UK
- Registered: 2005-02-18
- Posts: 143
Re: rc wierdness with network
I installed arch on a new system last week and I get the same error on init, but I'm able to get out to my network and the internet just fine after I log in, so I've just been disregarding the error.
v/r
Suds
Offline
#7 2005-07-18 15:00:18
- tdphys
- Member
- From: Lower Mainland
- Registered: 2005-06-14
- Posts: 50
Re: rc wierdness with network
Actually , the network is commented out because it wasn't working and I didn't want to wait for it 
Offline
#8 2005-07-25 05:02:59
- mvdlubbe
- Member
- Registered: 2004-05-13
- Posts: 14
Re: rc wierdness with network
I'm having the same issue.
When booting, the network fails. Right after logging in, when I su and /etc/rc.d/network start, it does start.
in /var/log/errors.log it says
dhcpcd [2739: timed out waiting for a valid DHCP server response
Which could indicate a problem with the DHCP server but the other clients in the network are working (and not running arch).
Offline
#9 2005-07-26 17:04:55
- mvdlubbe
- Member
- Registered: 2004-05-13
- Posts: 14
Re: rc wierdness with network
It seems to me to be something with the (new) forcedeth.
Just after installing a new Arch from 0.7 base cd, there is no problem, the network starts immediately.
Then, after pacman -Syu, it only starts after logging in. But there's more. When not loading the module in rc.conf, but modprobing it from the shell, you can't immediately start the network either, it fails. Then, after 5-10 seconds, /etc/rc.d/network start does work.
Having no desire to dig deeper than this, I use hotplug to address my other onboard NIC, this works fine. And with great quickness.
So, just use another NIC. 
.
Offline