You are not logged in.

#1 2012-08-09 12:02:45

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

WiFi goes off after boot

I have two kernels - regular ARCH kernel, and a linux-pf kernel which I use 99% of the time.

The problem is, than whenever I boot with the -pf kernel, the WiFi radio becomes disabled 1-2 minutes after boot, loosing all connectivity (even if it is already connected to a network). I then have to go into WICD, enable radio, refresh, and then connect to network again. The problem occurs after EVERY reboot, but never upon resume.
This does not happen if I boot from regular kernel.

What could be causing it?

Offline

#2 2012-08-09 12:15:30

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,542

Re: WiFi goes off after boot

If you have a broadfailure card, you will probably need broadcom-wl-pf-core2.


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#3 2012-08-09 12:39:22

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: WiFi goes off after boot

Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron]

Offline

#4 2012-08-13 09:44:00

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: WiFi goes off after boot

Any ideas welcome.

Offline

#5 2012-08-13 12:20:09

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,491

Re: WiFi goes off after boot

You can check power-saving status when it is connected with "iwconfig".
Also you can describe shortly what you have tried to find out the reason and if the logs give strange non-broadfailure output upon disconnect.

Offline

#6 2012-08-13 15:53:28

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: WiFi goes off after boot

Power Management:off
Apparently, driver for this card does not support Power Management.

Which log file should I be looking in?

Offline

#7 2012-08-13 17:13:58

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,414

Re: WiFi goes off after boot

... hopefully you know you have a /var/log folder yeah?  What is in there?  I would suggest checking out messages.log and everything.log as a place to start.  My system also has a wicd folder in which it stores wicd related log files.  So... poke around and see what you get.

Offline

#8 2012-08-15 16:20:47

Lockheed
Member
Registered: 2010-03-16
Posts: 1,550

Re: WiFi goes off after boot

Here's some logs:

errors.log
Aug 15 18:08:31 panzor kernel: [   21.253980] e1000e 0000:00:19.0: eth0: Hardware Error
Aug 15 18:08:31 panzor kernel: [   21.915275] e1000e 0000:00:19.0: eth0: Hardware Error
Aug 15 18:08:38 panzor bluetoothd[1356]: input-headset driver probe failed for device 64:A7:69:48:33:49
Aug 15 18:08:38 panzor bluetoothd[1356]: hci0: Set Discoverable (0x0006) failed: Not Powered (0x0f)
Aug 15 18:08:52 panzor dhcpcd[1592]: dhcpcd not running
Aug 15 18:08:52 panzor dhcpcd[1628]: dhcpcd not running
Aug 15 18:08:54 panzor dhcpcd[1660]: dhcpcd not running
Aug 15 18:09:01 panzor dhcpcd[1707]: wlan0: sendmsg: Cannot assign requested address
Aug 15 18:11:20 panzor dhcpcd[2602]: dhcpcd not running


