Dom 0 latest update disabled my wireless device.

[pc revival]

I have been using Qubes for a while now on my personal computers. With the latest update to Dom 0 on Qubes 4.0.3 my wireless card has disappeared. I still have the wired connection but no wireless device available. It was working fine until I did this update and rebooted.

I haven't seen anything else similar listed anywhere.

My desktop is an HP 530 with an Intel 3168NGW wireless card.

Any help or suggestions will be welcome.

Thanks

[Guerlan]

I know almost nothing about qubes internals but did you try to see if your pci card is mounted to sys-net as a PCI device? Does it appear there? Is it mounted in other qube?

[pc revival]

I ran dmesg on sys-net and found this error

   16.185851] iwlwifi 0000:00:06.0: Detected Intel(R) Dual Band Wireless AC 3168, REV=0x220
[   16.211008] iwlwifi 0000:00:06.0: Can't parse phy_sku in B0, empty sections
[   16.211027] iwlwifi 0000:00:06.0: Failed to read NVM: -61
[   16.224013] iwlwifi 0000:00:06.0: Failed to run INIT ucode: -61

Anyone have any ideas?

[bill...@gmail.com]

I did a search on this.  There have been a number of folk complaining of it on the fedora groups.  It seems to have been a problem with a recent kernel update.

It's happened to me, too.  On the fedora boards, it is fixed by installing the newest kernel update.  My problem is that I don't have an ethernet connection, and rely entirely on wirelss.  So... I can't update the kernel because I can't get on the intertubes.  I"m going to try one of my old usb wireless devices and see if any of them work...

billo 

 

[bill...@gmail.com]

You might try changing the template for sys-net from fedora to debian.  However, for me, it turns out that the debian template has old firmware for my wireless device, and so I can't get wireless with it, either.  But at least it's a different error....

[pc revival]

Thanks for the reply. Your answer flipped a switch in my brain and I checked the fedora issues. The answer was so simple for me. You might try it too. Go into the qube settings for sys-net. Click on the advanced tab and there in the upper right corner you can choose an earlier kernel. Reboot the computer and presto my wireless is working again.

Thanks for all the help

[bill...@gmail.com]

Thanks.  That worked for me, too.

Loading the firmware into Debian and using that for sys-net did *not* work -- because it uses the same kernel.  I found a router to plug into an downloaded the firmware for the debian template.  I switched from not having the right firmware to replicating the fedora issue.  Now my Debian sys-net gives the "can't parse" error.

However, dropping back to a previous kernel fixes things.  

[Ulrich Windl]

>>> <bill...@gmail.com> schrieb am 14.03.2020 um 01:21 in Nachricht
<8634_1584145286_5E6C2386_8634_1604_1_f5cd14a3-460b-49a4-a5bc-45c21fc9d81f@googl
groups.com>:

Yes, I'd wish USB tethering via mobile would work in such cases (as it does in Tails, BTW).

>
> billo
>
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to qubes-users...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/f5cd14a3-460b-49a4-a5bc-45c21fc
> 9d81f%40googlegroups.com.