Antw: [EXT] [qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-16 Thread Ulrich Windl
>>> 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

[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-14 Thread billollib
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 f

[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-13 Thread 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 th

[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-13 Thread billollib
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 yo

[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-13 Thread billollib
> > 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 d

[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-12 Thread kysstfafm
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

[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-12 Thread pc revival
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] iwlwi

[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-11 Thread kysstfafm
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

[qubes-users] Re: Dom 0 latest update disabled my wireless device.

2020-03-11 Thread 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? 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 per