Huge Network Issue

kylepotts · 2010-06-24 18:58:42

I have been having this problem since last night. I have two answers on what the problem could be. Since the recent Linux-firmware update my wireless hasn't worked. Its is a wusb54gc which uses rt73usb module. The second is dhcpcd.

Here is my problem. I can not connect to my wireless at all. I do a

 iwconfig wlan0 essid "haxor-net"

and then a

 dhcpcd wlan0

and then I get a time out. I have tried to increase the timeout time but that didn't help. I also tried removing the /var/lib/dhcpcd lease file and that hasn't seemed to work. I know this is an update problem because I can boot an arch live cd and do the commands and I can connect. What do you think the problem is?

ewaller · 2010-06-24 19:58:52

Did you check the output of iwconfig to ensure that you actually associated with your AP?

kylepotts · 2010-06-24 20:22:38

What part if iwconfig would show that?

ewaller · 2010-06-24 20:51:50

ewaller@odin:~ 1005 %iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"woodlyn"
          Mode:Managed  Frequency:2.457 GHz  Access Point: 00:24:01:67:44:43
          Bit Rate=54 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=59/70  Signal level=-51 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ewaller@odin:~ 1006 %

In this case, I am associated with the access point whose MAC is 00:24:01:67:44:43
If there is no association, this field is not displayed

kylepotts · 2010-06-24 22:33:22

nope, it says Access point: Not-associated

tomk · 2010-06-24 22:37:47

Check dmesg for related messages.

ewaller · 2010-06-24 22:42:47

Until it associates, dhcpcd cannot do anything. That limits the scope to your first assertion.

Can you provide a little more info on your wireless network?
Encrypted ? WEP? WPA? WPA2?

