Wlan0 dhcpcd timeout on no carrier issue

Ok so after trying to fix this problem myself and google coming up with nothing relevant i come here asking for help.
I havent had a problem with my wireless since installing Arch but recently its been giving me alot of trouble.
in wicd it cant see any of the networks (i can still connect if i plug in an ethernet cable) and when i ifconfig it doesnt show up with wlan0
So i tried # ifconfig wlan0 up and then it shows up and manually i cant iwlist wlan0 scan and it will actually scan and show the ap's in the area and i can even iwconfig wlan0 essid "essid" and then iwconfig will show me connected but when i try and dhcpcd wlan0 it says
dhcpcd[1420]: version 5.2.12 starting
dhcpcd[1420]: wlan0: waiting for carrier
dhcpcd[1420]: timed out
and thats it.
I connected to the hardline and updated everything and it still does that
catting out /sys/class/net/wlan0/carrier displays 0
I use ath5k as my driver and am using the most up-to-date default kernel.
any help would be great!

markbabc wrote:
My bad i read that as "is it your wireless card"
lspci says its
01:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
and in /etc/rc.conf my daemons array is
DAEMONS=(@syslong-ng @dbus !netfs @crond @alsa @wicd @sshd)
but thats been like that for a long time and hasnt been edited in a few months
That is my card and I use ath5k as well.  The fact that your interface isn't showing up would seem to point to a problem with your ath5k module.  Are you sure it is loading properly?  Perhaps you could try a modprobe ath5k and see if that doesn't improve things for you.  You could try these instructions and see if they don't help you:
https://wiki.archlinux.org/index.php/Wi … etup#ath5k
Also, do not enable the network daemon.  You should not have any other networking daemons active except wicd.  See the wicd page for an example daemons array:
https://wiki.archlinux.org/index.php/Wicd#Initial_Setup
Last edited by the sad clown (2011-04-20 02:12:56)

