No wi-fi on ASROck-X570 MB-SOLVED!

[woodyb12]

System Specs:

Code: Select all

System:    Host: Lil-Monster Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop Mobo: ASRock model: X570 Phantom Gaming-ITX/TB3 serial: <filter> 
           BIOS: American Megatrends v: P2.80 date: 11/30/2020 
CPU:       Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 
           L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 115200 
           Speed: 3270 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 2300 2: 2082 3: 2200 
           4: 2311 5: 2270 6: 2274 7: 2246 8: 2309 9: 2075 10: 2339 11: 2270 12: 2298 13: 2293 
           14: 2257 15: 2379 16: 2200 
Graphics:  Device-1: AMD Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] vendor: VISIONTEK 
           driver: radeon v: kernel bus ID: 2a:00.0 
           Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD CAPE VERDE (DRM 2.50.0 4.19.0-5-amd64 LLVM 7.0.0) 
           v: 4.5 Mesa 18.2.6 direct render: Yes 
Audio:     Device-1: AMD Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] 
           vendor: VISIONTEK driver: snd_hda_intel v: kernel bus ID: 2a:00.1 
           Device-2: AMD vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 2c:00.4 
           Sound Server: ALSA v: k4.19.0-5-amd64 
Network: Device-1: Intel driver: N/A port: N/A bus ID: 25:00.0 
           Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: 5.4.0-k port: e000 
           bus ID: 26:00.0 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 5.24 GiB (1.1%) 
           ID-1: /dev/nvme0n1 model: Sabrent Rocket 4.0 500GB size: 465.76 GiB 
Partition: ID-1: / size: 31.25 GiB used: 5.13 GiB (16.4%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: /home size: 124.99 GiB used: 113.4 MiB (0.1%) fs: ext4 dev: /dev/nvme0n1p3 
           ID-3: swap-1 size: 256.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p4 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch/ stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 282 Uptime: 3m Memory: 31.34 GiB used: 672.8 MiB (2.1%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33 

As you can see, there are two Intel drivers listed. These same drivers show up in the "network assistant" program,and the "loaded drivers" in the "linux drivers" tab are "wl" and "igb".
What should I do next? ASROck does not show any Linux solutions. I have done a google search and have found that I might have to upgrade to [at least ] a 5.1 kernel and [ possibly install ] "iwl-wi-fi firmware??? Any reason[s] why I should Not follow this advise? Any help would be appreciated; as always!

SOLVED!

[j2mcgreg]

With such a new motherboard, you should be using the AHS (Advanced Hardware Systems) version of MX. It will give you a 5 series kernel and all the latest firmware. If you don't want all the hassle of re-installing, you can use MXPI (MX Package Installer) to install either the Debian 5.1 of 5.8 kernels. Personally, I'd reinstall with AHS.

[Stevo]

Plus it should "just work" in an AHS or MX-KDE Live Session, where we know for sure that it won't on the standard MX 4.19 kernel. Give it a try!

You can just install AHS over your existing install, and can choose to preserve your /home and existing user settings, so that should make it rather quick and painless. If you do just update to a newer kernel (5.10 recommended as 5.8 is end-of-life), you must also update your installed firmware packages from the test repo. This is easily done by using MX Package Installer, test repo tab, searching for "firmware", and upgrading installed versions.

[woodyb12]

I just downloaded the 19.4.1 ahs to do a re-install. But what about the iwfl-wi-fi package? Should I just do: "sudo apt install -t buster-backports firmware-iwlwifi ???

[Eadwine Rose]

I'd check to see if it works by default on the new install first.

[woodyb12]

O.K.

[Stevo]

We already ship AHS/KDE editions with backported firmware, so unless it's something soooper-dooper new or has some quirky wi-fi on-off switch shenanigans going on, it should work in the Live session.

QSI isn't showing any Intel wi-fi device, only the wired NIC, so I can't say for sure that it needs iwlwifi-firmware at all. If all goes well, the QSI from the Live AHS session will show what the wifi device actually is.

Edit: I missed that your first QSI shows MX 18, in spite of you posting it in the correct section. That makes about what I said about it being too old to support recent hardware go double. Is there any particular reason why you tried an older release on a newer motherboard instead of the latest?

[woodyb12]

SOLVED!

[Eadwine Rose]

Edit: I missed that your first QSI shows MX 18, in spite of you posting it in the correct section. That makes about what I said about it being too old to support recent hardware go double. Is there any particular reason why you tried an older release on a newer motherboard instead of the latest?

He did not post in the right section. I moved it here when I saw MX18 in the QSI.

[Stevo]

Edit: I missed that your first QSI shows MX 18, in spite of you posting it in the correct section. That makes about what I said about it being too old to support recent hardware go double. Is there any particular reason why you tried an older release on a newer motherboard instead of the latest?

He did not post in the right section. I moved it here when I saw MX18 in the QSI.

So I can take off the bag and go maskless now?

Anyway, chalk up another win for AHS!