Trouble connecting to WiFi with Intel 9560 interface

Peabnuts123

New Member
Mar 19, 2019
2
0
1
33
Howdy all. I've recently built a new server and would love to set up Proxmox on it. However, I seem to be running into the classic Linux problem that my hardware is too new for the system to work properly. I'm having a really hard time getting wireless to work. My motherboard is a Micro ATX Z390 Aorus Pro Wifi and the wireless chip on it is an Intel 9560 (the latest at the time of writing, AFAIK). FWIW an ethernet connection works perfectly but a wired setup is out of the question for me.
FWIW I'm intermediately experienced at using Linux. I've tried various configurations in `/etc/network/interfaces` and installing `wpasupplicant`, `wireless-tools` etc but faced a myriad of issues. In a last ditch effort I've installed `network-manager` and (using CLI but also using nmtui on a fresh install) I get what seems to be a "correct config" that crashes / errors / doesn't work. When I try to connect or bring up the wireless adaptor I get the same exact messages as the person in this post: -snip- I can't post this link because I'm new. See bottom of this post (1)

I've also seen this doing stuff manually by hand through other means (ifup, wpa_supplicant, etc.), which makes me feel like all of these common scenarios are "correct config" (but something else is still wrong).
I have also tried installing Proxmox on top of Debian (stretch). On Debian, network manager was completely able to connect to the wifi (after installing latest `firmware-iwlwifi` from non-free) and Proxmox installed okay on top of that. However, with that setup, I'm facing constant issues that seem to boil down to "Proxmox isn't quite in a comfortable configuration" (e.g. AppArmor doesn't start which keeps my LXC containers from starting, etc.) which leads me to believe the best way to setup and run Proxmox is by itself. I've tried installing `firmware-iwlwifi` over the top of Proxmox itself (forcing a conflict with `pve-firmware`) but it didn't seem to change anything. My wireless interface does show up and interact okay on Proxmox so the drivers are obviously working ~somewhat.
Anyway, this working setup on Debian means that some-way… SOME-how… my wireless NIC can be configured to run on Linux / Debian, but I can't seem to figure it out through Proxmox vanilla. Does anybody have any insight into how to diagnose/resolve this issue?


(1) Logs very similar to the issues i'm getting: (from AskUbuntu forums "Ubuntu freezes for a few seconds with error “Microcode SW error detected”". Question ID #1071051)

