[qubes-users] Popup When Starting or Shutting down Whonix VMs

[pudding]

Hello,
today after updating my whonix-ws-15 and whonix-gw-15 template, every 
time I start or shut down any of my whonix AppVMs or templateVMs, I get 
the "Operation execution" popup like the attached pic 3 or 4 times. It's 
pretty annoying. I tried updating dom0 from current-testing repo, but 
the problem persists. Is there any way to make the popup disappear? 
Thank you!


--
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/b503584a-37a5-31eb-f16c-26dc3fd440ea%40cock.li.

Re: [qubes-users] Re: whonix tor browser customization

['awokd' via qubes-users]

awokd:
> Brendan Hoar:
>> On Tue, Sep 10, 2019 at 2:40 PM 'awokd' via qubes-users <
>> qubes-users@googlegroups.com> wrote:
> 
>>> I haven't seen this preset question. Is there a way to trigger it?
>>>
>>
>> I dropped all my whonix-14 VMs and templates yesterday and used salt to
>> install the whonix-15 templates (again: I'm also on the R4 current-testing
>> repo), and I see the question once every dispvm start.
> 
> I have one of my PCs on current-testing as well (thanks to ADW's nudging
> on the list a while back) and will update it. Wonder if I need a new -15
> template. Thanks for the heads up and details!
> 
This worked perfectly:

- update
- terminal on whonix-ws-15
- sudo nano /etc/torbrowser.d/50_user.conf
- tb_security_slider_safest=true
- save and poweroff

Dispvm Tor Browsers now default to Safest. I see the user.js it copies
is only 2 lines long with no identifiers, so it should have no
fingerprint impact beyond what takes place when a user moves the slider
as far as I can tell. Nice work adrelanos and 0brand and any others I
may have missed.

-- 
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/10bb0304-b444-537b-4bbe-a1234105716c%40danwin1210.me.

Re: [qubes-users] Re: Suspend to RAM not working

[drogo]

On Tuesday, September 10, 2019 at 5:22:32 PM UTC-4, Claudia wrote:
>
> drogo: 
> > 
> > 
> > On Sunday, June 24, 2018 at 10:12:17 PM UTC-4, cooloutac wrote: 
> >> 
> >> On Friday, June 15, 2018 at 5:59:46 PM UTC-4, drogo wrote: 
> >>> My newly built system is unable to suspend. The process starts, but 
> >> fails and ends up with just a locked screen. This is a desktop, so 
> there 
> >> shouldn't be any wifi drivers causing issues. But I'm not sure if 
> there's a 
> >> module that might be making it resume right away. 
> >>> 
> >>> Any ideas where to start troubleshooting this? 
> >>> 
> >>> HCL report is attached. 
> >>> 
> >>> 
> >>> Thank 
> >> 
> >> You can try to see if it suspends on the same baremetal feodora version 
> as 
> >> dom0 to narrow it down to a qubes or xen issue, or try newer fedora and 
> see 
> >> if its a kernel issue. 
> >> 
> >> I had similar issue with suspend ot ram,  but upon resume sys-net has 
> no 
> >> network.  restarting module or network connection doesnt' work.   the 
> >> suggested fix of blacklisting network driver module for my desktop in 
> the 
> >> qubes file, in my case ethernet, didn't work either. 
> >> 
> > 
> > I know it's been a  while, and I'm hesitant to resurrect an old thread, 
> but 
> > I put this on hold for a bit. Also, this system is my daily driver, so 
> > re-installing would be a big interruption. 
>
> (Just chiming in here so sorry if I missed anything important) 
>
> You don't have to reinstall, just try suspending in a Fedora 25 and/or 
> Fedora 30 live CD. In my experience, if suspend is going to work at all, 
> it should work in a live CD just the same. Worth a try, considering it's 
> trivial to do. 
>
> - 
> This free account was provided by VFEmail.net - report spam to 
> ab...@vfemail.net  
>   
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of 
> the NSA's hands! 
> $24.95 ONETIME Lifetime accounts with Privacy Features!   
> 15GB disk! No bandwidth quotas! 
> Commercial and Bulk Mail Options!   
>

I must be tired or something (for a year?? :) ) but I completely forgot 
about a live-USB.

Just grabbed a copy of Fedora 30, and it suspends successfully. Both by 
hitting the power button, and by choosing the "pause" icon from the user 
menu. 

Thanks for the reminder! 

-- 
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/331d268f-002a-4f25-8a0d-c19c91d0b630%40googlegroups.com.

Re: [qubes-users] R4.0.1 UEFI black screen after boot

['awokd' via qubes-users]

