[SOLVED] Asus 1005PE ethernet | Atheros AR8132 | dhcpcd eth0:timed out

Hello, this was solved through the following process BUT:
pacman -Syu updated my system and kernel. After that update I needed
to reverse the line that I changed before in rc.conf. I change it back to
MODULes=() [removed !atl1c atl1e] which leads to atl1c being loaded
autmoatically. Seems they fixed the problem in a update.
These threads helped me:
( I )http://bbs.archlinux.org/viewtopic.php?id=78891
( II )http://www.ubuntugeek.com/howto-setup-n … aunty.html
Current driver for AR8132:
( III )AR81Family-linux-v1.0.1.6.tar.gz http://partner.atheros.com/Drivers.aspx
Hardware:
Asus eeePC 1005PE with Atheros AR8132 ethernet device.
uname -r:
2.6.30-ARCH
Problems:
eth0 not showing up at ifconfig
ethernet device not showing up at lspci
at boot error ar "Start Network"
dhcpcd: timed out
ridiculous count of errors Tx, Rx ..
Removing battery and power cord for a while and then booting without lan cable helped
recognizing the ethernet device at lspci (and eth0 at ifconfig if I remeber right). Plugging
the lan cable produced a high count of errors at Tx, Rx.
(II)
Get the driver (III) and get it ready(II):
tar -xzvf AR81Family-linux-v1.0.1.6.tar.gz
cd src
make
make install
(the note about "#define IRQ_HANDLED 1" (II) wasn't necessary for me. My guess is they updated the driver and it is no longer necessary.)
edit the /etc/rc.conf, prevent atl1c from loading, add atl1e:
MODULES=(!atl1c atl1e) [should look similar to this]
reboot
After reboot the error "dhcpcd: timed out" or "eth0: interface not found or invalid" was fixed,
"ping -c 3 www.google.com" was successful.
lsmod shows atl1e and ifconfig shows eth0.
I hope this is useful to someone, it took me a while to figure it out.
===================================================
O L D
===================================================
Hello,
I installed Arch yesterday on my Asus 1005PE and am trying to get online since.
Wired should be easier but there is a problem.
I am connecting through a router with DHCP. While booting it fails after
'Starting Network': 'dhcpcd: eth0: interface not found or invalid'
Same error when I enter '/etc/rc.d/network restart'.
ifconfig -a
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)
wlan0 Link encap:Ethernet HWaddr 00:25:D3:D8:CF:CA
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)
wmaster0 Link encap:UNSPEC HWaddr 00-25-D3-D8-CF-CA-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU:0 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)
lspci
( . . . nothing with Ethernet, just Intel, VGA, .. )
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
I think I saw the lan device recognised once, but rebooting doesn't help.
I read WPA encryption makes WLAN more complicated so I hope you can help me out with my wired connection.
- Felix
Last edited by phlex (2010-03-20 15:48:04)

This is already in my rc.conf:
MOD_AUTOLOAD="yes"
MODULES=()
USELVM="no"
HOSTNAME="newton"
eth0="dhcp"
INTERFACES=(eth0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
DAEMONS=(syslog-ng network netfs crond)
I don't see lines missing there.
Unplugging the power cord and removing the battery for some minutes helped somehow (found that odd tip through google). I booted without the lan cable connected and the Atheros AR8132 / L1c was recognized.
Got a new problem then. /etc/rc.d/network restart leads to:
:: Stopping Network [DONE]
:: Starting Network [BUSY]
dhcpcd: timed out
[FAIL]
dhcpcd eth0 leads to:
dhcpcd: version 5.0.6 starting
dhcpcd: eth0: waiting for carrier
dhcpcd: timed out
Suprisingly the 1005HA has the same ethernet device and should be working out of the box..

Similar Messages

[SOLVED] Issue with eth0 (eth0: timed out)

Hi there people, just installed Arch on my PC (again). The first time I had no problems with this, but now it is really bothering me. Well, my PC only access the net via wireless, so I have no wired connection for it. Here's my /etc/rc.conf:
# /etc/rc.conf
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid MySpot key ABCDEFABCDEF1234567ABCDEFC"
INTERFACES=(eth0 wlan0)
Well, everything is working fine, I can get access to the internet on bootup. My only concern is that my system is taking awfully long to boot. It takes about 1-2 minutes on "::Starting Network", then it shows me "eth0: timed out". Then it takes about 10 secs to start my wlan0 interface and the system finishes booting. I had previously installed Arch 2008.12, and the Starting Network only took about 10 secs to start my wlan0. I have already tried commenting out the eth0 line and putting a ! in front of eth0 on INTERFACES, but doing that only shows me an error message for my wlan0 and render my internet unusable on system bootup. So, my questions are:
1) Do I really need the eth0 interface for my connection (since I'm using wlan0 for wireless connection) ? Why can't I comment it out?
2) If I really need eth0, how can I make my boot time go faster, or how can I make it not time out?
Thanks in advance for any help given...
EDIT: problem solved, see Post 8 below for answers...
Last edited by gabscic (2009-03-25 03:40:43)

