Re: [qubes-users] Realtek wifi adapter rtl8821ce

2019-04-06 Thread Jayen Desai
On Saturday, April 6, 2019 at 12:44:58 AM UTC+5:30, awokd wrote:
> Jayen Desai wrote on 4/5/19 3:55 PM:
> > Hello,
> > 
> > I have realtek wifi adapter in my lenovo laptop ideapad 330 15arr model. It 
> > is not recognised by sys-net VM. I have downloaded the driver package from 
> > the following link:
> 
> > I think development workflow is different in Qubes OS. Any pointers, help, 
> > ideas?
> 
> If you haven't already, try switching sys-net to use the debian-9 
> template. It might work with no extra effort. If not, check to see if 
> there's a firmware package available (in Debian).
> 
> https://www.qubes-os.org/doc/managing-vm-kernel/ is instructive. Note 
> "[i]nstalling additional kernel modules is cumbersome." The key is that 
> since kernels are supplied by dom0, you can't just compile in a module 
> in a template.
> 
> An ugly way to make it work would be to clone debian-9 to a standalone 
> VM, boot using its local kernel, compile in your module, then use that 
> as your sys-net. It would break several Qubes protection features if you 
> do that. Fedora would also work if you can get u2mfn/DKMS working. The 
> better way to do it is described in the above link, or you could 
> purchase a better supported Wifi card. :)

Thanks awokd for your help. I think the best option for me would be to go in 
for a supported wifi card. Can you suggest a supported wifi card which supports 
wireless AC standards and will work out-of-the box with Qubes OS R4.0?

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3fb9380d-1c18-47c7-8fde-cf65c61498eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Realtek wifi adapter rtl8821ce

2019-04-05 Thread Jayen Desai
Hello,

I have realtek wifi adapter in my lenovo laptop ideapad 330 15arr model. It is 
not recognised by sys-net VM. I have downloaded the driver package from the 
following link:

https://github.com/endlessm/linux/tree/master/drivers/net/wireless/rtl8821ce

Since sys-net VM is based on fedora 29 template, I have tried to follow the 
steps given in the link below to make it work in sys-net VM:

https://nova.moe/solve-realtek-rtl8821ce-driver-on-fedora/

However when I try to compile the package, I get the following error:

[user@sys-net rtl8821ce]$ ls
Kconfig   clean  hal  include  platform runwpa
Makefile  core   ifcfg-wlan0  os_dep   rtl8821c.mk  wlan0dhcp
[user@sys-net rtl8821ce]$ vi Makefile
[user@sys-net rtl8821ce]$ pwd
/home/user/rtl8821ce/rtl8821ce
[user@sys-net rtl8821ce]$ make
make ARCH=x86_64 CROSS_COMPILE= -C 
/lib/modules/4.14.74-1.pvops.qubes.x86_64/build 
M=/home/user/rtl8821ce/rtl8821ce  modules
make[1]: Entering directory 
'/usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build'
make[2]: *** No rule to make target 
'/home/user/rtl8821ce/rtl8821ce/core/rtw_cmd.o', needed by 
'/home/user/rtl8821ce/rtl8821ce/8821ce.o'.  Stop.
make[1]: *** [Makefile:1527: _module_/home/user/rtl8821ce/rtl8821ce] Error 2
make[1]: Leaving directory '/usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build'
make: *** [Makefile:1902: modules] Error 2
[user@sys-net rtl8821ce]$ pwd

I think development workflow is different in Qubes OS. Any pointers, help, 
ideas?

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cf29f7b4-1b3b-4194-b1b6-3bc4529019f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 4 boot stuck at: "[ OK ] Reached target Basic System. "

