OK thanks Nick for confirming.

For the WiFi part, yeah, we're stuck - can't get it working on this board. It's impossible for this class of mPCIe WiFI card without connectivity through the mPCIe connector. I figure the manufacturer's rep who sold this to me must have been quoting their experience on a similar albeit different version of this main board.

Since we do have USB connectivity, and the drivers for the RTL8822 are kinda "iffy" at this point (our developer at work has this exact same complaint), I'm going to try an rt3070-based card. I'll be back once I have the new card installed, either with a success story or more questions. Thanks again!

BTW: I've had a good experience for years with an AP in my attic. I think it's probably due to better average line-of-sight between the radios than if its at the same level as everyone in the house. Just my experience.

Unfortunately, yes, it looks like it is loading. Then I have no idea what to do about the WiFi part of it.

Hey Nick,

[root@gateway ~]# dmesg | grep -i bluetooth
[ 9.161183] Bluetooth: Core ver 2.22
[ 9.161237] Bluetooth: HCI device and connection manager initialized
[ 9.161251] Bluetooth: HCI socket layer initialized
[ 9.161255] Bluetooth: L2CAP socket layer initialized
[ 9.161267] Bluetooth: SCO socket layer initialized
[ 9.241576] Bluetooth: hci0: read Intel version: 370710018002030d56
[ 9.241583] Bluetooth: hci0: Intel device is already patched. patch num: 56
[root@gateway ~]#

Looks like it, correct?

Be very careful what you choose. It is a minfield. I have a USB device using, I thing, the RTL8812AU and I cannot get the drivers to work (or, could not last time I tried). The driver either does not support the correct PCI ID's, or, if you get a later one, will compile in Debian but not EL7/Centos/ClearOS due to the way they backport stuff. I believe you cannot get the correct version of hostapd for it, but I'm not sure. I'll have to look again some time, but I've tried many drivers on the www.

Does the Bluetooth part of the card initialise?

dmesg | grep -i bluetooth

Perfect - thank you both for the detailed response!

I also received a response from the manufacturer -

Dear Customer,
This is due to the limited number of PCIe lanes available on the CPU. Even though the card is connected through the PCIe form factor, the electrical connection on the hardware is through the USB.

As I suspected - for this board, I must use an mPCIe card that requires only the USB interface. Some examples of this are cards based upon the RT3070, or the RTL8192, RTL8191 or RTL8822 chips.

My preference would be to use an mPCIe card that uses the RTL8822, such as the RTL8822BU, as the chipset is one we are investigating at work as well. It came out in 2018.

So the firmware package is provided by linux-firmware and you should already have the version for the current 7.5 kernel installed as the linux-firmware package is a dependency of the kernel.

rt3070 firmware is in there as well

[root@server ~]# yum provides /usr/lib/firmware/rt2870.bin

Loaded plugins: clearcenter-marketplace, fastestmirror

ClearCenter Marketplace: fetching repositories...

Loading mirror speeds from cached hostfile

 <snip>

linux-firmware-20180220-62.git6d51311.el7.noarch : Firmware files used by the

                                                 : Linux kernel

Repo        : clearos-centos-verified

Matched from:

Filename    : /usr/lib/firmware/rt2870.bin







linux-firmware-20180220-62.1.git6d51311.el7_5.noarch : Firmware files used by

                                                     : the Linux kernel

Repo        : clearos-centos-verified

Matched from:

Filename    : /usr/lib/firmware/rt2870.bin







linux-firmware-20180220-62.2.git6d51311.el7_5.noarch : Firmware files used by

                                                     : the Linux kernel

Repo        : clearos

Matched from:

Filename    : /usr/lib/firmware/rt2870.bin







linux-firmware-20180220-62.2.git6d51311.el7_5.noarch : Firmware files used by

                                                     : the Linux kernel

Repo        : clearos-centos-verified

Matched from:

Filename    : /usr/lib/firmware/rt2870.bin







linux-firmware-20180220-62.2.git6d51311.el7_5.noarch : Firmware files used by

                                                     : the Linux kernel

Repo        : @clearos-centos-verified

Matched from:

Filename    : /usr/lib/firmware/rt2870.bin

So the firmware package is provided by linux-firmware and you should already have the version for the current 7.5 kernel installed as the linux-firmware package is a dependency of the kernel.

Try doing a:

locate rt2870

Hi,

Still working on this. I contacted the mfr rep and they claim the 7260 AC works fine out-of-the-box for Windows and Linux. I've told them that we've gotten the USB interface to recognize it, but that the PCI interface doesn't. And I've asked them to please tell me how to get the OS to see it.

