From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tiberiu Subject: Re: ath wireless power management failure Date: Tue, 7 Feb 2017 18:17:44 +0200 Message-ID: <5899F328.9020307@tehnoetic.com> References: <87h9461ko4.fsf@elephly.net> <87y3xi9hz2.fsf@gnu.org> <5899E621.2010701@tehnoetic.com> <87shnquigv.fsf@elephly.net> <5899E97D.2000607@tehnoetic.com> <87poiuugxo.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51567) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cb8Sp-0002a7-1C for help-guix@gnu.org; Tue, 07 Feb 2017 11:17:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cb8Sk-0001oZ-W9 for help-guix@gnu.org; Tue, 07 Feb 2017 11:17:54 -0500 In-Reply-To: <87poiuugxo.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: help-guix On 07.02.2017 18:03, Ricardo Wurmus wrote: > Tiberiu writes: >=20 >> Do you also have ath9k log messages and if so, could you please paste >> them here? Also, what chip does your WiFi card have? >=20 > There aren=E2=80=99t many ath9k log messages. Here are the messages fr= om > yesterday and today: >=20 > Feb 6 00:35:57 localhost vmunix: [ 11.849588] ath9k 0000:02:00.0: en= abling device (0000 -> 0002) > Feb 6 00:35:57 localhost vmunix: [ 12.052196] ath9k 0000:02:00.0 wlp= 2s0: renamed from wlan0 > Feb 6 09:23:44 localhost vmunix: [ 12.052555] ath9k 0000:02:00.0 wlp= 2s0: renamed from wlan0 > Feb 6 16:41:02 localhost vmunix: [21782.562086] [] a= th_isr [ath9k] > Feb 6 16:48:04 localhost vmunix: [ 67.024255] ath9k 0000:02:00.0 wlp= 2s0: renamed from wlan0 > Feb 6 18:18:40 localhost vmunix: [ 5507.166605] [] a= th_isr [ath9k] > Feb 6 18:25:22 localhost vmunix: [ 25.190524] ath9k 0000:02:00.0 wlp= 2s0: renamed from wlan0 > Feb 6 22:02:25 localhost vmunix: [ 53.568402] ath9k 0000:02:00.0 wlp= 2s0: renamed from wlan0 > Feb 7 07:49:13 localhost vmunix: [ 4619.392030] ath9k 0000:02:00.0: Re= fused to change power state, currently in D3 > Feb 7 07:53:51 localhost vmunix: [ 64.161516] ath9k 0000:02:00.0 wlp= 2s0: renamed from wlan0 > Feb 7 08:39:19 localhost vmunix: [ 2787.166577] [] a= th_isr [ath9k] > Feb 7 08:50:07 localhost vmunix: [ 18.319719] ath9k 0000:02:00.0: en= abling device (0000 -> 0002) > Feb 7 08:50:07 localhost vmunix: [ 18.652179] ath9k 0000:02:00.0 wlp= 2s0: renamed from wlan0 > Feb 7 11:55:49 localhost vmunix: [ 69.031690] ath9k 0000:02:00.0 wlp= 2s0: renamed from wlan0 >=20 > lspci says this about my network controller: >=20 > 02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Ad= apter (PCI-Express) (rev 01) >=20 > It used to work fine for several months. Not sure if it=E2=80=99s fail= ing or if > there=E2=80=99s bad interaction with the kernel/libreboot. To make sure it's not a hardware problem, you could boot with a Live USB with Trisquel 7.0 (it has an older stable kernel) and see if you have stable WiFi. If not, maybe this is a good opportunity to upgrade to the best WiFi card compatible with fully free systems: Tehnoetic N450DB (a/b/g/n compliant, up to 450Mbps, Dual Band, 3-antenna connectors): https://tehnoetic.com/tet-n450db Tiberiu -- https://tehnoetic.com