NUC: Drivers for Intel AC-9462 wireless

MikeC

Renowned Member
Jan 11, 2016
71
0
71
Bay Area, California
Hello, all.
I've done a fresh install of Proxmox 5.1 on a new NUC 7CJYH and don't see the AC-9462 wireless in lspci at all. Any ideas whan I need to do to enable that device. I handles both Wifi and Bluetooth, and I'd like to at a minimum get Wifi working.

Thanks.
 
Hi,

Intel wireless driver are property, so you have to enable the non-free repository.

see
https://wiki.debian.org/iwlwifi
When I try to follow the steps here, it tells me that it needs to remove the following packages in order to install firmware-iwlwifi:
Code:
1)     proxmox-ve [5.2-2 (now, stable)]
2)     pve-firmware [2.0-4 (now, stable)]
3)     pve-kernel-4.15 [5.2-1 (now, stable)]
I assume that this would break the proxmox install, so I will need to find another way to install the proper drivers to get wifi working.
 
Hey, @Taylor Murphy

have you managed to do anything about it? Similar NUC here, with the same wifi card. After adding the "non-free" to the repository list, I've updated the "pve-firmware" package (haven't installed "firmware-iwlwifi" package) and the adapter showed up. Unfortunately, I haven't been able to do anything further with it. It's down and stays down whatever I try to do. I'm a total noob, so that wasn't much up till now.

The relevant part of the lspci -k output:
Code:
0:0c.0 Network controller: Intel Corporation Device 31dc (rev 03)
        Subsystem: Intel Corporation Device 02a4
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

The dmesg | grep -e iwl -e wlp output:
Code:
[    4.234332] iwlwifi 0000:00:0c.0: enabling device (0000 -> 0002)
[    4.253387] iwlwifi 0000:00:0c.0: loaded firmware version 34.3125811985.0 op_mode iwlmvm
[    4.278133] iwlwifi 0000:00:0c.0: Detected Intel(R) Dual Band Wireless AC 9462, REV=0x318
[    4.331209] iwlwifi 0000:00:0c.0: base HW address: bl:bl:bl:bl:bl:bl
[    4.446013] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    4.859923] iwlwifi 0000:00:0c.0 wlo2: renamed from wlan0
[   68.347970] iwlwifi 0000:00:0c.0: Conflict between TLV & NVM regarding enabling LAR (TLV = enabled NVM =disabled)

The ip a output:
Code:
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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether bl:bl:bl:bl:bl:bl brd ff:ff:ff:ff:ff:ff
3: wlo2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether bl:bl:bl:bl:bl:bl brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether bl:bl:bl:bl:bl:bl brd ff:ff:ff:ff:ff:ff
    inet xxx.xxx.xxx.xxx/24 brd xxx.xxx.xxx.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::xxxxxxxx:xxxx:xxxx/64 scope link
       valid_lft forever preferred_lft forever

Going with the "conflict" listed in the last line of dmesg output, first I've tried a suggestion I found somewhere -
Code:
sudo modprobe -r iwlwifi && sudo modprobe iwlwifi lar_disable=Y
, but got
Code:
modprobe: FATAL: Module iwlwifi is in use.
; then I've tried puting
Code:
options iwlwifi lar_disable=Y
in /etc/modprobe.d/iwlwifi.conf and rebooting, but still no luck with the ip link set wlo2 up command.
 
I have exactly the same problem with "apt-get install firmware-iwlwifi" from non-free debian repository.
It conflicts with pve-firmware and I can't go on. I need to use the bluetooth device in the nuc for a project.
There is a way to install non-free firmwares using pve-firmware package?
 
There is a way to install non-free firmwares using pve-firmware package?
You can't install any packages what conflict with pve-firmware.

The only way is to extract the files and copy them manually.
 
You can't install any packages what conflict with pve-firmware.

The only way is to extract the files and copy them manually.

This is exactly what I want to achieve.
I have identified the firmware files for Intel Bluetooth but I can't copy them in /lib/firmware (it is mounted read only)
What is the correct way to add firmware files manually?
 
Download the firmware deb.
extract the deb with "ar".
extract the data.tar
copy the content. The structure is in the data tar.
 
Nice, but the content must be copied in /lib/firmware which is read only:

Code:
./firmware:
total 40208
drwxr-xr-x 3 root root    4096 Feb 24 03:43 .
drwxr-xr-x 3 root root    4096 Feb 24 03:43 ..
drwxr-xr-x 2 root root    4096 Feb 24 03:43 intel
-rw-r--r-- 1 root root  337520 Feb 24 03:43 iwlwifi-1000-5.ucode
-rw-r--r-- 1 root root  337572 Feb 24 03:43 iwlwifi-100-5.ucode
-rw-r--r-- 1 root root  689680 Feb 24 03:43 iwlwifi-105-6.ucode
-rw-r--r-- 1 root root  701228 Feb 24 03:43 iwlwifi-135-6.ucode
-rw-r--r-- 1 root root  695876 Feb 24 03:43 iwlwifi-2000-6.ucode
-rw-r--r-- 1 root root  707392 Feb 24 03:43 iwlwifi-2030-6.ucode
-rw-r--r-- 1 root root  918268 Feb 24 03:43 iwlwifi-3160-17.ucode
-rw-r--r-- 1 root root  669872 Feb 24 03:43 iwlwifi-3160-9.ucode
-rw-r--r-- 1 root root 1028092 Feb 24 03:43 iwlwifi-3168-22.ucode
-rw-r--r-- 1 root root 1036276 Feb 24 03:43 iwlwifi-3168-29.ucode
-rw-r--r-- 1 root root  150100 Feb 24 03:43 iwlwifi-3945-2.ucode
-rw-r--r-- 1 root root  187972 Feb 24 03:43 iwlwifi-4965-2.ucode
-rw-r--r-- 1 root root  340696 Feb 24 03:43 iwlwifi-5000-5.ucode
-rw-r--r-- 1 root root  337400 Feb 24 03:43 iwlwifi-5150-2.ucode
-rw-r--r-- 1 root root  454608 Feb 24 03:43 iwlwifi-6000-4.ucode
-rw-r--r-- 1 root root  444128 Feb 24 03:43 iwlwifi-6000g2a-5.ucode
-rw-r--r-- 1 root root  677296 Feb 24 03:43 iwlwifi-6000g2a-6.ucode
-rw-r--r-- 1 root root  679436 Feb 24 03:43 iwlwifi-6000g2b-6.ucode
-rw-r--r-- 1 root root  469780 Feb 24 03:43 iwlwifi-6050-5.ucode
-rw-r--r-- 1 root root 1049340 Feb 24 03:43 iwlwifi-7260-17.ucode
-rw-r--r-- 1 root root  680508 Feb 24 03:43 iwlwifi-7260-9.ucode
-rw-r--r-- 1 root root 1180412 Feb 24 03:43 iwlwifi-7265-17.ucode
-rw-r--r-- 1 root root  697828 Feb 24 03:43 iwlwifi-7265-9.ucode
-rw-r--r-- 1 root root 1028376 Feb 24 03:43 iwlwifi-7265D-22.ucode
-rw-r--r-- 1 root root 1036432 Feb 24 03:43 iwlwifi-7265D-29.ucode
-rw-r--r-- 1 root root 2120860 Feb 24 03:43 iwlwifi-8000C-22.ucode
-rw-r--r-- 1 root root 2486572 Feb 24 03:43 iwlwifi-8000C-36.ucode
-rw-r--r-- 1 root root 1811984 Feb 24 03:43 iwlwifi-8265-22.ucode
-rw-r--r-- 1 root root 2498044 Feb 24 03:43 iwlwifi-8265-36.ucode
-rw-r--r-- 1 root root 2678284 Feb 24 03:43 iwlwifi-9000-pu-b0-jf-b0-34.ucode
-rw-r--r-- 1 root root 2520568 Feb 24 03:43 iwlwifi-9000-pu-b0-jf-b0-38.ucode
-rw-r--r-- 1 root root 2620464 Feb 24 03:43 iwlwifi-9000-pu-b0-jf-b0-41.ucode
-rw-r--r-- 1 root root 2678092 Feb 24 03:43 iwlwifi-9260-th-b0-jf-b0-34.ucode
-rw-r--r-- 1 root root 2521412 Feb 24 03:43 iwlwifi-9260-th-b0-jf-b0-38.ucode
-rw-r--r-- 1 root root 2620656 Feb 24 03:43 iwlwifi-9260-th-b0-jf-b0-41.ucode

./firmware/intel:
total 3892
drwxr-xr-x 2 root root   4096 Feb 24 03:43 .
drwxr-xr-x 3 root root   4096 Feb 24 03:43 ..
-rw-r--r-- 1 root root     18 Feb 24 03:43 ibt-11-5.ddc
-rw-r--r-- 1 root root 588196 Feb 24 03:43 ibt-11-5.sfi
-rw-r--r-- 1 root root     14 Feb 24 03:43 ibt-12-16.ddc
-rw-r--r-- 1 root root 585328 Feb 24 03:43 ibt-12-16.sfi
-rw-r--r-- 1 root root     14 Feb 24 03:43 ibt-17-0-1.ddc
-rw-r--r-- 1 root root 625216 Feb 24 03:43 ibt-17-0-1.sfi
-rw-r--r-- 1 root root     14 Feb 24 03:43 ibt-17-16-1.ddc
-rw-r--r-- 1 root root 641280 Feb 24 03:43 ibt-17-16-1.sfi
-rw-r--r-- 1 root root     14 Feb 24 03:43 ibt-18-0-1.ddc
-rw-r--r-- 1 root root 625216 Feb 24 03:43 ibt-18-0-1.sfi
-rw-r--r-- 1 root root     14 Feb 24 03:43 ibt-18-16-1.ddc
-rw-r--r-- 1 root root 641280 Feb 24 03:43 ibt-18-16-1.sfi
-rw-r--r-- 1 root root  22069 Feb 24 03:43 ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq
-rw-r--r-- 1 root root  25853 Feb 24 03:43 ibt-hw-37.7.10-fw-1.0.2.3.d.bseq
-rw-r--r-- 1 root root  23105 Feb 24 03:43 ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
-rw-r--r-- 1 root root  25775 Feb 24 03:43 ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
-rw-r--r-- 1 root root     96 Feb 24 03:43 ibt-hw-37.7.bseq
-rw-r--r-- 1 root root  31056 Feb 24 03:43 ibt-hw-37.8.10-fw-1.10.2.27.d.bseq
-rw-r--r-- 1 root root  39295 Feb 24 03:43 ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
-rw-r--r-- 1 root root  48587 Feb 24 03:43 ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
-rw-r--r-- 1 root root     96 Feb 24 03:43 ibt-hw-37.8.bseq
 