duc...@disroot.org:
> This is an issue that's been reported before, and some solutions appear
> to be out there, including re-installing with Legacy boot. However, they
> all seem to involve modifying the installer prior to installation or
> making changes via a GRUB menu. I'm never presented with a GRUB menu
> with either (I suspect that's a UEFI issue), so I'm not quite sure how
> to proceed with troubleshooting.  I want to stick with UEFI-only boot as
> far as possible.
> 
> The last messages echoed before the black screen are:
> 
>> [VT-D]Passed iommu=no-igfx option.  Disabling IGD VT-d engine.
>> Scrubbing Free RAM on 1 nodes using 2 CPUs
>> .done.
>> Initial low memory virq threshold set at 0x4000 pages.
>> Std. Loglevel: All
>> Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
>> Xen is relinquishing VGA console.
> 
> The screen goes black indefinitely at this point.
> 
> This is a device with only integrated GPU so I suspected this might be a
> problem.
> 
> How should I proceed?
> 
Intel integrated GPU usually works well as is. Are you getting the black
screen when you boot the installer, or after it completes and reboots?

-- 
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/5d1285f1-d7b0-8ff9-4abb-dc40e3e9db91%40danwin1210.me.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

['awokd' via qubes-users]

muhammad19238...@gmail.com:
> 
> 
> On Tuesday, September 10, 2019 at 8:57:51 PM UTC+1, awokd wrote:

>> https://github.com/endlessm/linux/tree/master/drivers/net/wireless/rtl8821ce,
>>  
>>
>> which is different than yours. 
>>
> I'm not entirely sure what to do with this driver. I have successfully ran 
> make(after correcting some header references in a few files). When I run 
> "insmod 8821ce.ko" I get "ERROR: could not insert module 8821ce.ko: Unknown 
> symbol in module". Here is an ls of my build directory, 
> https://paste.ie/view/f43bc2e3
> 
Sorry, don't have that adapter myself so can only give general pointers.
Check out the 0 scored answer at the bottom here, maybe it will work
better? They are using the driver in Debian 10 you were first attempting.

https://askubuntu.com/questions/990378/wi-fi-not-working-on-lenovo-thinkpad-e570-realtek-rtl8821ce

-- 
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/de53a59a-c654-b8ff-b85e-a6794ec246d3%40danwin1210.me.

Re: [qubes-users] Re: Suspend to RAM not working

[Claudia]

drogo:



On Sunday, June 24, 2018 at 10:12:17 PM UTC-4, cooloutac wrote:


On Friday, June 15, 2018 at 5:59:46 PM UTC-4, drogo wrote:

My newly built system is unable to suspend. The process starts, but

fails and ends up with just a locked screen. This is a desktop, so there
shouldn't be any wifi drivers causing issues. But I'm not sure if there's a
module that might be making it resume right away.


Any ideas where to start troubleshooting this?

HCL report is attached.


Thank


You can try to see if it suspends on the same baremetal feodora version as
dom0 to narrow it down to a qubes or xen issue, or try newer fedora and see
if its a kernel issue.

I had similar issue with suspend ot ram,  but upon resume sys-net has no
network.  restarting module or network connection doesnt' work.   the
suggested fix of blacklisting network driver module for my desktop in the
qubes file, in my case ethernet, didn't work either.



I know it's been a  while, and I'm hesitant to resurrect an old thread, but
I put this on hold for a bit. Also, this system is my daily driver, so
re-installing would be a big interruption.


(Just chiming in here so sorry if I missed anything important)

You don't have to reinstall, just try suspending in a Fedora 25 and/or 
Fedora 30 live CD. In my experience, if suspend is going to work at all, 
it should work in a live CD just the same. Worth a try, considering it's 
trivial to do.


-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/018c95b4-b3cf-4fdb-1634-1362aaf1e155%40vfemail.net.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

[muhammad19238219]

On Tuesday, September 10, 2019 at 8:57:51 PM UTC+1, awokd wrote:
>
> muhammad...@gmail.com : 
> > 
> > 
> > On Tuesday, September 10, 2019 at 8:31:12 PM UTC+1, 
> muhammad...@gmail.com 
> > wrote: 
>
> >> I dont know what top posting is but I will assume you mean write 
> >> underneath the quote, please correct me otherwise.  On fedora, I see my 
> >> wifi adapter in "lshw -C network" as unclaimed(and is not present in ip 
> -a 
> >> and have already rebooted) 
>
> Thank you. 
>
> > Ok scratch that, after rebooting qubes I now see the adapter in ip -a. 
> > However, I cannot use it, nmcli device wifi list reports nothing(nmcli 
> > radio wifi reports "enabled") 
> >   
> > 
> If you've tried building the driver on both templates and neither are 
> working, maybe it's the driver? That thread I linked earlier was using a 
> driver from 
>
> https://github.com/endlessm/linux/tree/master/drivers/net/wireless/rtl8821ce, 
>
> which is different than yours. 
>
I'm not entirely sure what to do with this driver. I have successfully ran 
make(after correcting some header references in a few files). When I run 
"insmod 8821ce.ko" I get "ERROR: could not insert module 8821ce.ko: Unknown 
symbol in module". Here is an ls of my build directory, 
https://paste.ie/view/f43bc2e3

-- 
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/4f80fd0f-71dd-4b89-b84b-d716bd450d9d%40googlegroups.com.

[qubes-users] R4.0.1 UEFI black screen after boot

[duc01k]

This is an issue that's been reported before, and some solutions appear
to be out there, including re-installing with Legacy boot. However, they
all seem to involve modifying the installer prior to installation or
making changes via a GRUB menu. I'm never presented with a GRUB menu
with either (I suspect that's a UEFI issue), so I'm not quite sure how
to proceed with troubleshooting.  I want to stick with UEFI-only boot as
far as possible.

The last messages echoed before the black screen are:

>[VT-D]Passed iommu=no-igfx option.  Disabling IGD VT-d engine.
>Scrubbing Free RAM on 1 nodes using 2 CPUs
>.done.
>Initial low memory virq threshold set at 0x4000 pages.
>Std. Loglevel: All
>Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
>Xen is relinquishing VGA console.

The screen goes black indefinitely at this point.

This is a device with only integrated GPU so I suspected this might be a
problem.

How should I proceed?

-- 
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/531bddd7-ecc8-95ff-9203-bbe8b3923df6%40disroot.org.

[qubes-users] Re: Suspend to RAM not working

[drogo]

On Sunday, June 24, 2018 at 10:12:17 PM UTC-4, cooloutac wrote:
>
> On Friday, June 15, 2018 at 5:59:46 PM UTC-4, drogo wrote:
> > My newly built system is unable to suspend. The process starts, but 
> fails and ends up with just a locked screen. This is a desktop, so there 
> shouldn't be any wifi drivers causing issues. But I'm not sure if there's a 
> module that might be making it resume right away.
> > 
> > Any ideas where to start troubleshooting this?
> > 
> > HCL report is attached.
> > 
> > 
> > Thank
>
> You can try to see if it suspends on the same baremetal feodora version as 
> dom0 to narrow it down to a qubes or xen issue, or try newer fedora and see 
> if its a kernel issue.   
>
> I had similar issue with suspend ot ram,  but upon resume sys-net has no 
> network.  restarting module or network connection doesnt' work.   the 
> suggested fix of blacklisting network driver module for my desktop in the 
> qubes file, in my case ethernet, didn't work either. 
>

I know it's been a  while, and I'm hesitant to resurrect an old thread, but 
I put this on hold for a bit. Also, this system is my daily driver, so 
re-installing would be a big interruption.

I tried combing through system logs as well as running a stack trace on the 
suspend command. I've also changed video cards, as I was using Nvida 
before. 

sleep fail in logfile = https://pastebin.com/xtC7t4GY
trace output of suspend cmd = https://pastebin.com/WpfX7JPg
new HCL = https://pastebin.com/dqtP4snc
lspci output = https://pastebin.com/PedWnPUr

I changed video cards to a Radeon HD 8570. That seems to bring new issues, 
as before the system would attempt to suspend, but fail, then come back up 
and be usable. Now it fails to suspend, and when it comes back up, the 
display is mangled and unusable. 

Do I have to do any tweaking for the video card now that I've changed? 

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/a1cb0958-3aaf-4076-a360-d50d23f93ed2%40googlegroups.com.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

['awokd' via qubes-users]

muhammad19238...@gmail.com:
> 
> 
> On Tuesday, September 10, 2019 at 8:31:12 PM UTC+1, muhammad...@gmail.com 
> wrote:

>> I dont know what top posting is but I will assume you mean write 
>> underneath the quote, please correct me otherwise.  On fedora, I see my 
>> wifi adapter in "lshw -C network" as unclaimed(and is not present in ip -a 
>> and have already rebooted)

Thank you.

> Ok scratch that, after rebooting qubes I now see the adapter in ip -a. 
> However, I cannot use it, nmcli device wifi list reports nothing(nmcli 
> radio wifi reports "enabled") 
>  
> 
If you've tried building the driver on both templates and neither are
working, maybe it's the driver? That thread I linked earlier was using a
driver from
https://github.com/endlessm/linux/tree/master/drivers/net/wireless/rtl8821ce,
which is different than yours.

-- 
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/459b21e6-4c1d-7627-031f-5d94fab548e7%40danwin1210.me.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

[muhammad19238219]

On Tuesday, September 10, 2019 at 8:31:12 PM UTC+1, muhammad...@gmail.com 
wrote:
>
> On Tuesday, September 10, 2019 at 7:35:12 PM UTC+1, awokd wrote:
>>
>> muhammad...@gmail.com: 
>> > Ok, it worked to an extent. The build succeeded and the driver now 
>> displays 
>> > the interface in ip -a, however it works no more than that. I have 
>> passed 
>> > through the adapter and turned off sys-net. systemctl shows that the 
>> > wpa_supplicant service is running, but wpa_supplicant@wls7.service is 
>> > reported as "inactive (dead)", when I try to start the service, I get a 
>> > reported "Timed out waiting for device 
>> > sys-subsystem-net-devices-wls7.service.device"(That is more or less the 
>> > entire error) in journalctl -xe. 
>> > 
>> > On Tuesday, September 10, 2019 at 6:00:10 PM UTC+1, awokd wrote: 
>> >> 
>> >> muhammad...@gmail.com : 
>> >>> After selecting no kernel, my VM no longer boots. I think I should 
>> have 
>> >>> mentioned that I am using debian-9-minimal. What should I install to 
>> >>> overcome this? 
>> >>> 
>> >>> On Tuesday, September 10, 2019 at 3:49:45 PM UTC+1, awokd wrote: 
>>  
>>  muhammad...@gmail.com : 
>> > Hello and thank you, but how does one go about installing the stock 
>>  kernel, 
>> > is it something I do in qubes or in the VM? I assume this would 
>> work 
>>  with 
>> > fedora 30 as well. 
>> > 
>> > On Monday, September 9, 2019 at 9:58:36 PM UTC+1, awokd wrote: 
>> >> 
>> >> muhammad...@gmail.com : 
>> >>> I am trying to build these drivers on a debian-9 template based 
>> >> vm(my 
>> >> own 
>> >>> sys-net, I rather debian than fedora, and I have already tried 
>> and 
>> >> got 
>> >> the 
>> >>> same result on fedora). The drivers are found here 
>> >>> https://github.com/tomaspinho/rtl8821ce . I installed these 
>> easily 
>> >> on 
>> >> other 
>> >>> Debian systems and had no such issue. If i try build with the 
>> >>> DKMS-install.sh provided, I get this error: pastebin.com/aX9kmZg3 
>> >> and 
>> >> in 
>> >>> the make.log, pastebin.com/XiFfzGWG . If i try build with make, 
>> I 
>> >> get 
>> >> this 
>> >>> error: pastebin.com/w1QDw5w6 . I looked around and found some 
>> >> related 
>> >>> issues on github but lacked solutions at least that I saw, but I 
>> >> need 
>> >> these 
>> >>> drivers urgently so apologies if this is common knowledge. 
>> >>> 
>> >> 
>> >> 
>> https://www.mail-archive.com/qubes-users@googlegroups.com/msg27754.html 
>> >> 
>> >> 
>> > 
>>  Qubes menu/sys-net/qube settings/advanced/kernel=none. Try Debian 
>> first 
>>  the same way if you prefer it; the problem might have been fixed 
>> since 
>>  the linked post. 
>>  
>>  
>> >>> 
>> >> Try the standard/non-minimal template, or Fedora's (again standard). 
>> >> 
>> >> 
>> > 
>> Same with Fedora? 
>>
>> PS Please don't top-post in mailing lists. 
>>
>> I dont know what top posting is but I will assume you mean write 
> underneath the quote, please correct me otherwise.  On fedora, I see my 
> wifi adapter in "lshw -C network" as unclaimed(and is not present in ip -a 
> and have already rebooted)
>
Ok scratch that, after rebooting qubes I now see the adapter in ip -a. 
However, I cannot use it, nmcli device wifi list reports nothing(nmcli 
radio wifi reports "enabled") 
 

-- 
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/4d05c636-2c3a-4420-8c7b-61848c044ed9%40googlegroups.com.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

[muhammad19238219]

On Tuesday, September 10, 2019 at 7:35:12 PM UTC+1, awokd wrote:
>
> muhammad...@gmail.com : 
> > Ok, it worked to an extent. The build succeeded and the driver now 
> displays 
> > the interface in ip -a, however it works no more than that. I have 
> passed 
> > through the adapter and turned off sys-net. systemctl shows that the 
> > wpa_supplicant service is running, but wpa_supplicant@wls7.service is 
> > reported as "inactive (dead)", when I try to start the service, I get a 
> > reported "Timed out waiting for device 
> > sys-subsystem-net-devices-wls7.service.device"(That is more or less the 
> > entire error) in journalctl -xe. 
> > 
> > On Tuesday, September 10, 2019 at 6:00:10 PM UTC+1, awokd wrote: 
> >> 
> >> muhammad...@gmail.com : 
> >>> After selecting no kernel, my VM no longer boots. I think I should 
> have 
> >>> mentioned that I am using debian-9-minimal. What should I install to 
> >>> overcome this? 
> >>> 
> >>> On Tuesday, September 10, 2019 at 3:49:45 PM UTC+1, awokd wrote: 
>  
>  muhammad...@gmail.com : 
> > Hello and thank you, but how does one go about installing the stock 
>  kernel, 
> > is it something I do in qubes or in the VM? I assume this would work 
>  with 
> > fedora 30 as well. 
> > 
> > On Monday, September 9, 2019 at 9:58:36 PM UTC+1, awokd wrote: 
> >> 
> >> muhammad...@gmail.com : 
> >>> I am trying to build these drivers on a debian-9 template based 
> >> vm(my 
> >> own 
> >>> sys-net, I rather debian than fedora, and I have already tried and 
> >> got 
> >> the 
> >>> same result on fedora). The drivers are found here 
> >>> https://github.com/tomaspinho/rtl8821ce . I installed these 
> easily 
> >> on 
> >> other 
> >>> Debian systems and had no such issue. If i try build with the 
> >>> DKMS-install.sh provided, I get this error: pastebin.com/aX9kmZg3 
> >> and 
> >> in 
> >>> the make.log, pastebin.com/XiFfzGWG . If i try build with make, I 
> >> get 
> >> this 
> >>> error: pastebin.com/w1QDw5w6 . I looked around and found some 
> >> related 
> >>> issues on github but lacked solutions at least that I saw, but I 
> >> need 
> >> these 
> >>> drivers urgently so apologies if this is common knowledge. 
> >>> 
> >> 
> >> https://www.mail-archive.com/qubes-users@googlegroups.com/msg27754.html 
> >> 
> >> 
> > 
>  Qubes menu/sys-net/qube settings/advanced/kernel=none. Try Debian 
> first 
>  the same way if you prefer it; the problem might have been fixed 
> since 
>  the linked post. 
>  
>  
> >>> 
> >> Try the standard/non-minimal template, or Fedora's (again standard). 
> >> 
> >> 
> > 
> Same with Fedora? 
>
> PS Please don't top-post in mailing lists. 
>
> I dont know what top posting is but I will assume you mean write 
underneath the quote, please correct me otherwise.  On fedora, I see my 
wifi adapter in "lshw -C network" as unclaimed(and is not present in ip -a 
and have already rebooted)