wicd.log
2012/08/15 18:08:38 :: ---------------------------
2012/08/15 18:08:38 :: wicd initializing...
2012/08/15 18:08:38 :: ---------------------------
2012/08/15 18:08:38 :: wicd is version 1.7.2.4 768
2012/08/15 18:08:38 :: setting backend to external
2012/08/15 18:08:38 :: trying to load backend external
2012/08/15 18:08:38 :: successfully loaded backend external
2012/08/15 18:08:38 :: trying to load backend external
2012/08/15 18:08:38 :: successfully loaded backend external
2012/08/15 18:08:38 :: Automatically detected wireless interface wlan0
2012/08/15 18:08:38 :: setting wireless interface wlan0
2012/08/15 18:08:38 :: automatically detected wired interface eth0
2012/08/15 18:08:38 :: setting wired interface eth0
2012/08/15 18:08:38 :: setting wpa driver nl80211
2012/08/15 18:08:39 :: setting use global dns to False
2012/08/15 18:08:39 :: setting global dns
2012/08/15 18:08:39 :: global dns servers are None None None
2012/08/15 18:08:39 :: domain is None
2012/08/15 18:08:39 :: search domain is None
2012/08/15 18:08:39 :: setting automatically reconnect when connection drops True
2012/08/15 18:08:39 :: Setting dhcp client to 0
2012/08/15 18:08:40 :: Wireless configuration file found...
2012/08/15 18:08:40 :: Wired configuration file found...
2012/08/15 18:08:40 :: chmoding configuration files 0600...
2012/08/15 18:08:40 :: chowning configuration files root:root...
2012/08/15 18:08:40 :: Using wireless interface...wlan0
2012/08/15 18:08:40 :: Using wired interface...eth0
2012/08/15 18:08:46 :: Autoconnecting...
2012/08/15 18:08:49 :: No wired connection present, attempting to autoconnect to wireless network
2012/08/15 18:08:52 :: hidden
2012/08/15 18:08:52 :: trying to automatically connect to...ateochao
2012/08/15 18:08:52 :: Connecting to wireless network ateochao
2012/08/15 18:08:54 :: Putting interface down
2012/08/15 18:08:54 :: Releasing DHCP leases...
2012/08/15 18:08:54 :: Setting false IP...
2012/08/15 18:08:54 :: Stopping wpa_supplicant
2012/08/15 18:08:54 :: Flushing the routing table...
2012/08/15 18:08:54 :: Putting interface up...
2012/08/15 18:08:56 :: Generating psk...
2012/08/15 18:08:56 :: Attempting to authenticate...
2012/08/15 18:09:01 :: Running DHCP with hostname panzor
2012/08/15 18:09:01 :: dhcpcd[1707]: version 5.6.0 starting
2012/08/15 18:09:01 ::
2012/08/15 18:09:01 :: dhcpcd[1707]: wlan0: sending IPv6 Router Solicitation
2012/08/15 18:09:01 ::
2012/08/15 18:09:01 :: dhcpcd[1707]: wlan0: sendmsg: Cannot assign requested address
2012/08/15 18:09:01 ::
2012/08/15 18:09:01 :: dhcpcd[1707]: wlan0: rebinding lease of 192.168.0.45
2012/08/15 18:09:01 ::
2012/08/15 18:09:01 :: dhcpcd[1707]: wlan0: acknowledged 192.168.0.45 from 192.168.0.254
2012/08/15 18:09:01 ::
2012/08/15 18:09:01 :: dhcpcd[1707]: wlan0: checking for 192.168.0.45
2012/08/15 18:09:01 ::
2012/08/15 18:09:05 :: dhcpcd[1707]: wlan0: sending IPv6 Router Solicitation
2012/08/15 18:09:05 ::
2012/08/15 18:09:06 :: dhcpcd[1707]: wlan0: leased 192.168.0.45 for 43200 seconds
2012/08/15 18:09:06 ::
2012/08/15 18:09:06 :: dhcpcd[1707]: forked to background, child pid 1758
2012/08/15 18:09:06 ::
2012/08/15 18:09:06 ::
2012/08/15 18:09:06 :: DHCP connection successful
2012/08/15 18:09:06 :: not verifying
2012/08/15 18:09:07 :: Connecting thread exiting.
2012/08/15 18:09:09 :: Sending connection attempt result success
2012/08/15 18:11:24 :: Autoconnecting...
2012/08/15 18:11:24 :: No wired connection present, attempting to autoconnect to wireless network
2012/08/15 18:11:24 :: Unable to autoconnect, you'll have to manually connect
2012/08/15 18:11:29 :: Autoconnecting...
2012/08/15 18:11:29 :: No wired connection present, attempting to autoconnect to wireless network
2012/08/15 18:11:29 :: Unable to autoconnect, you'll have to manually connect
2012/08/15 18:11:34 :: Autoconnecting...

messages.log
Aug 15 18:11:17 panzor dhcpcd[1758]: wlan0: carrier lost
Aug 15 18:11:18 panzor kernel: [  188.239368] mmc0: card d555 removed
Aug 15 18:11:18 panzor kernel: [  188.246581] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Aug 15 18:11:18 panzor kernel: [  188.303006] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Aug 15 18:11:18 panzor kernel: [  188.360714] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Aug 15 18:11:18 panzor kernel: [  188.417745] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Aug 15 18:11:18 panzor kernel: [  188.474726] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
Aug 15 18:11:19 panzor dhcpcd[2573]: sending signal 1 to pid 1758
Aug 15 18:11:19 panzor dhcpcd[1758]: received SIGHUP, releasing
Aug 15 18:11:19 panzor dhcpcd[1758]: wlan0: removing interface
Aug 15 18:11:19 panzor dhcpcd[2573]: waiting for pid 1758 to exit
Aug 15 18:11:20 panzor kernel: [  191.081691] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 15 18:13:17 panzor ntpd[3573]: ntpd 4.2.6p5@1.2349-o Sat Jun  9 05:23:54 UTC 2012 (1)
Aug 15 18:13:17 panzor ntpd[3573]: proto: precision = 0.838 usec
Aug 15 18:13:17 panzor ntpd[3573]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Aug 15 18:13:17 panzor ntpd[3573]: Listen and drop on 1 v6wildcard :: UDP 123
Aug 15 18:13:17 panzor ntpd[3573]: Listen normally on 2 lo 127.0.0.1 UDP 123
Aug 15 18:13:17 panzor ntpd[3573]: Listen normally on 3 lo ::1 UDP 123
Aug 15 18:13:17 panzor ntpd[3573]: peers refreshed


Some of the first lines might be from the previous session from before the reboot.

Last edited by Lockheed (2012-08-15 16:22:30)

Offline

#9 2012-08-16 09:06:16

dunric29a
Member
Registered: 2005-12-16
Posts: 23

Re: WiFi goes off after boot

The same in my case, after the last kernel upgrade. Broadcom BCM4313 card.
Check also the state with rfkill - ie. with

rfkill list

Offline

Board footer

Powered by FluxBB