You are not logged in.
Pages: 1
Just got a new laptop -- an HP Pavilion dv6. The hardware setup went extremely smoothly, but I'm having some trouble keeping the wifi up. Whenever you take the laptop out of standby, it will not reconnect to the network -- I can't figure out anything short of a full reboot to get it back up. it just stalls out on 'obtaining IP address' for a while until it eventually fails.
Hardware info:
[root@myhost urza9814]# lspci | grep -i network
0d:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
rfkill list after pulling out of standby:
[root@myhost urza9814]# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
iwconfig before:
[root@myhost urza9814]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:"linksys"
Mode:Managed Frequency:2.412 GHz Access Point: 58:6D:8F:80:28:3E
Bit Rate=54 Mb/s Tx-Power=14 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=56/70 Signal level=-54 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:17 Missed beacon:0
and after:
[root@myhost urza9814]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:"linksys"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=14 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Offline
After you come out of standby, what are the results of iwlist scan ??
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Here's iwlist scan:
wlan0 Scan completed :
Cell 01 - Address: 58:6D:8F:80:28:3E
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=55/70 Signal level=-55 dBm
Encryption key:off
ESSID:"linksys"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=000000c8597d6183
Extra: Last beacon: 643ms ago
IE: Unknown: 00076C696E6B737973
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 050400010000
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: DD090010180204F0000000
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
Here's dmesg too if it helps, meant to post that originally. The 'fail to flush' message and 'link not ready' are the only ones that aren't there on boot too, Googling them gave nothing useful when I tried.
[ 706.496214] PM: resume of devices complete after 35671.424 msecs
[ 706.496509] PM: Finishing wakeup.
[ 706.496510] Restarting tasks ... done.
[ 706.508279] video LNXVIDEO:00: Restoring backlight state
[ 706.562203] video LNXVIDEO:01: Restoring backlight state
[ 712.226221] iwlagn 0000:0d:00.0: L1 Disabled; Enabling L0S
[ 712.289485] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 712.420452] r8169 0000:07:00.0: eth0: link down
[ 712.421021] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 727.265593] iwlagn 0000:0d:00.0: L1 Disabled; Enabling L0S
[ 727.331348] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 727.460588] r8169 0000:07:00.0: eth0: link down
[ 727.461161] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 727.515414] iwlagn 0000:0d:00.0: L1 Disabled; Enabling L0S
[ 727.580872] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 729.600991] wlan0: direct probe to 58:6d:8f:80:28:3e (try 1/3)
[ 729.800414] wlan0: direct probe to 58:6d:8f:80:28:3e (try 2/3)
[ 730.000196] wlan0: direct probe to 58:6d:8f:80:28:3e (try 3/3)
[ 730.199979] wlan0: direct probe to 58:6d:8f:80:28:3e timed out
[ 732.234407] iwlagn 0000:0d:00.0: fail to flush all tx fifo queues
[ 763.487901] iwlagn 0000:0d:00.0: L1 Disabled; Enabling L0S
[ 763.564029] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 763.614237] wlan0: direct probe to 58:6d:8f:80:28:3e (try 1/3)
[ 763.670779] r8169 0000:07:00.0: eth0: link down
[ 763.671348] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 763.813019] wlan0: direct probe to 58:6d:8f:80:28:3e (try 2/3)
[ 764.012806] wlan0: direct probe to 58:6d:8f:80:28:3e (try 3/3)
[ 764.212583] wlan0: direct probe to 58:6d:8f:80:28:3e timed out
[ 766.247011] iwlagn 0000:0d:00.0: fail to flush all tx fifo queues
Offline
Well, the interface is working and can see your access point.
How are you managing the link? network daemon, wicd, networkmanager, or other?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
wicd with the kde plasmoid client
Offline
Pages: 1