Code:
Aug 31 23:24:48 laptop2 kernel: [35714.735364] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
Aug 31 23:24:48 laptop2 kernel: [35714.735776] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Aug 31 23:24:48 laptop2 kernel: [35714.735785] iwlwifi 0000:00:14.3: Status: 0x00000100, count: 6
Aug 31 23:24:48 laptop2 kernel: [35714.735792] iwlwifi 0000:00:14.3: Loaded firmware version: 34.0.0
Aug 31 23:24:48 laptop2 kernel: [35714.735801] iwlwifi 0000:00:14.3: 0x00000942 | ADVANCED_SYSASSERT
Aug 31 23:24:48 laptop2 kernel: [35714.735808] iwlwifi 0000:00:14.3: 0x000022F0 | trm_hw_status0
Aug 31 23:24:48 laptop2 kernel: [35714.735815] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
Aug 31 23:24:48 laptop2 kernel: [35714.735821] iwlwifi 0000:00:14.3: 0x00456D06 | branchlink2
Aug 31 23:24:48 laptop2 kernel: [35714.735826] iwlwifi 0000:00:14.3: 0x0046064A | interruptlink1
Aug 31 23:24:48 laptop2 kernel: [35714.735836] iwlwifi 0000:00:14.3: 0x00000000 | interruptlink2
Aug 31 23:24:48 laptop2 kernel: [35714.735854] iwlwifi 0000:00:14.3: 0xFFDFFFB2 | data1
Aug 31 23:24:48 laptop2 kernel: [35714.735873] iwlwifi 0000:00:14.3: 0x03010100 | data2
Aug 31 23:24:48 laptop2 kernel: [35714.735885] iwlwifi 0000:00:14.3: 0x000F0602 | data3
Aug 31 23:24:48 laptop2 kernel: [35714.735890] iwlwifi 0000:00:14.3: 0x000118DE | beacon time
Aug 31 23:24:48 laptop2 kernel: [35714.735895] iwlwifi 0000:00:14.3: 0xA12B3C82 | tsf low
Aug 31 23:24:48 laptop2 kernel: [35714.735899] iwlwifi 0000:00:14.3: 0x0000003E | tsf hi
Aug 31 23:24:48 laptop2 kernel: [35714.735904] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
Aug 31 23:24:48 laptop2 kernel: [35714.735908] iwlwifi 0000:00:14.3: 0x0004D252 | time gp2
Aug 31 23:24:48 laptop2 kernel: [35714.735913] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
Aug 31 23:24:48 laptop2 kernel: [35714.735918] iwlwifi 0000:00:14.3: 0x00000022 | uCode version major
Aug 31 23:24:48 laptop2 kernel: [35714.735922] iwlwifi 0000:00:14.3: 0x00000000 | uCode version minor
Aug 31 23:24:48 laptop2 kernel: [35714.735927] iwlwifi 0000:00:14.3: 0x00000312 | hw version
Aug 31 23:24:48 laptop2 kernel: [35714.735931] iwlwifi 0000:00:14.3: 0x00489008 | board version
Aug 31 23:24:48 laptop2 kernel: [35714.735936] iwlwifi 0000:00:14.3: 0x0000001C | hcmd
Aug 31 23:24:48 laptop2 kernel: [35714.735941] iwlwifi 0000:00:14.3: 0x00023000 | isr0
Aug 31 23:24:48 laptop2 kernel: [35714.735952] iwlwifi 0000:00:14.3: 0x00000000 | isr1
Aug 31 23:24:48 laptop2 kernel: [35714.735966] iwlwifi 0000:00:14.3: 0x08001802 | isr2
Aug 31 23:24:48 laptop2 kernel: [35714.735979] iwlwifi 0000:00:14.3: 0x404140C0 | isr3
Aug 31 23:24:48 laptop2 kernel: [35714.735993] iwlwifi 0000:00:14.3: 0x00000000 | isr4
Aug 31 23:24:48 laptop2 kernel: [35714.736003] iwlwifi 0000:00:14.3: 0x0A2C001C | last cmd Id
Aug 31 23:24:48 laptop2 kernel: [35714.736008] iwlwifi 0000:00:14.3: 0x00000000 | wait_event
Aug 31 23:24:48 laptop2 kernel: [35714.736012] iwlwifi 0000:00:14.3: 0x000000D4 | l2p_control
Aug 31 23:24:48 laptop2 kernel: [35714.736017] iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
Aug 31 23:24:48 laptop2 kernel: [35714.736021] iwlwifi 0000:00:14.3: 0x00000007 | l2p_mhvalid
Aug 31 23:24:48 laptop2 kernel: [35714.736026] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
Aug 31 23:24:48 laptop2 kernel: [35714.736031] iwlwifi 0000:00:14.3: 0x0000000D | lmpm_pmg_sel
Aug 31 23:24:48 laptop2 kernel: [35714.736042] iwlwifi 0000:00:14.3: 0x12111721 | timestamp
Aug 31 23:24:48 laptop2 kernel: [35714.736053] iwlwifi 0000:00:14.3: 0x0000B8B8 | flow_handler
A
 
Hi,

firmware-iwlwifi
this package will be removed if you install proxmox-ve because it conflicts with the pve-firmware package.
This step is easy to download the package firmware-iwlwifi and extract it and copy it in the target dir.

Note the most wireless nic do not support bridgemode so you can't run a bridge on it and you have to use a routed/nated setup.
 
Hey wolfgang I appreciate the reply.
As I said in my original post I tried force-installing the `firmware-iwlwifi` package as a proof of concept but it didn’t really affect anything.
 
I had trouble connecting internet... Thanks wolfgang it worked for me. It looks like its not working for all. Firmware-iwlwfi package is working on some selected devices. If firmware-iwiwfi package is not working on your device then 192.168.1.7 IP Panel might be helpful.
 
Last edited:
So after downloading the firmware and extracting what exactly do I move? From another thread I gather I extract the firmware, then extract the data.tar and move all the ucode files from the newly created lib/firmware extracted from the data.tar file to the actual lib/firmware directory. I tried this and haven't had any luck.
 

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!