You are not logged in.
Pages: 1
Hey there,
a small intro. I'v used linux slightly before casually, but now i wanted to learn more and dig abit deeper. So i figured Archi would be perfect for that.
Did the net core install to my PC, everything seemed to go nicely cept one thing. When i boot my machine i ged network deamon [FAIL] error. So i cant connect to internet. But the weirdest thing is when i do # /etc/rc.d/network restart i get [DONE] and everything is fine. I could make a script that manually restarts the network daemon afther login, but its not the solution in my eyes
So i would really appreciate if you cold help me
Some conf files that could help:
#ifconfig
eth0 Link encap:Ethernet HWaddr 00:18:F3:A4:8D:85
inet addr:192.168.3.207 Bcast:192.168.3.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58624 errors:0 dropped:0 overruns:0 frame:0
TX packets:318 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9192317 (8.7 Mb) TX bytes:49323 (48.1 Kb)
Interrupt:21 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
network part of my rc.conf file:
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)
# 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)
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
part of my /var/log/daemon.log when i log:
Jul 7 17:09:30 nanduko init: Entering runlevel: 3
Jul 7 17:09:30 nanduko dhcpcd[3881]: version 5.2.5 starting
Jul 7 17:09:30 nanduko dhcpcd[3881]: eth0: rebinding lease of 192.168.3.207
Jul 7 17:09:40 nanduko dhcpcd[3881]: eth0: broadcasting for a lease
Jul 7 17:10:00 nanduko dhcpcd[3881]: timed out
Jul 7 17:10:00 nanduko dhcpcd[3881]: allowing 8 seconds for IPv4LL timeout
Jul 7 17:10:07 nanduko dhcpcd[3881]: eth0: offered 192.168.3.207 from 192.168.2.1
Jul 7 17:10:07 nanduko dhcpcd[3881]: eth0: acknowledged 192.168.3.207 from 192.168.2.1
Jul 7 17:10:07 nanduko dhcpcd[3881]: eth0: checking for 192.168.3.207
Jul 7 17:10:08 nanduko dhcpcd[3881]: timed out
Jul 7 18:02:11 nanduko init: Switching to runlevel: 6
Jul 7 18:02:52 nanduko init: Entering runlevel: 3
Jul 7 18:02:52 nanduko dhcpcd[3883]: version 5.2.5 starting
Jul 7 18:02:52 nanduko dhcpcd[3883]: eth0: rebinding lease of 192.168.3.207
Jul 7 18:03:02 nanduko dhcpcd[3883]: eth0: broadcasting for a lease
Jul 7 18:03:22 nanduko dhcpcd[3883]: timed out
Jul 7 18:04:29 nanduko init: Switching to runlevel: 6
Jul 7 18:05:09 nanduko init: Entering runlevel: 3
Jul 7 18:05:09 nanduko dhcpcd[3860]: version 5.2.5 starting
Jul 7 18:05:09 nanduko dhcpcd[3860]: eth0: rebinding lease of 192.168.3.207
Jul 7 18:05:19 nanduko dhcpcd[3860]: eth0: broadcasting for a lease
Jul 7 18:05:39 nanduko dhcpcd[3860]: timed out
Jul 7 18:13:04 nanduko dhcpcd[3942]: version 5.2.5 starting
Jul 7 18:13:04 nanduko dhcpcd[3942]: eth0: rebinding lease of 192.168.3.207
Jul 7 18:13:04 nanduko dhcpcd[3942]: eth0: acknowledged 192.168.3.207 from 192.168.2.1
Jul 7 18:13:04 nanduko dhcpcd[3942]: eth0: checking for 192.168.3.207
Jul 7 18:13:08 nanduko dhcpcd[3942]: eth0: leased 192.168.3.207 for 21600 seconds
Jul 7 18:13:08 nanduko dhcpcd[3942]: forked to background, child pid 3963
Jul 7 21:13:08 nanduko dhcpcd[3963]: eth0: renewing lease of 192.168.3.207
Offline
Hi,
As a Arch newbie myself I can't really say that I can fix your problem but I can contribute my findings.
I had the same problem as you, network connection failed during boot up but it was no problem getting connected after boot up. I assume that you use some sort of display manager ? In that case you can install [wiki]wicd[/wiki]. Just follow the wiki page to set it up. Works like a charm for me. I also tried Networkmanager but I couldn't enable my wireless with that let alone connect to the internet.
Hopefully I could help.:)
Last edited by Varg (2010-07-08 09:32:18)
github - tweets
avatar: The Oathmeal
Offline
Some more info would be nice.
How are you connected to the internet? Are you connected to a LAN? Can you communicate within the LAN?
Offline
Hi,
As a Arch newbie myself I can't really say that I can fix your problem but I can contribute my findings.
I had the same problem as you, network connection failed during boot up but it was no problem getting connected after boot up. I assume that you use some sort of display manager ? In that case you can install [wiki]wicd[/wiki]. Just follow the wiki page to set it up. Works like a charm for me. I also tried Networkmanager but I couldn't enable my wireless with that let alone connect to the internet.Hopefully I could help.:)
Do you have the appropriate wireless drivers and firmware?
Offline
Varg wrote:....
Do you have the appropriate wireless drivers and firmware?
I think so. At first it just didn't start at boot up but worked fine when I manually started it. With wicd there is no problem, I log in to KDE and as soon as the wicd icon is in the system tray I get the message connection established.
Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
Subsystem: AMBIT Microsystem Corp. AR5BXB63 802.11bg NIC
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f0400000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [60] Express Legacy Endpoint, MSI 00
Capabilities: [90] MSI-X: Enable- Count=1 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Kernel driver in use: ath5k
Kernel modules: ath5k
Last edited by Varg (2010-07-08 10:46:31)
github - tweets
avatar: The Oathmeal
Offline
tobier wrote:Varg wrote:....
Do you have the appropriate wireless drivers and firmware?
I think so. At first it just didn't start at boot up but worked fine when I manually started it. With wicd there is no problem, I log in to KDE and as soon as the wicd icon is in the system tray I get the message connection established.
Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01) Subsystem: AMBIT Microsystem Corp. AR5BXB63 802.11bg NIC Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at f0400000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Count=1 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Kernel driver in use: ath5k Kernel modules: ath5k
Oh right, apparently I didn't read your post properly, sorry Seems to me like you have all the proper drivers etc.
EDIT: confused some stuff, nevermind.
Last edited by tobier (2010-07-08 11:07:38)
Offline
Klaabu, what does your DAEMONS=() line (in /etc/rc.conf) look like?
Also, checkout the Troubleshooting section at http://wiki.archlinux.org/index.php/Network, there's some info on DHCP issues.
Last edited by murffatksig (2010-07-08 20:54:46)
"Oh, they have the internet on computers now."
Offline
Hey again and thanks for all the replies. The community rocks here
i gave some misleading information on my first post. As i say-d on bootup network daemon [FAILS] and if i log in my
#ifconfig looks like this actually:
eth0 Link encap:Ethernet HWaddr 00:18:F3:A4:8D:85
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:49 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6316 (6.1 Kb) TX bytes:1872 (1.8 Kb)
Interrupt:21 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
so i have no net and cant ping my LAN
after i do /rc.d/network restart i get ip adress from dhcp and everything is OK. So drivers should be ok maby some modules wont get loaded before
network daemon wants to start?
@murffatksig
my Deamons part in rc.conf looks like this:
DAEMONS=(@syslog-ng network netfs @crond sshd)
Best,
klaabu
Offline
Pages: 1