Thanks for answering. Well, I think eth0 is being detected correctly. Here is the output for ifconfig:
eth0 Link encap: Ethernet Hwaddr 00:18:F3:87:97:41
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)
Interrupt:19
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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap: Ethernet Hwaddr 00:15:AF:09:BC:E7
inet addr: 192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
RX packets:1903 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:615024 (606.6 Kb) TX bytes:1020 (1020.0 b)
wmaster0 Link encap: UNSPEC Hwaddr 00-15-AF-09-BC-E7-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING 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)
Well, I hope that can help. Searched the net and the forums, and every problem related to this is with people who are actually trying to use the eth0 interface for connection. In my case, I don't think I need it, I only need the wlan0. What I'm trying to do is get rid of eth0 while letting wlan0 work.

Toshiba Portégé M800-10C , eth0:timed out

So , i'm trying to install archlinux with the new archboot 2008.12 isos
Everything installed fine via a cd install (arch64), so i rebooted on my computer to find that internet via ethernet doesn't work.
Ethernet & Wifi worked just fine on linux mint or ubuntu 8.10
The boot-up process displays an "eth0: timed out" on startup, heres the output of lspci for ethernet and wifi :
07:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 12)
08:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
hwdetect --net
MODULES=(sky2 iwlagn iwlcore)
lsmod correctly shows that iwlagn and iwlcore are loaded
iwlwifi-5000-ucode is correctly installed
eth0 is correctly set as eth0=dhcp in /etc/rc.conf
running dhcpcd eth0 outputs :
eth0: dhcpcd 4.0.4 starting
eth0: broadcasting for a lease
eth0: timed out
Damn i want to use arch so bad :'( help !

mar00n wrote:P.S. I'd like to post the output of commands, but since I don't have internet access through Arch and I only have one PC, I have to reboot under windows to go on the forum...
Save the output to a file:
[karol@black ~]$ ifconfig -a > if.log
[karol@black ~]$ cat if.log
eth0 Link encap:Ethernet HWaddr 00:09:6B:F3:A8:42
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:939338 errors:0 dropped:0 overruns:0 frame:0
TX packets:251922 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1267079090 (1208.3 Mb) TX bytes:27331350 (26.0 Mb)
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:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:880 (880.0 b) TX bytes:880 (880.0 b)

Hi there can anyone help. I am connected to the internet by ethernet but my connection keeps timing out and my network diagnostics shows all green and network connection ok but still no internet connection. the other wireless laptop in my flat works well.

Hi there can anyone help. I am connected to the Internet by Ethernet but my connection keeps timing out and my network diagnostics shows all green and network connection ok but still no Internet connection. the other wireless laptop in my flat works well. Could the other wireless laptops being used in my flat be affecting my connection. what can I do to get connected, keep connected. Thanks for any ideas out there.

My network connected for a few hours then went back to timing out. I have not changed anything. However there four additional laptop users in my family who do not seem to be having any problems using their wireless connection. Could their film and music downloads be causing the timing out of my connection and if so is there a way I could prioritizes my computer or limit their use?

Ethernet Atheros AR8132 / L is gone after .34-update

The ethernet controller: 07:00.0 Ethernet controller: Atheros Communications Atheros AR8132 / L1c Gigabit Ethernet Adapter (rev c0)
was just not showing up anywhere after a update to .34 Has been working just fine until this update. Ifconfig was just displaying the lo interface after the update, which kind of baffled me - I didn't expect an ethernet network card to not work in a newer kernel.
Thanks to the wireless driver from AUR for my wifi card, I'm online again, but I would still like the ethernet card to work. Also, this should probably be reported somewhere upstream, if it isn't already? I feel a bit selfish when I fin a solution for mysel without sharing it the proper way to save others the trouble.
Last edited by naguz (2010-06-23 12:05:06)