I've been researching some things and I'm beginning to believe that for this particular main board, the WiFi mPCIe interface is not quite as advertised.

Quick question (hopefully): Do either of you know if the AzureWave AW-NU706H, based upon the RT3070L chip, is supported by the ClearOS 7.5 kernel? I'm guessing not just because tried to load the firmware for it (yum install rt2870-firmware, which should have worked) but it's not found in the repos.

Yes, It's actually an M.2 slot in that system - so has PCI Express 3.0, Serial ATA 3.0, USB 3.0 and NVMe (via PCIe) connectivity. Fair enough it is installed The PCIe sub-system should show something like this running lspci, and that card working properly...

02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 6b)

    Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c070]

    Kernel driver in use: iwlwifi

    Kernel modules: iwlwifi

The AR5BXB92 uses the AR9280 chipset...

Just google your card and "linux driver". It looks like the ATHEROS AR5B22 takes the ath9k. I'll let you search for the other one but there is a chance you'll be out of luck.

Alternatively you take the PDC ID from "lspci -knn" and search for that. If you find the driver then try a modinfo for the driver and see if the built in one lists the relevant PCI ID.

Hi Nick and Tony,

I did the last set of commands Nick sent::

[root@gateway ~]# lspci -knn | egrep -i 'eth|wifi|wire' -A 3
01:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
02:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
03:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
04:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e

[root@gateway ~]# lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 11)
Subsystem: Intel Corporation Device [8086:2212]
Kernel driver in use: iosf_mbi_pci
Kernel modules: iosf_mbi
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 11)
Subsystem: Intel Corporation Device [8086:2212]
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Multimedia controller [0480]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Camera ISP [8086:0f38] (rev 11)
Subsystem: Intel Corporation Device [8086:2212]
00:13.0 SATA controller [0106]: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller [8086:0f23] (rev 11)
Subsystem: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller [8086:0f23]
Kernel driver in use: ahci
Kernel modules: ahci
00:14.0 USB controller [0c03]: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35]
Kernel driver in use: xhci_hcd
00:1a.0 Encryption controller [1080]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18]
00:1c.0 PCI bridge [0604]: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 [8086:0f48] (rev 11)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 [8086:0f4a] (rev 11)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 [8086:0f4c] (rev 11)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 4 [8086:0f4e] (rev 11)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge [0601]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.3 SMBus [0c05]: Intel Corporation Atom Processor E3800 Series SMBus Controller [8086:0f12] (rev 11)
Subsystem: Intel Corporation Atom Processor E3800 Series SMBus Controller [8086:0f12]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
02:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
03:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
04:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e

[root@gateway ~]# modprobe iwlwifi
[root@gateway ~]# ip link show
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 pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:e0:67:10:86:08 brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:e0:67:10:86:09 brd ff:ff:ff:ff:ff:ff
4: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:e0:67:10:86:0a brd ff:ff:ff:ff:ff:ff
5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:e0:67:10:86:0b brd ff:ff:ff:ff:ff:ff
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
link/none
7: tun1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
link/none
8: tun2: <POINTOPOINT,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 500
link/none
9: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0


I know the card is installed because I installed it. There are settings in the BIOS for all four of the PCI as well as the USB ports, and as far as I can tell everything is on/enabled.

[root@gateway ~]# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 005: ID 046d:c058 Logitech, Inc. M115 Mouse
Bus 001 Device 004: ID 060b:0540 Solid Year DeltaCo TB-106U Keyboard
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[root@gateway ~]#

Device 003 is from the USB portion of the 7260 card.

So it seems that either the card doesn't have a functional PCI portion, or the issue lies in the PCI system somewhere on the motherboard. Let me know if you disagree with this.

I have a couple of other cards - an ATHEROS AR5B22 and AR5BXB92 - I can try to see if I can get any different responses from the PCI system. And I have another system at work I can use to see if the 7260 responds on PCI there.

If you can point me to the driver package to download for the Atheros cards that would be helpful. Also any other insights into possible PCI issues or other things I can check would help as well.

Thanks again to both of you for helping with this!

If this is the same Yanling system with E3845 Atom CPU - then it didn't show here... lspci output

The places that I checked on the web for this little box during that other thread all indicated the WiFi was optional. Have you actually checked inside to see that there is a WiFi card installed in the mini-PCIE slot, and inserted properly?

Bother. Typo:

lspci -knn | egrep -i 'eth|wifi|wire' -A 3