2019-04-03 Thread Jayen Desai
On Wednesday, April 3, 2019 at 7:52:38 PM UTC+5:30, cub...@tutamail.com wrote:
> Hi,
> 
> Please help! 
> 
> I've shut down my Qubes 4 system last night and it wouldn't restart. After 
> providing my disk encryption password the system is stucks at:
> 
> 
> 
> "[ OK ] Reached target Basic System. "
> 
> followed by numerous line with:
> 
> [] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
> timeout scripts
> 
> [] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
> timeout scripts
> 
> [] dracut -initqueue[338]: Warning: dracut-initqueue timeout - starting 
> timeout scripts
> 
> .
> 
> [] dracut -initqueue[338]: Warning: Could not boot.
> 
> [] dracut -initqueue[338]: Warning: /dev/mapper/qubes_dev0-root does not 
> exist
> 
> [] dracut -initqueue[338]: Warning: /dev/qubes_dev0/root does not exist
> 
> Starting Dracut Emergency Shell...
> 
> 
> 
> This is very strange. I haven't even updated 'dom0' lately and the system 
> shut down clean. But it just wouldn't start today. 
> 
> 
> 
> If I can't recover the Qubes-OS system as the whole please help me retrieve 
> data/files that I have in my AppVM volumes. How can this be done. 
> 
> 
> 
> This is an emergency for me and I would be immensely grateful for somebody's 
> help to either fix systms boot, so that it could start again, OR help to 
> connect my system disk to other OS and retrieve the data. 
> 
> 
> 
> Thank you !
> 
> cubecub

Have you tried rescue mode using installation media? You can try it and I 
believe it should help. I had used rescue mode to edit my xen.cfg file which 
had helped to me boot the system one again in case I had passed some wrong 
parameters to xen.cfg. You can access rescue mode by pressing ctl+alt+f5. May 
be it will help 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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6079c7b0-acaa-4d1f-8c60-caec837d475b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Windows 10 and 7 X64 installation in UEFI mode

2019-04-02 Thread Jayen Desai
I could accomplish Windows 10 and 7 X64 installation by following the steps 
given in the link below:

https://www.qubes-os.org/doc/windows-vm/

I have followed steps given under Qubes 4.0 - Windows VM installation. I have 
not installed QWT in Windows 10 and 7 X64. I notice that both installations are 
under legacy BIOS. I would like to install them under UEFI BIOS for faster 
loading speed. I have also installed windows10 under virtualbox in UEFI mode 
and I can see the difference in loading speed. Is there a way to install 
windows 10/7 under UEFI mode in Qubes 4.0?
 

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dd857c18-b094-4ad8-872e-89677b760e32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.

2019-04-02 Thread Jayen Desai
On Wednesday, March 27, 2019 at 2:45:12 PM UTC+5:30, Lorenzo Lamas wrote:
> Afaik the specific attack only worked on Intel CPU's, OpenBSD disables SMT on 
> other manufacturers as well as they believe other CPU's have similar issues.
> I run Qubes on an Intel machine, so I have SMT disabled, but haven't noticed 
> any performance hit.

Thanks for your input. However I have gone ahead and enabled all 8 CPUs. I am 
ready to take some risk.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1cd14c11-b840-4868-a55d-d15390ea80c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.

2019-03-27 Thread Jayen Desai
On Wednesday, March 27, 2019 at 11:24:57 AM UTC+5:30, Jayen Desai wrote:
> On Wednesday, March 27, 2019 at 8:57:42 AM UTC+5:30, Jayen Desai wrote:
> > On Wednesday, March 27, 2019 at 5:21:23 AM UTC+5:30, unman wrote:
> > > On Tue, Mar 26, 2019 at 02:00:24PM -0700, CooSee wrote:
> > > > snip !
> > > > 
> > > > change the default entry to smp=on in xen.cfg or BOOTX64.CFG if using 
> > > > UEFI.
> > > > 
> > > > greetings
> > > > 
> > > 
> > > Shouldn't that be "smt=on"?
> > > 
> > > You should probably look at QSB#43 before doing this in any case.
> > > The relevant Xen advisory (273) said that for HVM and PVH guests,
> > > leakage can only be prevented entirely by disabling SMT/Hyper-threading.
> > > I don't think that advice has changed, despite the provision of patches
> > > now incorporated in to Qubes.
> > 
> > It appears that "smt=on" is default. However I passed that as a parameter 
> > to the kernel command line. However the problem still remains. It brings up 
> > only 4 CPUs instead of 8 CPUs. Please help.
> 
> I have gone through QSB#43 and Xen advisory 273 and I understand that only 
> Intel core CPUs are affected by them. My laptop is Lenovo Ideapad 330 15ARR 
> model. It is AMD Ryzen 5 2500 quadcore system. I believe it should not be 
> impacted by the above advisories. This is to further clarify the issue.