Well, a "modprobe atl1c" makes my card (which is not th same as yours - which is even a wireless card, using a diferent driver, so probably no relevance) show up in networkmanager and ifconig output. I am currently moving, so I have no ethernet cable availible to see if it actually works. But strange that the driver is not detected and loaded automaticly.

[solved]eth0: timed out

Hi,
I am having problems getting internet connection bia ethernet.
I have no way of posting the exact files from the arch box, but here is my rc.conf network part:
eth0="dhcp"
INTERFACES=(eth0)
ROUTES=(!gateway)
And i can not connect
It always says it timed out.
Last edited by Fork (2008-06-20 22:43:22)

What is your router's IP address? That will be your gateway's address, and before the "ROUTES=(!gateway)" line, you need to put this:
gateway="default gw 192.168.0.1"
where 192.168.0.1 is the router's IP address; yours may differ (mine is 192.168.1.1, for example).
and it should connect. Also, you should make sure that the "network" daemon is up and running and is in the DAEMONS section at the bottom of /etc/rc.conf.
Last edited by kclive18 (2008-06-20 17:17:13)

Eth0 timed out after upgrade is driving me crazy!

I just updated my system, and my network has become unreachable, ifconfig shows some weird ip address and I'm REALLY lost here, did some research on the forums but nothing helped me...i think it is cuz of dhcpcd...i guess, added the -A option to it but did not work, and I also do not know how to downgrade the package to an older version to check whether that solves the issue..if someone could instruct me on what to do i'd really appreciate it....
well, thanks in advance for your answers, GO ARCH
Last edited by HighD (2007-11-05 07:19:30)

Hello could you please post here your rc.conf or network-profiles, also check daemon.log will by help full. If you use dhcpcd daemon, weird ip is assigned from /var/lib/dhcpcd/dhcpcd-eth*.info. So you could try remove that file, daemon will create new one.

When I try to dowwnload Firefox on my ASUS netbook, I get message "The operation timed out." and it doesn't load

ASUS model Eee PC 1015 PEB
Kaspersky
Windows 7

Hello,
What have you tried so far?
Can you try reinstalling Firefox? Uninstall it from your Control Panel > Programs and Features/Add or Remove Programs (if you want to keep your bookmarks and other information, do '''not''' delete personal information). After uninstalling, delete the Mozilla Firefox folder to remove any damaged files leftover from the uninstall (your profile is in a different location so will be unaffected by this):
* (32 bit installation) C:\Program Files\Mozilla Firefox
* (64 bit installation) C:\Program Files (x86)\Mozilla Firefox
Download and reinstall the latest copy:
* https://www.mozilla.org/en-US/firefox/all/
For more information, see
* http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Clean_reinstall

Dhcpcd is timing out.

Hello World (of Arch Linux awesomeness)!
I recently managed to acquire the guts to install the Arch OS which I had been hearing about a lot recently. I followed all of the instructions in the installer and the beginner's wiki, and now have a fresh install of Arch. Most of the choices I made were the defaults.
Now, this is the point that the beginner's wiki told me to set up my internet. I have an Airlink 101 card (awlh3028) which uses an rtl8185 chipset. From messing with this for a while in Ubuntu, I learned that the best way to get it working is using the Windows 98 drivers with ndiswrapper. I did that, and it worked.
When I backed up, I migrated everything to a data partition I have... except for the drivers. >.< Stupid me. Thankfully, I still have the cd with the drivers. I mounted the cd onto /media/cd. I then mounted my data partition onto /media/data. Then I ran the following command:
cp /media/cd/Drivers/Win98 /media/data/drivers
No dice. I tried moving the *.inf and *.sys files one-by-one. Still no dice.
Okay then, I thought. I told ndiswrapper to use the files off of the CD directly. I ran the following commands:
ndiswrapper -i /media/cd/Drivers/Win98
ndiswrapper -l
ndiswrapper -m
depmod -a
modprobe ndiswrapper
Then I edited my /etc/rc.conf and included ndiswrapper as a module.
Now
iwlist wlan0 scan
still gives me the error message:
Interface doesn't support scanning : Network is down
And at this point, I turn to the Arch Linux community I keep hearing so much praise about. I am by no means an experienced user, but if I don't understand something, I don't hesitate to look it up. Please help me.
Thank you!
Last edited by rednano12 (2009-10-26 01:17:40)