-- 
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/9ea4c864-87fe-4863-84eb-53fe05906eba%40googlegroups.com.

Re: [qubes-users] Re: whonix tor browser customization

['awokd' via qubes-users]

Brendan Hoar:
> On Tue, Sep 10, 2019 at 2:40 PM 'awokd' via qubes-users <
> qubes-users@googlegroups.com> wrote:

>> I haven't seen this preset question. Is there a way to trigger it?
>>
> 
> I dropped all my whonix-14 VMs and templates yesterday and used salt to
> install the whonix-15 templates (again: I'm also on the R4 current-testing
> repo), and I see the question once every dispvm start.

I have one of my PCs on current-testing as well (thanks to ADW's nudging
on the list a while back) and will update it. Wonder if I need a new -15
template. Thanks for the heads up and details!

-- 
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/215ab3c8-fe47-d279-437e-6810cc4df9d9%40danwin1210.me.

Re: [qubes-users] Re: whonix tor browser customization

[Brendan Hoar]

On Tue, Sep 10, 2019 at 2:40 PM 'awokd' via qubes-users <
qubes-users@googlegroups.com> wrote:

> brendan.h...@gmail.com:
>
> > Under whonix-15, the whonix developers have inserted a presetting
> question
> > on startup allowing you to choose what you want the default on startup
> to
> > be, and the bug where the setting is one way, and the buggy behavior
> above
> > does not seem to be present.
>
> I haven't seen this preset question. Is there a way to trigger it?
>

