[qubes-users] Re: Dell XPS 9560 4k resolution issues
On Friday, June 30, 2017 at 10:37:58 AM UTC+1, randy march wrote: > I have the same notebook like you. > I simply go to system tools - display and change resolution to 1920x1080. > > But I would like to have a 4k resolution with scaled everything... > > how can you do this? > > > will qubes 4.0 solve this issue? Hi Randy, I only have one resolution showing, and that is what I am trying to change. Does your brightness control work? What versions of Qubes do you have? and which kernel? Also which kernel options? I believe I read somewhere HiDPI will be better supported in 4.0 Thanks! David -- 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/c7753611-f7ed-480c-86ab-c41e689aa2c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Dell XPS 15 9560
On Monday, February 20, 2017 at 8:16:35 AM UTC, Stefan wrote: > Hi, > > installed Qubes 3.2 on my new laptop. After some initial problems, it > seems to be working great! > > After installing from the ISO image, the graphics driver was working > fine (at least I remember it this way), only suspend to RAM crashed the > machine. I updated all packages (fedora template and dom0), and after a > reboot, X used the framebuffer driver and did not detect the Intel > graphics chip :-( > > Both problems were solved by enabling the qubes-dom0-unstable repo and > updating the dom0 kernel to the version provided there. Intel VGA and > Suspend to RAM are working fine now. > > > The nvidia chip (GTX 1050) is not supported by the nouveau driver, and I > didn't go through the pain (not to speak of the security concerns) of > manually installing the latest proprietary driver from nVidia on dom0. > > > Suspend to RAM seems to have some problem with the WLAN driver, though. > After some suspend cycles, WLAN won't come up again. I put the driver > ath10k_pci to the suspend-module-blacklist, I think this did the trick. > > > Stefan. Thanks for the work Stefan. - Any chance anyone has the 4k screen? I am having issues setting a lower resolution than 4k or working with HiDPI overall, what were your approaches? - Also any luck in being able to set brightness levels? thanks, David -- 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/a7c7a098-0adc-4f40-9d02-8c7eb9429a88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Dell XPS 9560 4k resolution issues
Hi all, I have been struggling to find a good way to use my 4k display. For context, I have looked for setting HiDPI, am aware of https://github.com/QubesOS/qubes-issues/issues/1951 and others, but at least for now I see HiDPI as a half solution. I don't care about my full screen resolution in Qubes, so I am ok in setting it to something like 1920x1080, the issue is I am not being able to. Since the only mode available in xrandr is 3840x2160 I am forced to add a new mode. I ran cvt 1920 1080 60 in dom0, get: Modeline "1920x1080 60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync I --newmode and --addmode to default and when I try setting the mode: xrandr --verbose --output default --mode 1920x1080_60.00 xrandr: Failed to get size of gamma for output default crtc 0: disable screen 0: 1920x1080 508x286 mm 95.92dpi crtc 0: 1920x1080_60.00 59.96 +0+0 "default" xrandr: Configure crtc 0 failed crtc 0: disable screen 0: revert crtc 0: revert I have tried a few things, ran out of ideas, sorry if this is a bit too basic but am a bit stuck. Best. David -- 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/1480f289-07b4-49dc-b2e0-fceba3695942%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] debian 8, rc.local not running
Unman, Sorry my bad, missed that he had written it was executable. David On Sunday, June 12, 2016 at 11:34:40 PM UTC+1, Unman wrote: > > On Sun, Jun 12, 2016 at 07:05:06AM -0700, David Nogueira wrote: > > Hey, > > > > Actually having the same issue on a fedora23 template AppVM, tried > > debugging as suggest by unman but still not luck. > > > > And then I chmoded +x rc.local and it started working. > > > > Best, > > > > David > > > > On Friday, June 10, 2016 at 10:07:41 PM UTC+1, Unman wrote: > > > > > > On Fri, Jun 10, 2016 at 02:23:35AM -0700, Andrew David Wong wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > > > Hash: SHA512 > > > > > > > > On 2016-06-09 19:31, Drew White wrote: > > > > > Hi folks, > > > > > > > > > > Debian 8... > > > > > > > > > > On boot, the rc.local file doesn't execute after the system has > > > > > booted. > > > > > > > > > > What could be wrong? > > > > > > > > > > root@***:/rw/config# ls -al total **M drwxr-xr-x 3 root > > > > > root 4.0K Jun 10 12:24 . drwxr-xr-x 9 root root 4.0K Jun 8 12:11 > > > > > .. -rwxr-xr-x 1 user user 5198 Jun 10 12:20 rc.local > > > > > > > > > > > > > > > it's executable by everyone, readable by everyone, so there should > > > > > be no issues, right? > > > > > > > > > > Hope someone can help please? > > > > > > > > > > Every time my PC starts, that VM should set up all the ports to be > > > > > forwarded and more. I'm about ready to build an applicaiton to > > > > > handle all the ports and all because Qubes doesn't have something > > > > > that handles it all in one, they are all separate and distinct, > > > > > when they shouldn't really be. > > > > > > > > > > I have other issues with the Qubes Windows Tools too, but that's > > > > > another post, and I have pictures and a way around getting them to > > > > > work on large resolutions, like they say there is a bug for. > > > > > > > > > > > > > Just a guess here, but shouldn't it be owned by root:root? That's > how > > > > it is in my Fedora VMs, anyway... > > > > > > > > - -- > > > > Andrew David Wong (Axon) > > > > Community Manager, Qubes OS > > > > https://www.qubes-os.org > > > > -BEGIN PGP SIGNATURE- > > > > > > > > iQIcBAEBCgAGBQJXWocYAAoJENtN07w5UDAwxVMP/2251XpbWdzfzYiCxFn1WWiL > > > > 7Wj2S0A318kbVO+4V/1AzEdueK2AtDxWv8/2T2ph21HnU8d3TJ4t+NRyUtrhDNYw > > > > oUXAovakTlp+S4gY1R18d6C4iXl3t6+LcAGZLgXjHVLbvk+Nc5DNt2gQJ4u5fT/H > > > > JX+1ar4Ee8/maHjXKfODOyXiBwq8vepA0zkB7ybSzEKOECIGb4PWyad1/VnmDo0B > > > > QURcCc9t46YeLA5Ko+ZyNCxUbRULnXoRFO7RvBW6iogzaH3DN3rEQyhY1fEqjZbN > > > > 9S/7EuGHI1BQtHEHmvXMZ++F0OoxaBa9X3Gwf6eFghYGeZAdNwySp+uAufSynwJq > > > > tJC9rPVy83PszQR+6/ZZz4CI5RSqzcOr/KN+I3e1CZlvU13B5JrHhboAdXTarXzU > > > > UvrPL321Km77ODvlQlgvRci9NeBmAWBhLpk+8ozysRc/8x/AiGRoM87l1/7PSyLu > > > > jvBsPYiMx+5N8JQO3uKaZFoO7tCy1O7IWIx45sO9awZcCgG+RTsfTu5FfTW8zpzr > > > > 836xCDxVRc2G2NevT/QsTZOA/YXeN2KIHoBLi2+DH9VXggKmilhYt3Gg0/LlBagk > > > > 8FzWu5TtaDbxRRehnfGFiwMeIAGsgXf2N+vfEpGzjZ8ZuRY7i1x7UjZZNMKzc8WF > > > > +Jh5GvM+nJ1/P4CmhHpm > > > > =XDPS > > > > -END PGP SIGNATURE- > > > > > > > Hi Drew > > > > > > I dont beleieve the user is significant. > > > > > > Nor do I think it likely that rc.local isnt executing, (althoygh this > is > > > not impossible.) > > > > > > To start troubleshooting, try inserting a simple log command at the > > > start of the file: > > > echo `date` >> /home/user/log > > > would do. > > > > > > See if the log is written on boot. > > > If it is, then you need to look at the exact commands you are using. I > > > recall at one time specifying full path although I no longer do so. > > > > > > I use rc.local to set iptables policies etc. and it works flawlessly. > > > > > > If you still cant get it working, post the file contents. > > > > > > unman > > > > > David, > > if you look at Drew's output you will see that the file is already > executable, so this will not be his problem. > > It's clearly stated in the docs that you need to apply chmod +x: > Look at https://www.qubes-os.org/doc/config-files/ > > unman > -- 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/ff1a600b-6b01-46a7-9cf7-73847fdd142a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] debian 8, rc.local not running
Hey, Actually having the same issue on a fedora23 template AppVM, tried debugging as suggest by unman but still not luck. And then I chmoded +x rc.local and it started working. Best, David On Friday, June 10, 2016 at 10:07:41 PM UTC+1, Unman wrote: > > On Fri, Jun 10, 2016 at 02:23:35AM -0700, Andrew David Wong wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > On 2016-06-09 19:31, Drew White wrote: > > > Hi folks, > > > > > > Debian 8... > > > > > > On boot, the rc.local file doesn't execute after the system has > > > booted. > > > > > > What could be wrong? > > > > > > root@***:/rw/config# ls -al total **M drwxr-xr-x 3 root > > > root 4.0K Jun 10 12:24 . drwxr-xr-x 9 root root 4.0K Jun 8 12:11 > > > .. -rwxr-xr-x 1 user user 5198 Jun 10 12:20 rc.local > > > > > > > > > it's executable by everyone, readable by everyone, so there should > > > be no issues, right? > > > > > > Hope someone can help please? > > > > > > Every time my PC starts, that VM should set up all the ports to be > > > forwarded and more. I'm about ready to build an applicaiton to > > > handle all the ports and all because Qubes doesn't have something > > > that handles it all in one, they are all separate and distinct, > > > when they shouldn't really be. > > > > > > I have other issues with the Qubes Windows Tools too, but that's > > > another post, and I have pictures and a way around getting them to > > > work on large resolutions, like they say there is a bug for. > > > > > > > Just a guess here, but shouldn't it be owned by root:root? That's how > > it is in my Fedora VMs, anyway... > > > > - -- > > Andrew David Wong (Axon) > > Community Manager, Qubes OS > > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > > > > iQIcBAEBCgAGBQJXWocYAAoJENtN07w5UDAwxVMP/2251XpbWdzfzYiCxFn1WWiL > > 7Wj2S0A318kbVO+4V/1AzEdueK2AtDxWv8/2T2ph21HnU8d3TJ4t+NRyUtrhDNYw > > oUXAovakTlp+S4gY1R18d6C4iXl3t6+LcAGZLgXjHVLbvk+Nc5DNt2gQJ4u5fT/H > > JX+1ar4Ee8/maHjXKfODOyXiBwq8vepA0zkB7ybSzEKOECIGb4PWyad1/VnmDo0B > > QURcCc9t46YeLA5Ko+ZyNCxUbRULnXoRFO7RvBW6iogzaH3DN3rEQyhY1fEqjZbN > > 9S/7EuGHI1BQtHEHmvXMZ++F0OoxaBa9X3Gwf6eFghYGeZAdNwySp+uAufSynwJq > > tJC9rPVy83PszQR+6/ZZz4CI5RSqzcOr/KN+I3e1CZlvU13B5JrHhboAdXTarXzU > > UvrPL321Km77ODvlQlgvRci9NeBmAWBhLpk+8ozysRc/8x/AiGRoM87l1/7PSyLu > > jvBsPYiMx+5N8JQO3uKaZFoO7tCy1O7IWIx45sO9awZcCgG+RTsfTu5FfTW8zpzr > > 836xCDxVRc2G2NevT/QsTZOA/YXeN2KIHoBLi2+DH9VXggKmilhYt3Gg0/LlBagk > > 8FzWu5TtaDbxRRehnfGFiwMeIAGsgXf2N+vfEpGzjZ8ZuRY7i1x7UjZZNMKzc8WF > > +Jh5GvM+nJ1/P4CmhHpm > > =XDPS > > -END PGP SIGNATURE- > > > Hi Drew > > I dont beleieve the user is significant. > > Nor do I think it likely that rc.local isnt executing, (althoygh this is > not impossible.) > > To start troubleshooting, try inserting a simple log command at the > start of the file: > echo `date` >> /home/user/log > would do. > > See if the log is written on boot. > If it is, then you need to look at the exact commands you are using. I > recall at one time specifying full path although I no longer do so. > > I use rc.local to set iptables policies etc. and it works flawlessly. > > If you still cant get it working, post the file contents. > > unman > -- 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/d108f60e-d057-489f-916b-44d092e68c53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