rednano12 wrote:
At fresh reboot after the change made to /etc/conf.d/dhcpcd
IEEE 802.11g ESSID: off/any
Mode:auto Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate: 54 Mb/s Tx-Power: 20dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc: 0 Missed beacon:0
Dont post the output after booting, I mean after associating:
Bring the interface up: "ifconfig wlan0 up"
Do "iwconfig wlan0 essid whatever key whatever" to try to associate with the access point first...
If after trying to associate "iwconfig wlan0" says "Access Point: Not-Associated" then keep retrying to associate (I remember that I had to do this with the latest install CD, it got fixed after updating the kernel/dhcpcd).
After it successfully associates (Access Point: so and so), post the output of "iwconfig wlan0"
The "-t 60" you copied into /etc/conf.d/dhcpcd increases the timeout to 60 secs, try increasing it.
e: Until you fix it with manual network setup, disable the network daemon in rc.conf. Something is telling me that /etc/conf.d/wireless isn't set up properly
And to make it a little easier on you: you don't have to reboot after dhcpcd/network modifications. ndiswrapper worked after rebooting because the alias (/etc/modprobe.d/ndiswrapper.conf) and the module (modprobe ndiswrapper) weren't set. Remember, Linux seldom needs to reboot.
Last edited by gog (2009-10-26 04:26:33)

Atheros AR8132 ethernet no longer detected?

Hello, all. I have an absolutely bizarre hardware issue (concerning the Atheros AR8132 PCI-E Fast Ethernet Controller) that has been giving me quite a bit of grief for a while, and having completely hit a wall on this one, I'm reaching out for help.
I'm a reasonably-experienced Linux user of several years, and had been running Ubuntu 9.10 on an Acer AOD250 netbook for several months out. I know that this model has wireless issues out-of-the-box (easily fixed), but it did not have any noticeable ethernet issues. That is, until I attempted an installation of Arch.
During the installation, the ethernet card was initially detected, but unable to be used (because of a bad module in the kernel released with the installer). As I didn't know the fix for this at the time, I decided to reinstall Ubuntu 9.10. This time, however, the system failed to recognize the wired ethernet whatsoever. Instead, the external activity lights for the port (green and orange) are ALWAYS on, yet the device doesn't function.
I have done a successful install of the latest drivers directly from Atheros for the device and have them automatically loading with the kernel during boot, but as the device isn't recognized, the drivers aren't doing any good.
Relevant information:
root@niobium:~# ifconfig -a
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:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)
pan0 Link encap:Ethernet HWaddr a2:13:34:bd:b2:bc
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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 0c:60:76:42:9c:fb
inet addr:192.168.1.107 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::e60:76ff:fe42:9cfb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5021 errors:0 dropped:0 overruns:0 frame:0
TX packets:3810 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5328753 (5.3 MB) TX bytes:739212 (739.2 KB)
root@niobium:~# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
01:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)
Judging by the name, the Atheros AR8123 uses a PCI-E (express) adapter. Especially curious is the following section of the output:
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
I suspect that my "lost" ethernet card may be on the mysteriously-absent Port 3.
My knowledge of hardware manipulation from the terminal is very limited, and I have no idea where to go from here, so any help will be greatly appreciated.

Well, since this was solved, I had a similar issue with a desktop computer that I built ~ 5 or 6 years ago. I had bought a mobo, it didn't work so I exchanged it for the same model. Got it home and Win XP installed, and found out that the on board network card had a mac address burned in of all 0's, so it didn't work. I didn't want to make the 2 hour round trip to the store again, so I threw in a linksys 10/100 and disabled the onboard lan and called it good. Years later I gave that machine to my parents, and years later again(two weaks ago) I replaced their router while I was visiting. That computer couldn't connect again, I finally figured out that even though the onboard lan was still disabled, windows was showing that card and not the linksys. So I enabled/disabled the bad card, and moved the good card up a pci slot and all was well.
Anyways, your problem reminded me of that, just wondering if it was a similar situation.

[SOLVED] dhcpcd@eth0.service failure

