You are not logged in.
i installed ntp package with pacman. followed the wiki guide.
i don't know if my network not working has anything to do with that but anyhow,
i have to do "dhcpcd eth0" manuall now after each log in to get it working. what could be the problem?
thanks in advance
/etc/rc.conf :
http://rafb.net/paste/results/4fBFLQ74.html
syslog.log :
http://rafb.net/paste/results/0VZgiO87. … LrL45.html
Offline
What output do you get when you run
/etc/rc.d/network start
? Are you using the Arch64 port? There's a bug regarding the /etc/rc.d/network-script. Check Arch64 FAQ for the solution.
A bus station is where a bus stops.
A train station is where a train stops.
On my desk I have a workstation.
Offline
What output do you get when you run
/etc/rc.d/network start
? Are you using the Arch64 port? There's a bug regarding the /etc/rc.d/network-script. Check Arch64 FAQ for the solution.
i can connect after boot if i do
# dhcpcd eth0
manually.
Anyhow, this is what i get:
[root@box vladuz976]# /etc/rc.d/network start
:: Starting Network [BUSY] DHCP Client Daemon v.1.3.22-pl4
Copyright (C) 1996 - 1997 Yoichi Hariguchi <yoichi@fore.com>
Copyright (C) January, 1998 Sergei Viznyuk <sv@phystech.com>
Location: http://www.phystech.com/download/
Usage: dhcpcd [-dknrBCDHNRSTY] [-l leasetime] [-h hostname] [-t timeout]
[-i vendorClassID] [-I ClientID] [-c filename] [-s [ipaddr]]
[-w windowsize] [-L ConfigDir] [-G [gateway]] [interface]
[FAIL]
[root@box vladuz976]#
i'm also not using the arch64 port.
i looked more into the ntp thing since all this happend after installing the ntp package and editing the /etc/ntp.conf file
i edit the file according to the wiki. but after boot the file is overwritten to it's original contenct. no idea how and why.
i removed the package with "pacman -Rs ntp" and took the "ntpd" out of the DAEMONS in /etc/rc.conf
my /etc/rc.conf has
MODULES=(8139too snd-pcm-oss snd-cmipci)
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
DAEMONS=(syslog-ng hwd network netfs crond alsa sshd)
i just don't see why it wouldn't start the network.
Offline
You get output from dhcpcd when you run the /etc/rc.d/network so there must be something wrong with the syntax. Check out the network-script and change the "dchpcd" command in it.
A bus station is where a bus stops.
A train station is where a train stops.
On my desk I have a workstation.
Offline
i can't find a mistake anywhere. can someone help looking?
Offline
Could you post the contents of /etc/conf.d/dhcpcd? It contains the arguments that are passed to the dhcp client, and as far as I can tell, that is the part where the network start script chokes.
Offline
Could you post the contents of /etc/conf.d/dhcpcd? It contains the arguments that are passed to the dhcp client, and as far as I can tell, that is the part where the network start script chokes.
I helped fix this last night over IRC. If you notice that the network script seems to spew "dhcpcd --help" type info (implying an invalid argument). It turns out that the DHCP_ARGS had "-h -N $HOSTNAME".
-h takes an argument ($HOSTNAME) and -N was placed in the middle. Moving the -N to the end (or removing it altogether) fixed the problem.
Offline
sh__ wrote:Could you post the contents of /etc/conf.d/dhcpcd? It contains the arguments that are passed to the dhcp client, and as far as I can tell, that is the part where the network start script chokes.
I helped fix this last night over IRC. If you notice that the network script seems to spew "dhcpcd --help" type info (implying an invalid argument). It turns out that the DHCP_ARGS had "-h -N $HOSTNAME".
-h takes an argument ($HOSTNAME) and -N was placed in the middle. Moving the -N to the end (or removing it altogether) fixed the problem.
That's right!!!!
Getting rid of the "-N" fixes it!
just interesting how it got there in the first place.
thanks again!!
Offline