Re: [qubes-users] Qubes 3.2RC1: number of issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-21 22:04, Dima Puntus wrote: > Hi, > > Here's the info: > > System: HP Elitebook 2570p (3840QM, Intel HD4000, 16GB RAM, 250GB > SSD) > > Qubes 3.2RC1, > > 1. Dual monitor setup seems glitchy, by default the system mirrors > the screens but if you force it via xrandr, the laptop screen goes > black, can't right click on it but can drag windows into it and > maximize. The panel always stays on the external monitor. Same > setup using Qubes 3.1 works like a charm out of the box. There's no > display/monitor section under system settings. > Yes, others have also reported this. It seems that there are some missing packages in dom0. For now, you can work around this by installing kscreen: $ sudo qubes-dom0-update kscreen This should make KDE recognize your external monitor. Then you should be able to run kscreen like so: $ kcmshell5 kscreen (Thanks go to Micah Lee for providing these instructions.) Tracking here: https://github.com/QubesOS/qubes-issues/issues/2084 > 2. USB mouse (Razer Abyssus) sensitivity is too low by default and > can't be adjusted via system settings. Works fine in Qubes 3.1 > Trackpad is fine. > Hm, strange. Could this be a hardware compatibility issue with the mouse? Can you test whether it works with baremetal Fedora 23? > 4. Sensors Viewer doesn't register max CPU temps when changing > polling interval (I normally set it to 1-3sec). Same issue in Qubes > 3.1 > It sounds like this might just be a limitation of the Sensor Viewer applet. You may want to consider filing a report with whoever develops it. > 5. Plasma crashes when trying to change the default theme. That > seems to be related to plasma 5.x as it crashes on every standalone > linux machine for me including Kubuntu 16.04. > Might be worth filing a report with the KDE developers about this. > 6. Question: is it possible to set max CPU threshold per VM? I can > only set it for all 8 vcores using xenpm > I probably have no idea, but may I ask what exactly you mean by "threshold"? As in, speed? (You can adjust the number of VCPUs assigned to a VM in the "Advanced" tab of the VM's settings in Qubes Manager.) > Thank you and hope this info helps improving some rough edges in > the new version. > Thanks for your feedback! > Let me know if you have any questions. > > Dimitry > - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXa5UTAAoJENtN07w5UDAwtgAP/0LbD7HCQRWNN9eVHh3qIoik HeVBPmcHZGK8RbyfGRrQNyGB4/MkzzIok73+c373mr92y318S7VunqgymklXKb/U 0f0CsDKEZjWbgokGJ0dL6cTWx5EpBY9gdSrBPCLmPzIwJOTGxE6zOMQqk4GTpAtg ZkkvJpPGoYzzEjSrUEK59E2TKV4BK/az6o3wSbWG1fKM4nDjD2LDa8Osk/EmXKr4 1Zml8shaOddsJ8VkmNTdA93wJXQQJKtdVcVrCCiv0wI7FEakKwVPe5Mw3pdPONfa pZnMEr7fwPBhJDpbzW0/mBsAGhFGNyEIO1TWci86RgGOT8n9kD4zsPN/wnYsyeFp cBgOlU5SRuIZD2ibcipZPGBh8WiolbVG3E4vscZnGcZGsuQtyphI7HoAEtNAuA1j 8198hRRlM+0YF4MnKovOS8UkvIzHqRwSDC7OCXuJSbeOhAPNm0KqCqfenGzBHNcC 6Xn4EtUGyX56d2DH+kaJsQbED+Tfbf3pyW7xTSs/Gb5ON9zv903mKXEh9ZvmTgc6 hJK5vsUJn8k95lVdNV6DgqOB6fuzaevXaezfhV+O3MQ7UaDCu9ftLuqhul8hRXaS HhRFgPICMegu6DBseIb+jBJPQLf6YsiYqNI4MeaTCEp8vNNjWXySDfIblIOIos/S zWJesTA5FPoeNh7zeCTO =AQch -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/cade96c6-ea13-02c7-3fed-94d80b39f839%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2RC1: number of issues
3 and 6 are just questions I guess. Thank you On Wed, Jun 22, 2016 at 3:29 AM, Ilpo Järvinen wrote: > On Tue, 21 Jun 2016, Dima Puntus wrote: > > > 3. Dom0 is only seeing 3.8GB RAM. Is this by design? I can still allocate > > 10GB+ for individual VMs so the RAM must be visible by Xen. > > It's by design. However, this same limit was already implemented at least > for 3.1 that uses 1-4GB dom0 memory depending on how much memory the > machine has. Is there some particular issue associated to this question > or you just noticed the limit? > > IIRC, there's some parameter for this limit on some of the boot related > commandlines. > > > -- > i. -- 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/CAFGffdoaNOE6yMwCFnHnMdg9udhZEitAXR_%2BCC1yyknSLQq-wQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2RC1: number of issues
On Tue, 21 Jun 2016, Dima Puntus wrote: > 3. Dom0 is only seeing 3.8GB RAM. Is this by design? I can still allocate > 10GB+ for individual VMs so the RAM must be visible by Xen. It's by design. However, this same limit was already implemented at least for 3.1 that uses 1-4GB dom0 memory depending on how much memory the machine has. Is there some particular issue associated to this question or you just noticed the limit? IIRC, there's some parameter for this limit on some of the boot related commandlines. -- i. -- 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/alpine.DEB.2.10.1606221320300.3737%40whp-28.cs.helsinki.fi. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2RC1: number of issues
Hi, Here's the info: System: HP Elitebook 2570p (3840QM, Intel HD4000, 16GB RAM, 250GB SSD) Qubes 3.2RC1, 1. Dual monitor setup seems glitchy, by default the system mirrors the screens but if you force it via xrandr, the laptop screen goes black, can't right click on it but can drag windows into it and maximize. The panel always stays on the external monitor. Same setup using Qubes 3.1 works like a charm out of the box. There's no display/monitor section under system settings. 2. USB mouse (Razer Abyssus) sensitivity is too low by default and can't be adjusted via system settings. Works fine in Qubes 3.1 Trackpad is fine. 3. Dom0 is only seeing 3.8GB RAM. Is this by design? I can still allocate 10GB+ for individual VMs so the RAM must be visible by Xen. 4. Sensors Viewer doesn't register max CPU temps when changing polling interval (I normally set it to 1-3sec). Same issue in Qubes 3.1 5. Plasma crashes when trying to change the default theme. That seems to be related to plasma 5.x as it crashes on every standalone linux machine for me including Kubuntu 16.04. 6. Question: is it possible to set max CPU threshold per VM? I can only set it for all 8 vcores using xenpm Thank you and hope this info helps improving some rough edges in the new version. Let me know if you have any questions. Dimitry -- 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/CAFGffdpg%2B1_HWpGW1c3O6zMOA6u%3DJNaeOLhJJLgCSCdXNUf7Mw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