what is the output of iwlist scan? (Any scan results?)
what is the output of iwconfig? (Is Tx power On? If not, can you turn it on? Could it be a problem with rfkill?

kylepotts · 2010-06-24 23:35:19

 wlan0     IEEE 802.11bg  Mode:Managed  Access Point: Not-Associated   
          Tx-Power=0 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on

wlan0     Scan completed :
          Cell 01 - Address: 00:1C:DF:F4:D0:0B
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=42/70  Signal level=-68 dBm  
                    Encryption key:off
                    ESSID:"links-local"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              12 Mb/s; 24 Mb/s; 36 Mb/s
                    Bit Rates:9 Mb/s; 18 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000040aa6f1c
                    Extra: Last beacon: 36ms ago
                    IE: Unknown: 000B6C696E6B732D6C6F63616C
                    IE: Unknown: 010882848B968C98B048
                    IE: Unknown: 03010B
                    IE: Unknown: 0706555320010B1B
                    IE: Unknown: 2A0100
                    IE: Unknown: 32041224606C
                    IE: Unknown: DD180050F2020101000003A4000027A4000041435E0061211A01
                    IE: Unknown: DDA20050F204104A00011010440001011041000100103B0001031047001000000000000000011000001CDFF4D00B1021001242656C6B696E20436F72706F726174696F6E1023000C463544373233342D3420763410240009342E30302E303520201042000E31323931383732333431353931311054000800060050F20400011011001B42656C6B696E20576972656C65737320526F757465722857464129100800020004
          Cell 02 - Address: 00:22:A4:EB:30:29
                    Channel:8
                    Frequency:2.447 GHz (Channel 8)
                    Quality=26/70  Signal level=-84 dBm  
                    Encryption key:on
                    ESSID:"2WIRE003"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000069d4769b181
                    Extra: Last beacon: 1200ms ago
                    IE: Unknown: 00083257495245303033
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030108
                    IE: Unknown: 050400010002
                    IE: Unknown: 0706555320010B1B
                    IE: Unknown: 2A0100
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32043048606C
                    IE: Unknown: DD0E0050F204104A0001101044000102

My network is unencrypted for now until I get this solved out. I am not sure what rfkill is.

Here is an interesting part of dmesg

forcedeth 0000:00:0f.0: irq 28 for MSI/MSI-X
rt73usb 1-3.3:1.0: firmware: requesting rt73.bin
wlan0: authenticate with 00:1c:df:f4:d0:0b (try 1)
wlan0: authenticated
wlan0: associate with 00:1c:df:f4:d0:0b (try 1)
wlan0: RX AssocResp from 00:1c:df:f4:d0:0b (capab=0x421 status=0 aid=2)
wlan0: associated
cfg80211: Calling CRDA for country: US
cfg80211: Current regulatory domain updated by AP to: US
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
wlan0: disassociated from 00:1c:df:f4:d0:0b (Reason: 8)
wlan0: deauthenticating from 00:1c:df:f4:d0:0b by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
eth0: link down.
eth0: link up.
eth0: link down.
eth0: link up.

Last edited by kylepotts (2010-06-24 23:46:40)

ewaller · 2010-06-25 00:06:25

Are you in North America?

What happens if you try :

sudo ifconfig wlan0 up

Actually, things don't look that bad. Before the update of the regulatory stuff, it looks like you were actually associated with essid links-local, and it is a moderate distance from you
I don't see your essid ("haxor-net") in the scan :-/ Is it hidden? if so, can you unhide it for now, untill you get this working?
Iwlist scan works, and sees two of your neighbor's APs (The guy with "links-local" is quite trusting -- His router is wide open, which is why you associated with it)

kylepotts · 2010-06-25 02:12:09

Actually the guy with links-local is me. I change the ssid because u thought it was a router issue. This still doesn't help me though. I still can not connect via dhcpcd I have also tried dhclient that still doesn't work. Any idea I am at a total loss

hunterthomson · 2010-06-25 04:40:10

Have you tried setting the channel 11

iwconfig wlan0 channel 11 essid links-local

-------

It sounds like a driver problem to me simply because it happened after the update. I have a wusb54g that I use for aircrack-ng I was never able to get the standard driver to work. Did you get it to work? In any case I'd try to re-install the driver or try to blacklist other rt drivers.

Here is the ubuntu thread I have for setting up the injection driver for the wusb54g. I would not suggest this driver for normal use though because it doesn't support WPA.... However, good info to have anyway...And in there I show a list of conflicting drivers. Maybe try to ( modprobe -r ) some of them and see if it starts to work.

http://ubuntuforums.org/showthread.php?t=1178790
#Conflicts with the packet injection rt73 dirver
blacklist rt73usb
blacklist rt2570
blacklist rt2500usb
blacklist rt2x00usb
blacklist rt2x00lib

Last edited by hunterthomson (2010-06-25 04:46:51)

kylepotts · 2010-06-25 05:21:43

It doesn't work with current kernel version.

hunterthomson · 2010-06-25 05:55:18

Well you can try the Enhanced rt73 driver. At lest you can get online with it and use worthless WEP and do Packet injection .... or is that the driver that doesn't work with the 2.6.34?

Last edited by hunterthomson (2010-06-25 05:55:51)

kylepotts · 2010-06-25 06:02:20

It doesn't work with 2.6.34. It 2.6.34 they integrated rt73 into /lib/firmware. I am compiling kernel26-rc and we'll see how that goes. Any other ideas?

hunterthomson · 2010-06-25 07:11:52

Shoot. well, I guess you can always roll back to the old kernel.

tomk · 2010-06-25 10:25:21

kylepotts wrote:

It doesn't work with 2.6.34. It 2.6.34 they integrated rt73 into /lib/firmware.

No - in 2.6.34, all distributable firmware for a wide selection of drivers, including rt73, is provided in a separate package called linux-firmware. The rt73 driver is still where it always was i.e. /lib/modules/2.6.34-ARCH/kernel/drivers/net/wireless/rt2x00/rt73usb.ko .

kylepotts · 2010-06-25 12:44:47

How would you go about rolling back?

Thansk for the clarification Tomk

hunterthomson · 2010-06-25 13:15:19

Well first do a "modprobe -r" to all these drivers

$ ls /lib/modules/2.6.34-ARCH/kernel/drivers/net/wireless/rt2x00 | grep rt
rt2400pci.ko
rt2500pci.ko
NOT THIS ONE >rt2500usb.ko
rt2800lib.ko
rt2800pci.ko
rt2800usb.ko
rt2x00lib.ko
rt2x00pci.ko
NOT THIS ONE >rt2x00usb.ko
rt61pci.ko
BUT NOT THIS ONE -> rt73usb.ko <- NOT THIS ONE

That will temperately remove those driver modules.
Then see if you can make a connection.
If it works then you can add them to the module blacklist in... /etc/modprobe.d/blacklist.conf
like this...

blacklist rt2500usb.ko
blacklist rt2x00lib.ko

Also, try power cycling in the router.... but you probably already did that.

To roll back the Kernel. First check your cache to see if it is still there.... /var/cache/pacman/pkg
Try this command...

ls /var/cache/pacman/pkg | grep kernel26

If the older kernel is still there then you can install it with

sudo pacman -U kernel26WHATERVER.pkg.tar.gz

"I think" that will automatically install the old firmware packages for you and stuff.
If not. You can check the log file form pacman to see what the package name was of the old firmware package thing that the new one replaced.

/var/log/pacman.log

$ cat /var/log/pacman.log | grep firmware

[2010-02-09 19:25] installed kernel26-firmware (2.6.32.8-1)
[2010-02-24 22:30] upgraded kernel26-firmware (2.6.32.8-1 -> 2.6.32.9-1)
[2010-03-16 23:25] upgraded kernel26-firmware (2.6.32.9-1 -> 2.6.32.10-1)
[2010-04-10 03:44] upgraded kernel26-firmware (2.6.32.10-1 -> 2.6.33.2-1)
[2010-04-27 23:35] upgraded kernel26-firmware (2.6.33.2-1 -> 2.6.33.3-1)
[2010-05-10 03:28] upgraded kernel26-firmware (2.6.33.3-1 -> 2.6.33.3-2)
[2010-05-16 03:24] upgraded kernel26-firmware (2.6.33.3-2 -> 2.6.33.4-1)
[2010-06-22 13:05] removed kernel26-firmware (2.6.33.4-1)
[2010-06-22 13:05] installed linux-firmware (20100606-1)

Then look for that package in then cache and install it agin.

ls /var/cache/pacman/pkg | grep kernel26-firmware

------------------

Or, try that injection driver... It is not the best for managed mode and no WPA but at lest it works and you can do packet injection.

############
See this is why I love Linux. With Windows your suck messing around with the stupid GUI's like Event Manager. Sure, Windows has the wannabe Unix Shell DOS box but it can't do anything. Power shell is a little better but it still sucks. And if you forgot.. Ya, Windows Updates brake things too. I just spent 7hr's installing Server 2008 and their are several things that brake along the way while updating that you have to fix.

Last edited by hunterthomson (2010-06-26 01:58:46)

tomk · 2010-06-25 15:22:16

hunterthomson - fyi rt73usb depends on rt2x00lib and rt2x00usb. See modinfo for details.

kylepotts · 2010-06-25 17:13:29

Alright well this is what i have decided to do. I did a rsync with the home directory, And I also did an image with clonezilla. I am going to do a fresh install and get blacklist kernel26 and dhcpcd from geting upgraded until I find a fix. Now the question remains would this be a kernel bug? If so where should i post a bug report.

hunterthomson · 2010-06-26 01:51:37

Hum..... Well, I should have done this first thing.... I just plugged in my Linksys WUSB54G with the rt73 chip-set. I just did a ifconfig wlan1 up and set WICD to use it and I connected to my WPA2 AES 802.11g network just fine. I am connected to it right now.

I don't know man. Maybe there is something ells wrong. In any case if you do do a clean install I would not bother blacklisting the Kernel or anything. It should be working just fine.

---------

tomk - owe, ya, ... I should have done that.
depends: rt2x00lib,rt2x00usb,usbcore,crc-itu-t
vermagic: 2.6.34-ARCH SMP preempt mod_unload
parm: nohwcrypt:Disable hardware encryption. (bool)

tomk · 2010-06-26 07:29:20

hunterthomson - post your dmesg output. It might help the OP.

hunterthomson · 2010-06-28 02:34:49

Okay, here it is /var/lob/everything.log I got it after I plunged in the wusb54G with rt73 and connected to my wireless network.

It took several tries to get it to connect. This is also showing it connecting to two of my wireless AP's. One is connected to the other through cat5e and the GW-WAP (the one on the receiving end of the cat5e) is the only DHCP server.

The rest is kind of a cop out answer. I mean this rt73 card is working in Archlinux on WPA2-AES networks for me...... but you could also buy a backup wireless card....

I also have this Rosewill RNX-G1 it is only $20 from newegg.com and it has a RT8187 chipset. The same one that is in the Alfa AWUS036H. It works vary well for every use. I highly recommend it.
http://www.newegg.com/Product/Product.a … Tpk=RNX-G1

Jun 27 15:08:01 BlackSlab syslog-ng[5747]: Configuration reload request received, reloading configuration;
Jun 27 15:12:45 BlackSlab kernel: npviewer.bin[7149]: segfault at ec336004 ip 00000000f656d36c sp 00000000ffe46fd0 error 4 in libflashplayer.so[f5f3c000+b03000]
Jun 27 15:32:45 BlackSlab -- MARK --
Jun 27 15:52:45 BlackSlab -- MARK --
Jun 27 16:02:01 BlackSlab crond[5756]: FILE /var/spool/cron/root USER root PID 11593 job sys-hourly
Jun 27 16:15:44 BlackSlab kernel: npviewer.bin[9763]: segfault at f59c3054 ip 00000000f62d8993 sp 00000000ffb31570 error 4 in libflashplayer.so[f5f3a000+b03000]
Jun 27 16:31:16 BlackSlab kernel: usb 2-1.2: new high speed USB device using ehci_hcd and address 8
Jun 27 16:31:17 BlackSlab kernel: phy1: Selected rate control algorithm 'minstrel'
Jun 27 16:31:17 BlackSlab kernel: Registered led device: rt73usb-phy1::radio
Jun 27 16:31:17 BlackSlab kernel: Registered led device: rt73usb-phy1::assoc
Jun 27 16:31:17 BlackSlab kernel: Registered led device: rt73usb-phy1::quality
Jun 27 16:31:17 BlackSlab kernel: usbcore: registered new interface driver rt73usb
Jun 27 16:31:30 BlackSlab kernel: rt73usb 2-1.2:1.0: firmware: requesting rt73.bin
Jun 27 16:31:30 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:35:49 BlackSlab dhcpcd[13258]: sending signal 1 to pid 6261
Jun 27 16:35:49 BlackSlab dhcpcd[6261]: received SIGHUP, releasing
Jun 27 16:35:49 BlackSlab dhcpcd[6261]: wlan0: releasing lease of 192.168.1.110
Jun 27 16:35:49 BlackSlab dhcpcd[13258]: waiting for pid 6261 to exit
Jun 27 16:35:49 BlackSlab dhcpcd[6261]: wlan0: removing interface
Jun 27 16:35:49 BlackSlab kernel: mac80211-phy0: failed to remove key (0, 00:18:84:1e:97:89) from hardware (-22)
Jun 27 16:35:49 BlackSlab kernel: wlan0: deauthenticating from 00:18:84:1e:97:89 by local choice (reason=3)
Jun 27 16:35:49 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 27 16:35:49 BlackSlab kernel: cfg80211: Calling CRDA to update world regulatory domain
Jun 27 16:35:49 BlackSlab dhcpcd[13272]: dhcpcd not running
Jun 27 16:35:49 BlackSlab load-modules.sh: 'platform:regulatory' is not a valid module or alias name
Jun 27 16:35:49 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:35:49 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:35:49 BlackSlab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 27 16:36:08 BlackSlab dhcpcd[13307]: dhcpcd not running
Jun 27 16:36:08 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:36:08 BlackSlab dhcpcd[13313]: dhcpcd not running
Jun 27 16:36:08 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:36:08 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:36:08 BlackSlab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 27 16:36:09 BlackSlab dhcpcd[13321]: dhcpcd not running
Jun 27 16:36:09 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:36:12 BlackSlab kernel: wlan1: authenticate with 00:18:84:1e:97:89 (try 1)
Jun 27 16:36:12 BlackSlab kernel: wlan1: authenticated
Jun 27 16:36:12 BlackSlab kernel: wlan1: associate with 00:18:84:1e:97:89 (try 1)
Jun 27 16:36:12 BlackSlab kernel: wlan1: RX AssocResp from 00:18:84:1e:97:89 (capab=0x431 status=0 aid=1)
Jun 27 16:36:12 BlackSlab kernel: wlan1: associated
Jun 27 16:36:12 BlackSlab kernel: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Jun 27 16:36:13 BlackSlab dhcpcd[13341]: version 5.2.5 starting
Jun 27 16:36:13 BlackSlab dhcpcd[13341]: wlan1: broadcasting for a lease
Jun 27 16:36:23 BlackSlab kernel: wlan1: no IPv6 routers present
Jun 27 16:36:24 BlackSlab dhcpcd[13341]: wlan1: offered 192.168.1.119 from 192.168.1.1
Jun 27 16:36:43 BlackSlab dhcpcd[13341]: timed out
Jun 27 16:36:49 BlackSlab dhcpcd[13366]: dhcpcd not running
Jun 27 16:36:49 BlackSlab kernel: wlan1: deauthenticating from 00:18:84:1e:97:89 by local choice (reason=3)
Jun 27 16:36:49 BlackSlab kernel: cfg80211: Calling CRDA to update world regulatory domain
Jun 27 16:36:49 BlackSlab load-modules.sh: 'platform:regulatory' is not a valid module or alias name
Jun 27 16:36:49 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:36:49 BlackSlab dhcpcd[13383]: dhcpcd not running
Jun 27 16:36:49 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:36:49 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:36:49 BlackSlab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 27 16:36:50 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:36:57 BlackSlab dhcpcd[13402]: dhcpcd not running
Jun 27 16:36:57 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:36:57 BlackSlab dhcpcd[13408]: dhcpcd not running
Jun 27 16:36:57 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:36:58 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:36:58 BlackSlab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 27 16:36:58 BlackSlab dhcpcd[13416]: dhcpcd not running
Jun 27 16:36:58 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:37:00 BlackSlab kernel: wlan1: authenticate with 00:18:84:1e:97:89 (try 1)
Jun 27 16:37:00 BlackSlab kernel: wlan1: authenticated
Jun 27 16:37:00 BlackSlab kernel: wlan1: associate with 00:18:84:1e:97:89 (try 1)
Jun 27 16:37:00 BlackSlab kernel: wlan1: RX AssocResp from 00:18:84:1e:97:89 (capab=0x431 status=0 aid=1)
Jun 27 16:37:00 BlackSlab kernel: wlan1: associated
Jun 27 16:37:00 BlackSlab kernel: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Jun 27 16:37:01 BlackSlab dhcpcd[13434]: version 5.2.5 starting
Jun 27 16:37:01 BlackSlab dhcpcd[13434]: wlan1: broadcasting for a lease
Jun 27 16:37:11 BlackSlab kernel: wlan1: no IPv6 routers present
Jun 27 16:37:31 BlackSlab dhcpcd[13434]: timed out
Jun 27 16:37:38 BlackSlab dhcpcd[13460]: dhcpcd not running
Jun 27 16:37:38 BlackSlab kernel: wlan1: deauthenticating from 00:18:84:1e:97:89 by local choice (reason=3)
Jun 27 16:37:38 BlackSlab kernel: cfg80211: Calling CRDA to update world regulatory domain
Jun 27 16:37:38 BlackSlab load-modules.sh: 'platform:regulatory' is not a valid module or alias name
Jun 27 16:37:38 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:37:38 BlackSlab dhcpcd[13477]: dhcpcd not running
Jun 27 16:37:38 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:37:38 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:37:38 BlackSlab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 27 16:37:50 BlackSlab dhcpcd[13496]: dhcpcd not running
Jun 27 16:37:50 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:37:50 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:37:50 BlackSlab dhcpcd[13502]: dhcpcd not running
Jun 27 16:37:51 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:37:51 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:37:51 BlackSlab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 27 16:37:51 BlackSlab dhcpcd[13510]: dhcpcd not running
Jun 27 16:37:51 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:37:53 BlackSlab kernel: wlan1: authenticate with 00:18:f8:43:66:1b (try 1)
Jun 27 16:37:53 BlackSlab kernel: wlan1: authenticated
Jun 27 16:37:53 BlackSlab kernel: wlan1: associate with 00:18:f8:43:66:1b (try 1)
Jun 27 16:37:53 BlackSlab kernel: wlan1: RX AssocResp from 00:18:f8:43:66:1b (capab=0x411 status=0 aid=6)
Jun 27 16:37:53 BlackSlab kernel: wlan1: associated
Jun 27 16:37:53 BlackSlab kernel: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Jun 27 16:37:54 BlackSlab dhcpcd[13528]: version 5.2.5 starting
Jun 27 16:37:54 BlackSlab dhcpcd[13528]: wlan1: broadcasting for a lease
Jun 27 16:37:55 BlackSlab dhcpcd[13528]: wlan1: offered 192.168.1.119 from 192.168.1.1
Jun 27 16:37:55 BlackSlab dhcpcd[13528]: wlan1: acknowledged 192.168.1.119 from 192.168.1.1
Jun 27 16:37:55 BlackSlab dhcpcd[13528]: wlan1: checking for 192.168.1.119
Jun 27 16:38:00 BlackSlab dhcpcd[13528]: wlan1: leased 192.168.1.119 for 86400 seconds
Jun 27 16:38:00 BlackSlab dhcpcd[13528]: forked to background, child pid 13552
Jun 27 16:38:04 BlackSlab kernel: wlan1: no IPv6 routers present
Jun 27 16:38:38 BlackSlab dhcpcd[13603]: sending signal 1 to pid 13552
Jun 27 16:38:38 BlackSlab dhcpcd[13603]: waiting for pid 13552 to exit
Jun 27 16:38:38 BlackSlab dhcpcd[13552]: received SIGHUP, releasing
Jun 27 16:38:38 BlackSlab dhcpcd[13552]: wlan1: releasing lease of 192.168.1.119
Jun 27 16:38:38 BlackSlab dhcpcd[13552]: wlan1: removing interface
Jun 27 16:38:38 BlackSlab kernel: wlan1: deauthenticating from 00:18:f8:43:66:1b by local choice (reason=3)
Jun 27 16:38:39 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:38:39 BlackSlab kernel: cfg80211: Calling CRDA to update world regulatory domain
Jun 27 16:38:39 BlackSlab dhcpcd[13617]: dhcpcd not running
Jun 27 16:38:39 BlackSlab load-modules.sh: 'platform:regulatory' is not a valid module or alias name
Jun 27 16:38:39 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:38:39 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:38:39 BlackSlab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 27 16:38:42 BlackSlab dhcpcd[13634]: dhcpcd not running
Jun 27 16:38:42 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:38:42 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:38:42 BlackSlab dhcpcd[13640]: dhcpcd not running
Jun 27 16:38:43 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:38:43 BlackSlab kernel: e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
Jun 27 16:38:43 BlackSlab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 27 16:38:43 BlackSlab dhcpcd[13648]: dhcpcd not running
Jun 27 16:38:43 BlackSlab kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jun 27 16:38:45 BlackSlab kernel: wlan1: authenticate with 00:18:84:1e:97:89 (try 1)
Jun 27 16:38:45 BlackSlab kernel: wlan1: authenticated
Jun 27 16:38:45 BlackSlab kernel: wlan1: associate with 00:18:84:1e:97:89 (try 1)
Jun 27 16:38:45 BlackSlab kernel: wlan1: RX AssocResp from 00:18:84:1e:97:89 (capab=0x431 status=0 aid=1)
Jun 27 16:38:45 BlackSlab kernel: wlan1: associated
Jun 27 16:38:45 BlackSlab kernel: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Jun 27 16:38:46 BlackSlab dhcpcd[13667]: version 5.2.5 starting
Jun 27 16:38:46 BlackSlab dhcpcd[13667]: wlan1: broadcasting for a lease
Jun 27 16:38:56 BlackSlab kernel: wlan1: no IPv6 routers present
Jun 27 16:39:01 BlackSlab dhcpcd[13667]: wlan1: offered 192.168.1.119 from 192.168.1.1
Jun 27 16:39:01 BlackSlab dhcpcd[13667]: wlan1: acknowledged 192.168.1.119 from 192.168.1.1
Jun 27 16:39:01 BlackSlab dhcpcd[13667]: wlan1: checking for 192.168.1.119
Jun 27 16:39:06 BlackSlab dhcpcd[13667]: wlan1: leased 192.168.1.119 for 86400 seconds
Jun 27 16:39:06 BlackSlab dhcpcd[13667]: forked to background, child pid 13697

Last edited by hunterthomson (2010-06-28 03:07:16)

clearloon · 2010-06-28 21:09:12

##Deleting for irrelevance

Hi -

Your problem might be solved by this post:

http://bbs.archlinux.org/viewtopic.php?id=86260

I had this problem in the past (ie massive slow downs and/or drop outs) and turning off power saving fixed it.

Since the kernel update a few days ago I've been having the same problem so I tried the fix linked above.

YMMV but it worked for me - good luck!

cl

Last edited by clearloon (2010-06-28 21:10:16)

hunterthomson · 2010-06-29 03:32:19

Hum, you know I had that thought for a few minutes after seeing that option was on.

I think you should try that kylepotts

Last edited by hunterthomson (2010-06-29 03:35:00)

Arch Linux

#1 2010-06-24 18:58:42

Huge Network Issue

#2 2010-06-24 19:58:52

Re: Huge Network Issue

#3 2010-06-24 20:22:38

Re: Huge Network Issue

#4 2010-06-24 20:51:50

Re: Huge Network Issue

#5 2010-06-24 22:33:22

Re: Huge Network Issue

#6 2010-06-24 22:37:47

Re: Huge Network Issue

#7 2010-06-24 22:42:47

Re: Huge Network Issue

#8 2010-06-24 23:35:19

Re: Huge Network Issue

#9 2010-06-25 00:06:25

Re: Huge Network Issue

#10 2010-06-25 02:12:09

Re: Huge Network Issue

#11 2010-06-25 04:40:10

Re: Huge Network Issue

#12 2010-06-25 05:21:43

Re: Huge Network Issue

#13 2010-06-25 05:55:18

Re: Huge Network Issue

#14 2010-06-25 06:02:20

Re: Huge Network Issue

#15 2010-06-25 07:11:52

Re: Huge Network Issue

#16 2010-06-25 10:25:21

Re: Huge Network Issue

#17 2010-06-25 12:44:47

Re: Huge Network Issue

#18 2010-06-25 13:15:19

Re: Huge Network Issue

#19 2010-06-25 15:22:16

Re: Huge Network Issue

#20 2010-06-25 17:13:29

Re: Huge Network Issue

#21 2010-06-26 01:51:37

Re: Huge Network Issue

#22 2010-06-26 07:29:20

Re: Huge Network Issue

#23 2010-06-28 02:34:49

Re: Huge Network Issue

#24 2010-06-28 21:09:12

Re: Huge Network Issue

#25 2010-06-29 03:32:19

Re: Huge Network Issue

Board footer