I dropped all my whonix-14 VMs and templates yesterday and used salt to
install the whonix-15 templates (again: I'm also on the R4 current-testing
repo), and I see the question once every dispvm start.


>
> > You still have to set it again each time a disposable VM starts, but
> it's
> > more straightforward, at least in my opinion.
>
> Might be missing something here, but wouldn't that defeat the purpose?
> I'd like very much to set all my disposables to start on Safest.
>

>From my read, it is possible you could set it in the DVM template (there
are instructions on how to set the startup files in the filesystem to
bypass the question).

Here's the text of the dialog (some of the text hyperlinks elsewhere):



First Start of Tor Browser (AnonDist) - Security vs Usability Trade-off

In the stock Tor Browser configuration, JavaScript is enabled by default
for greater usability. The Tor Project provides a rationale for this
decision.

The producers of Tor Browser decided the security slider setting to be set
to "Standard" by default. Quote Tor Browser Manual:
You can further increase your security by choosing to disable certain web
features that can be used to attack your security and anonymity. You can do
this by increasing Tor Browser's Security Settings in the shield menu.
Increasing Tor Browser's security level will stop some web pages from
functioning properly, so you should weigh your security needs against the
degree of usability you require.
This popup question does not restrict your freedom to change security
slider settings at any time.

Responsible for this popup question is Tor Browser Starter by Whonix
developers. It is an usability feature, which might break in future.
Therefore the user is advised to verify that the security slider has the
expected setting. Please donate!