You have to be root to write in this dir.
 
Sure I am root but when I copy files in /lib/firmware seems to not persist after reboot.
They really should. What could be misleading here ist that usually the needed firmware is copied into the initramfs - and if you modify the directory and don't update your initramfs - it won't contain the firmwares.

Usually running `update-initramfs -k all -u` is enough to resolve this.

Hope this helps!
 
They really should. What could be misleading here ist that usually the needed firmware is copied into the initramfs - and if you modify the directory and don't update your initramfs - it won't contain the firmwares.

Usually running `update-initramfs -k all -u` is enough to resolve this.

Hope this helps!

I think this was the missing information for me.
I will try in the evening and report back.
 
Perfect, bluetooth firmware now loads:

Code:
[   67.617090] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[   69.297142] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc
 
I'm struggling to get Bluetooth working with my NUC8I3BEH. I've tried the steps listed here:

1. Download the Intel drivers
2. Extract the data tar file
3. Place all the drivers in the /lib/firmware directory
4. Reboot

This is what I get when I check for Bluetooth:

dmesg | grep -i blue
[ 3.955872] Bluetooth: Core ver 2.22 [ 3.955888] Bluetooth: HCI device and connection manager initialized [ 3.955890] Bluetooth: HCI socket layer initialized [ 3.955892] Bluetooth: L2CAP socket layer initialized [ 3.955897] Bluetooth: SCO socket layer initialized [ 3.980744] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 [ 3.981748] Bluetooth: hci0: Device revision is 2 [ 3.981749] Bluetooth: hci0: Secure boot is enabled [ 3.981749] Bluetooth: hci0: OTP lock is enabled [ 3.981750] Bluetooth: hci0: API lock is enabled [ 3.981750] Bluetooth: hci0: Debug lock is disabled [ 3.981751] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 3.989887] bluetooth hci0: Direct firmware load for intel/ibt-17-16-1.sfi failed with error -2 [ 3.989890] Bluetooth: hci0: Failed to load Intel firmware file (-2)

Any suggestions?

Sorry if my formatting is messed up. First post here
 
I'm struggling to get Bluetooth working with my NUC8I3BEH. I've tried the steps listed here:

1. Download the Intel drivers
2. Extract the data tar file
3. Place all the drivers in the /lib/firmware directory
4. Reboot

This is what I get when I check for Bluetooth:

.....................

Any suggestions?

You are missing the most important step just before reboot:

Usually running `update-initramfs -k all -u` is enough to resolve this.
 
Ok so I feel like Ive made a little progress, but still no luck. From my original post i was able to download the ibt-17-16-1.sfi and ibt-17-16-1.dcc files and place them in /lib/firmware/intel, but now this is the message I get:

dmesg | grep -i blue
[ 3.878518] Bluetooth: Core ver 2.22
[ 3.878531] Bluetooth: HCI device and connection manager initialized
[ 3.878533] Bluetooth: HCI socket layer initialized
[ 3.878535] Bluetooth: L2CAP socket layer initialized
[ 3.878539] Bluetooth: SCO socket layer initialized
[ 3.920878] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[ 3.921884] Bluetooth: hci0: Device revision is 2
[ 3.921885] Bluetooth: hci0: Secure boot is enabled
[ 3.921885] Bluetooth: hci0: OTP lock is enabled
[ 3.921886] Bluetooth: hci0: API lock is enabled
[ 3.921886] Bluetooth: hci0: Debug lock is disabled
[ 3.921887] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 3.924986] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 3.926243] Bluetooth: hci0: Failed to send firmware signature (-38)
[ 6.121388] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.121389] Bluetooth: BNEP filters: protocol multicast
[ 6.121392] Bluetooth: BNEP socket layer initialized
 
Ok I was able to get bluetooth up and running. When I went to move the contents of the firmware directory it didn't move the intel directory over just the contents of the firmware directory. Now I am trying to pass the BT through to a VM and when i run hciconfig -a on the host it shows it as USB so I pass the corresponding USB ID to the VM (Debian Stretch), when I run hcitool dev in VM console I get no device.
 
Hi all

I know this thread is old...

Anyone succeded in Wireless AC9560 to work in Proxmox ? (sorry for my english)

I have an Intel NUC nuc8i3beh

How can I check if it works?

I'm trying to install this LXC container that has as prerequisite that the Wifi adapter works, and I'm getting error when trying to install it.

Any suggestion?

Thanks
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!