Re: [qubes-users] websites suddenly don't work when connected to vpn
On 12/06/2018 02:25 AM, blupunk...@gmail.com wrote: Hi hi i have had a new install of qubes 4.0.1-rc1 working for some weeks now. i have successfully set up vpn connection through different ways including the old CLI method: https://www.qubes-os.org/doc/vpn/ and newer Qubes-vpn-support: https://github.com/tasket/Qubes-vpn-support I have done this with qubes 3.2 in the past with no hitch so not much of noob. but now out of the blue when I connect to a vpn that is successful, I cannot access websites in firefox or chromium - they time out. this is both within the proxy/vpn VM and from an appVM. i don't think it is a dns issue because when I open terminal in the vpnVM and appVM and ping 8.8.8.8 or hostnames like google.com they work fine. i am sure it was working before but something has happened since. I am able to access websites through the sys-firewall VM no problem. i have made new vpnVMs from scratch with stock openvpn configs, still same problem. It might help to know which ISP and maybe the VPN provider you're using. Where you download the VPN configs from also seems to make a difference. Check out this thread where the user had to work around the ISP's packet fragmentation requirement in order to access some websites: https://groups.google.com/d/msgid/qubes-users/8mSm0mD6lYCcvrvd2xg2BxF9fsGym1_K3aWvBGjI05C1MKa7hoM4bb5nOZVRp6njwWzfTwV_TA3f6hEpU-ttNxnRQOWtZeeOUWHozPumX4w%3D%40pm.me Also, simple stuff: Are you using Debian 9 (not 8) and clicking on "provides network" when you create the proxyVM? Does traceroute from the attached appVM show it going through the VPN address? perhaps a problem with firewall, iptables or a new debian update? seems like things were more seamless with 3.2 concerning vpn's. thanks guys -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/13cd3080-48bf-9b48-c36c-9169f535ebbd%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Nvidia dGPU (MX150) Passthrough Issues
Hey Guys, I'm wanting to pass my dGPU down to an HVM appVM, so I can enjoy dGPU performance sometimes (Test Firefox's GPU Rendering Engine) However I can't seem to start the appVM with the PCI Device Attached, I've set rd.qubes.hide_pci=01:00.0 Here's the Console Log: https://pastebin.com/aKYNFSK8 And the Xen Console Log (Stubdom): https://ufile.io/1ldov (I had to upload it because it's 500KB worth of logs) I have a feeling it has something to do with the stubdomain, but I'm not sure. Any help would be appreciated, Cheers! -- 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/b269334c-b1f2-416c-b607-aa66362937e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0 install on my Huawei Matebook X Pro failed
On Wednesday, December 5, 2018 at 10:06:33 AM UTC, Laurent Huguenot wrote: > I am trying to install Qubes 4.0 on my Matebook X Pro, but I am > > > > > experiencing problems. The USB key boot, but the boot freeze when > > > > > loading the initrd. I tried to modify the cfg file, commenting > > > > > noexitboot and mapbs and changing efi=no-rs, but no result. > > > > > > > Could you help me? > > > > > > > Many thanks > > > > > > > > > Laurent Huguenot Hi, I'm typing this from Qubes 4.0 on my Matebook X Pro, you need to make sure you're editing the .cfg file from the ANACONDA partition on the USB. Install it, then edit the newly created /boot/efi/EFI cfg to reflect the changes you did on the USB (efi=no-rs) -- 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/b22311aa-c399-4c9b-9245-413faff09dfe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Nvidia dGPU (MX150) Passthrough Issues
So that's weird, if I set it to provides network, and enable memory scaling it boots ``` [user@fedora-standalone ~]$ lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01) 00:03.0 VGA compatible controller: Device 1234: (rev 02) 00:04.0 USB controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 10) 00:07.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1) ``` -- 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/23b0e721-93f1-443c-8084-a0adc0cf4744%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] R3.2 Boot process crashes starting sys-usb
Hi, Folk's, the boot process in Release 3.2 crashes always during VM sys-usb start up. The error message : ... Illegal opcode ... Exists a way to disable the start of sys-usb for the boot ? For example are there some kernel parameters to surpress the start of choosen VM's ? Thanks in advance ciao -- 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/cd8efeb2-29fc-43ad-9f71-fa359186879e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0 install on my Huawei Matebook X Pro failed
Hi, I was sure that a solution should exist (I was so sad to not be able to use Qubes anymore :) ) I will try that. Thank you very much -- 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/fbdee3b9-3391-44d9-a299-ff01e6d4c485%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Custom Indicator
List. I'm using Qubes 3.2/XFCE4 and I want to add an indicator to show a status based on the contents of a file in dom0. I can set the contents of the file to 1 or 0, Yes or No, etc...from the vm where I am running a VPN connection. I want the panel to indicate if I am running the VPN connection or not. I have tried the "Generic Monitor" which allegedly shows the output of a command, as it would be logical to cat the file with a certain frequency and update the displayed results, but the only thing the "Generic Monitor" displays is the label given it. Are there other options which will actually function? Thanks in advance. Stuart -- 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/20181206101811.269b9bf5%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Nvidia dGPU (MX150) Passthrough Issues
Damn I'm close ``` 00:07.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1) Physical Slot: 7 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://groups.google.com/d/msgid/qubes-users/470215c3-ea12-425a-8ce3-e83c0d9d157c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Q4 qube-manager broke after dom0 software update yesterday
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/4/18 8:07 PM, Steve Coleman wrote: > I was away for a week and dutifully did all my software updates > upon returning. After updating Dom0 the qube-manager that was > running started having problems, so I restarted it, but it then > refused to run. > > RuntimeError: the PyQt4.QtCore and PyQt5.QtCore modules both wrap > the QtObject class > > The problem appears to be qube-manager/python3 is first picking up > references to PyQt5 when first launching, and later it is picking > up some PyQt4 references via > /usr/lib64/python3.5/site-packages/qubesadmin/__pycache__/*.pyc > files, which then load files from > /usr/lib64/python3.5/site-packages/PyQt4/__pycache__/* , and thus > PyQt4/QtGui.so gets loaded. > > It looks like the qubes-manager-4.0.22-1.noarch is the latest, > though I can't help but think this is a case of cache poisoning or > some Qt4/Qt5 environment issue. If so, can the __pycache__/*.pyc > files be removed and regenerated, or is there another way to avoid > the mixing of PyQt versions? > I think that PyQt5 is not installed on dom0 by default so this problem is not very likely to happen. Also it seems that all imports from Qube Manager source specify version 4. Please tell if you know some reliable steps for reproduce it. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlwJUHsACgkQFBMQ2OPt CKWr+A//Qx8jQ3xuZDNGTmIKUvVBLJNau01wHdRVF+bBW0S7RxfjiwHXjTJ5DLTU L/ne1fCjGDPG7kV3fqy2sXq0Lfl1brPiIQpcU82f/LpHBsIGb6Uz33vfDGF8hNkC ZEaK76KHxoA9Z3OVwic/x56kwbLuvXDX8d6M8K37ZOfOxgsgoY7WbGQDf/0dBK6Y auAnPxQ8K3vhS/prJi2u+DWASBnEkM9d94tCeOFhpVHYkpv/6F1PMhx5CSTy/lwN aSOy1IUkL54WJ4QwT3NNoIKkd+vhxHHOjvvSeKCQcAANoYkgtkhwEJDD/AQn9bE4 EDAZ8yV3QfHElg64x9SIbQJh5rrlLJpKOLnMMslzQl1zIrAzy5V5YcInXiic6VK8 cNDX+FT07kz5+PoqZ5eUMrnbFjbCE4t53sGRuTS+Zd1QdVIEHTvHd2ToMUfeEBX+ tnLTbqg+rhh/F6oirI+L/jx5oSrye5vNvx5kcg4Q0y4AbEWPY0DVZWuemuMVBQGl 4TqG8zQN7CNU6yW8GRHBf3dLi9DtJVS9LUVe+HlC0AYZw2JDUFGxpo6Jb4LxZ791 V9k/FFzH4CLeRs9nh2aoQDFnjK4PcEEifJep9Grbi+z4wGHxN/VB/+aVU4acKJ/I 9Kdr+D4lvlYV6hGY0qxYugj7L26itILsEBPqeGpomsR+2NgKOus= =NNXh -END PGP SIGNATURE- -- 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/ce0c19d5-8414-e8be-80df-a4f843f5a4b1%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How many gigabytes of memory is required for G505s?
On 12/05/2018 06:19 PM, '我' via qubes-users wrote: > Hello. > > When reading this list I thought G505s A10 is the best laptop for Qubes. > So I'd like to purchase it, but I am wondering how many memory to put in. > > Could you give me some advice? > 2x8GB DDR3 1600mhz SODIMM's so 16GB and yes it is the best - remember to install coreboot with microcode updates btw (check binary only repo + generate microcode from tree) -- 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/4901408e-f3b0-6a12-69ac-21eda8960240%40gmx.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Q4 qube-manager broke after dom0 software update yesterday
On 12/6/18 11:38 AM, donoban wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/4/18 8:07 PM, Steve Coleman wrote: I was away for a week and dutifully did all my software updates upon returning. After updating Dom0 the qube-manager that was running started having problems, so I restarted it, but it then refused to run. RuntimeError: the PyQt4.QtCore and PyQt5.QtCore modules both wrap the QtObject class The problem appears to be qube-manager/python3 is first picking up references to PyQt5 when first launching, and later it is picking up some PyQt4 references via /usr/lib64/python3.5/site-packages/qubesadmin/__pycache__/*.pyc files, which then load files from /usr/lib64/python3.5/site-packages/PyQt4/__pycache__/* , and thus PyQt4/QtGui.so gets loaded. It looks like the qubes-manager-4.0.22-1.noarch is the latest, though I can't help but think this is a case of cache poisoning or some Qt4/Qt5 environment issue. If so, can the __pycache__/*.pyc files be removed and regenerated, or is there another way to avoid the mixing of PyQt versions? I think that PyQt5 is not installed on dom0 by default so this problem is not very likely to happen. Also it seems that all imports from Qube Manager source specify version 4. Ok, thanks. At least I now know which direction to go to debug this problem. There must be some tool installed that pulled in PyQt5 then. I'll check the dependencies and see what that might be, or otherwise remove that package. One would think that python would have a way to control this as a dynamic PATH configuration. If they do have control of this dynamic loading I have not found that feature yet. Please tell if you know some reliable steps for reproduce it. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlwJUHsACgkQFBMQ2OPt CKWr+A//Qx8jQ3xuZDNGTmIKUvVBLJNau01wHdRVF+bBW0S7RxfjiwHXjTJ5DLTU L/ne1fCjGDPG7kV3fqy2sXq0Lfl1brPiIQpcU82f/LpHBsIGb6Uz33vfDGF8hNkC ZEaK76KHxoA9Z3OVwic/x56kwbLuvXDX8d6M8K37ZOfOxgsgoY7WbGQDf/0dBK6Y auAnPxQ8K3vhS/prJi2u+DWASBnEkM9d94tCeOFhpVHYkpv/6F1PMhx5CSTy/lwN aSOy1IUkL54WJ4QwT3NNoIKkd+vhxHHOjvvSeKCQcAANoYkgtkhwEJDD/AQn9bE4 EDAZ8yV3QfHElg64x9SIbQJh5rrlLJpKOLnMMslzQl1zIrAzy5V5YcInXiic6VK8 cNDX+FT07kz5+PoqZ5eUMrnbFjbCE4t53sGRuTS+Zd1QdVIEHTvHd2ToMUfeEBX+ tnLTbqg+rhh/F6oirI+L/jx5oSrye5vNvx5kcg4Q0y4AbEWPY0DVZWuemuMVBQGl 4TqG8zQN7CNU6yW8GRHBf3dLi9DtJVS9LUVe+HlC0AYZw2JDUFGxpo6Jb4LxZ791 V9k/FFzH4CLeRs9nh2aoQDFnjK4PcEEifJep9Grbi+z4wGHxN/VB/+aVU4acKJ/I 9Kdr+D4lvlYV6hGY0qxYugj7L26itILsEBPqeGpomsR+2NgKOus= =NNXh -END PGP SIGNATURE- -- 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/b456beb0-be3a-6019-282c-23e0cdfbcef7%40jhuapl.edu. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Custom Indicator
On 12/6/18 6:18 PM, Stuart Perkins wrote: List. I'm using Qubes 3.2/XFCE4 and I want to add an indicator to show a status based on the contents of a file in dom0. I can set the contents of the file to 1 or 0, Yes or No, etc...from the vm where I am running a VPN connection. I want the panel to indicate if I am running the VPN connection or not. I have tried the "Generic Monitor" which allegedly shows the output of a command, as it would be logical to cat the file with a certain frequency and update the displayed results, but the only thing the "Generic Monitor" displays is the label given it. You can't `cat` a file, the command you configure in the applet has to be an executable. You also have to specify the full path, '~' or $HOME won't work. Here's for instance the output of a script that displays my batteries' status + current power: dom0 $ ~/bin/batstat 65 | 79 30 | 34 P: 6.9 The script is configured as `/home/user/bin/batstat` in the applet. (I'm on R4 but I think I used to have the same setup with R3.2). -- 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/3a4fb926-b33a-3a9c-1a9b-5440c99c7cfe%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes4.0 on gen3 X1 looses disk on resume from suspend
Hi All, New to Qubes so hopefully I just missed some thing obvious. When resuming from suspend on Lenovo X1 Carbon (gen3) with fresh Qubes 4.0 install I'm loosing access to the physical disk on resume. This looked very similar to https://github.com/QubesOS/qubes-issues/issues/3049 and is first noticeable as I/O errors in App VMs and Dom0, but that but was closed a long time ago so presumably a new install followed bu dom0-update should get me caught up with that? To cut out various other hardware resume issues I replicated this with all network and usb VMs down just Dom0 and a "vault" style no-network AppVM running. Repeating with closing the lid in text console (rather than Xwindows) I can see (but not effectively copy) error messages. ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psparse-364) ACPI Error: Method parse/execution failed \_PR.CPU1._CST, AE_NOT_FOUND (20170728/psparse-550) ata1.00: revalidation failed (errno=-5) ata1.00: revalidation failed (errno=-5) sd 0:0:0:0: rejecting I/O to off lien device then a bunch of device-mapper and EXT4 errors that likely result from that initial failure. from time stamps the ACPI errors appear to be when going to sleep though not 100% sure the disc errors are definitely on resume. screenshot here: https://people.csail.mit.edu/jon/qubes_disk_error.jpg I was previously running Debian Testing and a few older Ubuntu releases and they had been OK with resume from sleep on this hardware. Maybe there's something extra I need to poke in Fedora land? I found some notes about blacklisting wireless modules in net domain but nothing Dom0 related. Any clues? Thanks, -Jon -- 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/CABZB-shNn5uMjj424RR2zNohH8SBcOfPyj6n7kghafbmBqeQNw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] [R4.0] CPU Freq Scaling, or "Why am I stuck at 2.1 Ghz?"
Finally received my new Thinkpad X1 Yoga 3rd gen. i7-8650U up to 4.2 Ghz Turbo How can I debug/check that my CPU governor/frequency is scaling correcting under Qubes R4? So far, the only thing I've found is xentop/xl top that lists the CPU - as a never-changing 2.1 Ghz. Maybe this isn't the best way to measure CPU freq under dom0? All other tools seemed to want to use xfce4 tools, which seemed to only be specific to that fedora VM - and not the xen host. /TL;DR I let Windows 10 register itself before wiping the disk and installing Qubes R4. Under Windows, Google Chrome benchmarked around 5300 pts with the online tool I was using. As a test, I also installed Arch Linux briefly to test Chrome performance, and it came in around 4500 pts. I chalk that up to not optimizing anything on the system - just a raw install and no tweaks. Now, under Qubes R4.0, I'm still noticing a lot of sluggishness/slowdowns just like my older Thinkpad Helix has always had under Qubes R3.2 (and one of the reasons why I waited for this quad core CPU to upgrade my Qubes install). I could never benchmark Chrome under that Helix dual-core low-powered device. I loaded up Chrome on a new debian-9 VM and... Almost the same extremely sluggish performance. Google Chrome can't even get partially through the benchmarks without timing out, much less finish them. I've tried assigning 4 and even 8 vcpus to try to max things out. I am wondering where to start to debug this. Is it a dom0 cpu scaling thing? Does Qubes impose some artificial throttling? Is it a lag in iGPU rendering through the DisplayVM? (this DisplayVM is a new concept to me, still trying to figure it out) I've spent about 3 days on this device with various other issues to get to this point (no S3 sleep yet, pixel-perfect scaling of the HDR 1440p 14" display, etc). I few duckduckgo searches hasn't turned anything up yet; so, i'll continue when I have some time. Thanks! -E -- 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/1bbc7347-95f0-4a72-bea5-2e58b40220c7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Nvidia dGPU (MX150) Passthrough Issues
FYI, I plan on doing this as well when I get my P1 in a few weeks. > I've installed the nvidia driver and disabled/blacklisted nouveau, however I > can't use bumblebee due it complaining there's no Intel GPU (Using `00:03.0 > VGA compatible controller: Device 1234: (rev 02)`) > My research led me to believe that you won't be able to use bumblebee with Qubes, as bumblebee expects both the Intel iGPU and Nvidia dGPU drivers in the same domain and Hybrid Graphics enabled in the BIOS. Since Qubes separates this by having the iGPU in dom0 (soon to be a new GUI domU?), and you are using pci-passthru dGPU to another domU, it won't have both. I plan on experimenting with this as well; however, I already know that the dGPU will always have to be active in this setup - killing any battery savings. What I don't know is if xen will put the dGPU will go into a power-savings mode if the domU it is attached to is shutdown. Or, better yet, if bumblebee can be installed in dom0 even with dGPU set as pci-passthru. I have my doubts; but, that is my plan to experiment with. My fallback is to disable the dGPU in the BIOS when on the road and switch back to Hybrid when only docked and only when I want to loadup AutoCAD or Blender (very rarely). However, I already know the X1 Exteme, and I'm guessing the P1, won't allow the Nvidia GPU to be disabled in the bios like earlier generation Thinkpads. Bleh, lots of workarounds. > So it's there, I just can't tell applications to render on the dGPU, so > close... > How can you tell "it's there"? Maybe look for it in the log such as: # grep "X Driver" /var/log/Xorg.0.log If you see something listed as Nvidia, then it is indeed loaded and could be used to offload hardware acceleration (such as Blender or perhaps AutoCAD shading). What I don't know is if rendering 3D to the screen would work within Qubes. OT: On my new Qubes/gaming desktop I am upgrading, I'll have all 4 displays connected to a single low-end GPU via HDMI inputs (monitors are currently all 1080p@120Hz). However, the 2x Vega 64s will connect via DVI (DP-to-DVI) to my primary 3 monitors for EyeFinity. A trick I saw someone do with Xen on youtube was to "disconnect" the monitors from HDMI of the first GPU - this frees up their signal. Then, within another domU, enable the DP output and BAM, the monitors come back - dedicated to the gaming domU. That should work with Qubes I believe with an HVM. However, I don't think that works with laptops though - unless you want to try dedicating the output of a specific external port to an external display. Maybe that might work? - keeping it disconnected from dom0, and enabling the output via xrandr within your nvidia dom0? -- 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/92324f5e-f474-45ef-93ee-bc5b41eaa6e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [R4.0] CPU Freq Scaling, or "Why am I stuck at 2.1 Ghz?"
On 12/7/18 1:54 AM, Eric Duncan wrote: Finally received my new Thinkpad X1 Yoga 3rd gen. i7-8650U up to 4.2 Ghz Turbo How can I debug/check that my CPU governor/frequency is scaling correcting under Qubes R4? So far, the only thing I've found is xentop/xl top that lists the CPU - as a never-changing 2.1 Ghz. Maybe this isn't the best way to measure CPU freq under dom0? All other tools seemed to want to use xfce4 tools, which seemed to only be specific to that fedora VM - and not the xen host. see `xenpm` eg. in dom0: sudo xenpm get-cpufreq-para /TL;DR I let Windows 10 register itself before wiping the disk and installing Qubes R4. Under Windows, Google Chrome benchmarked around 5300 pts with the online tool I was using. As a test, I also installed Arch Linux briefly to test Chrome performance, and it came in around 4500 pts. I chalk that up to not optimizing anything on the system - just a raw install and no tweaks. Now, under Qubes R4.0, I'm still noticing a lot of sluggishness/slowdowns just like my older Thinkpad Helix has always had under Qubes R3.2 (and one of the reasons why I waited for this quad core CPU to upgrade my Qubes install). I could never benchmark Chrome under that Helix dual-core low-powered device. It could be that the smt=off "fix" for L1TF causes you pain (see issues 4372 and 4252). Unplug your laptop from AC, open a VM, browse the web casually and check your power consumption - a recent laptop should be between 5 to 7 W on Qubes with light usage. If you see something >10W (like I did), try to re-enable smt - which is not really a good thing to do but that's that or throwing the laptop out of the window. Note: I haven't tested if recent kernels fixed the issue. I loaded up Chrome on a new debian-9 VM and... Almost the same extremely sluggish performance. Google Chrome can't even get partially through the benchmarks without timing out, much less finish them. I've tried assigning 4 and even 8 vcpus to try to max things out. You shouldn't configure more vcpus that cpus, that'll add overhead. I am wondering where to start to debug this. Is it a dom0 cpu scaling thing? Does Qubes impose some artificial throttling? Is it a lag in iGPU rendering through the DisplayVM? (this DisplayVM is a new concept to me, still trying to figure it out) DisplayVM ? AFAIK Qubes dev are working to isolate the gui stuff into a specific domain but I think it was planned for 4.1. Or maybe you meant dispVM ? If yes, disposable VMs in R4 are a bit different than R3.2 (way more flexible). I've spent about 3 days on this device with various other issues to get to this point (no S3 sleep yet, pixel-perfect scaling of the HDR 1440p 14" display, etc). I few duckduckgo searches hasn't turned anything up yet; so, i'll continue when I have some time. Good luck :) -- 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/23b47a1f-d34b-7d9d-057b-1d71e343a0e7%40maa.bz. For more options, visit https://groups.google.com/d/optout.