Preseeding:

It is possible to avoid this popup question by preseeding the answer to it.
For that create a file /etc/torbrowser.d/50_user.conf with the follow
contents, if you want to answer "Yes".
tb_security_slider_safest=true
Or if you want to answer "No".
tb_security_slider_safest=false
Technical Details:

This script is: /usr/bin/torbrowser
Function: tb_security_slider
All this would do is copying file
/usr/share/torbrowser/security-slider-highest.js to
/home/user/.tb/tor-browser/Browser/TorBrowser/Data/Browser/profile.default/user.js.

cp /usr/share/torbrowser/security-slider-highest.js
/home/user/.tb/tor-browser/Browser/TorBrowser/Data/Browser/profile.default/user.js

Set Tor Browser Security Slider to Safest?


[No] [Yes]



My read is that whonix dev(s) do not want to contradict the choices of the
Tor project, even if controversial (I see good arguments on both sides).

Whonix dev(s) are also probably (I am guessing here) tired of getting
questions about these settings every day.

I'll paraphrase: "Here's the shotgun. Use it wisely. Know where your limbs
are at all times."

B

PS - why I continued to see the bug where the setting and behavior were
different in -14 vs. -15 I don't know, but I do have a more recent version
of TB in -15, so maybe that's it.

-- 
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/CAOajFeeXa4c_qgnf1tWJVEmU73G%3DWjbBLMEpAM0GqQg36ybHuw%40mail.gmail.com.

Re: [qubes-users] Re: whonix tor browser customization

['awokd' via qubes-users]

brendan.h...@gmail.com:

> Under whonix-15, the whonix developers have inserted a presetting question 
> on startup allowing you to choose what you want the default on startup to 
> be, and the bug where the setting is one way, and the buggy behavior above 
> does not seem to be present. 

I haven't seen this preset question. Is there a way to trigger it?

> You still have to set it again each time a disposable VM starts, but it's 
> more straightforward, at least in my opinion.

Might be missing something here, but wouldn't that defeat the purpose?
I'd like very much to set all my disposables to start on Safest.

-- 
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/b1203360-24aa-4b67-ab4b-030fb4784bf0%40danwin1210.me.

Re: [qubes-users] Re: whonix tor browser customization

[brendan . hoar]

On Tuesday, September 10, 2019 at 2:13:46 PM UTC-4, tetra...@danwin1210.me 
wrote:

> Did upstream (Tor) also change the NoScript settings to block all 
> javascript on all sites by default, even at the lowest Tor Browser 
> security level? 
>

Not exactly. Upstream intended the security slider to be set at Standard 
and the behavior to be Javascript mostly on.

However, some TB versions (I experienced tihs under whonix-14 at least) has 
an issue, where while it defaults to the "Standard" setting as per 
upstream, TB acted as if set to the "Safest" setting. This appears to be a 
TB bug.

Manually adjusting the setting back and forth in firefox preferences fixes 
the issue for that session, but the problem appears again on restart.
 

> This is what seems to be happening for me. It is a pain, since any 
> attempt to fix the settings goes away once the disposable Whonix VM 
> dies. 
>

Under whonix-15, the whonix developers have inserted a presetting question 
on startup allowing you to choose what you want the default on startup to 
be, and the bug where the setting is one way, and the buggy behavior above 
does not seem to be present. 

You still have to set it again each time a disposable VM starts, but it's 
more straightforward, at least in my opinion.

Brendan

-- 
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/ff177f9c-1a91-4893-aacb-cf74b39b0a74%40googlegroups.com.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

['awokd' via qubes-users]

muhammad19238...@gmail.com:
> Ok, it worked to an extent. The build succeeded and the driver now displays 
> the interface in ip -a, however it works no more than that. I have passed 
> through the adapter and turned off sys-net. systemctl shows that the 
> wpa_supplicant service is running, but wpa_supplicant@wls7.service is 
> reported as "inactive (dead)", when I try to start the service, I get a 
> reported "Timed out waiting for device 
> sys-subsystem-net-devices-wls7.service.device"(That is more or less the 
> entire error) in journalctl -xe.
> 
> On Tuesday, September 10, 2019 at 6:00:10 PM UTC+1, awokd wrote:
>>
>> muhammad...@gmail.com : 
>>> After selecting no kernel, my VM no longer boots. I think I should have 
>>> mentioned that I am using debian-9-minimal. What should I install to 
>>> overcome this? 
>>>
>>> On Tuesday, September 10, 2019 at 3:49:45 PM UTC+1, awokd wrote: 

 muhammad...@gmail.com : 
> Hello and thank you, but how does one go about installing the stock 
 kernel, 
