[Solved] wlan0 carrier timed out - AR9285

Good evening, fellows.
I've been reading this forums for some time now, and I've decided to register and to post a problem that probably has a simpler solution than what I'm thinking about right now.
So, I have a quick script for connecting to a WPA wlan0 address (home one), and I keep getting:
dhcpcd[...]: version 5.5.6 starting
dhcpcd[...]: wlan0: waiting for carrier
dhcpcd[...]: timed out
The script is:
#!/bin/bash
ip link set wlan0 down
rm /var/lib/dhcpcd/dhcpcd-wlan0.lease
rm /var/run/wpa_supplicant/wlan0
iwconfig wlan0 channel auto
ip link set wlan0 up
wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
dhcpcd wlan0
ip addr show wlan0
The strange part comes when I'm trying to run this script, as it has been working flawlessly until yesterday. Do you see anything strange?
lspci:
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
rc.conf daemons:
DAEMONS=(hwclock syslog-ng netfs sshd crond dbus)
(I've never needed any type of modules or modprobe configuration for this)
lsmod |grep ath:
ath9k 92940 0
ath9k_common 2096 1 ath9k
ath9k_hw 358828 2 ath9k_common,ath9k
ath 15393 3 ath9k_hw,ath9k_common,ath9k
mac80211 396060 1 ath9k
cfg80211 17621 3 mac80211,ath,ath9k
Also, I'm not on a graphical interface, but a console-only view. (aka I have to startx to logon onto xfce, but I rarely do). I'm using 3.3.1-1-ARCH kernel, might this be the same problem as exposed here?
Last edited by kseniya (2012-04-12 21:59:58)

.:B:. wrote:
If you're on kernel 3.3.1, there are issues with ath9k on that one. Either downgrade the kernel or install compat-wireless.
There are quite a few threads around there already... Can't miss them .
Yup, I bet the one that I was quoting on the last sentence might be one of those, sorry for the duplicity. However, I'd probably wait until 3.4, as it's now on rc2 -- maybe there we'll have that issue solved on both sides.
Thanks!

Similar Messages

[SOLVED] error: Resolving timed out after 10000 milliseconds

EDIT: it was a DNS lookup problem. I don't know why but it is better to manually specify nameservers in resolv.conf than in the home router control panel (a NETGEAR DGN2200v3). See the #3 post.
Hi
I just installed arch and I need to downgrade to xorg 1.12 to be able to use catalyst proprietary driver (legacy).
As I read into the wiki, I added the two required repos:
[catalyst-hd234k]
Server = http://catalyst.wirephire.com/repo/catalyst-hd234k/$arch
[xorg112]
Server = http://catalyst.wirephire.com/repo/xorg112/$arch
when I try to do an update, I get "database file does not exist".
In logs appears a curl error 28, timeout error, but the repository is online (I can ping it and I can browse its contents with firefox).
What can I do?
sudo LANG=C pacman -Syy
warning: database file for 'xorg112' does not exist
warning: database file for 'catalyst-hd234k' does not exist
:: Synchronizing package databases...
error: failed retrieving file 'xorg112.db' from catalyst.wirephire.com : Resolving timed out after 10000 milliseconds
error: failed to update xorg112 (download library error)
error: failed retrieving file 'catalyst-hd234k.db' from catalyst.wirephire.com : Resolving timed out after 10000 milliseconds
error: failed to update catalyst-hd234k (download library error)
core 105.0 KiB 122K/s 00:01 [######################] 100%
extra 1412.9 KiB 418K/s 00:03 [######################] 100%
community 1929.7 KiB 447K/s 00:04 [######################] 100%
multilib 95.7 KiB 115K/s 00:01 [######################] 100%
Last edited by yell! (2013-03-10 14:16:22)

yell! wrote:
thanks for replying. I edited the first post.
Solved:
After a lot of hours trying wget, aria2 and curl, with a lot of options, I just stopped observing pacman output behaviour in the console.
Seemed that it was a DNS lookup problem but, in my resolv.conf, the specified nameserver was my home router.
Anyway, I changed that specifying google's nameservers; is working now. It's a weird thing because in my homerouter I was already using google's nameservers.
Now I can open the repos in browser without lag.
Example of my resolv.conf:
Before:
# home router nameserver
nameserver 192.168.0.1
After:
#Google nameservers
nameserver 8.8.8.8
nameserver 8.8.4.4
Thanks you help me so much love you

[Solved] Shutdown - systemd timing out attempting to unmount NFS

I have the following line in /etc/fstab:
192.168.1.5:/srv/nsf4/main /shares nfs noauto,nofail,x-systemd.automount,_netdev,x-systemd.device-timeout=14,size=32768,wsize=32768 0 0
This works properly in the sense that systemd does not hold up the system when booting, and it does mount the directory upon first access, however the system hangs at shutdown in a manner consistent with systemd shutting down the network before attempting to unmount the drive. Indeed, even when the system is running, I can manually run
systemctl stop NetworkManager.service
and a call to
systemctl status shares.mount
shows that the mount is still active.
I can't attach anything, but here's a pastebin of my shutdown log:
http://pastebin.com/rTJxZDF5
Also, here's what I get from systemctl show shares.mount:
http://pastebin.com/a9ZUeX6z
Finally, I will describe the debugging I have done to this point. First, if I manually unmount the share before shutting down, it shuts down immediately. I am using systemd's automount option, however the same thing happens without automount (or fstab for that matter - simply manually mounting an NFS share and shutting down results in the shutdown taking about 2-3 minutes). I also added additional items to the Require= and After= lines for shares.mount, specifically I tried adding network.target, NetworkManager.service, and wpa_supplicant.service. In each case, I did observe that manually running
systemctl stop NetworkManager.service
(for instance) now did cause the share to be unmounted, however if I shutdown the computer without manually stopping NetworkManager.service, for instance, it would still stall for 2 minutes before timing out.
Last edited by process91 (2015-04-02 02:20:37)

I have had similar problems, although on my system, I use fstab to mount the NAS to /mnt and then I use bind mounts to mount NAS folders to my home directory.
Without the bind mounts everything worked perfectly. WIth the bind mounts, the system would hang on shutdown/reboot.
Unfortunately, I only experience this problem with NetworkManager. I use Gnome, so would love the network integration, but this issue is a deal breaker for me. Currently I use systemd-networkd with a custom extension to show network connectivity in the Gnome panel. The shutdown process works flawlessly (bind mounts and NAS mounts both mounted and unmounted without issue).
Obviously not an ideal solution, but perhaps try using something other then NetworkManager to see if you still experience issues, if not, it does isolate the issue to being a NetworkManager problem.
I do want to go back to NetworkManager for the integration with my desktop aspect, but for now I am happy with a working system without it.
Cheers.

[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..

[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.

[SOLVED] dhcpcd: timed out

I want to install Arch using wifi. I'm trying to connect to my WPA network before I even begin.
I did this (with my own network and passphrase in place)
wpa_passphrase mywireless "secretpassphrase"
wpa_passphrase mywireless "secretpassphrase" > /etc/wpa_supplicant.conf
ifconfig wlan0 up
wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
dhcpcd wlan0
And got:
dhcpcd: version 5.2.2 starting
dhcpcd: wlan0: waiting for carrier
dhcpcd: timed out
What's wrong?
EDIT: Long story. Wrong key
Last edited by RocketLauncher (2010-07-21 09:36:10)

Before starting dhcpd, make sure you are connected - run wpa_supplicant without the -B switch to check for errors.

[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.

ITunes connection has timed out - solved on Mac

I have a MacBook Pro, running OS 10.5.8. I am running iTunes 10.5. Every time I went to purchase an app thru the iTunes store, on login attempt, I'd receive an error message that the iTunes connection had timed out.
All of the Apple troubleshooting support I checked said to check the connection (duh), check the version of iTunes was current, and for Windows users, the version of IE. Check check check. Everything was fine.
I finally stumbled on this article first: http://support.apple.com/kb/ts3297
Following the steps as outlined, led to checking the firewall. Not understanding what step(5) meant "Reduce the restrictions on access in the firewall" because the connections for iTunes were allowed, I ended up clicking on the Advanced button, and then opening the console log. In the console log, I found numerous errors from "com.apple.kdcmond" that was attempting to access my computer. I was concerned it was some vicious attack on the computer, but after a search of "com.apple.kdcmond" found another post complaining of the same error messages that I was receiving. The clip from below was a response to fix the problem. I followed the directions.... as it said, my computer name was missing from the field where it belonged. Entering my hard drive name in the blank field, fixed my iTunes problem. Hope this helps someone else.
I just had the same problem. I solved it by going to the Sharing System Preference and entering my computer name, which was blank. It had been entered previously, and I'm not sure how it was deleted. At any rate, the error messages went away.

Just wanted to add, when I logged on earlier to post the first question, the message "Connection has timed out" seemed to happen within seconds. This was going from the log in page back to the forum page.
Sometimes, the message does not appear for a minute or so when loading a new page or as before, when going from one page to another within a domain.
This time, the forum page loaded without a problem and no error between log in page and returning to forum.
Therefore, this is an intermittent problem.
Suggestions?

How to up the timeout setting to solve password reset portal error "Authentication gate timed out waiting for a challenge response"?

Hi Everyone,
We have the password portal up and running on one box and another server with FIM R2 and SharePoint 2010. All is good with the exception that our end users typically get distracted during the password registration and/or reset process and receive:
"An error has occurred. Please try again, and if the problem persists, contact your help desk or system administrator. (Error 3000) ". The timeout kicks in after 5 minutes of inactivity in the browser.
The FIM Service log shows the following:
"Authentication gate timed out waiting for a challenge response".
I have confirmed that the default password portal web.config setting is <add key="SessionTimeoutInMinutes" value="20" />.
We have also updated Microsoft.ResourceManagement.Service.exe.config per this
article to the following but with no luck:
<resourceManagementClient resourceManagementServiceBaseAddress="myAddress" timeoutInMilliseconds="600000" />
<resourceManagementService externalHostName="myHost" dataReadTimeoutInSeconds="600" dataWriteTimeoutInSeconds="600"/>
We did not update the Windows SharePoint Servicesweb.config setting per the article about since we are on SharePoint 2010.
There is no NLB or firewall in front on this server.
If anyone has any solution to how to solve this on FIM R2/SharePoint 2010 please let me know.
Cheers!

FIM_Admin,
You could try changing the receiveTimeoutInSeconds parameter of the resourceManagementService node in your Microsoft.ResourceManagement.Service.exe.config file. However, you are warned not to do this unless instructed to by MS customer support.
http://msdn.microsoft.com/en-us/library/windows/desktop/ee652424(v=vs.100).aspx
http://technet.microsoft.com/en-us/library/ff800821(v=ws.10).aspx

[SOLVED] dmraid "Timed out waiting for device" at boot

Created a bug report with solution proposal: https://bugs.archlinux.org/task/33166
I created a virtual machine to demonstrate the problem
https://docs.google.com/open?id=0B40Hp1 … WZUQ21xZk0
The root and the other mount points are all on one raid disk. Although the root mounts quickly, other mount points cause timeouts at boot time.
dmraid prints that all /dev/mapper/isw_* devices are created.
I think /dev/disk/by-uuid/* links are created too, but for some reason systemd doesn't see them.
After boot I can execute "mount -a" without errors.
here's my fstab:
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=e89249d8-49a5-415b-8f9b-97de5cfbe82d / ext3 defaults
UUID=c37f8bdd-3d6c-495f-bf8a-5ef059e55254 swap swap defaults 0 0
UUID=91988343-dd89-43b9-8975-babb0b9510a2 /media/ARCHLINUXNEW ext4 nofail 0 1
UUID=62C813E9C813B9ED /media/distrpart ntfs-3g rw,nofail
UUID=E0A1-D623 /media/realboot vfat rw,codepage=866,iocharset=utf8,umask=002,noatime,nofail
# journalctl -b
Dec 15 00:25:24 localhost kernel: firewire_core 0000:05:03.0: created device fw0: GUID 0011d800017a5dd7, S400
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-E0A1\x2dD623.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/realboot.
Dec 15 00:26:50 localhost systemd[1]: Job media-realboot.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-62C813E9C813B9ED.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/distrpart.
Dec 15 00:26:50 localhost systemd[1]: Job media-distrpart.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/ARCHLINUXNEW.
Dec 15 00:26:50 localhost systemd[1]: Job media-ARCHLINUXNEW.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/91988343-dd89-43b9-8975-babb0b9510a2.
Dec 15 00:26:50 localhost systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.service/start failed with result 'dependency
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /dev/disk/by-uuid/c37f8bdd-3d6c-495f-bf8a-5ef059e55254.
Dec 15 00:26:50 localhost systemd[1]: Reached target Swap.
Note the 1.5 minute pause
# mount | grep /dev/mapper
/dev/mapper/isw_ebaifefjbf_Volume0p9 on / type ext3 (rw,relatime,stripe=64,data=ordered)
/dev/mapper/isw_ebaifefjbf_Volume0p1 on /media/realboot type vfat (rw,noatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp866,iocharset=utf8,shortname=mixed,errors=remount-ro)
/dev/mapper/isw_ebaifefjbf_Volume0p8 on /media/ARCHLINUXNEW type ext4 (rw,relatime,stripe=64,data=ordered)
/dev/mapper/isw_ebaifefjbf_Volume0p5 on /media/distrpart type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
Last edited by leniviy (2012-12-22 16:06:25)

I've ran into exactly same problem lately, but finally solved it.
Setup: Intel Fake RAID, mirror, partitioned as:
/dev/mapper/isw_dfjeffgfaj_rootvol1 /boot
/dev/mapper/isw_dfjeffgfaj_rootvol2 /
/dev/mapper/isw_dfjeffgfaj_rootvol3 /home (dm-crypted)
In /etc/fstab i had following mountpoints:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
/dev/mapper/isw_dfjeffgfaj_rootvolp1 /boot ext4 rw,relatime,data=ordered 0 2
and boot hung on waiting for /dev/mapper/isw_dfjeffgfaj_rootvolp1. Solution involves changing dev path to UUID:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
UUID=44809529-11d9-4f53-9652-7b97ed077225 /boot ext4 rw,relatime,data=ordered 0 2
For some reason symlinks /dev/mapper/isw* are not present during systemd mount.

[SOLVED] "eth1 timed out" but by iwconfig-command it works

Hi,
Strange, Im setting up my wireless with ipw2200-fw. I used the template-Network-Profile and changed the settings like this:
# Network Profile
DESCRIPTION="wifi profile"
# Network Settings
INTERFACE=eth1
HOSTNAME=myhostname
# Interface Settings (use IFOPTS="dhcp" for DHCP)
IFOPTS="dhcp"
#GATEWAY=192.168.0.1
# DNS Settings (optional)
# Wireless Settings (optional)
ESSID="essid"
KEY=1234567890
IWOPTS="mode managed essid $ESSID channel 11 key restricted $KEY"
#WIFI_INTERFACE=wlan0 # use this if you have a special wireless interface
# that is linked to the real $INTERFACE
#WIFI_WAIT=5 # seconds to wait for the wireless card to
# associate before bringing the interface up
#USEWPA="yes" # start wpa_supplicant with the profile
#WPAOPTS="" # use "" for normal operation or specify additional
# options (eg, "-D ipw")
# see /etc/wpa_supplicant.conf for configuration
#AUTOWPA="yes" # automatically configure WPA
#PASSKEY="" # wpa passkey/phrase. for use with AUTOWPA
When I boot up with kernel-option "net=home" it results in a "eth1 timed out". But if I use the following iwconfig-command, it works:
iwconfig eth1 mode managed essid "essid" channel 11 key restricted 1234567890
What is wrong with my config? Maybe the kernel-parameter is not correct?
Thanks for help.
Last edited by curana (2007-05-29 09:59:08)

that configurations are wrong.
http://wiki.archlinux.org/index.php/Con … or_DHCP_IP
btw the is no differences of packages between 2008.06 and 2009.02. that versions are for installers only. if you didn't know until now archlinux is a rolling release distributions.
Last edited by wonder (2009-02-19 00:53:24)

[Solved with dhcpcd-5.1.5-1] dhcpcd-5.1.4-1, timed out

Hello,
I experienced a timed out issue with the new release of dhcpcd. When launched, it indicates a time out, so it can't get information about the network. Downgrading to dhcpcd-5.1.3-1 is the only fix I found.
Is anyone else experiencing this upgrade issue ?
My ethernet card :
Ethernet controller: nVidia Corporation nForce2 Ethernet Controller
Last edited by keronn (2010-02-04 08:17:09)

I have the same problem. Thought it had something to do with the new version of dhcpcd, so I did a fresh install (it's a test machine), added dhcpcd in the IGNORE list and updated the system. The version of dhcpcd is 4.0.10-1 and the kernel is 2.6.32.3-1
Upon first reboot after the system update eth0 received an address, but every reboot since I experience the timeout problem. The DHCP server does acknowledge the test-machine, but the test-machine doesn't apply the address. Anyway it seems the problem isn't dhcpd as such, maybe a problem with a network driver in 2.6.32?
Edit:
Hmm.. There's 2 NIC's in the test-machine, but it seems random which module is loaded first and apparently what interface get the name eth0 and eth1. I remember that listing the modules in the right order in rc.conf can help, and upon reboot the test-machine correctly received a DHCP address! There's just one strange thing.. The 2. NIC (eth1) is set to a static address, but during my "debugging" I set it to DHCP so both NIC's should get an address from DHCP. However, when restarting the network ifconfig still reported that eth1 was set to the static address?? How could the static address be used when I commented that line out? As if rc.conf was not read?
Edit2:
So besides the weird static address thing (which doesn't matter now), DHCP works every time now when rebooting. BUT this is with the old dhcpcd. I haven't tried upgrading it and dhcpcd is still ignored in pacman.conf. Now that the test-machine is behaving I think I'll let it be, sorry to be such a chicken.. I'll keep an eye on this issue and hope it'll work with a new version of dhcpcd soon.
Last edited by numasan (2010-01-20 21:58:19)

[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)

Require help to solve Connection timed out error while reload initial data

Dear Developers,
I have installed SAP NetWeaver and SAP ME SDK 2.0 on my laptop and working from offshore, the SAP ME WIP and ODS database is situated at onsite. The installation is working fine, however, after developing Activity Hooks, at the step where I need to Reload Initial Data for the Site where I want the Activity to be used I get the below error message:
500 Connection timed out
Error: -5
Version: 7011
Component: ICM
Date/Time: Wed Mar 07 12:37:38 2012
Module: icxxthr.c
Line: 4184
Server: <laptop_hostname>_<SID>_00
Error Tag: {-}
Detail: Connection to partner timed out after 600s
© 2001-2009, SAP AG
How to find out what is causing this error? When I use the hostname of the onsite SAP ME application pointing to the same database, Reload Initial Data works fine. I need to reload initial data from laptop SAP ME application only, beacause the activity hook classes reside on my laptop, before I send the SAPME.sca files for common server build.

Hello,
Please try to increase PROCTIMEOUT ICM parameter for the corresponding server\port. If it does not help, please, check NW default traces for ME errors and share your results with us.
Best regards,
Alex.

Why can't I update my IPad 2 to IOS 5? Itunes always say "The connection has timed out" whenever I tried to update my IPad 2.

I've already tried my best to update my IPad 2 into IOS 5 since it's lunch into the world. So I open up my Itunes in my PC, connected my IPad 2 with the cable, and clicked "Update". So then I waited for a while till I finish all the steps or whatsoever. Then ITunes's bar showed something like "Downloading software for the IPad" "12 hours remaining" So then I waited and waited and waited, 9 hours are remaining and suddenly a window poped-up saying that my network connection had timed out and i had to try again even when my internet connection is really on the fast lane. I wonder if it's my IPad's problem or ITunes. Please help me to solve this problem.

Sadly there are some 'bad carriers' out there. If you have a VERY long download(and iPad OS updates can be 100s of megabytes) and the carrier has an interruption in service(router reboots, modem disconnects, etc) iTunes will timeout.
You might want to try updating later in the evening when usage starts to drop off(kids go to bed, people start watching cable instead of Netflix/Hulu) or early in the morning.
The other alternative is to update at a friend's place who might have a better carrier or is on a better subnet

[Solved] wlan0 carrier timed out - AR9285

Similar Messages

Maybe you are looking for