[solved] ASRock J4105-ITX + Intel® Wireless 7265D

folatt · 2018-01-04 20:38:45

I'm trying to get my wi-fi card to work using NetworkManager.
After plugging it in, the wi-fi networks are disconnected and stays grey.

The card is however found.

[me@MyComputer ~]$ inxi -N
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           Card-2: Intel Wireless 7265 driver: iwlwifi

unblocked

[me@MyComputer ~]$ rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

It's firmware driver loads fine.

[me@MyComputer ~]$ dmesg | grep iwlwifi
[   16.674101] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[   16.687961] iwlwifi 0000:02:00.0: loaded firmware version 29.610311.0 op_mode iwlmvm
[   16.840606] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
[   16.858408] iwlwifi 0000:02:00.0: base HW address: 44:03:2c:1c:7a:50
[   16.903646] Modules linked in: i915(+) iwlmvm(+) intel_rapl snd_soc_skl intel_telemetry_pltdrv intel_punit_ipc intel_telemetry_core snd_soc_skl_ipc mac80211 intel_pmc_ipc snd_soc_sst_ipc i2c_algo_bit x86_pkg_temp_thermal snd_soc_sst_dsp intel_powerclamp nls_iso8859_1 drm_kms_helper coretemp snd_hda_ext_core nls_cp437 kvm_intel snd_soc_sst_match snd_hda_intel vfat fat snd_soc_rt298 iwlwifi snd_soc_rt286 kvm snd_soc_rl6347a snd_hda_codec snd_soc_core drm cfg80211 irqbypass intel_cstate intel_rapl_perf snd_compress mousedev wdat_wdt pcspkr snd_pcm_dmaengine snd_hda_core input_leds evdev r8169 led_class joydev snd_hwdep i2c_i801 lpc_ich ucsi_acpi mac_hid intel_gtt mii typec_ucsi tpm_tis tpm_tis_core snd_pcm tpm typec thermal fan shpchp rfkill_gpio agpgart snd_timer i2c_hid ac97_bus syscopyarea battery
[   16.925483] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0

But inet/inet6 address is missing for my wireless.