Now all 8 CPUs are brought up. Thanks for your advice. Earlier I was have both 
smt=on and smt=off on the kernel commandline. It was my mistake that I did not 
notice smt=off towards the end of the command line.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2e1918a3-a1dd-49e2-b56b-328cf7c47f72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.

2019-03-26 Thread Jayen Desai
On Wednesday, March 27, 2019 at 8:57:42 AM UTC+5:30, Jayen Desai wrote:
> On Wednesday, March 27, 2019 at 5:21:23 AM UTC+5:30, unman wrote:
> > On Tue, Mar 26, 2019 at 02:00:24PM -0700, CooSee wrote:
> > > snip !
> > > 
> > > change the default entry to smp=on in xen.cfg or BOOTX64.CFG if using 
> > > UEFI.
> > > 
> > > greetings
> > > 
> > 
> > Shouldn't that be "smt=on"?
> > 
> > You should probably look at QSB#43 before doing this in any case.
> > The relevant Xen advisory (273) said that for HVM and PVH guests,
> > leakage can only be prevented entirely by disabling SMT/Hyper-threading.
> > I don't think that advice has changed, despite the provision of patches
> > now incorporated in to Qubes.
> 
> It appears that "smt=on" is default. However I passed that as a parameter to 
> the kernel command line. However the problem still remains. It brings up only 
> 4 CPUs instead of 8 CPUs. Please help.

I have gone through QSB#43 and Xen advisory 273 and I understand that only 
Intel core CPUs are affected by them. My laptop is Lenovo Ideapad 330 15ARR 
model. It is AMD Ryzen 5 2500 quadcore system. I believe it should not be 
impacted by the above advisories. This is to further clarify the issue.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/94b9e5d2-4bcf-46cb-ba2b-39e722d672eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.

2019-03-26 Thread Jayen Desai
On Wednesday, March 27, 2019 at 5:21:23 AM UTC+5:30, unman wrote:
> On Tue, Mar 26, 2019 at 02:00:24PM -0700, CooSee wrote:
> > snip !
> > 
> > change the default entry to smp=on in xen.cfg or BOOTX64.CFG if using UEFI.
> > 
> > greetings
> > 
> 
> Shouldn't that be "smt=on"?
> 
> You should probably look at QSB#43 before doing this in any case.
> The relevant Xen advisory (273) said that for HVM and PVH guests,
> leakage can only be prevented entirely by disabling SMT/Hyper-threading.
> I don't think that advice has changed, despite the provision of patches
> now incorporated in to Qubes.

It appears that "smt=on" is default. However I passed that as a parameter to 
the kernel command line. However the problem still remains. It brings up only 4 
CPUs instead of 8 CPUs. Please help.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/11a003d7-94ca-4d3f-ac89-9840d336dec0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.

2019-03-26 Thread jayen . desai
On Tuesday, March 26, 2019 at 5:36:42 PM UTC+5:30, jayen...@gmail.com wrote:
> Only 4 CPUs are brought up. Remaining 4 are parked.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c9d36778-84e4-4520-b814-6739f8466464%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Only 4 CPUs are brought up. Remaining 4 are parked.

2019-03-26 Thread jayen . desai
Only 4 CPUs are brought up. Remaining 4 are parked.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d26c5f98-7c02-4aa6-a55b-3bcece56105a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.