(extra space before "wire" but it should not have mattered). Can you see it if you just do "lspci -knn". From this link it should show something like:

02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 6b)

    Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c070]

    Kernel driver in use: iwlwifi

    Kernel modules: iwlwifi

Device 8086:08b1 is covered by the iwlwifi driver (but you snipped the output from the modinfo)

The driver should have loaded automatically on boot but obviously didn't.

I'd be concerned if it does not show with the lspci command. You are stuck if it does not. Either you have a failed card or are missing some sort of PCI Bus driver, I think.

Having done the modprobe, does the card show with "ip link show"?

So the first time I did
[root@gateway ~]# lsmod | grep iwlwif

I just got the prompt back. So I did the second, third and forth commands.


The 2nd time I did lsmod | grep iwlwif :

[root@gateway ~]# lsmod | grep iwlwif
iwlwifi 210814 0
cfg80211 623433 1 iwlwifi

[root@gateway ~]# modinfo iwlwifi
...
alias: pci:v00008086d00004232sv*sd00001304bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001204bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001301bc*sc*i*
alias: pci:v00008086d00004232sv*sd00001201bc*sc*i*
depends: cfg80211
intree: Y
vermagic: 3.10.0-862.11.6.v7.x86_64 SMP mod_unload modversions
signer: CentOS Linux kernel signing key
sig_key: A8:3C:CC:61:6B:01:A2:80:BB:33:24:28:04:9F:6F:0F:0D7:3B:76
sig_hashalgo: sha256
parm: swcrypto:using crypto in software (default 0 [hardware]) (int)
parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
parm: amsdu_size:amsdu size 0: 12K for multi Rx queue devices, 4K for other devices 1:4K 2:8K 3:12K (default 0) (int)
parm: fw_restart:restart firmware in case of error (default true) (bool)
parm: antenna_coupling:specify antenna coupling in dB (default: 0 dB) (int)
parm: nvm_file:NVM file name (charp)
parm: d0i3_disable:disable d0i3 functionality (default: Y) (bool)
parm: lar_disable:disable LAR functionality (default: N) (bool)
parm: uapsd_disable:disable U-APSD functionality bitmap 1: BSS 2: P2P Client (default: 3) (uint)
parm: bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
parm: led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
parm: power_save:enable WiFi power management (default: disable) (bool)
parm: power_level:default power save level (range from 1 - 5, default: 1) (int)
parm: fw_monitor:firmware monitor - to debug FW (default: false - needs lots of memory) (bool)
parm: d0i3_timeout:Timeout to D0i3 entry when idle (ms) (uint)
parm: disable_11acisable VHT capabilities (default: false) (bool)
[root@gateway ~]#


[root@gateway ~]# lspci -knn | egrep -i 'eth| wifi|wire' -A 3
01:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
02:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
03:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
04:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: Intel Corporation Device [8086:0000]
Kernel driver in use: e1000e
Kernel modules: e1000e
[root@gateway ~]#

These are obviously just the onboard Ethernet NICs.

I know if for lsusb, we get:

[root@gateway ~]# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 005: ID 046d:c058 Logitech, Inc. M115 Mouse
Bus 001 Device 004: ID 060b:0540 Solid Year DeltaCo TB-106U Keyboard
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[root@gateway ~]#

Device 003 is the BT controller on the 7260 card.

No. 6-8 are OpenVPN and 9, I think, could be libreswan/ipsec. This suggests you are missing the NIC drivers. Can you see if the iwlwifi driver is being loaded:

lsmod | grep iwlwif

If it is not, try loading it with a:

modprobe iwlwifi

If the NIC still does not show, please give the output to:

modinfo iwlwifi

and something like:

lspci -knn | egrep -i 'eth| wifi|wire' -A 3

Then cut the output down to just that of the Intel card.

OK thanks Dirk.

So when I do "ip link show" I get the following:

[root@gateway ~]# ip link show
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 pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:e0:67:10:86:08 brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:e0:67:10:86:09 brd ff:ff:ff:ff:ff:ff
4: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:e0:67:10:86:0a brd ff:ff:ff:ff:ff:ff
5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:e0:67:10:86:0b brd ff:ff:ff:ff:ff:ff
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
link/none
7: tun1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
link/none
8: tun2: <POINTOPOINT,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 500
link/none
9: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0

#2 - #5 are the on-board LAN ports. Would one of more of #6 - #9 correspond to the 7260 AC card (mPCIe connected to the only PCIe connector on the motherboard)?

See Nick’s post