On Thursday, March 12, 2020 at 8:14:09 PM UTC-5, pc revival wrote: > > 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? > > > On Wednesday, March 11, 2020 at 9:30:54 PM UTC-4, pc revival wrote: >> >> 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 >> > Well, one thing I will say that you could try (*** spoiler alert *** I suspect I know in advance that it could work) is switching sys-net back to the previous kernel (guessing 4.19.100, should only have to change just this one VM) at least until another update comes down. Since sys-net is using the previous kernel (if you didn't manually remove any of it), that should allow the firmware to load for the WiFi NIC (we're assuming as in your case it was working before the update). If you can't figure out how to, there being many ways, here's at least one:
- Access the Qube settings dialog for the sys-net (or whatever your primary equivalent VM is) while you have the VM & it's dependencies shutdown - check the 2nd tab (Advanced, right?) of that dialog for the kernel section - look for the best alternative to the setting & hit apply below - try to start that VM, test as much as you require to see if it helped The trouble can be, remembering that you moved off of the newest kernel on a given VM & might want to check periodically about that situation so you can switch back to current (nothing that will clearly & obviously remind you otherwise). I believe that if you change something like this at least two things you can count on: 1. the held-up kernel will not be removable when it should be (in use somewhere) & 2. you won't know whether to jump for joy because it works or worry yourself silly because you don't know whether this leaves you worse off than if it hadn't BTW, have you checked into IRC (FreeNode, channel #qubes) to ask yet? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/04959c5e-4bbe-428b-8950-98af4f77f12f%40googlegroups.com.