I am trying to move from initscripts to systemd on a server I have no physical access to (luckily I do have a rescue system...).
With only network left in DAEMONS, connectivity comes up just fine, and I see a "dhcpcd -q" process running in the background.
However, removing that last initscripts daemon and using [email protected] fails.
The server has eth0 only and a static IP.
% sudo systemctl start [email protected]
Job for [email protected] failed. See 'systemctl status [email protected]' and 'journalctl' for details.
% systemctl status [email protected]
[email protected] - dhcpcd on eth0
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
Active: failed (Result: resources) since Tue, 16 Oct 2012 11:26:05 +0200; 44s ago
Process: 14105 ExecStart=/sbin/dhcpcd -A -q -w %I (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/[email protected]/eth0
Oct 16 11:26:05 cutie.skaaf.net systemd[1]: Starting dhcpcd on eth0...
Oct 16 11:26:05 cutie.skaaf.net systemd[1]: Failed to start dhcpcd on eth0.
The relevant part of journalctl comes in two shapes, I'm not sure what that depends on.
Oct 16 11:26:05 xxx systemd[1]: Starting dhcpcd on eth0...
Oct 16 11:26:05 xxx dhcpcd[14105]: sending commands to master dhcpcd process
Oct 16 11:26:05 xxx dhcpcd[314]: control command: dhcpcd[14105]: sending commands to master dhcpcd process
Oct 16 11:26:05 xxx dhcpcd[314]: handle_args: no interface
Oct 16 11:26:05 xxx dhcpcd[314]: control command: /sbin/dhcpcd -A -q -w eth0
Oct 16 11:26:05 xxx systemd[1]: PID file /run/dhcpcd-eth0.pid not readable (yet?) after start.
Oct 16 11:26:05 xxx systemd[1]: Failed to start dhcpcd on eth0.
Oct 16 11:26:05 xxx systemd[1]: Unit [email protected] entered failed state.
and
Oct 16 11:27:14 xxx systemd[1]: Starting dhcpcd on eth0...
Oct 16 11:27:14 xxx dhcpcd[14145]: sending commands to master dhcpcd process
Oct 16 11:27:14 xxx dhcpcd[314]: control command: dhcpcd[14145]: sending commands to master dhcpcd process
Oct 16 11:27:14 xxx systemd[1]: PID file /run/dhcpcd-eth0.pid not readable (yet?) after start.
Oct 16 11:27:14 xxx systemd[1]: Failed to start dhcpcd on eth0.
Oct 16 11:27:14 xxx systemd[1]: Unit [email protected] entered failed state.
Now maybe this is trying to tell me that dhcpcd is already running? However the result is the same with "systemctl restart ...".
Upon boot up with no network DAEMON but [email protected] enabled, I simply can't get in.
I also tried editing /usr/lib/systemd/system/dhcpcd\@.service and making everything explicit in ExecStart, but I don't see any more useful output, and systemctl still claims the start failed.
Running dhcpcd eth0 explicitly gives no error exit code:
% sudo dhcpcd eth0
dhcpcd[14347]: sending commands to master dhcpcd process
Questions:
- why does systemctl think the start failed?
- can I find any more debugging info anywhere? Perhaps reboot with sytemd dhcpcd only and redirect journalctl logs to a text file that I can then view from the rescue system?
- why does network DAEMON manage to start dhcpcd, while systemd fails?
Thanks for any help or pointers in advance!
Last edited by nickray (2012-10-16 12:13:41)

Glad you got it working. I would go ahead and mark it as solved.
nickray wrote:Is there a way to do the "systemctl enable" from a rescue system (by editing some file), as was
possible before with /etc/rc.conf? Otherwise I would never have been able to solve this .
When you do a systemctl enable, it shows you what it's doing, making a symlink. If you need to do it by hand, you just have to make the appropriate symlink in /etc/systemd/system to the service file in /usr/lib/systemd/system
nickray wrote:Scimmia, any pointers to read more about the DHCD/DHCPCD issues?
The place I usually start is Wikipedia: http://en.wikipedia.org/wiki/Dhcp
To put it simply, it lets a DHCP client (dhcpcd = dhcp client daemon) request networking information from a DHCP server. The server selects an IP from the pool of IP addresses that it has, and sends that information back to the client along with all the other needed network configuration info. The client automatically configures everything and you're up and running without having to do any manual configuration at all.

Dhcpcd eth0 on every boot SOLVED

Hi, I just installed Duke on my IBM T30 and it won't connect to eth0 automatically.
I have to type "dhcpcd eth0" every boot and it connects OK.
Have I missed a setting somewhere?
Thanks for your help
Regards
Last edited by drum (2007-05-23 07:12:18)

Thanks
I read it and discovered there was a space between eth0 and the = sign.
Cheers mate all fixed

[Solved] Failing to start dhcpcd@eth0 inside libvirt-lxc vm

What the subject says.
I was thinking that this could be some systemd 197 related problem. I've downgraded
to 196 and the problem remains. I have the latest version of all packages (linux, libvirt, etc.)
See the log below, please. Note that the there is a eth0 interface.
[arch@gitolite ~]$ ip link
12: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 02:00:00:00:00:17 brd ff:ff:ff:ff:ff:ff
14: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
[arch@gitolite ~]$ sudo systemctl start dhcpcd@eth0
A dependency job for [email protected] failed. See 'journalctl -xn' for details.
[arch@gitolite ~]$ sudo journalctl -xn
-- Logs begin at Fri, 2013-01-18 18:32:42 UTC, end at Fri, 2013-01-18 22:32:09 U
Jan 18 22:29:58 gitolite sudo[45]: pam_unix(sudo:session): session opened for us
Jan 18 22:29:58 gitolite systemd[1]: Expecting device sys-subsystem-net-devices-
-- Subject: Unit sys-subsystem-net-devices-eth0.device has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d495
-- Unit sys-subsystem-net-devices-eth0.device has begun starting up.
Jan 18 22:31:28 gitolite systemd[1]: Job sys-subsystem-net-devices-eth0.device/s
Jan 18 22:31:28 gitolite systemd[1]: Timed out waiting for device sys-subsystem-
-- Subject: Unit sys-subsystem-net-devices-eth0.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c
-- Unit sys-subsystem-net-devices-eth0.device has failed.
-- The result is timeout.
Jan 18 22:31:28 gitolite systemd[1]: Dependency failed for dhcpcd on eth0.
-- Subject: Unit [email protected] has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c
-- Unit [email protected] has failed.
-- The result is dependency.
Jan 18 22:31:28 gitolite systemd[1]: Job [email protected]/start failed with r
Jan 18 22:31:28 gitolite systemd[1]: Job sys-subsystem-net-devices-eth0.device/s
Jan 18 22:31:28 gitolite sudo[45]: pam_unix(sudo:session): session closed for us
Jan 18 22:32:09 gitolite sudo[48]: arch : TTY=console ; PWD=/home/arch ; USER=ro
Jan 18 22:32:09 gitolite sudo[48]: pam_unix(sudo:session): session opened for us
libvirt configuration is simple:
<domain type='lxc'>
<name>gitolite</name>
<uuid>3122bf1d-11bb-0dd8-be64-7e352b3f8694</uuid>
<memory unit='KiB'>262144</memory>
<currentMemory unit='KiB'>262144</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='x86_64'>exe</type>
<init>/sbin/init</init>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/lib/libvirt/libvirt_lxc</emulator>
<filesystem type='mount' accessmode='passthrough'>
<source dir='/mnt/gitolite'/>
<target dir='/'/>
</filesystem>
<interface type='network'>
<mac address='02:00:00:00:00:17'/>
<source network='default'/>
</interface>
<console type='pty'>
<target type='lxc' port='0'/>
</console>
</devices>
</domain>
Can anyone help, please?
Last edited by masm (2013-01-25 21:12:30)

I'm trying to get this running without using systemd.
I restart the domain, and do
# ip link set eth0 up
# ip link show eth0
14: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 02:00:00:00:00:17 brd ff:ff:ff:ff:ff:ff
# dhcpcd eth0
dhcpcd[44]: version 5.6.4 starting
dhcpcd[44]: eth0: if_init: Read-only file system
dhcpcd[44]: eth0: interface not found or invalid
What does this mean? I googled for it, but didn'g find anything
In the guest, the only filesystem marked as read-only is /sys.
Any idea?

[SOLVED] Asus eee 1000H : netcfg and wicd unable to obtain IP

Hi,
I just installed arch linux on my asus eee 1000h, but I can't get
wireless to work. I installed the packages:
- wireless_tools
- netcfg
I have been reading through the beginners guide and the wireless setup guide,
but still no success.
I did
lspci | grep -i net
And found out I had to add the firmware for my card, so I did that and:
ifconfig wlan0 up
worked. So I did:
iwlist wlan0 scan
And found the network I wanted to connect too, so I do:
iwconfig wlan0 essid network_id key wep_hex_key
But I dont get associated to any access point, so I tried:
ifconfig wlan0 down
ifconfig wlan0 up
Sometimes this gets me associated to the access point, however, it seems to
be pretty unstable. Usually it 'looses' it's association after a short period
of time.
Then I do:
dhcpcd wlan0
However, I just get the output
dhcpcd: version 5.2.2 starting
dhcpcd: broadcasting for a lease
dhcpcd: timed out
I check "iwconfig wlan0" at it says it is still associated to the access point.
I have tried netcfg, but it also just get's timed out waiting for a lease.
I've tried to get this to work for a long time now, but can't seem to get it to
work. I've read somewhere that it might be a bug in dhcpcd? If you have a
suggestion for something to try, please keep in mind that I am not at all
familiar with arch linux and explain accordingly.
I installed arch linux because I want a distribution that forces me to learn
more about linux, I just did'nt think it would be this much trouble, been trying
for a couple of days now, I have allready learned alot though.
Thanks for any reply.
EDIT: I also tried setting the timeout to 120, it did not work
EDIT 2: I tried using netcfg again. It first returned:
WPA Authentication/Association Failed
I tried again, and it returned:
DHCP IP lease attempt failed
Does this mean I have to use wpa encryption? I find this
strange as I am connecting to the same network with
my ubuntu machine using wep encryption.
Last edited by khs (2011-04-20 12:31:28)

edit your /etc/rc.conf to blacklist all of the modules that interfere with the rt2860sta module:
MODULES=(!rt2800pci !rt61pci !rt2x00pci !rt2800usb !rt2800lib !rt2x00usb !rt2x00lib)
don't initialize network with any other services:
#eth0="dhcp"
#wlan0="dhcp"
INTERFACES=()
make sure you don't have conflicting daemons running:
DAEMONS=(syslog-ng dbus wicd netfs crond)
then restart and try again(or go through rmmod and stopping and starting the individual services)
btw... I am using arch+wicd on my eee 1000h to write this post, so if you have any more problems just let me know.
also check out the eee 901 archwiki page it has a lot of good info and links.
Last edited by trash (2011-04-20 00:23:21)

[solved] dhcpcd: timed out after reinstalling arch

Hi erveryone!
After reinstalling arch I can't connect to my wireless network anymore.
Typed:
wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant_vienna.conf
dhcpcd wlan0
Got:
dhcpcd: wlan0: waiting for carrier
dhcpcd: timed out
wpa_supplicant_vienna.conf (ssid and psk deleted):
network={
ssid=""
proto=RSN
pairwise=CCMP TKIP
key_mgmt=WPA-PSK
psk=
I reinstalled arch on my netbook at the same time and there's everything working fine (even with the same wireless-card). The only difference between the two systems is that my laptop has an i686 installation while on my netbook I've installed x86_64.
Things I've tried:
+ Update the system via wired-connection (mirrors.kernel.org) --> the download never gets faster than 10KB/s (?).
+ Configure the wireless interface via netcfg --> same problem
+ Reinstalled again and only changed LOCALE in /etc/rc.conf --> same problem
So you may see, I have no idea what I could be doing wrong and hope that theres anybody out there who knows what to do!
P.S. Well, i have now by-passed my problem.
1.) Created a list of packages installed during system-update on my netbook.
2.) In this list I changed package-name-x86_64.tar.gz to package-name-i686.tar.gz
3.) Downloaded the list with wget.
4.) Ccopied the packages to my laptop
5.) Created a local repository and made a system-update.
Last edited by kronfeld (2010-05-04 17:34:43)

Hi trusktr
This might seem stupid but are you sure you are using "eth0" and not "eth1" etc.? As an example I have two on-board lans and I'm plugged into eth1. I had to change rc.conf as it defaults to using eth0.
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth1="dhcp"
INTERFACES=(eth1)
Since I am using eth1 and not eth0 here is what I get when I try:
ifconfig eth0:
eth0 Link encap:Ethernet HWaddr 00:04:4B:00:88:0E
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)
Interrupt:23 Base address:0x6000
Look familiar?
I'm not saying this is the case but it could be something as simple as that.
ifconfig -a
should show you how many lans you have.
Thought I would drop the obvious first in case that's all it is.

[SOLVED] Asus 1005PE ethernet | Atheros AR8132 | dhcpcd eth0:timed out

Similar Messages

Maybe you are looking for