From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Lost wireless interface after updates
Date: Sun, 18 Oct 2015 22:27:18 +0300 [thread overview]
Message-ID: <CAJ1xhMV31gUpgyfJKydgJhdNtKRAS_eKfnLQmroGxRKBiC++ZQ@mail.gmail.com> (raw)
In-Reply-To: <CAFvvX=a=Zv6hZd22ne7BtEj_qn0uHJ9=LODKcyRB0OQ7fXV20A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6812 bytes --]
On Sun, Oct 18, 2015 at 9:22 PM, Mansour Al Akeel <mansour.alakeel@gmail.com
> wrote:
> Hello all,
>
> ifconfig -a
> enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.7 netmask 255.255.255.0 broadcast 192.168.1.255
> ether f0:de:f1:6f:6d:00 txqueuelen 1000 (Ethernet)
> RX packets 42308 bytes 45223536 (43.1 MiB)
> RX errors 0 dropped 3 overruns 0 frame 0
> TX packets 29996 bytes 4063319 (3.8 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device interrupt 20 memory 0xf1600000-f1620000
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> loop txqueuelen 0 (Local Loopback)
> RX packets 6688 bytes 2077181 (1.9 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 6688 bytes 2077181 (1.9 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> wlp3s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
> ether a0:88:b4:97:b5:2c txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
Your wired interface seems to be up, while your wireless one seems to be
down. Do you normally have both interfaces up?
> ===========================================================
>
> iwconfig
>
> wlp3s0 IEEE 802.11abgn ESSID:off/any
> Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
> Retry short limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
>
> During the last update, did you by any chance update your
'net-wireless/wpa_supplicant'? If so, can you ensure your '/etc/conf.d/net'
and '/etc/wpa_supplicant/wpa_supplicant.conf' are in order.
If you are using openrc, what is the output of:
root# rc-update show | grep net
> The relevant dmesg:
>
> [64508.554638] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
> [64525.117691] cfg80211: Calling CRDA to update world regulatory domain
> [64525.120109] Intel(R) Wireless WiFi driver for Linux
> [64525.120113] Copyright(c) 2003- 2014 Intel Corporation
> [64525.120460] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't
> have ASPM control
> [64525.123065] iwlwifi 0000:03:00.0: loaded firmware version
> 18.168.6.1 op_mode iwldvm
> [64525.125585] cfg80211: World regulatory domain updated:
> [64525.125590] cfg80211: DFS Master region: unset
> [64525.125593] cfg80211: (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp), (dfs_cac_time)
> [64525.125600] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
> (N/A, 2000 mBm), (N/A)
> [64525.125604] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz),
> (N/A, 2000 mBm), (N/A)
> [64525.125607] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
> (N/A, 2000 mBm), (N/A)
> [64525.125612] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz,
> 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
> [64525.125617] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz,
> 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
> [64525.125620] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz),
> (N/A, 2000 mBm), (0 s)
> [64525.125623] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz),
> (N/A, 2000 mBm), (N/A)
> [64525.125627] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000
> KHz), (N/A, 0 mBm), (N/A)
> [64525.130881] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
> [64525.130888] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
> [64525.130891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
> [64525.130896] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R)
> Advanced-N 6205 AGN, REV=0xB0
> [64525.131109] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
> [64525.131401] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.
> [64525.142887] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
> [64525.155277] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
> [64525.162396] systemd-udevd[21982]: renamed network interface wlan0 to
> wlp3s0
> [64525.219188] iwlwifi 0000:03:00.0: Failed to run INIT ucode: -132
> [64525.219379] iwlwifi 0000:03:00.0: Unable to initialize device.
> [64525.290764] iwlwifi 0000:03:00.0: Failed to run INIT ucode: -132
> [64525.290942] iwlwifi 0000:03:00.0: Unable to initialize device.
> [64525.292024] iwlwifi 0000:03:00.0: Failed to run INIT ucode: -132
> [64525.292237] iwlwifi 0000:03:00.0: Unable to initialize device.
>
>
>
A Google search suggested a possible firmware bug. See the link below.
https://forums.gentoo.org/viewtopic-t-979860-view-next.html?sid=06f41bee184e5f8a8463f3d82373067e
================================================================
> lspci
>
> 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
> Family DRAM Controller (rev 09)
> 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
> Core Processor Family Integrated Graphics Controller (rev 09)
> 00:16.0 Communication controller: Intel Corporation 6 Series/C200
> Series Chipset Family MEI Controller #1 (rev 04)
> 00:16.3 Serial controller: Intel Corporation 6 Series/C200 Series
> Chipset Family KT Controller (rev 04)
> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
> Connection (rev 04)
> 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
> Family USB Enhanced Host Controller #2 (rev 04)
> 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
> Family High Definition Audio Controller (rev 04)
> 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
> Family PCI Express Root Port 1 (rev b4)
> 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
> Family PCI Express Root Port 2 (rev b4)
> 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
> Family PCI Express Root Port 4 (rev b4)
> 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
> Family PCI Express Root Port 5 (rev b4)
> 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
> Family USB Enhanced Host Controller #1 (rev 04)
> 00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC
> Controller (rev 04)
> 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series
> Chipset Family 6 port SATA AHCI Controller (rev 04)
> 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family
> SMBus Controller (rev 04)
> 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205
> [Taylor Peak] (rev 34)
> 05:00.0 System peripheral: Ricoh Co Ltd PCIe SDXC/MMC Host Controller (rev
> 04)
> 0d:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host
> Controller (rev 04)
>
>
[-- Attachment #2: Type: text/html, Size: 8378 bytes --]
next prev parent reply other threads:[~2015-10-18 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 18:22 [gentoo-user] Lost wireless interface after updates Mansour Al Akeel
2015-10-18 18:49 ` Mick
2015-10-18 19:27 ` Alexander Kapshuk [this message]
2015-10-19 4:12 ` Stroller
2015-10-19 10:32 ` Mansour Al Akeel
2015-10-19 21:52 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ1xhMV31gUpgyfJKydgJhdNtKRAS_eKfnLQmroGxRKBiC++ZQ@mail.gmail.com \
--to=alexander.kapshuk@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox