| 1 |
On Wed, Jul 29 2015, Mick wrote: |
| 2 |
|
| 3 |
> On Wednesday 29 Jul 2015 01:36:22 gottlieb@×××.edu wrote: |
| 4 |
>> I am having trouble with wireless on a new install (gnome/systemd). |
| 5 |
>> |
| 6 |
>> lspci reports |
| 7 |
>> 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) |
| 8 |
>> |
| 9 |
>> I looked this up and it requires the iwlwifi driver and iwlmvm, which I |
| 10 |
>> enabled in the kernel (as modules). lsmod reports |
| 11 |
>> Module Size Used by |
| 12 |
>> iwlmvm 142993 0 |
| 13 |
>> mac80211 425803 1 iwlmvm |
| 14 |
>> x86_pkg_temp_thermal 4567 0 |
| 15 |
>> iwlwifi 88075 1 iwlmvm |
| 16 |
>> |
| 17 |
>> I have merged linux-firmware and ls /lib/firmware/*7265* reports |
| 18 |
>> /lib/firmware/iwlwifi-7265-10.ucode /lib/firmware/iwlwifi-7265-9.ucode |
| 19 |
>> /lib/firmware/iwlwifi-7265-12.ucode |
| 20 |
>> /lib/firmware/iwlwifi-7265D-10.ucode /lib/firmware/iwlwifi-7265-8.ucode |
| 21 |
>> /lib/firmware/iwlwifi-7265D-12.ucode |
| 22 |
>> |
| 23 |
>> dmsg | grep iwl reports |
| 24 |
>> [ 2.819953] iwlwifi 0000:02:00.0: irq 48 for MSI/MSI-X |
| 25 |
>> [ 2.824130] iwlwifi 0000:02:00.0: loaded firmware version 23.11.10.0 |
| 26 |
>> op_modeiwlmvm [ 2.836969] iwlwifi 0000:02:00.0: Detected Intel(R) Dual |
| 27 |
>> Band Wireless AC 7265, REV=0x210 [ 2.838620] iwlwifi 0000:02:00.0: L1 |
| 28 |
>> Disabled - LTR Enabled [ 2.838775] iwlwifi 0000:02:00.0: L1 Disabled - |
| 29 |
>> LTR Enabled [ 2.896168] ieee80211 phy0: Selected rate control algorithm |
| 30 |
>> 'iwl-mvm-rs' [ 2.899325] iwlwifi 0000:02:00.0 wlp2s0: renamed from |
| 31 |
>> wlan0 |
| 32 |
>> |
| 33 |
>> The complaint seems to be "L1 disabled" |
| 34 |
>> |
| 35 |
>> NetworkManager started the wired network but failed with the wireless |
| 36 |
>> E6430s ~ # systemctl -l status NetworkManager |
| 37 |
>> ● NetworkManager.service - Network Manager |
| 38 |
>> Loaded: loaded (/usr/lib64/systemd/system/NetworkManager.service; |
| 39 |
>> enabled; vendor preset: enabled) Active: active (running) since Tue |
| 40 |
>> 2015-07-28 19:56:57 EDT; 9min ago Main PID: 232 (NetworkManager) |
| 41 |
>> CGroup: /system.slice/NetworkManager.service |
| 42 |
>> ├─232 /usr/sbin/NetworkManager --no-daemon |
| 43 |
>> └─256 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf |
| 44 |
>> /var/run/dhclient-eno1.pid -lf |
| 45 |
>> /var/lib/NetworkManager/dhclient-0caab3d6-148f-416a-9906-547ed08596bf-eno1 |
| 46 |
>> .lease -cf /var/lib/NetworkManager/dhclient-eno1.conf eno1 |
| 47 |
>> |
| 48 |
>> Jul 28 19:56:59 E6430s dhclient[256]: bound to 192.168.1.107 -- renewal in |
| 49 |
>> 43096 seconds. Jul 28 19:56:59 E6430s NetworkManager[232]: <info> |
| 50 |
>> NetworkManager state is now CONNECTED_GLOBAL Jul 28 19:56:59 E6430s |
| 51 |
>> NetworkManager[232]: <info> Policy set 'Wired connection 1' (eno1) as |
| 52 |
>> default for IPv4 routing and DNS. Jul 28 19:56:59 E6430s |
| 53 |
>> NetworkManager[232]: <info> (eno1): Activation: successful, device |
| 54 |
>> activated. Jul 28 19:57:01 E6430s NetworkManager[232]: <info> (wlp2s0): |
| 55 |
>> supplicant interface state: disconnected -> inactive Jul 28 19:57:05 |
| 56 |
>> E6430s NetworkManager[232]: <info> startup complete Jul 28 19:57:31 |
| 57 |
>> E6430s NetworkManager[232]: <info> (eno1): Activation: Stage 4 of 5 (IPv6 |
| 58 |
>> Configure Timeout) scheduled... Jul 28 19:57:31 E6430s |
| 59 |
>> NetworkManager[232]: <info> (eno1): Activation: Stage 4 of 5 (IPv6 |
| 60 |
>> Configure Timeout) started... Jul 28 19:57:31 E6430s NetworkManager[232]: |
| 61 |
>> <info> (eno1): Activation: Stage 4 of 5 (IPv6 Configure Timeout) |
| 62 |
>> complete. Jul 28 19:57:57 E6430s NetworkManager[232]: <info> (wlp2s0): |
| 63 |
>> supplicant interface state: inactive -> scanning |
| 64 |
>> |
| 65 |
>> What step did I forget? |
| 66 |
>> |
| 67 |
>> thanks in advance, |
| 68 |
>> allan |
| 69 |
> |
| 70 |
> There are reports of driver problems, so you may not have forgotten anything. |
| 71 |
> Usual suggestion is to run the latest kernel and firmware, but I don't have |
| 72 |
> this card to know more about it. What happens after the 'inactive -> |
| 73 |
> scanning' step above? Have you tried to disconnect the wired ethernet |
| 74 |
> connection and wait a bit longer for the wireless? |
| 75 |
|
| 76 |
I just wrote an addendum that crossed in the mail with your msg. This |
| 77 |
kernel with these drivers worked last week. I just noticed that I |
| 78 |
didn't have an /etc/wpa_supplicant so added the same trivial one I have |
| 79 |
on my current machine |
| 80 |
# The below line not be changed otherwise we refuse to work |
| 81 |
ctrl_interface=/var/run/wpa_supplicant |
| 82 |
|
| 83 |
network={ |
| 84 |
key_mgmt=NONE |
| 85 |
priority=-9999999 |
| 86 |
} |
| 87 |
Unplugging the wired enet didn't help (I waited a minute). |
| 88 |
The trivial /etc/wpa_supplicant/wpa_supplicant.conf had no effect. |
| 89 |
|
| 90 |
It looks strange. dmesg shows the iwlwifi driver responding, |
| 91 |
recognizing the card, and loading the microcode using iwlmvm (see above) |
| 92 |
What does L1 disabled mean? I googled and found other getting that msg |
| 93 |
but no explanation of what it means. |
| 94 |
|
| 95 |
thanks, |
| 96 |
allan |
Archives