> is it something I do in qubes or in the VM? I assume this would work 
 with 
> fedora 30 as well. 
>
> On Monday, September 9, 2019 at 9:58:36 PM UTC+1, awokd wrote: 
>>
>> muhammad...@gmail.com : 
>>> I am trying to build these drivers on a debian-9 template based 
>> vm(my 
>> own 
>>> sys-net, I rather debian than fedora, and I have already tried and 
>> got 
>> the 
>>> same result on fedora). The drivers are found here 
>>> https://github.com/tomaspinho/rtl8821ce . I installed these easily 
>> on 
>> other 
>>> Debian systems and had no such issue. If i try build with the 
>>> DKMS-install.sh provided, I get this error: pastebin.com/aX9kmZg3 
>> and 
>> in 
>>> the make.log, pastebin.com/XiFfzGWG . If i try build with make, I 
>> get 
>> this 
>>> error: pastebin.com/w1QDw5w6 . I looked around and found some 
>> related 
>>> issues on github but lacked solutions at least that I saw, but I 
>> need 
>> these 
>>> drivers urgently so apologies if this is common knowledge. 
>>>
>>
>> https://www.mail-archive.com/qubes-users@googlegroups.com/msg27754.html 
>>
>>
>
 Qubes menu/sys-net/qube settings/advanced/kernel=none. Try Debian first 
 the same way if you prefer it; the problem might have been fixed since 
 the linked post. 


>>>
>> Try the standard/non-minimal template, or Fedora's (again standard). 
>>
>>
> 
Same with Fedora?

PS Please don't top-post in mailing lists.

-- 
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/7fdf7466-ce64-d921-f67e-b30a567b495f%40danwin1210.me.

Re: [qubes-users] Re: whonix tor browser customization

[tetrahedra via qubes-users]

On Fri, Sep 06, 2019 at 09:00:00AM +, Patrick Schleizer wrote:

panina:

On 8/9/19 9:05 AM, Patrick Schleizer wrote:

panina:
Namely, they removed NoScript from the toolbar, so that the
NoScript cannot be used as intended.



We did not. Decision by upstream, The Tor Project.



https://forums.whonix.org/t/workstation-15-dropped-both-noscript-and-https/7733

Thanks, duly noted. Is there any chance to get them to add a setting for
this? Or re-think their decision?



It's not up to me at all. The Tor Project is the only point of contact
fo this.


Did upstream (Tor) also change the NoScript settings to block all
javascript on all sites by default, even at the lowest Tor Browser
security level?

This is what seems to be happening for me. It is a pain, since any
attempt to fix the settings goes away once the disposable Whonix VM
dies.

--
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/20190908102257.GA997%40danwin1210.me.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

[muhammad19238219]

Ok, it worked to an extent. The build succeeded and the driver now displays 
the interface in ip -a, however it works no more than that. I have passed 
through the adapter and turned off sys-net. systemctl shows that the 
wpa_supplicant service is running, but wpa_supplicant@wls7.service is 
reported as "inactive (dead)", when I try to start the service, I get a 
reported "Timed out waiting for device 
sys-subsystem-net-devices-wls7.service.device"(That is more or less the 
entire error) in journalctl -xe.

On Tuesday, September 10, 2019 at 6:00:10 PM UTC+1, awokd wrote:
>
> muhammad...@gmail.com : 
> > After selecting no kernel, my VM no longer boots. I think I should have 
> > mentioned that I am using debian-9-minimal. What should I install to 
> > overcome this? 
> > 
> > On Tuesday, September 10, 2019 at 3:49:45 PM UTC+1, awokd wrote: 
> >> 
> >> muhammad...@gmail.com : 
> >>> Hello and thank you, but how does one go about installing the stock 
> >> kernel, 
> >>> is it something I do in qubes or in the VM? I assume this would work 
> >> with 
> >>> fedora 30 as well. 
> >>> 
> >>> On Monday, September 9, 2019 at 9:58:36 PM UTC+1, awokd wrote: 
>  
>  muhammad...@gmail.com : 
> > I am trying to build these drivers on a debian-9 template based 
> vm(my 
>  own 
> > sys-net, I rather debian than fedora, and I have already tried and 
> got 
>  the 
> > same result on fedora). The drivers are found here 
> > https://github.com/tomaspinho/rtl8821ce . I installed these easily 
> on 
>  other 
> > Debian systems and had no such issue. If i try build with the 
> > DKMS-install.sh provided, I get this error: pastebin.com/aX9kmZg3 
> and 
>  in 
> > the make.log, pastebin.com/XiFfzGWG . If i try build with make, I 
> get 
>  this 
> > error: pastebin.com/w1QDw5w6 . I looked around and found some 
> related 
> > issues on github but lacked solutions at least that I saw, but I 
> need 
>  these 
> > drivers urgently so apologies if this is common knowledge. 
> > 
>  
> https://www.mail-archive.com/qubes-users@googlegroups.com/msg27754.html 
>  
>  
> >>> 
> >> Qubes menu/sys-net/qube settings/advanced/kernel=none. Try Debian first 
> >> the same way if you prefer it; the problem might have been fixed since 
> >> the linked post. 
> >> 
> >> 
> > 
> Try the standard/non-minimal template, or Fedora's (again standard). 
>
>

-- 
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/b7f376e7-d08d-42ec-823d-34952ce13650%40googlegroups.com.

[qubes-users] QSB #51: Insufficient validation of backup compression filter on restore

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Qubes Community,

We have just published Qubes Security Bulletin (QSB) #51:
Insufficient validation of backup compression filter on restore.
The text of this QSB is reproduced below. This QSB and its accompanying
signatures will always be available in the Qubes Security Pack (qubes-secpack).

View QSB #51 in the qubes-secpack:



Learn about the qubes-secpack, including how to obtain, verify, and read it:



View all past QSBs:




```
 ---===[ Qubes Security Bulletin #51 ]===---

 2019-09-10

Insufficient validation of backup compression filter on restore


Summary
===

The Qubes backup format has an option for user-selected compression
filters. While Qubes backups are authenticated and encrypted, the choice
of compression filter in a given backup is not further validated on
restore. Under specific conditions, an attacker capable of circumventing
backup authentication could exploit the lack of compression filter
validation in order to execute arbitrary commands when a backup is
restored.

Impact
==

In Qubes OS, backups are encrypted and authenticated using a passphrase.
You must enter your backup passphrase when attempting to restore a
backup. If your passphrase successfully authenticates the backup, it
will be decrypted and restored. Otherwise, the operation will be aborted
before the contents of the backup are further processed.

In order to exploit this vulnerability, an attacker would have to create
a malicious backup that would successfully pass authentication and
induce you to restore it. In practice, this means that the attacker
would effectively have to (1) learn your backup passphrase and (2)
replace one of your backups with a malicious version. If the attacker is
unable to achieve either condition (or an equivalent), the vulnerability
cannot be exploited.

Therefore, if you have only restored backups protected by strong, secret
passphrases, then you are not affected. Likewise, if you have only
restored backups from trusted, secure locations, then you are not
affected. However, if you have ever restored a backup with a weak or
non-secret passphrase that was also stored in an untrusted location,
then your system may be compromised. This bug can be exploited reliably
and silently only when both conditions are met.

(Note: In this context, "restoring" a backup also includes use of the
Qubes "verify backup" functionality, since verification works by
simulating the restore process.)

Details
===

The ability to use a user-specified "compression filter" (in practice:
an argument to `tar -I`/`tar --use-compress-program`) was introduced in
Qubes Backup Format Version 3. [1] Alternate compression programs are
specified by the user via `qvm-backup --compress-filter [...]` and are
stored in the backup metadata. Originally, they were stored in the
`compressed` header field, then later in the `compression-filter` field.
The whole backup, including its metadata, is authenticated via an HMAC
with the backup passphrase. There is no further validation of the
contents of the specific `compressed` or `compression-filter` field.

In order to exploit this vulnerability, an attacker would have to create
or modify a backup for the user to restore. In order for the HMAC
authentication to succeed, the attacker would have to know the
passphrase that the user will enter when attempting to restore, e.g., by
cracking the user's passphrase or somehow inducing the user to enter a
passphrase provided by the attacker. Furthermore, the attacker would
have to induce the user to select the attacker's malicious backup for a
restore operation, e.g., by replacing one of the user's genuine backups
with a malicious version (which would require that the attacker have
write access to the user's backup storage location) or somehow
convincing the user to restore a backup provided by the attacker.

The internal structure of backups is one outer uncompressed
multi-session-concatinated (via `tar -A`) tar archive. The first session
contains an uncompressed and unauthenticated `backup-header`. This
untrusted backup header file is initially only inspected to determine
the backup archive format to determine how to proceed with further
extraction. The following tar sessions contain a `backup-header.hmac`
file used to authenticate the backup header before deeper inspection,
and other files (qubes.xml, vmXX/{private,etc.}.img) which are each
wrapped in their own tar archives and then wrapped in their own
encryption and authentication.

Since qubes.xml is itself contained in an inner potentially-compressed
tar archive, the decompression filter is also used when verifying a
backup, i.e., when the `--verify-only` flag is passed to
`qvm-backup-restore` or when the "Verify backup 

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

['awokd' via qubes-users]

muhammad19238...@gmail.com:
> After selecting no kernel, my VM no longer boots. I think I should have 
> mentioned that I am using debian-9-minimal. What should I install to 
> overcome this?
> 
> On Tuesday, September 10, 2019 at 3:49:45 PM UTC+1, awokd wrote:
>>
>> muhammad...@gmail.com : 
>>> Hello and thank you, but how does one go about installing the stock 
>> kernel, 
>>> is it something I do in qubes or in the VM? I assume this would work 
>> with 
>>> fedora 30 as well. 
>>>
>>> On Monday, September 9, 2019 at 9:58:36 PM UTC+1, awokd wrote: 

 muhammad...@gmail.com : 
> I am trying to build these drivers on a debian-9 template based vm(my 
 own 
> sys-net, I rather debian than fedora, and I have already tried and got 
 the 
> same result on fedora). The drivers are found here 
> https://github.com/tomaspinho/rtl8821ce . I installed these easily on 
 other 
> Debian systems and had no such issue. If i try build with the 
> DKMS-install.sh provided, I get this error: pastebin.com/aX9kmZg3 and 
 in 
> the make.log, pastebin.com/XiFfzGWG . If i try build with make, I get 
 this 
> error: pastebin.com/w1QDw5w6 . I looked around and found some related 
> issues on github but lacked solutions at least that I saw, but I need 
 these 
> drivers urgently so apologies if this is common knowledge. 
>
 https://www.mail-archive.com/qubes-users@googlegroups.com/msg27754.html 


>>>
>> Qubes menu/sys-net/qube settings/advanced/kernel=none. Try Debian first 
>> the same way if you prefer it; the problem might have been fixed since 
>> the linked post. 
>>
>>
> 
Try the standard/non-minimal template, or Fedora's (again standard).

-- 
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/f152ab5b-f7f7-6edd-b8bd-d4e0554d064a%40danwin1210.me.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

[muhammad19238219]

After selecting no kernel, my VM no longer boots. I think I should have 
mentioned that I am using debian-9-minimal. What should I install to 
overcome this?

On Tuesday, September 10, 2019 at 3:49:45 PM UTC+1, awokd wrote:
>
> muhammad...@gmail.com : 
> > Hello and thank you, but how does one go about installing the stock 
> kernel, 
> > is it something I do in qubes or in the VM? I assume this would work 
> with 
> > fedora 30 as well. 
> > 
> > On Monday, September 9, 2019 at 9:58:36 PM UTC+1, awokd wrote: 
> >> 
> >> muhammad...@gmail.com : 
> >>> I am trying to build these drivers on a debian-9 template based vm(my 
> >> own 
> >>> sys-net, I rather debian than fedora, and I have already tried and got 
> >> the 
> >>> same result on fedora). The drivers are found here 
> >>> https://github.com/tomaspinho/rtl8821ce . I installed these easily on 
> >> other 
> >>> Debian systems and had no such issue. If i try build with the 
> >>> DKMS-install.sh provided, I get this error: pastebin.com/aX9kmZg3 and 
> >> in 
> >>> the make.log, pastebin.com/XiFfzGWG . If i try build with make, I get 
> >> this 
> >>> error: pastebin.com/w1QDw5w6 . I looked around and found some related 
> >>> issues on github but lacked solutions at least that I saw, but I need 
> >> these 
> >>> drivers urgently so apologies if this is common knowledge. 
> >>> 
> >> https://www.mail-archive.com/qubes-users@googlegroups.com/msg27754.html 
> >> 
> >> 
> > 
> Qubes menu/sys-net/qube settings/advanced/kernel=none. Try Debian first 
> the same way if you prefer it; the problem might have been fixed since 
> the linked post. 
>
>

-- 
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/0a2bb142-a3e1-44a0-8be6-9b2150a73c47%40googlegroups.com.

[qubes-users] Just bought ASUS KGPE-D16 2x G34 DDR3 /max. 256GB for QubesOS.

['one-eye-pirate' via qubes-users]

Hello, guys!
Has anyone found a solution to use 256GB RAM instead of 192GB possible like 
this guide https://www.coreboot.org/Board:asus/kgpe-d16 ?
IOMMU/VT-d/AMD-Vi and PCI passthrough works good on this board?

Thanks ;)

Sent with [ProtonMail](https://protonmail.com) Secure Email.

-- 
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/mlH9wwYZ5yN4Y9wYVCcLZTjoXyIZH7-Uu2OheIgxCPpk1kiehywAMzQsGGDjv9D1hRs_lt-rwQVJWDqghRqYzaOYgS_Kjfnl-MB6yIq3iA4%3D%40protonmail.com.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

['awokd' via qubes-users]

muhammad19238...@gmail.com:
> Hello and thank you, but how does one go about installing the stock kernel, 
> is it something I do in qubes or in the VM? I assume this would work with 
> fedora 30 as well.
> 
> On Monday, September 9, 2019 at 9:58:36 PM UTC+1, awokd wrote:
>>
>> muhammad...@gmail.com : 
>>> I am trying to build these drivers on a debian-9 template based vm(my 
>> own 
>>> sys-net, I rather debian than fedora, and I have already tried and got 
>> the 
>>> same result on fedora). The drivers are found here 
>>> https://github.com/tomaspinho/rtl8821ce . I installed these easily on 
>> other 
>>> Debian systems and had no such issue. If i try build with the 
>>> DKMS-install.sh provided, I get this error: pastebin.com/aX9kmZg3 and 
>> in 
>>> the make.log, pastebin.com/XiFfzGWG . If i try build with make, I get 
>> this 
>>> error: pastebin.com/w1QDw5w6 . I looked around and found some related 
>>> issues on github but lacked solutions at least that I saw, but I need 
>> these 
>>> drivers urgently so apologies if this is common knowledge. 
>>>
>> https://www.mail-archive.com/qubes-users@googlegroups.com/msg27754.html 
>>
>>
> 
Qubes menu/sys-net/qube settings/advanced/kernel=none. Try Debian first
the same way if you prefer it; the problem might have been fixed since
the linked post.

-- 
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/1beee6fa-9cb8-cb43-9596-ba74990d1bad%40danwin1210.me.

Re: [qubes-users] Reminder: Please help test new updates and provide feedback!

[brendan . hoar]

FYI, running Thinkpad W520 running R4 w/ current-testing & kernel-latest, 
updated to current-testing's bevy of updates this morning.

Everything is smooth so far.

Brendan

-- 
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/8dd7c99d-04bc-4283-b49d-c6ffa286e50d%40googlegroups.com.

Re: [qubes-users] Trouble building RTL8821CE WiFi drivers

[muhammad19238219]

Hello and thank you, but how does one go about installing the stock kernel, 
is it something I do in qubes or in the VM? I assume this would work with 
fedora 30 as well.

On Monday, September 9, 2019 at 9:58:36 PM UTC+1, awokd wrote:
>
> muhammad...@gmail.com : 
> > I am trying to build these drivers on a debian-9 template based vm(my 
> own 
> > sys-net, I rather debian than fedora, and I have already tried and got 
> the 
> > same result on fedora). The drivers are found here 
> > https://github.com/tomaspinho/rtl8821ce . I installed these easily on 
> other 
> > Debian systems and had no such issue. If i try build with the 
> > DKMS-install.sh provided, I get this error: pastebin.com/aX9kmZg3 and 
> in 
> > the make.log, pastebin.com/XiFfzGWG . If i try build with make, I get 
> this 
> > error: pastebin.com/w1QDw5w6 . I looked around and found some related 
> > issues on github but lacked solutions at least that I saw, but I need 
> these 
> > drivers urgently so apologies if this is common knowledge. 
> > 
> https://www.mail-archive.com/qubes-users@googlegroups.com/msg27754.html 
>
>

-- 
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/e79e18be-4812-4898-bbe1-aa94e2bcf43d%40googlegroups.com.