[qubes-users] Re: Please help with Qubes 4.0 rc4 on 8th Generation Intel
On Tuesday, 13 March 2018 06:37:22 UTC, mrp...@gmail.com wrote: > On Wednesday, February 14, 2018 at 1:22:42 PM UTC+7, Krišjānis Gross wrote: > > On Monday, 5 February 2018 14:13:25 UTC, Krišjānis Gross wrote: > > > Hi, > > > > > > I have recently installed Qubes 4.0 rc4 on a new 8th generation Intel > > > hardware and have an issue that I would like to get help with. > > > > > > The issue is that graphics appear to be very very slow. Each time there > > > is some visual activity on the screen it is vary 'laggy'. I noticed that > > > whenever there is a GUI action, the process called Xorg is using 100% of > > > one of the processor cores. > > > > > > I have made captured a video of how that looks: > > > https://drive.google.com/open?id=1vrtVnVLu6WBrMl_6O-R7qs2syyOKypnQ > > > > > > I have also gathered some logs that might help to resolve this: > > > 1) archive of /var/logs folder: > > > https://drive.google.com/open?id=171-f2-d3D_CPrSFJKFwcuIrQgZXYf5L3 > > > 2) result of "sudo journalctl -b > journal.log" : > > > https://drive.google.com/open?id=1eOJMT4uGAQyatXFcQvF9ElGRpbdTTQSp > > > > > > Hardware details: > > > MB: ASRock Z370 Pro4 > > > https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp > > >CPU: Intel® Core™ i5-8600K > > > https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz > > > > > >RAM: 16 GB DDR4 > > > > > > > > > Please help to resolve this! > > > > Thank You, awokd! > > > > That indeed helped to resolve the issue! > > > > The exact steps that I did was: > > 1) Install Qubes 4.0 rc4; > > 2) Start Qubes. Notice the software rendering of the video; > > 3) Open dom0 terminal and edit /boot/efi/EFI/qubes/xen.cfg (e.g. sudo > > nano /boot/efi/EFI/qubes/xen.cfg) > > Replace 2 occurances of "i915.preliminary_hw_support=1" with > > "i915.alpha_support=1"; > > 4) Reboot the system. > > Hi Krišjānis Gross, > > Is your system with Qubes 4.0 rc4 still working fine?Did the graphic > issue relapse? > > Since you posted on February, have there been any other issues? > > Thanks, Hi mrp2pp, Yes, the system is working very nice. Graphic issue is gone and has not repeated. I have not had any issues (with exception to those that I have created myself with my limited knowledge in this area). -- 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/abb1391c-bea3-4dcd-9c71-b6b078fbab41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - ASRock Z370 Pro4, i5-8600K
Hi, I have recently installed Qubes 4 rc4 on 8th gen intel CPU. HCL details attached to this e-mail. Note: There was an issue with graphic adapter. More details here: https://groups.google.com/forum/#!msg/qubes-users/YjNkEM1srSk/ljMSWgNTBAAJ Other than that everything works very nice. Kind regards, Krisjanis -- 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/CA%2BbLPogPufk7veLDtF73DBOSDu8n%2B3QPEB81-25TmHywO9HARQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-ASRock-Z370_Pro4-20180218-113044.yml Description: application/yaml Qubes-HCL-ASRock-Z370_Pro4-20180218-113044.cpio.gz Description: GNU Zip compressed data
[qubes-users] Re: Please help with Qubes 4.0 rc4 on 8th Generation Intel
On Monday, 5 February 2018 14:13:25 UTC, Krišjānis Gross wrote: > Hi, > > I have recently installed Qubes 4.0 rc4 on a new 8th generation Intel > hardware and have an issue that I would like to get help with. > > The issue is that graphics appear to be very very slow. Each time there is > some visual activity on the screen it is vary 'laggy'. I noticed that > whenever there is a GUI action, the process called Xorg is using 100% of one > of the processor cores. > > I have made captured a video of how that looks: > https://drive.google.com/open?id=1vrtVnVLu6WBrMl_6O-R7qs2syyOKypnQ > > I have also gathered some logs that might help to resolve this: > 1) archive of /var/logs folder: > https://drive.google.com/open?id=171-f2-d3D_CPrSFJKFwcuIrQgZXYf5L3 > 2) result of "sudo journalctl -b > journal.log" : > https://drive.google.com/open?id=1eOJMT4uGAQyatXFcQvF9ElGRpbdTTQSp > > Hardware details: > MB: ASRock Z370 Pro4 https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp >CPU: Intel® Core™ i5-8600K > https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz > >RAM: 16 GB DDR4 > > > Please help to resolve this! Thank You, awokd! That indeed helped to resolve the issue! The exact steps that I did was: 1) Install Qubes 4.0 rc4; 2) Start Qubes. Notice the software rendering of the video; 3) Open dom0 terminal and edit /boot/efi/EFI/qubes/xen.cfg (e.g. sudo nano /boot/efi/EFI/qubes/xen.cfg) Replace 2 occurances of "i915.preliminary_hw_support=1" with "i915.alpha_support=1"; 4) Reboot the system. -- 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/c0bc2bcb-92a8-4f33-b836-ee31803e9bf9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Please help with Qubes 4.0 rc4 on 8th Generation Intel
Hi, I have recently installed Qubes 4.0 rc4 on a new 8th generation Intel hardware and have an issue that I would like to get help with. The issue is that graphics appear to be very very slow. Each time there is some visual activity on the screen it is vary 'laggy'. I noticed that whenever there is a GUI action, the process called Xorg is using 100% of one of the processor cores. I have made captured a video of how that looks: https://drive.google.com/open?id=1vrtVnVLu6WBrMl_6O-R7qs2syyOKypnQ I have also gathered some logs that might help to resolve this: 1) archive of /var/logs folder: https://drive.google.com/open?id=171-f2-d3D_CPrSFJKFwcuIrQgZXYf5L3 2) result of "sudo journalctl -b > journal.log" : https://drive.google.com/open?id=1eOJMT4uGAQyatXFcQvF9ElGRpbdTTQSp Hardware details: MB: ASRock Z370 Pro4 https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp CPU: Intel® Core™ i5-8600K https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz RAM: 16 GB DDR4 Please help to resolve this! -- 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/75f955b6-d802-42db-a2c7-9e68cc5bbaa9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes OS 4.0-rc4 has been released!
On Thursday, 1 February 2018 02:44:13 UTC, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Dear Qubes Community, > > We're pleased to announce the fourth release candidate for Qubes 4.0! > This release contains important safeguards against the [Spectre and > Meltdown attacks][qsb-37], as well as bug fixes for many of the issues > discovered in the [previous release candidate][4.0-rc3]. A full list of > the Qubes 4.0 issues closed so far is available [here][closed-issues]. > Further details about this release, including full installation > instructions, are available in the [Qubes 4.0 release > notes][release-notes]. The new installation image is available on the > [Downloads] page. > > As always, we're immensely grateful to our community of testers for > taking the time to [discover and report bugs]. Thanks to your efforts, > we're able to fix these bugs *before* the final release of Qubes 4.0. We > encourage you to continue diligently testing this fourth release > candidate so that we can work together to improve Qubes 4.0 before the > stable release. > > Major changes in Qubes 4.0-rc4 > - -- > > The Qubes VM Manager is back by popular demand! The returning Qubes > Manager will be slightly different from the 3.2 version. Specifically, > it will not duplicate functionality that is already provided by the new > 4.0 widgets. Specific examples include attaching and detaching block > devices, attaching and detaching the microphone, and VM CPU usage. > > In addition, the default TemplateVMs have been upgraded to Fedora 26 and > Debian 9. > > The Qubes 4.0 stable release > - > > If the testing of 4.0-rc4 does not reveal any major problems, we hope to > declare it the stable 4.0 release without any further significant > changes. In this scenario, any bugs discovered during the testing > process would be fixed in subsequent updates. > > If, on the other hand, a major issue is discovered, we will continue > with the standard [release schedule], and Qubes 4.0 stable will be a > separate, later release. > > Current Qubes 4.0 Users > - --- > > Current users of Qubes 4.0-rc3 can upgrade in-place by downloading the > latest updates from the testing repositories in both > [dom0][dom0-testing] and [TemplateVMs][domU-testing]. As explained in > [QSB #37][qsb-37], Qubes 4.0-rc4 uses PVH instead of HVM for almost all > VMs without PCI devices by default as a security measure against > Meltdown, and this change will also be released as a patch for existing > Qubes 4.0 installations in the coming days. Therefore, current Qubes 4.0 > users will benefit from this change whether they upgrade in-place from a > previous release candidate or perform a clean installation of 4.0-rc4. > > If you wish to upgrade in-place and have manually changed your VM > settings, please note the following: > > 1. By default, Qubes 4.0-rc3 used kernel 4.9.x. However, PVH mode will >require kernel >= 4.11. This is fine, because we will include kernel >4.14 in the PVH update. However, if you have manually changed the >kernel setting for any of your VMs, the update will not automatically >override that setting. Those VMs will still be using an old kernel, >so they will not work in PVH mode. Therefore, you must must either >change their settings to use the new kernel or change the VM mode >back to HVM. > > 2. If you have created a Windows VM, and you rely on it running in HVM >mode, you must explicitly set its mode to HVM (since the default mode >after applying the PVH update will be PVH rather than HVM). You can >do this either through the VM Settings GUI or by using the >`qvm-prefs` command-line tool to change the `virt_mode` property. > > > [qsb-37]: https://www.qubes-os.org/news/2018/01/11/qsb-37/ > [4.0-rc3]: https://www.qubes-os.org/news/2017/11/27/qubes-40-rc3/ > [closed-issues]: > https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+milestone%3A%22Release+4.0%22+is%3Aclosed > [release-notes]: https://www.qubes-os.org/doc/releases/4.0/release-notes/ > [discover and report bugs]: https://www.qubes-os.org/doc/reporting-bugs/ > [release schedule]: > https://www.qubes-os.org/doc/version-scheme/#release-schedule > [4.0-bugs]: > https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93=is%3Aopen+is%3Aissue+milestone%3A%22Release+4.0%22+label%3Abug > [dom0-testing]: > https://www.qubes-os.org/doc/software-update-dom0/#testing-repositories > [domU-testing]: > https://www.qubes-os.org/doc/software-update-vm/#testing-repositories > [Downloads]: https://www.qubes-os.org/downloads/ > > This announcement is also available on the Qubes website: > https://www.qubes-os.org/news/2018/01/31/qubes-40-rc4/ > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > >
[qubes-users] Re: Please help with custom template build
On Tuesday, 23 January 2018 17:36:00 UTC, Krišjānis Gross wrote: > Hi, > > I am trying to build a custom installation .iso. I have an issue that I have > purchased a new set of hardware that does not work with the current builds of > qubes. I am trying to build the most updated version with hope that it could > work. > > I am running a Fedora linux and trying to build with these instructions: > https://www.qubes-os.org/doc/building-archlinux-template/ > > I use the ./setup to create the installation configuration. > > make install-deps goes fine. > make get-sources goes smooth as well > > but I get an error when running the mage qubes command. > Here is what I get: > > [krish@localhost qubes-builder]$ make qubes > Currently installed dependencies: > git-2.14.3-2.fc27.x86_64 > rpmdevtools-8.10-3.fc27.noarch > rpm-build-4.14.0-2.fc27.x86_64 > createrepo-0.10.3-12.fc27.noarch > debootstrap-1.0.92-1.fc27.noarch > dpkg-dev-1.18.24-3.fc27.noarch > python2-sh-1.12.14-2.fc27.noarch > dialog-1.3-10.20170509.fc27.x86_64 > dpkg-dev-1.18.24-3.fc27.noarch > debootstrap-1.0.92-1.fc27.noarch > PyYAML-3.12-5.fc27.x86_64 > make[1]: Entering directory '/home/krish/qubes-builder' > -> Preparing fc25 build environment > -> Initializing RPM database... > -> Retreiving core RPM packages... > -> Verifying signatures... > Filename: > /home/krish/qubes-builder/cache/fc25/base_rpms/acl-2.2.52-13.fc25.x86_64.rpm > is not signed. Exiting! > make[1]: *** > [/home/krish/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:86: > /home/krish/qubes-builder/chroot-fc25/home/user/.prepared_base] Error 1 > make[1]: Leaving directory '/home/krish/qubes-builder' > make: *** [Makefile:224: vmm-xen-dom0] Error 1 > > > Does anyone has an idea of what I do wrong or how to resolve this? > I have attached the builder.conf file that I have. Tried to build on Fedora 25 but did not succeed. Did not get the same issue but there was something else that did not work. Kind of gave up trying because of Qubes 4 RC4 release. thank You to everyone for the 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/445fe880-2720-4cc2-8754-eb1013bc3f5c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Please help with 8th Generation Intel i5
On Wednesday, 17 January 2018 19:24:05 UTC, Krišjānis Gross wrote: > Hi, > > Was using Qubes 3.2 on 4th generation i5 processor when decided to upgrade my > hardware. > > Purchased 8th gen i5 processor and MB. Now when I start my Qubes only dom0 is > started. no other VM is started unfortunately. > > Here is the hardware details: >MB: ASRock Z370 Pro4 https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp >CPU: Intel® Core™ i5-8600K > https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz >RAM: 16 GB DDR4 > > > Qubes 3.2. boots but feels very slow. e.g. when I type the characters appear > with considerable delay. Mouse is not working. I can only do something with > PS2 keyboard. > > I tried to run Qubes installation but failed to do that. 3.2 did not start > the installation at all. > Qubes 4.0rc3 installation did get to some point and resulted in error. > I have attached some screen shots of 4.0 installation. > > Not sure what to do next. Read in some other topics that others had an issue > with new hardware. > > Please help to resolve this. I really really want to continue using Qubes. it > is such an awesome system! Thank You for the recommendation, awokd! I did not find the time to try that out. Will try everything again with the most recent release. And if there will be issues will post a new question thread. -- 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/be49321c-834f-4e89-bc35-672b0982a7d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Please help with custom template build
On Tuesday, 23 January 2018 17:36:00 UTC, Krišjānis Gross wrote: > Hi, > > I am trying to build a custom installation .iso. I have an issue that I have > purchased a new set of hardware that does not work with the current builds of > qubes. I am trying to build the most updated version with hope that it could > work. > > I am running a Fedora linux and trying to build with these instructions: > https://www.qubes-os.org/doc/building-archlinux-template/ > > I use the ./setup to create the installation configuration. > > make install-deps goes fine. > make get-sources goes smooth as well > > but I get an error when running the mage qubes command. > Here is what I get: > > [krish@localhost qubes-builder]$ make qubes > Currently installed dependencies: > git-2.14.3-2.fc27.x86_64 > rpmdevtools-8.10-3.fc27.noarch > rpm-build-4.14.0-2.fc27.x86_64 > createrepo-0.10.3-12.fc27.noarch > debootstrap-1.0.92-1.fc27.noarch > dpkg-dev-1.18.24-3.fc27.noarch > python2-sh-1.12.14-2.fc27.noarch > dialog-1.3-10.20170509.fc27.x86_64 > dpkg-dev-1.18.24-3.fc27.noarch > debootstrap-1.0.92-1.fc27.noarch > PyYAML-3.12-5.fc27.x86_64 > make[1]: Entering directory '/home/krish/qubes-builder' > -> Preparing fc25 build environment > -> Initializing RPM database... > -> Retreiving core RPM packages... > -> Verifying signatures... > Filename: > /home/krish/qubes-builder/cache/fc25/base_rpms/acl-2.2.52-13.fc25.x86_64.rpm > is not signed. Exiting! > make[1]: *** > [/home/krish/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:86: > /home/krish/qubes-builder/chroot-fc25/home/user/.prepared_base] Error 1 > make[1]: Leaving directory '/home/krish/qubes-builder' > make: *** [Makefile:224: vmm-xen-dom0] Error 1 > > > Does anyone has an idea of what I do wrong or how to resolve this? > I have attached the builder.conf file that I have. Like in installing Fedora 25 on the system and perform the build procedure on that? Will give it a try. Thank You for advice! -- 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/5929b0fe-f056-48a6-9678-5ddeedd82c14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Please help with custom template build
On Tuesday, 23 January 2018 19:36:00 UTC+2, Krišjānis Gross wrote: > Hi, > > I am trying to build a custom installation .iso. I have an issue that I have > purchased a new set of hardware that does not work with the current builds of > qubes. I am trying to build the most updated version with hope that it could > work. > > I am running a Fedora linux and trying to build with these instructions: > https://www.qubes-os.org/doc/building-archlinux-template/ > > I use the ./setup to create the installation configuration. > > make install-deps goes fine. > make get-sources goes smooth as well > > but I get an error when running the mage qubes command. > Here is what I get: > > [krish@localhost qubes-builder]$ make qubes > Currently installed dependencies: > git-2.14.3-2.fc27.x86_64 > rpmdevtools-8.10-3.fc27.noarch > rpm-build-4.14.0-2.fc27.x86_64 > createrepo-0.10.3-12.fc27.noarch > debootstrap-1.0.92-1.fc27.noarch > dpkg-dev-1.18.24-3.fc27.noarch > python2-sh-1.12.14-2.fc27.noarch > dialog-1.3-10.20170509.fc27.x86_64 > dpkg-dev-1.18.24-3.fc27.noarch > debootstrap-1.0.92-1.fc27.noarch > PyYAML-3.12-5.fc27.x86_64 > make[1]: Entering directory '/home/krish/qubes-builder' > -> Preparing fc25 build environment > -> Initializing RPM database... > -> Retreiving core RPM packages... > -> Verifying signatures... > Filename: > /home/krish/qubes-builder/cache/fc25/base_rpms/acl-2.2.52-13.fc25.x86_64.rpm > is not signed. Exiting! > make[1]: *** > [/home/krish/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:86: > /home/krish/qubes-builder/chroot-fc25/home/user/.prepared_base] Error 1 > make[1]: Leaving directory '/home/krish/qubes-builder' > make: *** [Makefile:224: vmm-xen-dom0] Error 1 > > > Does anyone has an idea of what I do wrong or how to resolve this? > I have attached the builder.conf file that I have. Thank You for help, awokd! > Maybe confirm you have the master signing key as trusted? Seems to be in place see below: [krish@localhost qubes-builder]$ gpg --edit-key 0x36879494 gpg (GnuPG) 1.4.22; Copyright (C) 2015 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. pub 4096R/36879494 created: 2010-04-01 expires: never usage: SC trust: ultimate validity: ultimate [ultimate] (1). Qubes Master Signing Key gpg> fpr pub 4096R/36879494 2010-04-01 Qubes Master Signing Key Primary key fingerprint: 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494 > Note the .trustdb the builder uses isn't in the default location. I think that I did the steps described in manual to copy the .trustdb: # Assuming qubes-builder is in your home directory cp .gnupg/pubring.gpg qubes-builder/keyrings/git/ cp .gnupg/trustdb.gpg qubes-builder/keyrings/git/ > Otherwise, it might just be a Fedora glitch on the mirror you hit, try > another? How can I do that? >I have also had multiple issues with this (I started out with Qubes 3.2), and >> eventually gave up. > > When I came back to Qubes 4 RC3 I found this: > https://github.com/QubesOS/qubes-issues/issues/3185 > > And the steps there worked for me. > > Hope this helps. Thank You for the advice! Seems a bit beyond my understanding and knowledge but will give it a try. -- 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/8f0e59d7-ccab-48d3-8daf-18776f6ad33b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Please help with 8th Generation Intel i5
On Wednesday, 17 January 2018 21:24:05 UTC+2, Krišjānis Gross wrote: > Hi, > > Was using Qubes 3.2 on 4th generation i5 processor when decided to upgrade my > hardware. > > Purchased 8th gen i5 processor and MB. Now when I start my Qubes only dom0 is > started. no other VM is started unfortunately. > > Here is the hardware details: >MB: ASRock Z370 Pro4 https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp >CPU: Intel® Core™ i5-8600K > https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz >RAM: 16 GB DDR4 > > > Qubes 3.2. boots but feels very slow. e.g. when I type the characters appear > with considerable delay. Mouse is not working. I can only do something with > PS2 keyboard. > > I tried to run Qubes installation but failed to do that. 3.2 did not start > the installation at all. > Qubes 4.0rc3 installation did get to some point and resulted in error. > I have attached some screen shots of 4.0 installation. > > Not sure what to do next. Read in some other topics that others had an issue > with new hardware. > > Please help to resolve this. I really really want to continue using Qubes. it > is such an awesome system! Thank You for the help, donban! I can not find a kern.log or dmesg. I did find the Xorg log files. (This is all on the Fedora that I recently installed on this same hardware). Xorg Log files attached. Here is what I have in /var/log foder: [krish@localhost ~]$ ls /var/log/ -la total 2412 drwxr-xr-x. 17 root root 4096 Jan 24 20:34 . drwxr-xr-x. 22 root root 4096 Nov 5 09:35 .. drwxrwxr-x. 2 root root 4096 Jan 19 17:43 anaconda drwx--. 2 root root 4096 Dec 14 19:23 audit drwxr-xr-x. 2 root root 4096 Sep 19 10:54 blivet-gui -rw-r--r--. 1 root root 10155 Jan 24 20:33 boot.log -rw---. 1 root utmp384 Jan 23 20:18 btmp drwxr-xr-x. 2 chrony chrony 4096 Sep 15 13:19 chrony drwxr-xr-x. 2 root root 4096 Oct 26 09:49 cluster drwxr-xr-x. 2 lp sys4096 Jan 12 13:28 cups -rw-r--r--. 1 root root1722708 Jan 24 20:43 dnf.librepo.log -rw-r--r--. 1 root root 127175 Jan 24 20:43 dnf.log -rw-r--r--. 1 root root 10304 Jan 24 20:43 dnf.rpm.log -rw-r--r--. 1 root root 0 Jan 19 17:47 dpkg.log -rw-r--r--. 1 root root544 Jan 24 20:33 firewalld drwx--x--x. 2 root gdm4096 Nov 30 16:21 gdm drwxr-xr-x. 2 root root 4096 Jan 12 17:06 glusterfs -rw---. 1 root root 1294 Jan 19 21:30 grubby -rw-r--r--. 1 root root 23421 Jan 24 20:43 hawkey.log drwx--. 2 root root 4096 Oct 25 15:35 httpd drwxr-sr-x+ 3 root systemd-journal4096 Jan 19 17:43 journal -rw-rw-r--. 1 root utmp 292292 Jan 24 20:34 lastlog drwx--. 3 root root 4096 Dec 4 19:15 libvirt drwx--. 2 root root 4096 Aug 4 14:35 ppp -rw-r--r--. 1 root root 1040 Oct 26 13:30 README drwx--. 3 root root 4096 Jan 8 17:10 samba drwx--. 2 root root 4096 Nov 8 12:25 speech-dispatcher drwxr-x---. 2 root root 4096 Dec 4 22:57 sssd -rw---. 1 root root 64064 Jan 19 17:42 tallylog -rw-r--r--. 1 root root772 Jan 19 18:39 vmware-vmusr.log -rw-rw-r--. 1 root utmp 14976 Jan 24 20:34 wtmp -rw-r--r--. 1 root gdm 17416 Jan 24 20:34 Xorg.0.log -rw-r--r--. 1 root gdm 18210 Jan 23 22:32 Xorg.0.log.old -rw-r--r--. 1 root krish 16760 Jan 24 20:34 Xorg.1.log -rw-r--r--. 1 root krish 18099 Jan 23 22:32 Xorg.1.log.old -- 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/60d24f11-2147-4e27-9e8a-be360924175b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [45.324] (--) Log file renamed from "/var/log/Xorg.pid-1147.log" to "/var/log/Xorg.0.log" [45.348] X.Org X Server 1.19.6 Release Date: 2017-12-20 [45.348] X Protocol Version 11, Revision 0 [45.348] Build Operating System: 4.14.11-300.fc27.x86_64 [45.348] Current Operating System: Linux localhost.localdomain 4.14.13-300.fc27.x86_64 #1 SMP Thu Jan 11 04:00:01 UTC 2018 x86_64 [45.348] Kernel command line: BOOT_IMAGE=/vmlinuz-4.14.13-300.fc27.x86_64 root=/dev/mapper/fedora
[qubes-users] Re: Please help with custom template build
On Tuesday, 23 January 2018 17:36:00 UTC, Krišjānis Gross wrote: > Hi, > > I am trying to build a custom installation .iso. I have an issue that I have > purchased a new set of hardware that does not work with the current builds of > qubes. I am trying to build the most updated version with hope that it could > work. > > I am running a Fedora linux and trying to build with these instructions: > https://www.qubes-os.org/doc/building-archlinux-template/ > > I use the ./setup to create the installation configuration. > > make install-deps goes fine. > make get-sources goes smooth as well > > but I get an error when running the mage qubes command. > Here is what I get: > > [krish@localhost qubes-builder]$ make qubes > Currently installed dependencies: > git-2.14.3-2.fc27.x86_64 > rpmdevtools-8.10-3.fc27.noarch > rpm-build-4.14.0-2.fc27.x86_64 > createrepo-0.10.3-12.fc27.noarch > debootstrap-1.0.92-1.fc27.noarch > dpkg-dev-1.18.24-3.fc27.noarch > python2-sh-1.12.14-2.fc27.noarch > dialog-1.3-10.20170509.fc27.x86_64 > dpkg-dev-1.18.24-3.fc27.noarch > debootstrap-1.0.92-1.fc27.noarch > PyYAML-3.12-5.fc27.x86_64 > make[1]: Entering directory '/home/krish/qubes-builder' > -> Preparing fc25 build environment > -> Initializing RPM database... > -> Retreiving core RPM packages... > -> Verifying signatures... > Filename: > /home/krish/qubes-builder/cache/fc25/base_rpms/acl-2.2.52-13.fc25.x86_64.rpm > is not signed. Exiting! > make[1]: *** > [/home/krish/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:86: > /home/krish/qubes-builder/chroot-fc25/home/user/.prepared_base] Error 1 > make[1]: Leaving directory '/home/krish/qubes-builder' > make: *** [Makefile:224: vmm-xen-dom0] Error 1 > > > Does anyone has an idea of what I do wrong or how to resolve this? > I have attached the builder.conf file that I have. > Maybe the downloaded rpm is wrong? Did you try to remove it from cache and force it to download again? Yes, I tried the whole process multiple times. - Tried cleaning the qubes-builder/cache folder. - Tried other versions of fedora and got similar error. e.g. starting with /cache/fc23 > Also, did you download the keys and mark as trusted, or did .setup do it > for you? See the first few steps here: > https://www.qubes-os.org/doc/building-archlinux-template/ > > There's a rumor rc4 may be out soon. Yes, I did that and I think that I did it correctly. Could post more details if you think this could be the root cause. looking forward for the RC4 :) -- 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/32c89429-350b-4bb3-ac77-a66fe0328f2a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Please help with custom template build
Hi, I am trying to build a custom installation .iso. I have an issue that I have purchased a new set of hardware that does not work with the current builds of qubes. I am trying to build the most updated version with hope that it could work. I am running a Fedora linux and trying to build with these instructions: https://www.qubes-os.org/doc/building-archlinux-template/ I use the ./setup to create the installation configuration. make install-deps goes fine. make get-sources goes smooth as well but I get an error when running the mage qubes command. Here is what I get: [krish@localhost qubes-builder]$ make qubes Currently installed dependencies: git-2.14.3-2.fc27.x86_64 rpmdevtools-8.10-3.fc27.noarch rpm-build-4.14.0-2.fc27.x86_64 createrepo-0.10.3-12.fc27.noarch debootstrap-1.0.92-1.fc27.noarch dpkg-dev-1.18.24-3.fc27.noarch python2-sh-1.12.14-2.fc27.noarch dialog-1.3-10.20170509.fc27.x86_64 dpkg-dev-1.18.24-3.fc27.noarch debootstrap-1.0.92-1.fc27.noarch PyYAML-3.12-5.fc27.x86_64 make[1]: Entering directory '/home/krish/qubes-builder' -> Preparing fc25 build environment -> Initializing RPM database... -> Retreiving core RPM packages... -> Verifying signatures... Filename: /home/krish/qubes-builder/cache/fc25/base_rpms/acl-2.2.52-13.fc25.x86_64.rpm is not signed. Exiting! make[1]: *** [/home/krish/qubes-builder/qubes-src/builder-fedora/Makefile.fedora:86: /home/krish/qubes-builder/chroot-fc25/home/user/.prepared_base] Error 1 make[1]: Leaving directory '/home/krish/qubes-builder' make: *** [Makefile:224: vmm-xen-dom0] Error 1 Does anyone has an idea of what I do wrong or how to resolve this? I have attached the builder.conf file that I have. -- 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/4eff29f6-8f72-48d5-9454-81ed235231c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. # = # CONFIGURATION FILE FOR QUBES-BUILDER # = # # THIS CONFIGURATION FILE IS INDENDED TO ONLY BE USED WITH THE `setup` SCRIPT. # - # # This configuration file (`templates.conf`) will be linked to by `setup` as # `builder.conf`. (ln -s example-configs/templates.conf builder.conf) # # To use the `setup` script, just run `setup` in the qubes-builder root # directory. A series of dialogs will be presented prompting various # configuration available and then all build configuration files will # automatically be generated based on the options selected. # # `setup` can be re-run again at any time to change configuration options. # Previous options selected will be retained to allow quick switching of # branches, templates to build, etc. # # Setup uses the following as markers to indicate where to place configuration # values: # [=setup section start=] - Start inserting on the next line # [=setup section end=] - Stop insert mode # # Anything between these markers will be replaced, therefore: # - do not place any user configurations within these markers, or those # configurations will be replaced next time setup is run # - do not remove or modify the markers or setup will be unable to function # # - #CONFIGURATION FILES INCLUDED WITH THIS CONFIGURATION # - # Other configuration files are also included to offer maximum flexibility. To # determine which configuration files are actually being included when using # this configuration file as a base, use the `about` target: # `make about` # # The other configuration files included (if they exist which some of them are # automatically generated by `setup`) are as follows: # - example-configs/qubes-os-r2.conf: If RELEASE == 2; Default Release 2 # configuration file # - example-configs/qubes-os-master.conf: If RELEASE == 3; Default Release 3 # configuration file # - override.conf: `setup` will also offer to include `override.conf` if one # exists. More information on `overrides` below. # - example-configs/extended-rules.conf: Contains extra targets mostly for # building templates # # - #ADDITIONAL OVERRIDES # - # Instead of directly modifying this or any other `default` configuration # file, an override.conf
[qubes-users] Re: Please help with 8th Generation Intel i5
On Wednesday, 17 January 2018 21:24:05 UTC+2, Krišjānis Gross wrote: > Hi, > > Was using Qubes 3.2 on 4th generation i5 processor when decided to upgrade my > hardware. > > Purchased 8th gen i5 processor and MB. Now when I start my Qubes only dom0 is > started. no other VM is started unfortunately. > > Here is the hardware details: >MB: ASRock Z370 Pro4 https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp >CPU: Intel® Core™ i5-8600K > https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz >RAM: 16 GB DDR4 > > > Qubes 3.2. boots but feels very slow. e.g. when I type the characters appear > with considerable delay. Mouse is not working. I can only do something with > PS2 keyboard. > > I tried to run Qubes installation but failed to do that. 3.2 did not start > the installation at all. > Qubes 4.0rc3 installation did get to some point and resulted in error. > I have attached some screen shots of 4.0 installation. > > Not sure what to do next. Read in some other topics that others had an issue > with new hardware. > > Please help to resolve this. I really really want to continue using Qubes. it > is such an awesome system! Managed to install Fedora on this hardware and here is the boot.log that I can find in /var/log Does that help to understand 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/06dbbd2d-cb50-4dbe-a6a6-23f77643d0e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. boot.log.tar.gz Description: Binary data
[qubes-users] Re: qubes 4.0, fedora-26 template, intermittent trouble opening an appvms file manager
On Monday, 22 January 2018 02:15:49 UTC, pixel fairy wrote: > qubes 4.0 rc3 fedora-26 template > > running the file manager from a menu will always start an appvm if its not > running. but it wont always run the file manager. running terminal, or any > other apps always works. running nautilus from terminal always works too. > just not the file manager. but, sometimes, the file manager will work from > the menu. I have noticed the same behavior on 3.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/b36dcbaf-3ddd-4278-821e-620a500673e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Please help with 8th Generation Intel i5
@ Foppe de Haan >Most likely due to lacking hardware support (in the kernel) for the CL >>graphics chip (even though it's little more than a rebrand of KL's). Try >>installing a more recent (ideally 4.14-based) kernel. Iow, it's sort of >>related, because the issues you Please suggest how to install Qubes with different Kernel version. I have not idea how that can be done :) >Can you get sys-usb started? If so, use qvm-copy-to-vm in dom0 to copy the >logs to a VM, then to the flash drive. Otherwise, you could boot with a >live image of some type, mount the hard drive and copy out the logs. This was a /tmp log of installation process. Not sure that dom0 as such is available during the installation. >Both seem unhappy with your video card. What's in that laptop? Please post >Debian's boot log (redact hardware serial numbers & MAC addresses), and >Qubes' xl dmesg log if you can get it. The setup is not a laptop. It is a desktop see HW details below. Will try to get the Debian's boot log. > Here is the hardware details: >MB: ASRock Z370 Pro4 https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp >CPU: Intel® Core™ i5-8600K > https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz >RAM: 16 GB DDR4 -- 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/0b0601c0-460e-4fad-b80f-5a9b989ba86c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Moving dom0 screenshots immediately to VMs
On Friday, 19 January 2018 11:32:33 UTC, Alex Dubois wrote: > On Friday, 19 January 2018 08:55:27 UTC, wordsw...@gmail.com wrote: > > I've been working on a solution for this, but unfortunately there are too > > many factors that I'm not familiar with. > > > > My goal is to to able to: > > > > 1) Take a screenshot using the dom0 hotkey > > 2) In the "Screenshot" dialogue, select a script from the "Open with:" > > option > > 3) A text entry box that prompts me for the destination VM > > 4) The screenshot is sent to the indicated VM > > > > I think this can be accomplished with > > > > .desktop application file > > zenity > > qvm-move-to-vm/qvm-copy-to-vm/qvm-open-in-vm > > > > but I'm lost in the details. > > > > Current problems > > > > - I can't get dom0 to include my .desktop application files as "Open with:" > > options in the "Screenshot" dialogue > > - I'm not sure what format the screenshot is in initially... will the > > .desktop application receive a bunch of bits? Or the path to a temporary > > file? > > - I can figure out how to pipe the screenshot if it's a file, but I don't > > know how to handle a "bunch of bits" scenario > > > > Has anyone done this already? I'm aware of qvm-screenshot-tool.sh, which > > looks great, but the code is too complicated for me to review and I just > > need basic functionality anyway. > > https://github.com/evadogstar/qvm-screenshot-tool/blob/master/qvm-screenshot-tool.sh > > This could be useful feature. Happy to help for the dev part... > > What do you think about the default behavior being to: > - screen-shot only a VM window? Is it available? > - screen-shot an area that you lasso? > > I'm suggesting these because the Qubes default should always be the safest > that can be implemented... Could be a very useful feature! Current means of taking a screen shot are very very clumsy :) -- 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/4faa1a1e-e3ff-41a7-a5fd-3bd8354f0f03%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Please help with 8th Generation Intel i5
On Thursday, 18 January 2018 20:56:10 UTC, donoban wrote: > On 01/18/2018 11:15 AM, Krišjānis Gross wrote:> I did navigate to /tmp > and looked at some logs. Unfortunately I do not know what to look for > there. Took some screen shots (attached). Does that ring any bells? > > I think the problem is: > > (EE) VESA(0): V_BIOS address 0xaa7a0 out of range > > I've searched a little but I didn't find anything useful. I hope someone > could help you on this. > > > > > A side question- how can I copy the logs in /tmp to a flash drive or > > something in order to post those here? > > > > Which Linux distribution should I try to run in order to do a reasonable > > comparison? > > > > Ideally same as dom0, fedora-24?? I would try to guess what kernel > version starts to work fine with it and compare with built-in the qubes iso. Thank You for the suggestion! Will check that out. I tried to install Debian 9 on this hardware and all went fine. Only thing that I noticed when installation was finished was that there was a notification that system is running a " software emulated graphics" and therefore CPU usage might be considerably higher. Not sure whether that is relevant though. -- 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/dcfd1e6e-a845-4ecf-ac87-d9b2e3329ce1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