Similar Messages

  • 3G only connects Whatsapp and not other apps (NOT a carrier issue)

    Hi.
    Starting around 10 days ago, the 3G connection on my iPhone 4s suddenly stopped working. I cannot check email, browse anything, open any social media BUT Whatsapp, or play games online. Here's what I have done to try to fix it:
    1. Turning on Airplane Mode for a few seconds and turning it back off. Result: not ok.
    2. Resetting the network setting. Result: not ok.
    3. Contacting my carrier. Result: was suggested to change the APN.
    4. Changing the APN. Result: not ok.
    5. Rebooting the phone before Airplane Mode & Reset Network. Result: not ok.
    6. Rebooting the phone after Airplane Mode & Reset Network. Result: not ok.
    7. Reset All Settings. Result: not ok.
    8. Changing the sim card (same carrier that has data plan). Result: not ok. Meaning the issue is with the phone?
    9. Restoring to factory setting. Result: STILL NOT OK.
    10. Comparing setting with other iPhone 4s in the same area with same carrier & data plan. Result: all settings are exactly the same.
    11. Trying my sim card on another iPhone 4s. Result: works perfectly. So it's not a carrier issue, right?
    If I recall correctly, it started happening after I synced my music. I reverted the sync mid-way, because it was about to copy some songs I don't want to copy. Then I re-synced.
    It should NOT be the problem, but it cannot be a coincidence? Because I never changed any other setting or do anything unusual.
    Additional details:
    1. My phone is NOT jailbroken.
    2. I always purchase legally.
    3. 3G works to chat on Whatsapp, but I'm not able to download the media shared on Whatsapp no matter how small the size.
    4. Notification from Facebook and Echofon works fine.
    5. Sometimes when I open Echofon after a reboot tweets show up. Media on Whatsapp also already downloaded. But they don't continue showing up/not updating in real time.
    6. I have just updated to iOS 6.1.3, but the problem started before I updated and I think I only skipped 6.1.2, meaning my 3G did not work with 6.1.1 (the supposed correction to 6.1 with 3G issue), so I don't think it's an iOS issue.
    I'm so sorry for the long post, but I need to make it all clear. So... help? I'm desperate.
    Thanks, guys!

    UPDATE #2:
    I chatted with Ashley from Apple Support yesterday and she suggested me to restore the phone and set it up AS NEW, NOT restore from backup.
    And it worked!
    Of course, you have to back up everything, but I have my contacts, notes, and pictures on iCloud. All I did was merge them back to the phone from iCloud Setting.
    One downside: you'll lose all text messages. But it's worth it.
    So, thank you, Ashley!

  • How to fix a carrier issue

    Hello
    I have a Iphone 5S that is suppose to work on verizon but it wont so i called Apple and they told me it sounds like a carrier issue
    so this phone is unlocked but its shows at&t on apple system so i called at&t and they have no records of the phone so how do i fix this
    the phone was replace about 4 weeks ago by apple
    not to sure what to do
    please help

    Take it back to the Apple Store where you got it replaced. It sounds like you go the wrong phone.

  • Carrier issues, Iphone 3gs: Carrier is in the carrier list but does not connect = no service

    Right introduction, I live in the country signal for iphones under 02 in my area is 3-4 bars of GPRS signal. This is plenty to make and receive calls, texts and all that as use home wifi for internet simple. Everything working fine for about a year of having the phone, then did updates and started to see the "no service"  almost all the time and had to place my iphone in a signal spot just to get 1-2 bars and couldn't touch it without dropping out! Basically I could not use it at all and the crap about the signal now showing true signal is rubbish as before i could make calls fine and no drops, but now due to "no service" i can't make any calls or texts or anything. I have a ipod touch when nothing HAS CHANGED other than i can think when the update to 4.0 came along! I have been living with this for almost a year. I have done every possible solution, apple stores, 02 stores, new sim cards (many), every type of phone resetting possible, manually turning off 3g and other settings to turning everything off bar just basic GPRS signal. Network resets everything possible no joy what so ever.
    I have been paying for a year now for a phone that i can't use anywhere other than right next to a signal tower! Yes the phone connects to GPRS, EDGE, 3G when in town but just about. Before these problems i could get max 3G signal in my local town no issues but now struggle to get 1 bar of 3g in a town as well. The problem is I used to be able to use my phone as a phone where i needed to use the phone. Now i can't use the phone anywhere and get drop calls all the time when i do manage to get signal!!!!!!!
    Now i can't even connect to 02, yet at home under a manual carrier search all UK networks appear on the list including 02, I click on 02 and it comes up with the warning "network lost see settings" So my phone CAN find signal but does not connect to 02. This has been the case for a long time now and as stated before several sim cards latter and plenty of trips to apple and changes of phone make NO difference which makes me believe this is a software issue on apple's part. I only started getting these issues when the iphone 4 came out and updated the ios. Now what can i do, i can not downgrade the ios as i never jailbreaked my phone so don't have the files stored that i should to be able downgrade. Apple are offering 0 help with this, all i want to do is smash it to bits as it no longer works as a phone. I have to use a 10 year old nokia to call and actually use my contract that I PAY FOR. I PAID FOR MY PHONE and just after the warranty runs out as well and it seems all a software problem.
    I have searched all over the net to find no solutions to my problems this is a last resort before i do actually smash the thing and I love apple to bits but come on a simple software issue.
    I mean isn't it silly that i can't downgrade my ios and that apple don't support this and yet my issue seems to lie in there update.
    I know that the signal update reworked the algorithm to show true signal XXXXXXXXXXXXXXX um no it doesn't as now i have 0 signal as before i had no problems what so ever with dropping calls and the signal showing right so WHY WHY WHY.
    Please help I am so frustrated with things and need to solve this issue. Please ask anymore questions if you want more details about anything, i need to sort this out please.
    By the way i am running ios 4.3.3 yet bellow in the options this is not stated?? I have been updating hoping that it gets solved but only seems to get worse the more i update.
    Thanks
    James
    Thanks
    James

    Same problems, unfortunatley I updated to 5.0 1 hour before going on holiday for three weeks and no way to restore my phone to try to remove it.At the same time, drop outs, range problems and the most annoying was my music and apps were corrupted and would not function properly :-(

  • HT4528 I just bought a new 4s and I can't send or receive texts. Also when anyone calls me it comes up as unknown but I transferred all my contacts. Is this a carrier issue or is this my device?

    I just bought a new 4s and I can't send or receive texts. Also when anyone calls it comes up as "unknown" but I transferred all my contacts. Is this a device issue or a carrier problem?? I've tried everything. Reset the network and some a hard reset but no changes.

    I believe the root cause is IOS5.01. same problem on my iphone4s with IOS5.01. Now I have a expensive I-touch!  wake up steve.............. I suggest you change your sim cark from 64k to 128k. or just waiting next generation IOS.

  • 3GS Carrier Issue

    Hi all, our chairman has an issue with his 3GS. When he goes abroad it doesn't automatically select a carrier for him. He has to manually go in to the settings and search for one.
    I've never seen this before. Does anyone have a solution?!

    I've been having echo problems every since I got my new iPhone 4S.  My problem is different though.  I have not heard an echo of my voice ever...but the people I am talking to on the other end are getting an echo of their voice.  This only happens to them when they talk to me with my new phone and it's many different people.  It doesn't seem to matter if I'm talking to them on their land line or a mobile line.
    I had Apple swap the phone for a new one two weeks ago and I am still having the same problem...if in so fact that they actually swapped the phone.  They said they did.
    Today I went back to Apple and they wiped the phone clean and reinstalled the software, thinking that maybe it's a software problem.  Still didn't fix the problem.  I might be super unlucky and received two faulty phones, if so Apple has a big problem on their hands.
    Adjusting the volume on my phone while in a conversation doesn't really seem to help much.  Also, it doesn't happen on every call or the entire time I'm in the call.  Usually starts up about a minute or two into the conversation.
    HELP!

  • ZEN StonePlus-Semaphore timeout period expired+firmware issue

    Hello, im new here, i apolgize if the topic with same problem already exist. (i found similar, but from 2007.)
    I have a problem with my Zen Stone Plus 2GB. The firmware is broken i think. It wont turn up, pc wont recognize it in any way.
    I tried this :
    http://forums.creative.com/t5/MP3-Pl...67B37F890FAA05
    Hey I keep replying to myself. But this time it's good news, I've fixed the problem!
    Here are the steps I performed:
    . Put the player in recovery mode with these instructions (I was only able to do this once so follow the instructions carefully):
    Here are the instructions:
    a. Download and install the Mass Storage Drivers from the website.
    b. Press and hold the Play button while connecting your player to the PC. If you have a one-piece player then remove the battery first.
    c. Keep pressing Play until the New Hardware Wizard starts - this will only happen the first time you put your player into Recovery Mode.
    d. Complete the New Hardware Wizard.
    To check that you are in Recovery Mode open Device Manager (right-click My Computer and choose Properties, then the Hardware tab and Device Manager) and look for a Player Recovery Device entry.
    When in Recovery Mode you can reload the firmware.
    2. DO NOT INSTALL THE RIGHT FIRMWARE FOR ZEN STONE PLUS, instead upload the firmware for the MuVo player: http://files.creative.com/manualdn/D...W_LF__2_03.exe
    3. After the firmware has been updated go into recovery mode again but this time upload the correct firmware for Zen Stone Plus: http://is.europe.creative.com/suppor...ame=Windows+XP
    VOILA! The player has risen from death and can continue to be enjoyed!
    And this says the same :
    http://www.mycreativefansite.com/200...ue-on-zen.html
    NOW what I have done :
    . Installed drivers for creative players from their site [done]
    2. Inserted the player to the PC [done]
    3. Installed the "MP3 Player Recovery Device Drivers" (mentioned in above link) [done]
    4. My player is now in "recovery mode" it was recognized as "Player recovery device" [done]
    5. I tried to install the firmware for MUVO players (again see the link above) but it came up with the "Operating system reported error: The semaphore timeout period has expired" [fail]
    6. I tried to install the latest Zen Stone Plus firmware from creative site but again - "Operating system reported error: The semaphore timeout period has expired" [fail]
    http://img97.imageshack.us/img97/430/aerhbae.th.jpg - picture here !
    I tried MUVO V200.
    That error should came up within the installation of ZEN firmware, not the MUVO firmware. But my problem is : The MUVO firmware does the same error as the ZEN firmware.
    I also tried different firmware, for MUVO T200. It wont even turn on the update - "Your player is not connected, please connect your player" it says.
    Reseted milion times and the battery is charged by the way.
    ps : sorry for my english
    Thanks for your help !

    Anyone?

  • Telemarketing call filter app on iphone 5: Apple-Carrier issue?

    I am on my second iphone (5) and probably my last.  Besides the awful iMaps, I still cannot get an app to manage annoying telemarketing calls.  I was told by one of my business customers Apple does not allow them in the App Store due to contractual restrictions with ATT and Verizon.  Can anyone confirm this is true?  If so, it is definitely my last iphone and good by to Verizon at the end of my contract.

    You need to register your number with the federal Do Not Call list if you have not. If the calls you are receiving are from companies you have not done business with, are currently doing business with, or affiliates of companies you have/are doing business with then they shouldn't be calling you after your number is placed on the list (it may take up to 30 days I believe for the rolls to update). Otherwise, this isn't an iPhone issue. It wouldn't matter what phone you were using...telemarketers can call you if they have your number and you are not on the Do Not Call list. Also, tell the telemarketer that is contacting you that you want them to remove you from their calling list. They must do this if you request it. As mentioned, you can block some numbers either with the free option or with the monthly option.

  • Force fsck on boot and timeout waiting for device issues [SOLVED]

    Archlinux starts checking fs on every boot since linux and systemd packages were updated last night.
    systemd --->213-5
    linux ---->3.14.5-1
    Another issue appears with last update
    Timed out waiting for device dev-disk-by\x2duuid-9f780ada\x2d0671\
    Dependency failed for /dev/disk/by-uuid/9f780ada-0671-43d8-b036-f9
    Dependency failed for Swap.
    I have this issue on my laptop which was updated yesterday.I have also desktop running archlinux again I've just checked out the systemd and linux versions.The systemd package is not the latest one it's 212-3.I havent any problem on that machine.I guess systemd is responsible of this cause.
    I've just reboot and realized that systemd-fsck says Super block last write is in the future.Date and time is correct in BIOS same as on linux
    Last edited by gecici90 (2014-06-05 21:10:52)

    I had the same problem, I get in the recovery console after forced fsck.
    But downgrading systemd and systemd-sysvcompat to their previous version made it all work back again.
    The sorted list of the upgraded packages:
    [2014-06-05 21:11] [PACMAN] installed libx264 (1:142.20140311-4)
    [2014-06-05 21:11] [PACMAN] upgraded btrfs-progs (3.14.1-1 -> 3.14.2-2)
    [2014-06-05 21:11] [PACMAN] upgraded cifs-utils (6.2-1 -> 6.3-1)
    [2014-06-05 21:11] [PACMAN] upgraded imagemagick (6.8.9.1-2 -> 6.8.9.1-3)
    [2014-06-05 21:11] [PACMAN] upgraded filesystem (2013.05-2 -> 2014.05-2)
    [2014-06-05 21:11] [PACMAN] upgraded lib32-libdbus (1.8.0-1 -> 1.8.2-1)
    [2014-06-05 21:11] [PACMAN] upgraded libproxy (0.4.11-2 -> 0.4.11-3)
    [2014-06-05 21:11] [PACMAN] upgraded libpurple (2.10.9-1 -> 2.10.9-2)
    [2014-06-05 21:11] [PACMAN] upgraded libsystemd (212-3 -> 213-5)
    [2014-06-05 21:11] [PACMAN] upgraded libwbclient (4.1.7-1 -> 4.1.8-1)
    [2014-06-05 21:11] [PACMAN] upgraded openssl (1.0.1.g-1 -> 1.0.1.h-1)
    [2014-06-05 21:11] [PACMAN] upgraded perl (5.18.2-2 -> 5.20.0-2)
    [2014-06-05 21:11] [PACMAN] upgraded perl-xml-parser (2.41-4 -> 2.41-5)
    [2014-06-05 21:11] [PACMAN] upgraded perl-yaml-syck (1.27-1 -> 1.27-2)
    [2014-06-05 21:11] [PACMAN] upgraded pidgin (2.10.9-1 -> 2.10.9-2)
    [2014-06-05 21:11] [PACMAN] upgraded postgresql-libs (9.3.4-1 -> 9.3.4-2)
    [2014-06-05 21:11] [PACMAN] upgraded python2 (2.7.6-3 -> 2.7.7-1)
    [2014-06-05 21:11] [PACMAN] upgraded smbclient (4.1.7-1 -> 4.1.8-1)
    [2014-06-05 21:11] [PACMAN] upgraded subversion (1.8.9-1 -> 1.8.9-2)
    [2014-06-05 21:11] [PACMAN] upgraded systemd (212-3 -> 213-5)
    [2014-06-05 21:11] [PACMAN] upgraded systemd-sysvcompat (212-3 -> 213-5)
    [2014-06-05 21:11] [PACMAN] upgraded x264 (1:142.20140311-1 -> 1:142.20140311-4)
    [2014-06-05 21:11] [PACMAN] upgraded xchat (2.8.8-13 -> 2.8.8-14)
    [2014-06-05 21:11] [PACMAN] upgraded xfconf (4.10.0-3 -> 4.10.0-4)
    Downgrading systemd and systemd-sysvcompat makes my computer boots normally:
    [2014-06-05 21:43] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/systemd-212-3-x86_64.pkg.tar.xz /var/cache/pacman/pkg/systemd-sysvcompat-212-3-x86_64.pkg.tar.xz'
    [2014-06-05 21:43] [PACMAN] downgraded systemd (213-5 -> 212-3)
    [2014-06-05 21:43] [PACMAN] downgraded systemd-sysvcompat (213-5 -> 212-3)

  • HT4528 Carrier issue. Help!

    I have an iphone 4 under verizon wireless. Ive recently divorced and I was on my ex-wifes plan. I now have a new number under sprint. I need to know how i can get the carrier on my phones software switched from verizon to sprint, so that sprint will allow me to use it, otherwise they will not accept it. They want me to purchase thier phone of course. I know it can be done, but sprint refuses, claiming it cannot be done. Its simply a matter of switching the carrier to sprint instead of verizon on the phone itself. How do i go about this? PLEASE HELP ASAP!!! Thank you!
    If needed, my contact info is as follows, though i do not usually answer unknown calls on the first try, so you may need to leave a message so i know what the call is pertaining to. Thank you SO much to whomever can help me!
    Randy Folks
    mobile #: 352-727-6611
    email: [email protected]
    Again, i have an iphone 4 (NOT a 4 S) and simply need to know what it takes to switch the carrier from verizon to sprint on the phone software so that sprint will allow me to use it instead of buying ANOTHER iphone from them instead of using the perfectly good phone I already own. THANK YOU SO MUCH FOR ANY HELP!
    Regards,
    Randy
    Message was edited by: Snarfle

    Noble Seven wrote:
    I imagine if you could get Verizon to unlock the phone, then it wouldn't be difficult to get the device on Sprint. Have you asked Verizon about unlocking it?
    Verizon does NOT unlock the CDMA portion of the iphone.  That phone will never be able to be used on Sprint. 

  • Carrier issues

    My carrier says that i can go onto itunes and change my phone carrier to make it sim free but how do I go about doing this? what link should i go onto, I can't see any options.

    The carreir would have to unlock the iphone.
    If they offer this service, then they would unlock it and e-mail you with instructions on how to complete the unlock. This includes restoring as new.

  • My iphone 4s has a built in app called "voice Memos".  A colleague has an iPhone 4 unit which does not have this app. This has beem on my previous models.  Has it been discontinued? Is  it a carrier issue?

    "1  Which iphone models have the built in VOICE MEMOS app?  My 4S model has this, and i have also had this on my previous model.  A colleague has an iphone 4, and it is not showing.
    #2  Also, my 4S has a smart keyboard with the microphone icon to the left of the spacebar.  Which models have this?

    1) Either your friend has moved the icon into a folder or onto another screen, or they do not have a real iPhone (or their phone is jailbroken). It is present on all iPhones and can not be deleted.
    2) The 4S and higher have that. It requires Siri, which does not exist on the iPhone 4 and earlier.

  • Eth0 cold plug = ok but eth0 hotplug = no carrier

    Hello,
    I have a Lenovo ThinkPad Edge 13, i3 380UM.
    I have netcfg installed, but I only use it for wifi with wifi-select
    in my rc.conf I have:
    eth0="dhcp"
    INTERFACES=(eth0)
    DAEMONS=( @microcode @syslog-ng @network @crond @dbus @slim @alsa @laptop-mode )
    When I boot with plugged cable in eth0, the wired network work without any problem.
    But, if I boot, THEN plug a cable, restarting /etc/rc.d/network fails, dhcpcd give a "no carrier" error, and manual addressing with route / ifconfig doesn't help either.
    Please any idea?
    I saw http://ubuntuforums.org/archive/index.php/t-741147.html but in my case, I have alway separate interface for wired (eth0) en wifi (wlan0)

    Hello, this may be caused by PCI power management.
    What is the output of
    ip link show eth0
    If the line contains "NO-CARRIER" even though there's a cable connected to your eth0 port, it is possible that the device was auto-suspended and the media sense feature doesn't work. To solve this, first you need to find your ethernet controllers PCI address by
    lspci
    in my case the output looks like this:
    00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06)
    So the address is 00:19.0.
    Now let's check the PM status of the device by issuing
    cat "/sys/bus/pci/devices/0000:00:19.0/power/control"
    substituting 00:19.0 with the address obtained from lspci.
    If the output reads "auto", you can try to bring the device out of suspend by
    echo on > "/sys/bus/pci/devices/0000:00:19.0/power/control"
    Don't forget to substitute the address again.

  • Wireless issues

    I have a broadcom chipset wireless card. I installed b43 firmware and my card goes up with iwconfig wlan0 up but when i try to assign an ip with dhcpcd it sends a timeout error
    # dhcpcd wlan0
    dhcpcd[2214]: version 5.2.8 starting
    dhcpcd[2214]: wlan0: waiting for carrier
    dhcpcd[2214]: timed out
    With my eth0 no problems

    jacopastorius82 wrote:Now i think i have to install network manager gnome applet?
    And what have i to do when i move to a house with a new router? Just use network manager?
    network-manager-applet should do the trick.  Personally, I use wicd.  Six of one, half dozen of the other...
    Now, about security.  There are three types you will encounter on 802.11:
    WEP : The original 802.11 protocol, cracking tools were developed years ago so it should not be considered as secure.  It does keep every iphone or android passing by from using your connection.  Connection can be handled directly by iwconfig by just setting a key.
    WPA, WPA2:  Much stronger encryption (WPA2 much more so ... it uses AES encryption)
    To deal with WPA encrypted links, take a look at and install wpa_supplicant.  It integrates with network manager.
    So with networkmanger, the aplet, and wpa_supplicant, your system should have an applet that tells you about the available networks, manages their pass keys, and allows you to associate with them.
    Is the Dlink router yours?  If so, you really should look at locking it down.  Use its management interface to set the password, change the ESSID, enable encryption (at least WEP).  If you are paranoid, go with WPA.  If you are really paranoid, hide the access point by disabling the ESSID broadcast (Although it will no longer show up on your scans)
    If you leave your access point open, you are just inviting script kiddies from using your connection for something you may not condone (spam, porn, music downloading, etc...)
    edit fixed typo
    Last edited by ewaller (2010-10-31 16:57:29)

  • Intel4965 | Association/DHCP | Status Issue

    I can't reliably connect to any network. I have tried just iwconfig, wpa_supplicant, and netcfg with archassistant, and I can't figure out what the problem is.
    Generally, to connect I have to run these commands, and this will "usually", but NOT always get me connected to a WEP network.
    iwconfig wlan0 essid APNAME
    iwconfig wlan0 key 1234567890
    dhcpcd wlan0 <times out everytime>
    iwlist wlan0 scan <always shows results, although for 2 kernel revisions it didn't>
    rm /var/run/dhcpcd-wlan0.pid
    dhcpcd wlan0<finally works>
    Information/things I have tried.
    The 4965 module is in my modules array.
    ifconfig wlan0 up
    doesn't help.
    Putting 'wlan0' in the interfaces array in rc.conf doesn't help.
    I was able to connect with wpa_supplicant a few minutes ago. I still had to do that dhcpcd and iwlist stuff, but it worked.
    Then I put
    wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
    in my rc.local(command I used to get it working the first time, except the -B) and restarted. Starting up wpa_gui showed that I was associated, but I could not get an IP address. I disconnected, reconnected, did the dhcpcd stuff, and nothing
    Netcfg also didn't work. On launching archassistant, and then trying to connect to one of the profiles I set up through archassistant, I get this;
    wireless device set in config :
    wireless device used : wlan0
    profile started : npnwap 1
    error issuing netcfg command.
    Double clicking the archassistant icon in the tray, or trying to scan in archassistant, I get this error;
    error ifconfigUpProcess
    Dmesg;
    [zack@boxxy ~]$ dmesg | grep 4965
    iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.23k
    iwl4965: Copyright(c) 2003-2007 Intel Corporation
    iwl4965: Detected Intel Wireless WiFi Link 4965AGN
    iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
    phy0: Selected rate control algorithm 'iwl-4965-rs'
    I appreciate any suggestions.
    Zack
    Last edited by Sjoden (2008-07-07 21:03:21)

    Sorry I didn't post last night, we went to my sister in laws house.
    I started up my laptop at work today. Wicd took two tries to connect to my works WAP(s, we have 3 of them, all the same name, for roaming). I do a 'pacman -Syu'. It runs smoothly, only warning I get is about a font-config change. I only have 1 extra font pkg installed so I didn't worry about it.
    I reboot, and wicd fails. I can associate, but I can't get an IP address. I try all 3 WAPs, none work. I try different things for about 30 minutes, rebooting, retyping key, restarting the service and the tray.py for wicd, nothing.
    Plug in my network cable, Add the testing repo, re sync, and 'pacman -S testing/netcfg'. All runs fine. I make a profile from the default wep.example;
    [zack@boxxy ~]$ cat /etc/network.d/???wap
    CONNECTION="wireless"
    DESCRIPTION="???'s external wireless network."
    INTERFACE=wlan0
    SCAN="yes"
    SECURITY="wep"
    ESSID="???WAP"
    KEY="1234567890"
    IP="dhcp"
    I run 'netcfg2 ???wap'. It fails. I run it again, it finishes. I unplug the networking cable. No go. I remove the pid for dhcpcd on eth0, nothing. I kill dhcpcd and dhclient. Retry, nothing. I reboot, retry netcfg2, nothing again. I'm about to try and figure out how to use the quirks.
    From /var/log/messages.log;
    Jul 7 15:12:16 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
    Jul 7 15:12:16 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
    Jul 7 15:12:16 boxxy dhclient: All rights reserved.
    Jul 7 15:12:16 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Jul 7 15:12:16 boxxy dhclient:
    Jul 7 15:12:17 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:12:17 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:12:17 boxxy dhclient: Sending on Socket/fallback
    Jul 7 15:12:19 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:12:27 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:12:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
    Jul 7 15:12:51 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
    Jul 7 15:13:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    Jul 7 15:13:12 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Jul 7 15:13:20 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
    Jul 7 15:13:35 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
    Jul 7 15:13:48 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:13:48 boxxy dhclient: Trying recorded lease 192.168.5.24
    Jul 7 15:13:51 boxxy dhclient: Trying recorded lease 192.168.2.196
    Jul 7 15:13:54 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:14:26 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:14:26 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:14:29 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:14:29 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:14:29 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 3963
    Jul 7 15:14:29 boxxy dhclient: removed stale PID file
    Jul 7 15:14:29 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
    Jul 7 15:14:29 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
    Jul 7 15:14:29 boxxy dhclient: All rights reserved.
    Jul 7 15:14:29 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Jul 7 15:14:29 boxxy dhclient:
    Jul 7 15:14:30 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:14:30 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:14:30 boxxy dhclient: Sending on Socket/fallback
    Jul 7 15:14:31 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:14:39 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:14:55 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Jul 7 15:15:02 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
    Jul 7 15:15:15 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Jul 7 15:15:25 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
    Jul 7 15:15:44 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    Jul 7 15:15:56 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:15:56 boxxy dhclient: Trying recorded lease 192.168.5.24
    Jul 7 15:15:59 boxxy dhclient: Trying recorded lease 192.168.2.196
    Jul 7 15:16:02 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:17:31 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:17:31 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:17:33 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:17:33 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:17:33 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 5007
    Jul 7 15:17:33 boxxy dhclient: removed stale PID file
    Jul 7 15:17:33 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
    Jul 7 15:17:33 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
    Jul 7 15:17:33 boxxy dhclient: All rights reserved.
    Jul 7 15:17:33 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Jul 7 15:17:33 boxxy dhclient:
    Jul 7 15:17:34 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:17:34 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:17:34 boxxy dhclient: Sending on Socket/fallback
    Jul 7 15:17:35 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:17:40 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:17:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
    Jul 7 15:17:52 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Jul 7 15:18:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    Jul 7 15:18:14 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
    Jul 7 15:18:30 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
    Jul 7 15:18:48 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:18:48 boxxy dhclient: Trying recorded lease 192.168.5.24
    Jul 7 15:18:51 boxxy dhclient: Trying recorded lease 192.168.2.196
    Jul 7 15:18:54 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:21:39 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:21:40 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:21:59 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:21:59 boxxy r8169: eth0: link down
    Jul 7 15:21:59 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:22:01 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:22:01 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:22:02 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 6427
    Jul 7 15:22:02 boxxy dhclient: removed stale PID file
    Jul 7 15:22:02 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
    Jul 7 15:22:02 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
    Jul 7 15:22:02 boxxy dhclient: All rights reserved.
    Jul 7 15:22:02 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Jul 7 15:22:02 boxxy dhclient:
    Jul 7 15:22:03 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:22:03 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:22:03 boxxy dhclient: Sending on Socket/fallback
    Jul 7 15:22:04 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:22:12 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:22:31 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Jul 7 15:22:37 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Jul 7 15:22:48 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
    Jul 7 15:23:09 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
    Jul 7 15:23:27 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
    Jul 7 15:23:32 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:23:32 boxxy dhclient: Trying recorded lease 192.168.5.24
    Jul 7 15:23:35 boxxy dhclient: Trying recorded lease 192.168.2.196
    Jul 7 15:23:38 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:24:58 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:24:58 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:25:00 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:25:00 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:25:01 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 8688
    Jul 7 15:25:01 boxxy dhclient: removed stale PID file
    Jul 7 15:25:01 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
    Jul 7 15:25:01 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
    Jul 7 15:25:01 boxxy dhclient: All rights reserved.
    Jul 7 15:25:01 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Jul 7 15:25:01 boxxy dhclient:
    Jul 7 15:25:02 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:25:02 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:25:02 boxxy dhclient: Sending on Socket/fallback
    Jul 7 15:25:03 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:25:11 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:25:20 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Jul 7 15:25:26 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Jul 7 15:25:37 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Jul 7 15:25:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Jul 7 15:25:54 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Jul 7 15:26:01 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
    Jul 7 15:26:14 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Jul 7 15:26:21 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:26:21 boxxy dhclient: Trying recorded lease 192.168.5.24
    Jul 7 15:26:24 boxxy dhclient: Trying recorded lease 192.168.2.196
    Jul 7 15:26:27 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:29:35 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:29:35 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:29:37 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:29:37 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:29:38 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 9688
    Jul 7 15:29:38 boxxy dhclient: removed stale PID file
    Jul 7 15:29:38 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
    Jul 7 15:29:38 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
    Jul 7 15:29:38 boxxy dhclient: All rights reserved.
    Jul 7 15:29:38 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Jul 7 15:29:38 boxxy dhclient:
    Jul 7 15:29:39 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:29:39 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
    Jul 7 15:29:39 boxxy dhclient: Sending on Socket/fallback
    Jul 7 15:29:42 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:29:49 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:30:03 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Jul 7 15:30:10 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
    Jul 7 15:30:28 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Jul 7 15:30:38 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Jul 7 15:30:49 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
    Jul 7 15:31:04 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:31:04 boxxy dhclient: Trying recorded lease 192.168.5.24
    Jul 7 15:31:07 boxxy dhclient: Trying recorded lease 192.168.2.196
    Jul 7 15:31:10 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:31:55 boxxy r8169: eth0: link up
    Jul 7 15:31:56 boxxy r8169: eth0: link down
    Jul 7 15:31:57 boxxy r8169: eth0: link up
    Jul 7 15:32:00 boxxy r8169: eth0: link down
    Jul 7 15:32:02 boxxy r8169: eth0: link up
    Jul 7 15:32:32 boxxy NET: Registered protocol family 10
    Jul 7 15:32:32 boxxy lo: Disabled Privacy Extensions
    Jul 7 15:32:38 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
    Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: dhcpcd 3.2.1 starting
    Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: hardware address = 00:13:a9:f1:a0:b7
    Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: broadcasting for a lease
    Jul 7 15:33:30 boxxy dhcpcd[12617]: eth0: offered 10.0.1.106 from 10.0.1.200
    Jul 7 15:33:30 boxxy dhcpcd[12617]: eth0: checking 10.0.1.106 is available on attached networks
    Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: leased 10.0.1.106 for 86400 seconds
    Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding IP address 10.0.1.106/16
    Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding default route via 10.0.1.1 metric 0
    Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding route to 169.254.0.0/16 metric 0
    Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: exiting
    Jul 7 15:54:29 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
    Jul 7 15:54:29 boxxy ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Jul 7 15:55:39 boxxy ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Jul 7 15:55:42 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:55:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
    Jul 7 15:55:42 boxxy dhclient: DHCPOFFER from 10.0.1.200
    Jul 7 15:55:42 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
    Jul 7 15:55:42 boxxy dhclient: DHCPACK from 10.0.1.200
    Jul 7 15:55:42 boxxy dhclient: bound to 10.0.1.106 -- renewal in 32528 seconds.
    Jul 7 15:55:43 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
    Jul 7 15:55:45 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:55:48 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
    Jul 7 15:55:50 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:55:53 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
    Jul 7 15:55:59 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
    Jul 7 15:56:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Jul 7 15:56:00 boxxy r8169: eth0: link down
    Jul 7 15:56:06 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 13
    Jul 7 15:56:07 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
    Jul 7 15:56:19 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
    Jul 7 15:56:27 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
    Jul 7 15:56:29 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
    Jul 7 15:56:39 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
    Jul 7 15:56:44 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:56:44 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:56:48 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
    Jul 7 15:57:01 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:57:01 boxxy dhclient: Trying recorded lease 192.168.5.24
    Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: received SIGTERM, stopping
    Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing default route via 10.0.1.1 metric 0
    Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing route to 169.254.0.0/16 metric 0
    Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing IP address 10.0.1.106/16
    Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: exiting
    Jul 7 15:57:19 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:57:19 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
    Jul 7 15:57:20 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
    Jul 7 15:57:23 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:57:24 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
    Jul 7 15:57:25 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
    Jul 7 15:57:27 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Jul 7 15:57:30 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
    Jul 7 15:57:35 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
    Jul 7 15:57:38 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
    Jul 7 15:57:40 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 21
    Jul 7 15:57:41 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Jul 7 15:57:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
    Jul 7 15:57:45 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
    Jul 7 15:57:48 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
    Jul 7 15:57:49 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
    Jul 7 15:57:53 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
    Jul 7 15:58:01 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 16
    Jul 7 15:58:01 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
    Jul 7 15:58:07 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Jul 7 15:58:15 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Jul 7 15:58:17 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
    Jul 7 15:58:20 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:58:20 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:58:22 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
    Jul 7 15:58:26 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Jul 7 15:58:34 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
    Jul 7 15:58:36 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:58:36 boxxy dhclient: Trying recorded lease 192.168.5.24
    Jul 7 15:58:39 boxxy dhclient: Trying recorded lease 192.168.2.196
    Jul 7 15:58:42 boxxy dhclient: No working leases in persistent database - sleeping.
    Jul 7 15:58:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
    Jul 7 15:58:43 boxxy dhclient: No DHCPOFFERS received.
    Jul 7 15:58:43 boxxy dhclient: Trying recorded lease 10.0.1.106
    Jul 7 15:58:46 boxxy dhclient: No working leases in persistent database - sleeping.
    [root@boxxy examples]#
    From /var/log/pacman.log;
    [2008-07-07 13:25] synchronizing package lists
    [2008-07-07 13:26] starting full system upgrade
    [2008-07-07 14:42] upgraded freetype2 (2.3.6-1 -> 2.3.7-1)
    [2008-07-07 14:42] Symlinking new configuration files... done.
    [2008-07-07 14:42]
    [2008-07-07 14:42] ===> Important Fontconfig configuration change <===
    [2008-07-07 14:42]
    [2008-07-07 14:42] The way fontconfig is configured has been changed.
    [2008-07-07 14:42] Configuration is done via /etc/fonts/conf.avail and conf.d.
    [2008-07-07 14:42] Read /etc/fonts/conf.avail/README for more information.
    [2008-07-07 14:42]
    [2008-07-07 14:42] Configuration via /etc/fonts/local.conf is still possible,
    [2008-07-07 14:42] but is no longer recommended for options available in conf.avail.
    [2008-07-07 14:42]
    [2008-07-07 14:42] Adding missing configuration files... done.
    [2008-07-07 14:42] Removing outdated configuration files... done.
    [2008-07-07 14:43] updating font cache... done.
    [2008-07-07 14:43] upgraded fontconfig (2.5.0-1 -> 2.6.0-2)
    [2008-07-07 14:43] upgraded gcc-libs (4.3.1-1 -> 4.3.1-2)
    [2008-07-07 14:43] upgraded gcc (4.3.1-1 -> 4.3.1-2)
    [2008-07-07 14:43] upgraded glibmm (2.16.2-1 -> 2.16.4-1)
    [2008-07-07 14:43] >>> Updating module dependencies. Please wait ...
    [2008-07-07 14:43] >>> MKINITCPIO SETUP
    [2008-07-07 14:43] >>> ----------------
    [2008-07-07 14:43] >>> If you use LVM2, Encrypted root or software RAID,
    [2008-07-07 14:43] >>> Ensure you enable support in /etc/mkinitcpio.conf .
    [2008-07-07 14:43] >>> More information about mkinitcpio setup can be found here:
    [2008-07-07 14:43] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
    [2008-07-07 14:43]
    [2008-07-07 14:43] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2008-07-07 14:43] ==> Building image "default"
    [2008-07-07 14:43] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    [2008-07-07 14:43] :: Begin build
    [2008-07-07 14:43] :: Parsing hook [base]
    [2008-07-07 14:43] :: Parsing hook [udev]
    [2008-07-07 14:43] :: Parsing hook [autodetect]
    [2008-07-07 14:43] :: Parsing hook [pata]
    [2008-07-07 14:43] :: Parsing hook [scsi]
    [2008-07-07 14:43] :: Parsing hook [sata]
    [2008-07-07 14:43] :: Parsing hook [keymap]
    [2008-07-07 14:43] :: Parsing hook [filesystems]
    [2008-07-07 14:43] :: Generating module dependencies
    [2008-07-07 14:43] :: Generating image '/boot/kernel26.img'...SUCCESS
    [2008-07-07 14:43] ==> SUCCESS
    [2008-07-07 14:43] ==> Building image "fallback"
    [2008-07-07 14:43] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    [2008-07-07 14:43] :: Begin build
    [2008-07-07 14:43] :: Parsing hook [base]
    [2008-07-07 14:43] :: Parsing hook [udev]
    [2008-07-07 14:43] :: Parsing hook [pata]
    [2008-07-07 14:43] :: Parsing hook [scsi]
    [2008-07-07 14:43] :: Parsing hook [sata]
    [2008-07-07 14:44] :: Parsing hook [keymap]
    [2008-07-07 14:44] :: Parsing hook [filesystems]
    [2008-07-07 14:44] :: Generating module dependencies
    [2008-07-07 14:44] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
    [2008-07-07 14:44] ==> SUCCESS
    [2008-07-07 14:44] upgraded kernel26 (2.6.25.6-1 -> 2.6.25.10-1)
    [2008-07-07 14:44] upgraded lame (3.97-1 -> 3.98-1)
    [2008-07-07 14:44] upgraded libpng (1.2.28-1 -> 1.2.29-1)
    [2008-07-07 14:44] upgraded libsm (1.0.3-1 -> 1.1.0-1)
    [2008-07-07 14:44] upgraded libxfont (1.3.2-1 -> 1.3.3-1)
    [2008-07-07 14:44] upgraded libxft (2.1.12-1 -> 2.1.13-1)
    [2008-07-07 14:44] upgraded libxp (1.0.0-1 -> 1.0.0-2)
    [2008-07-07 14:44] upgraded randrproto (1.2.1-1 -> 1.2.2-1)
    [2008-07-07 14:44] upgraded libxrandr (1.2.2-1 -> 1.2.3-1)
    [2008-07-07 14:44] upgraded libxtrap (1.0.0-1 -> 1.0.0-2)
    [2008-07-07 14:44] upgraded libxxf86vm (1.0.1-1 -> 1.0.2-1)
    [2008-07-07 14:44] upgraded nss (3.12rc4-1 -> 3.12-1)
    [2008-07-07 14:44] upgraded xf86-input-mouse (1.2.3-1 -> 1.3.0-1)
    [2008-07-07 14:44] upgraded xorg-xauth (1.0.2-1 -> 1.0.3-1)
    [2008-07-07 14:44] upgraded xorg-xkb-utils (1.0.2-2 -> 7.3-1)
    [2008-07-07 14:44] upgraded xtrans (1.2-1 -> 1.2.1-1)
    [2008-07-07 15:33] synchronizing package lists
    [2008-07-07 15:33] starting full system upgrade
    [2008-07-07 15:34] upgraded pcre (7.7-1 -> 7.7-2)
    [2008-07-07 15:35] synchronizing package lists
    [2008-07-07 15:47] installed netcfg (2.1.0_B2-1)
    This is rediculous.
    Zack
    /edit
    I was able to load the google homepage after adding the preessid quirk, and using the 'netcfg' command instead of 'netcfg2'. I restarted, and it doesn't work(I'm pretty sure my eth cable was unplugged when loaded, could be wrong);
    [root@boxxy zack]# netcfg npnwap
    :: npnwap up - Wireless association failed. [FAIL]
    [root@boxxy zack]# netcfg npnwap
    :: npnwap up - Network unavailable [FAIL]
    [root@boxxy zack]# netcfg npnwap
    :: npnwap up - Network unavailable [FAIL]
    [root@boxxy zack]# netcfg2 npnwap
    :: npnwap up - Network unavailable [FAIL]
    [root@boxxy zack]# netcfg npnwap
    :: npnwap up - Network unavailable [FAIL]
    [root@boxxy zack]# killall wicd
    wicd: no process killed
    [root@boxxy zack]# /etc/rc.d/wicd stop
    :: Stopping wicd Daemon [DONE]
    [root@boxxy zack]# killall dhcpcd
    dhcpcd: no process killed
    [root@boxxy zack]# killall dhclient
    dhclient: no process killed
    [root@boxxy zack]# netcfg npnwap
    :: npnwap up - Network unavailable [FAIL]
    [root@boxxy zack]# netcfg2 npnwap
    :: npnwap up - Network unavailable [FAIL]
    [root@boxxy zack]# nano /etc/network.d/npnwap
    [root@boxxy zack]# netcfg npnwap
    :: npnwap up [DONE]
    [root@boxxy zack]# nano /etc/network.d/npnwap
    [root@boxxy zack]# /etc/rc.d/wicd stop
    :: Stopping wicd Daemon [DONE]
    [root@boxxy zack]# netcfg npnwap
    > npnwap already connected
    [root@boxxy zack]#
    Last edited by Sjoden (2008-07-07 21:36:17)

Maybe you are looking for