[me@MyComputer ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 70:85:c2:2a:10:5b brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.22/24 brd 192.168.178.255 scope global dynamic noprefixroute enp1s0
       valid_lft 857440sec preferred_lft 857440sec
    inet6 2001:983:8610:1:7db3:dbfb:4e1:c962/64 scope global dynamic noprefixroute 
       valid_lft 5112sec preferred_lft 3492sec
    inet6 fe80::bcd6:a590:353:13f8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether de:41:94:12:4c:e4 brd ff:ff:ff:ff:ff:ff

tcpdump shows no traffic going on

[me@MyComputer ~]$ sudo tcpdump -i wlp2s0 -vv
tcpdump: listening on wlp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
tcpdump: pcap_loop: The interface went down
0 packets captured
0 packets received by filter
0 packets dropped by kernel

NetworkManager shows that the interface wants to become active, but can't.

https://dpaste.de/rb9a

And there are no other network managers running (that I know of)

[me@MyComputer ~]$ systemctl list-units | grep -iE '(net|dhcp|wpa|conn|wicd)'
sys-devices-pci0000:00-0000:00:13.0-0000:01:00.0-net-enp1s0.device                       loaded active plugged   RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (Motherboard (one of many))
sys-devices-pci0000:00-0000:00:13.1-0000:02:00.0-net-wlp2s0.device                       loaded active plugged   Wireless 7265 (Dual Band Wireless-AC 7265)                                           
sys-subsystem-net-devices-enp1s0.device                                                  loaded active plugged   RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (Motherboard (one of many))
sys-subsystem-net-devices-wlp2s0.device                                                  loaded active plugged   Wireless 7265 (Dual Band Wireless-AC 7265)                                           
sys-fs-fuse-connections.mount                                                            loaded active mounted   FUSE Control File System                                                             
NetworkManager.service                                                                   loaded active running   Network Manager                                                                      
ntpd.service                                                                             loaded active running   Network Time Service                                                                 
wpa_supplicant.service                                                                   loaded active running   WPA supplicant                                                                       
network.target                                                                           loaded active active    Network

What to do?

Last edited by folatt (2019-12-27 21:51:42)

lo1 · 2018-01-05 14:18:29

Jan 04 23:17:29 MyComputer NetworkManager[378]: <info>  [1515104249.5666] device (wlp2s0): set-hw-addr: set MAC address to BE:D3:63:47:6C:BF (scanning)
Jan 04 23:17:29 MyComputer NetworkManager[378]: <info>  [1515104249.6109] device (wlp2s0): supplicant interface state: ready -> disconnected
Jan 04 23:17:29 MyComputer NetworkManager[378]: <info>  [1515104249.6163] device (wlp2s0): supplicant interface state: disconnected -> inactive
Jan 04 23:22:40 MyComputer NetworkManager[378]: <info>  [1515104560.5665] device (wlp2s0): set-hw-addr: set MAC address to F6:B1:B4:33:51:D4 (scanning)
Jan 04 23:22:40 MyComputer NetworkManager[378]: <info>  [1515104560.6112] device (wlp2s0): supplicant interface state: inactive -> disconnected
Jan 04 23:22:40 MyComputer NetworkManager[378]: <info>  [1515104560.6167] device (wlp2s0): supplicant interface state: disconnected -> inactive
Jan 04 23:27:55 MyComputer NetworkManager[378]: <info>  [1515104875.6267] device (wlp2s0): set-hw-addr: set MAC address to 2E:FA:7A:20:58:F6 (scanning)
Jan 04 23:27:55 MyComputer NetworkManager[378]: <info>  [1515104875.6673] device (wlp2s0): supplicant interface state: inactive -> disconnected
Jan 04 23:27:55 MyComputer NetworkManager[378]: <info>  [1515104875.6728] device (wlp2s0): supplicant interface state: disconnected -> inactive
Jan 04 23:33:10 MyComputer NetworkManager[378]: <info>  [1515105190.6093] device (wlp2s0): set-hw-addr: set MAC address to 6E:CA:DB:79:85:BC (scanning)
Jan 04 23:33:10 MyComputer NetworkManager[378]: <info>  [1515105190.6542] device (wlp2s0): supplicant interface state: inactive -> disconnected
Jan 04 23:33:10 MyComputer NetworkManager[378]: <info>  [1515105190.6594] device (wlp2s0): supplicant interface state: disconnected -> inactive
Jan 04 23:38:25 MyComputer NetworkManager[378]: <info>  [1515105505.5667] device (wlp2s0): set-hw-addr: set MAC address to B6:0F:C5:B4:0B:4C (scanning)
Jan 04 23:38:25 MyComputer NetworkManager[378]: <info>  [1515105505.6278] device (wlp2s0): supplicant interface state: inactive -> disconnected
Jan 04 23:38:25 MyComputer NetworkManager[378]: <info>  [1515105505.6331] device (wlp2s0): supplicant interface state: disconnected -> inactive
Jan 04 23:43:40 MyComputer NetworkManager[378]: <info>  [1515105820.5666] device (wlp2s0): set-hw-addr: set MAC address to 36:FB:BD:97:40:8C (scanning)
Jan 04 23:43:40 MyComputer NetworkManager[378]: <info>  [1515105820.6207] device (wlp2s0): supplicant interface state: inactive -> disconnected
Jan 04 23:43:40 MyComputer NetworkManager[378]: <info>  [1515105820.6263] device (wlp2s0): supplicant interface state: disconnected -> inactive

These are "errors", in the sense that the interface is going mad to become active: did you connect both through wpa_supplicant and NetworkManager? (don't do it, NetworkManager will call wpa_supplicant when needed AFAIK)
Please post how you connect step by step, and eventually try to connect manually through wpa_supplicant only with the debug "-d" option set.

folatt · 2018-01-05 21:48:09

I disabled wpa_supplicant.service and wil work with NetworkManager only.

I only enabled it because NetworkManager was and still is showing Wi-Fi networking as "disconnected".

I rebooted and am experiencing the same problems.

Last edited by folatt (2018-01-05 22:33:55)

lo1 · 2018-01-06 11:04:24

Disconnect enp1s0 and try connecting wlp2s0 with

wpa_supplicant -d -i wlp2s0 -c<(wpa_passphrase "SSID" "PASSWORD")

again, make sure you're not running NetworkManager when doing this, and paste the output here.

You need a root shell (su) to run wpa_supplicant like this.

Last edited by lo1 (2018-01-06 14:21:02)

folatt · 2018-01-06 22:52:58

Here you go, it freezes at the last line.

https://dpaste.de/FzMM

Last edited by folatt (2018-07-18 21:26:40)

lo1 · 2018-01-07 08:39:05

wlp2s0: No suitable network found

Either the SSID you entered is wrong (I doubt that, but let's take it into account...) or:
-you're too far from the router
-this wireless NIC isn't powerful enough to scan for relatively near networks
-you need to fine tune the driver

Let's assume it's the least, what's the output of

modinfo iwlwifi
systool -m iwlwifi -av

ewaller · 2018-01-07 16:38:03

As a sanity check, what are the output of iw phy and of sudo iw dev wlp2s0 scan
?

folatt · 2018-01-07 18:45:18

modinfo iwlwifi

[me@MyComputer ~]$ modinfo iwlwifi
modinfo: ERROR: Module alias iwlwifi not found.

systool -m iwlwifi -av

https://dpaste.de/g8iH

iw phy

https://dpaste.de/reQr

sudo iw dev wlp2s0 scan

[me@MyComputer ~]$ sudo iw dev wlp2s0 scan
command failed: Network is down (-100)

Last edited by folatt (2018-07-18 21:28:15)

ewaller · 2018-01-07 18:58:17

Let's try this:
sudo ip link set wlp2s0 up followed by the sudo iw dev wlp2s0 scan

lo1 · 2018-01-08 10:19:11

modinfo: ERROR: Module alias iwlwifi not found.

???

uname -r
ls /lib/modules/`uname -r`/kernel/drivers/net/wireless
ls /lib/modules/`uname -r`/build/drivers/net/wireless

Please post the full output of the above, if you have an "intel" folder inside .../net/wireless post the content of that too.

Also, as ewaller is noting, was the interface up when you run

sudo iw dev wlp2s0 scan
command failed: Network is down (-100)

folatt · 2018-01-08 20:03:11

ewaller

[me@MyComputer ~]$ sudo ip link set wlp2s0 up
[me@MyComputer ~]$ sudo iw dev wlp2s0 scan
[me@MyComputer ~]$

lo1

[me@MyComputer ~]$ uname -r
4.14.11-1-ARCH
[me@MyComputer ~]$ ls /lib/modules/4.14.12-1-ARCH/kernel/drivers/net/wireless
admtek  atmel     cisco  intersil  mediatek   ralink        realtek           rsi  ti               zydas
ath     broadcom  intel  marvell   quantenna  ray_cs.ko.xz  rndis_wlan.ko.xz  st   wl3501_cs.ko.xz
[me@MyComputer ~]$ ls /lib/modules/4.14.12-1-ARCH/kernel/drivers/net/wireless/intel
ipw2x00  iwlegacy  iwlwifi
[me@MyComputer ~]$ ls /lib/modules/4.14.12-1-ARCH/kernel/drivers/net/wireless/intel/iwlwifi
dvm  iwlwifi.ko.xz  mvm
[me@MyComputer ~]$ ls /lib/modules/4.14.12-1-ARCH/build/
vmlinux

Last edited by folatt (2018-01-08 21:56:06)

lo1 · 2018-01-09 11:25:58

There's something wrong with your kernel. What was the last time you did update it (check your pacman log)? Have a look at `pacman -Q linux`, eventually reinstall the kernel (and linux-headers) and make sure that `uname -r`is the same of /lib/modules/`uname -r`.

Check also inside /lib/firmware whether the driver is listed.

What is even more weird is that dmesg is reporting everything ok

folatt · 2018-01-09 20:41:51

lo1 wrote:

There's something wrong with your kernel. What was the last time you did update it (check your pacman log)? Have a look at `pacman -Q linux`, eventually reinstall the kernel (and linux-headers) and make sure that `uname -r`is the same of /lib/modules/`uname -r`.

Not long ago, but it seems like linux-headers was missing.

lo1 wrote:

Check also inside /lib/firmware whether the driver is listed.

It's listed.

...
-rw-r--r-- 1 root root  682K Dec  7 02:24 iwlwifi-7265-9.ucode
lrwxrwxrwx 1 root root    21 Dec  7 02:24 iwlwifi-7265D-10.ucode -> iwlwifi-7265-10.ucode
-rw-r--r-- 1 root root  980K Dec  7 02:24 iwlwifi-7265D-12.ucode
-rw-r--r-- 1 root root  986K Dec  7 02:24 iwlwifi-7265D-13.ucode
-rw-r--r-- 1 root root  1.4M Dec  7 02:24 iwlwifi-7265D-16.ucode
-rw-r--r-- 1 root root  1.4M Dec  7 02:24 iwlwifi-7265D-17.ucode
-rw-r--r-- 1 root root  1.4M Dec  7 02:24 iwlwifi-7265D-21.ucode
-rw-r--r-- 1 root root 1005K Dec  7 02:24 iwlwifi-7265D-22.ucode
-rw-r--r-- 1 root root 1009K Dec  7 02:24 iwlwifi-7265D-27.ucode
-rw-r--r-- 1 root root 1013K Dec  7 02:24 iwlwifi-7265D-29.ucode
-rw-r--r-- 1 root root  1.7M Dec  7 02:24 iwlwifi-8000C-13.ucode
...

What is even more weird is that dmesg is reporting everything ok

I find that strange as well.

..Well, so far the installation of the linux headers has at least led to the interface no longer starting as dormant, so I don't have to change it to default mode anymore everytime I reboot.

This command is now working:

https://dpaste.de/CFug

What's the equivalent of 'iwconfig wlan0 channel auto' for iw?

I'm asking because this section says that if I use dhcpcd and I get a 'waiting for carrier' error,
I should try to set it's channel mode to auto with iwconfig.

[me@MyComputer ~]$ sudo dhcpcd wlp2s0
wlp2s0: waiting for carrier
wlp2s0: carrier acquired
DUID 00:01:00:01:21:e4:04:76:70:85:c2:2a:10:5b
wlp2s0: IAID 2c:1c:7a:50
wlp2s0: adding address fe80::e269:45bf:1713:7cb2
wlp2s0: carrier lost
wlp2s0: deleting address fe80::e269:45bf:1713:7cb2
timed out
dhcpcd exited

This is what my manual attempt now looks like:

https://dpaste.de/CXqV

Last edited by folatt (2018-07-18 21:30:06)

lo1 · 2018-01-09 23:51:17

Ok, we're making some progress here, but:

What's the equivalent of 'iwconfig wlan0 channel auto' for iw?
I'm asking because this section says that if I use dhcpcd and I get a 'waiting for carrier' error,

this is not relevant because the carrier is actually acquired

dhcpcd wlp2s0 wrote:

wlp2s0: waiting for carrier
wlp2s0: carrier acquired

You could try another dhcp client (e.g. dhclient), but why are you trying to get an IP address?

I mean, did you finally manage to connect to your network? Does the SSID appear when you scan for networks with `iw dev wlp2s0 scan`?

folatt · 2018-01-10 06:41:42

lo1 wrote:

You could try another dhcp client (e.g. dhclient), but why are you trying to get an IP address?
I mean, did you finally manage to connect to your network? Does the SSID appear when you scan for networks with `iw dev wlp2s0 scan`?

No and no.

Is "NO-CARRIER" normal to see in `ip link`?

[me@MyComputer ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:2a:10:5b brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 7e:1a:1e:79:a3:29 brd ff:ff:ff:ff:ff:ff

P.S. wlp2s0 starts as dormant due to NetworkManager, not because I installed linux-header, but in any case, the drivers are now present, so those module commands started working, so it's still progress.

Last edited by folatt (2018-01-10 10:10:23)

lo1 · 2018-01-10 13:58:42

NO-CARRIER is normal due to the fact that the interface is UP but not associated with any access point/router, usually until the 4-way-handshake is complete.

I'm thinking: which IEEE 802.11 standards and which frequency does your router support? Check for your model online or have a look at its settings (you're searching for "802.11a/b/c/g/n")

And which protocols does your NIC support?

iwconfig wlp2s0

Look for "IEEE 802.11" and "Frequency", paste the output here along with information about your router.

Last edited by lo1 (2018-01-10 14:44:55)

folatt · 2018-01-11 00:08:52

I'm thinking: which IEEE 802.11 standards and which frequency does your router support? Check for your model online or have a look at its settings (you're searching for "802.11a/b/c/g/n")

Model: FRITZ!Box 7581

WiFi

Wireless AC (up to 1300 Mbit/s gross, 5 GHz) and N (up to 450 Mbit/s gross, 2.4 GHz)
Compatible with Wireless 802.11g, b and a
Secure ex works with WPA2 encryption
AVM Stick & Surf: automatic security for wireless surfing
WLAN can be turned on and off via switch and connected telephones
Wi-Fi Protected Setup (WPS)
Wireless guest access – secure surfing for friends and visitors
Wireless auto channel: Automated search for wireless LAN radio channel free of interference
Green AP mode for optimum performance at minimum power consumption

Wireless access point compliant with IEEE 802.11ac, n, g, b, a

And which protocols does your NIC support?

I'm not sure what you mean by that question.

iwconfig wlp2s0

wlp2s0    IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

Last edited by folatt (2018-01-11 08:09:52)

lo1 · 2018-01-11 11:07:32

I'm at a loss here, last thing I'd try is (make sure the interface is down and not managed):

rmmod iwlwifi
modprobe iwlwifi 11n_disable=1

Check with systool if the options has been succesfully set, and try connecting again. (you could pass this option with /etc/modprobe.d if in doubt)

folatt · 2018-01-12 06:41:05

I'm not sure how to do that.
I don't think I've succeeded.

[me@MyComputer ~]$ sudo ip link set wlp2s0 down
[me@MyComputer ~]$ sudo iwconfig wlp2s0 mode monitor
[me@MyComputer ~]$ sudo rmmod iwlwifi
rmmod: ERROR: Module iwlwifi is in use by: iwlmvm
[me@MyComputer ~]$ sudo rmmod iwlmvm
[me@MyComputer ~]$ sudo rmmod iwlwifi
[me@MyComputer ~]$ echo "11n_disable=1" | sudo tee /etc/modprobe.d/iwlwifi
11n_disable=1
[me@MyComputer ~]$ sudo modprobe iwlwifi 11n_disable=1
[me@MyComputer ~]$ sudo modprobe iwlmvm
[me@MyComputer ~]$ systool -m iwlwifi
Module = "iwlwifi"

[me@MyComputer ~]$

Since this doesn't seem to go anywhere,
I ordered an Intel Dual Band Wireless-AC 8265 and will try to use that instead.
If that doesn't work, that would eliminate a lot of possible causes wouldn't it?

Last edited by folatt (2018-01-12 07:45:25)

lo1 · 2018-01-12 10:29:23

folatt wrote:

[me@MyComputer ~]$ echo "11n_disable=1" | sudo tee /etc/modprobe.d/iwlwifi

Module configuration files muste be put inside modprobe.d with a ".conf" extension. But I'm not sure if you need to reboot for them to be applied.

[me@MyComputer ~]$ sudo modprobe iwlwifi 11n_disable=1
[me@MyComputer ~]$ systool -m iwlwifi

Anyway, the modprobe here should have worked, but you needed to input `systool -avm iwlwifi` to check for changes.

If this still doesn't work then I really don't know. I don't feel like suggesting people to buy new things, but since you've done this on your own let's see if that will work eventually.

Last edited by lo1 (2018-01-12 10:31:06)

folatt · 2018-01-24 09:03:02

I finally got the Intel® Wireless-AC Dual Band 8265.
And I have the same problem again.

[me@MyComputer ~]$ inxi -N
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           Card-2: Intel Wireless 8265 / 8275 driver: iwlwifi

[me@MyComputer ~]$ rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

[me@MyComputer ~]$ dmesg | grep iwlwifi
[   16.549173] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[   16.570125] iwlwifi 0000:02:00.0: loaded firmware version 34.0.1 op_mode iwlmvm
[   16.706240] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[   16.710223] Modules linked in: coretemp snd_soc_sst_ipc iwlmvm(+) i915(+) kvm_intel snd_soc_sst_dsp mac80211 snd_hda_ext_core snd_soc_sst_match nls_iso8859_1 snd_soc_rt298 nls_cp437 snd_soc_rt286 i2c_algo_bit vfat snd_soc_rl6347a drm_kms_helper kvm fat snd_soc_core iwlwifi snd_hda_intel drm snd_hda_codec irqbypass snd_hda_core intel_gtt snd_compress intel_cstate snd_pcm_dmaengine evdev wdat_wdt pcspkr r8169 snd_hwdep agpgart mei_me intel_rapl_perf cfg80211 i2c_i801 lpc_ich input_leds mii joydev syscopyarea mousedev tpm_tis sysfillrect led_class ucsi_acpi mac_hid tpm_tis_core snd_pcm typec_ucsi sysimgblt mei tpm fan thermal fb_sys_fops shpchp snd_timer typec i2c_hid rfkill_gpio snd button battery soundcore ac97_bus video pinctrl_broxton pinctrl_intel sch_fq_codel btusb btrtl btbcm btintel bluetooth
[   16.762184] iwlwifi 0000:02:00.0: base HW address: 74:e5:f9:98:29:ca
[   16.849591] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0

[me@MyComputer ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 70:85:c2:2a:10:5b brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.22/24 brd 192.168.178.255 scope global dynamic noprefixroute enp1s0
       valid_lft 863311sec preferred_lft 863311sec
    inet6 2001:983:8610:1:7db3:dbfb:4e1:c962/64 scope global dynamic noprefixroute 
       valid_lft 5463sec preferred_lft 3438sec
    inet6 fe80::bcd6:a590:353:13f8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 5e:50:f6:bf:fd:b6 brd ff:ff:ff:ff:ff:ff

journalctl -b -u NetworkManager --no-pager
https://dpaste.de/iS3e

modinfo iwlwifi
https://dpaste.de/KQbz

Last edited by folatt (2018-07-18 21:32:42)

WorMzy · 2018-01-24 09:24:07

[me@MyComputer ~]$ inxi -F
System:    Host: Slumberstone Kernel: 4.14.14-1-ARCH x86_64 bits: 64

But from your binned topic:

[me@MyComputer ~]$ modinfo iwlwifi
filename:       /lib/modules/4.14.13-1-ARCH/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko.xz

Have you updated this machine since posting that? Or is there still a discrepancy as seen in post #11? Do you have any other OSes on this machine? Do they share a boot/ESP?

folatt · 2018-01-24 09:26:49

WorMzy wrote:

Have you updated this machine since posting that? Or is there still a discrepancy as seen in post #11? Do you have any other OSes on this machine? Do they share a boot/ESP?

Yes, I updated the machine since posting that.
It resulted in the network card not being found, so I took it out and carefully put it back in.
The above post are the current results.

[update]

I notice that the MAC keeps changing of the network interface every few minutes.

[me@MyComputer ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 70:85:c2:2a:10:5b brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.22/24 brd 192.168.178.255 scope global dynamic noprefixroute enp1s0
       valid_lft 860301sec preferred_lft 860301sec
    inet6 2001:983:8610:1:7db3:dbfb:4e1:c962/64 scope global dynamic noprefixroute 
       valid_lft 6052sec preferred_lft 3424sec
    inet6 fe80::bcd6:a590:353:13f8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 2a:10:06:24:79:ce brd ff:ff:ff:ff:ff:ff
[me@MyComputer ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 70:85:c2:2a:10:5b brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.22/24 brd 192.168.178.255 scope global dynamic noprefixroute enp1s0
       valid_lft 860133sec preferred_lft 860133sec
    inet6 2001:983:8610:1:7db3:dbfb:4e1:c962/64 scope global dynamic noprefixroute 
       valid_lft 5885sec preferred_lft 3257sec
    inet6 fe80::bcd6:a590:353:13f8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 82:6b:7c:d3:91:85 brd ff:ff:ff:ff:ff:ff

Last edited by folatt (2018-01-24 10:21:59)

V1del · 2018-01-24 09:42:18

Maybe your router or the card has an issue with the changing MAC, try following https://wiki.archlinux.org/index.php/Ne … domization and disable the MAC address randomization.

In addition because it did cause a lot of similar issues, change to dhclient instead of NM's internal dhcp https://wiki.archlinux.org/index.php/Ne … HCP_client

Does your router work otherwise? Are you able to connect with other devices?

folatt · 2018-01-24 10:27:50

V1del wrote:

Maybe your router or the card has an issue with the changing MAC

I don't see how my router could be responsible for this. My router works fine.

[update]

The wi-fi part of my card has disappeared entirely again.
Could this be due to a faulty motherboard?

Last edited by folatt (2018-01-24 10:38:32)

Arch Linux

#1 2018-01-04 20:38:45

[solved] ASRock J4105-ITX + Intel® Wireless 7265D

#2 2018-01-05 14:18:29

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#3 2018-01-05 21:48:09

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#4 2018-01-06 11:04:24

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#5 2018-01-06 22:52:58

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#6 2018-01-07 08:39:05

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#7 2018-01-07 16:38:03

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#8 2018-01-07 18:45:18

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#9 2018-01-07 18:58:17

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#10 2018-01-08 10:19:11

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#11 2018-01-08 20:03:11

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#12 2018-01-09 11:25:58

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#13 2018-01-09 20:41:51

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#14 2018-01-09 23:51:17

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#15 2018-01-10 06:41:42

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#16 2018-01-10 13:58:42

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#17 2018-01-11 00:08:52

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#18 2018-01-11 11:07:32

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#19 2018-01-12 06:41:05

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#20 2018-01-12 10:29:23

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#21 2018-01-24 09:03:02

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#22 2018-01-24 09:24:07

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#23 2018-01-24 09:26:49

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#24 2018-01-24 09:42:18

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

#25 2018-01-24 10:27:50

Re: [solved] ASRock J4105-ITX + Intel® Wireless 7265D

Board footer