Antw: [EXT] [qubes-users] Re: Dom 0 latest update disabled my wireless device.
>>> schrieb am 14.03.2020 um 01:21 in Nachricht <8634_1584145286_5E6C2386_8634_1604_1_f5cd14a3-460b-49a4-a5bc-45c21fc9d81f@googl groups.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... 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+unsubscr...@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. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5E7074BF02A100037D2F%40gwsmtp.uni-regensburg.de.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
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. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/368ddf94-3210-4528-9851-275d3c77e944%40googlegroups.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
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 On Friday, March 13, 2020 at 8:57:58 PM UTC-4, bill...@gmail.com wrote: > > > 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 > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/740d6467-e8e4-4be7-8fff-1ae3c27e3369%40googlegroups.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
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 -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d127017a-bfd2-46bf-9ce1-6bdd0bfa9b4d%40googlegroups.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
> > 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 > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f5cd14a3-460b-49a4-a5bc-45c21fc9d81f%40googlegroups.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
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 :00:06.0: Detected Intel(R) Dual Band Wireless > AC 3168, REV=0x220 > [ 16.211008] iwlwifi :00:06.0: Can't parse phy_sku in B0, empty > sections > [ 16.211027] iwlwifi :00:06.0: Failed to read NVM: -61 > [ 16.224013] iwlwifi :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 qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/04959c5e-4bbe-428b-8950-98af4f77f12f%40googlegroups.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
I ran dmesg on sys-net and found this error 16.185851] iwlwifi :00:06.0: Detected Intel(R) Dual Band Wireless AC 3168, REV=0x220 [ 16.211008] iwlwifi :00:06.0: Can't parse phy_sku in B0, empty sections [ 16.211027] iwlwifi :00:06.0: Failed to read NVM: -61 [ 16.224013] iwlwifi :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 > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/809d9390-550b-4dc8-a278-824b7bf88cc1%40googlegroups.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
On Wednesday, March 11, 2020 at 11:28:08 PM UTC-5, Guerlan wrote: > > 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? > > On Wednesday, March 11, 2020 at 10:30:54 PM UTC-3, 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 >> > Often this sort of thing comes up in Qubes, where the 2nd poster is quite right to wonder whether or not you still have the wifi NIC attached to sys-net. However, in this case, the usual answer will not suffice as there is most definitely an issue with 4.19.107 & firmware on at least some hardware (I speak from experience with a similar chipset as the original poster). I have a laptop affected at the moment (not my only system nor my only Qubes one, so I am able to continue living/working & I am able to compare - but at first I hardly wanted to update any other systems when I noticed that the update borked my network on the laptop). I attempted to reach out & alert others but that can be complicated - eventually I proceeded with updates on a couple of systems with newer chipsets & those didn't have the problem although they all now contain the same version of the latest Qubes kernel. I solved my laptop problem temporarily in a manner I will describe - go to your sys-net & shut it down (likely need to shut sys-firewall down first) & see Qubes settings on sys-net. Check out the 2nd tab at the top of the settings dialog & look for the kernel section. Change that kernel & just that one item to the previous kernel & apply settings. Start your sys-net back up, then sys-firewall. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/504d8f5c-4c88-456d-ae79-de8cc271bf60%40googlegroups.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
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? On Wednesday, March 11, 2020 at 10:30:54 PM UTC-3, 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 > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6c292160-a22c-4f4b-b037-604344855de4%40googlegroups.com.
