[qubes-users] Re: HCL X570 Aorus Extreme v1.1 Ryzen 5950X R4.2-rc5
Sorry about the Typos, "I turned off SMT"* which fixed some R4.1 installer issues but not all. The installer fails to finish boot. On Saturday, December 9, 2023 at 9:01:36 AM UTC-5 Richard Horan wrote: > Hi, > > I could not post to the forum.qubes-os.org becuse I am a new user, so I > am posting here. > > I could not get R4.1 to work so it forced me to install the rc5. > I tried the R4.2 latest kernel but had network errors after updating, > which is an issue on GitHub. This is install is with the default kernel. > > I had installer issues with rc5 that the reboot button on install > sometimes does not work. And once on boot I got a CPU core locked > errors. > > I turning of SMT which fixed some installer problems with R4.1 but did not > fully fix the installer that hung up polling nvme. It could not load to > the install Wizzard. > > I am unhappy that I can not install the stable version. And wish I could > > I have not been using it long. I had tried a previous release on a M6800 > but due to hardware limits I could not use the current version and the > version that worked is no longer supported. I did not use it for long at > the time. I am starting over as a new user. > > Everything seems to work for R4.2 on x570 Aorus Extreme v.1.1 with Ryzen 9 > 5950X and AMD Radeon 5700XT Graphics. I have ECC Corsair memory installed. > > --- > layout: > 'hcl' > type: > 'Desktop' > hvm: > 'yes' > iommu: > 'yes' > slat: > 'yes' > tpm: > '2.0' > remap: > 'yes' > brand: | > Gigabyte Technology Co., Ltd. > model: | > X570 AORUS XTREME > bios: | > F37f > cpu: | > AMD Ryzen 9 5950X 16-Core Processor > cpu-short: | > FIXME > chipset: | > Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex > [1022:1480] > chipset-short: | > FIXME > gpu: | > Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 > XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) > gpu-short: | > FIXME > network: | > Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] > [1d6a:d107] (rev 02) > Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) > Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) > memory: | > 32685 > scsi: | > ST2NM007D-3D Rev: SN01 > CT2000MX500SSD1 Rev: 023 > ST2000DM006-2DM1 Rev: CC26 > CT2000MX500SSD1 Rev: 023 > usb: | > 3 > certified: > 'no' > versions: > - works: > 'FIXME:yes|no|partial' > qubes: | > R4.2.0-rc4 > xen: | > 4.17.2 > kernel: | > 6.1.62-1 > remark: | > FIXME > credit: | > FIXAUTHOR > link: | > FIXLINK > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3934b7c9-54a5-41a6-8f3d-823e22cf06b8n%40googlegroups.com.
[qubes-users] HCL X570 Aorus Extreme v1.1 Ryzen 5950X R4.2-rc5
Hi, I could not post to the forum.qubes-os.org becuse I am a new user, so I am posting here. I could not get R4.1 to work so it forced me to install the rc5. I tried the R4.2 latest kernel but had network errors after updating, which is an issue on GitHub. This is install is with the default kernel. I had installer issues with rc5 that the reboot button on install sometimes does not work. And once on boot I got a CPU core locked errors. I turning of SMT which fixed some installer problems with R4.1 but did not fully fix the installer that hung up polling nvme. It could not load to the install Wizzard. I am unhappy that I can not install the stable version. And wish I could I have not been using it long. I had tried a previous release on a M6800 but due to hardware limits I could not use the current version and the version that worked is no longer supported. I did not use it for long at the time. I am starting over as a new user. Everything seems to work for R4.2 on x570 Aorus Extreme v.1.1 with Ryzen 9 5950X and AMD Radeon 5700XT Graphics. I have ECC Corsair memory installed. --- layout: 'hcl' type: 'Desktop' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: '2.0' remap: 'yes' brand: | Gigabyte Technology Co., Ltd. model: | X570 AORUS XTREME bios: | F37f cpu: | AMD Ryzen 9 5950X 16-Core Processor cpu-short: | FIXME chipset: | Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] chipset-short: | FIXME gpu: | Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:d107] (rev 02) Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) memory: | 32685 scsi: | ST2NM007D-3D Rev: SN01 CT2000MX500SSD1 Rev: 023 ST2000DM006-2DM1 Rev: CC26 CT2000MX500SSD1 Rev: 023 usb: | 3 certified: 'no' versions: - works: 'FIXME:yes|no|partial' qubes: | R4.2.0-rc4 xen: | 4.17.2 kernel: | 6.1.62-1 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e1ab7f82-73ac-478b-9484-0700ff46d457n%40googlegroups.com. Qubes-HCL-Gigabyte_Technology_Co___Ltd_-X570_AORUS_XTREME-20231209-082927.yml Description: application/yaml Qubes-HCL-Gigabyte_Technology_Co___Ltd_-X570_AORUS_XTREME-20231209-082927.cpio.gz Description: GNU Zip compressed data
Re: [qubes-users] Debian 10 and clone have no ifconfig enabled
Thank you for getting back to me so soon. The '/sbin/ifconfig' brought up the screen. But I am unsure about how to clone a machine such that its not a template as per your suggestion. As part of the same problem, the firewall rules tab claims "Firewall has been modified manually - please us qvm-firewall for any further configuration." I did in the Services tab but nothing happened. Can't find on search how to clone a machine without it being a template. Thanks. R On Friday, February 21, 2020 at 5:33:26 PM UTC, unman wrote: > > On Fri, Feb 21, 2020 at 09:17:28AM -0800, Richard Gaylord wrote: > > Been trying to get network connection on Debian template and a clone to > get > > network connection. When I attempt to ping 8.8.8.8 I get: connect: > Network > > is unreachable. Same for ip address on local net assigned by qubes. > When > > I type "ifconfig -a" the reply is: "bash: ifconfig: command not found" > > I've tried sh, to avoid bash, and get "sh: 0: Can't open ifconfig" > > > > I can't update, upgrade or install katoolin, which was my initial > objective. > > > > Can anyone please get my Debian templates to get a network connection? > > > > Thanks. > > > > You shouldnt really do this in a template. > They dont have network connection, nor should they for security. > There is a proxy installed which allows you to run standard apt > operations to install software/upgrade. > > As a general point, your problem is permissions and path: > user doesnt have \sbin in path, so you have to specify: > `/sbin/ifconfig` > or `su - ifconfig` > > 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/701bc956-fe46-43b7-85c3-9ed3f7cae5c3%40googlegroups.com.
[qubes-users] Debian 10 and clone have no ifconfig enabled
Been trying to get network connection on Debian template and a clone to get network connection. When I attempt to ping 8.8.8.8 I get: connect: Network is unreachable. Same for ip address on local net assigned by qubes. When I type "ifconfig -a" the reply is: "bash: ifconfig: command not found" I've tried sh, to avoid bash, and get "sh: 0: Can't open ifconfig" I can't update, upgrade or install katoolin, which was my initial objective. Can anyone please get my Debian templates to get a network connection? Thanks. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0afd4dc1-01b2-4b05-986b-8bf4f30ed155%40googlegroups.com.
[qubes-users]
-- 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/CACyLhiwuWXkM41kbVJc9NxjpxdTUVVGR0iveb4XQzqDxdyUxeQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: X1 Carbon again; Qubes DSDT override?
On Thursday, November 8, 2018 at 3:04:12 PM UTC-6, mark...@gmail.com wrote: > On Monday, November 5, 2018 at 7:20:17 PM UTC+2, pkra...@gmail.com wrote: > > Dan, > > Thank you for the instructions! I would like to confirm the patch still > > works against 4.14.72.1 > > > > The only problem I had with original instruction is that yum didn't want to > > install another kernel (compiled one) with identical version (one was > > already installed since I did upgrade first) - I had to increment value in > > qubes-linux-kernel/rel file and recompile again so my version named as > > 4.14.72.2. > > hi friends just update the bios and choose the linux sleep option in the > bios, the issue has been fixed Can confirm. Perform the BIOS update, and enter BIOS configuration at boot: Config -> Power -> Sleep State -> Linux I switched xen.cfg default kernel to 4.14.18-1.pvops.qubes.x86_64. Sleep now works great! Laptop even wakes to XScreenSaver when lid is opened. -- 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/9b063218-082f-483f-b9ee-dc6a0e6ece91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0
Using the instructions in the post you referenced, I was able to apply the kernel patch successfully, and it finally started responding to power button presses from sleep! But it would immediately freeze up on wake at either a black screen or at XScreenSaver password prompt. I had to remove the USB-C Thunderbolt 3 controller from the devices list of the sys-usb vm in order to prevent this freeze, and now it works very well, with the minor annoyance of it taking a few seconds to fully recover and wake the display or respond to input. -- 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/4febfd85-afec-49e8-a0cb-2cfb10f0d33d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: X1 Carbon again; Qubes DSDT override?
Success! By process of elimination, I was able to pinpoint the wakeup issue to sys-usb. With further testing, I found that removing the USB-C Thunderbolt 3 Controller from sys-usb's device list resolved the issue. Will test further to see if fiddling with Thunderbolt BIOS assist mode will help. Might a BIOS update might fix this? (The BIOS is on N23ET40W v1.15 from 2018-04-13). Is there a way to update the BIOS without a Windows 10 utility? Side notes: 1. Despite dmidecode reporting back the proper magic LENOVO and X1 Carbon magic strings, I still need to manually specify acpi_force_s3=5 into my xen.cfg, otherwise the kernel patch does not appear to work. 2. My aside about needing the LiveCD Lenovo trick was irrelevant. I can install from an install disk created with dd, so I don't know what I was doing wrong the first time. -- 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/30f2ccdf-eb0c-4cef-aa4b-5acb9cc8ae80%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0
Just installed Qubes R4.0 on my X1 Carbon Gen 6 to find this issue still persists. Has anyone in this thread had any luck? I will not that I have not yet connected the device to the internet and, thus, have not run any updates for 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/9212cff6-8066-479d-8d98-666e46f71182%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0
On Monday, April 16, 2018 at 5:14:43 PM UTC-5, fiasc...@gmail.com wrote: > Summary: Install worked reasonably well and it boots with EFI into the > installed Qubes 4.0 nicely. There are a few issues to resolve. > > 1. I have the model with a touch screen and I haven't debugged how to make it > work yet (I'll get to that and post back what worked). > > 2. Suspend/resume doesn't work and I have to do a hard reset. A few times > (not all) I had to hard reset twice to get it to reboot properly. > > 3. HCL reports no TPM, but I have a dTPM 2.0. > > It's booting with UEFI smoothly. I haven't tested the mic, camera, or ports > except USB for storage yet. I'll update once I find fixes for the above. If > anyone could point me in the right direction for the suspend freezing issue, > let me know. I tried shutting down all VMs, including service VMs after > reading this, > https://groups.google.com/d/msg/qubes-users/81t26xq4MEI/HrfDEcjeAgAJ but the > problem persisted didn't change anything. Just installed Qubes R4.0 on my X1 Carbon Gen 6 to find this issue still persists. Has anyone in this thread had any luck? I have not yet updated 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/e4522283-051c-4542-87fb-fe3cad3791b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Why is there no qubes manager in V4.0?
On Wed, Nov 1, 2017, at 08:54 AM, Desobediente wrote: > Could the Qubes 4 users ellaborate what things I should be doing on > Qubes 3 to get used to not having the Qubes Manager available all > the time?> > -- > iuri.neocities.org > > -- > 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/CAF0bz4TdnXihBjPobqc%3DQ2NB8BCZMYzASPoOHNeLGEzH-toFHA%40mail.gmail.com[1].> > For more options, visit https://groups.google.com/d/optout. I donate monthly to the Qubes OpenCollective fund. My understanding is that it is dedicated to paying for user-friendly improvements such as the ones being discussed in this thread. When there's some feature I wish were included in a Qubes release, donating to the project helps me to feel more confident that the Qubes team will be able to pay someone to write them someday. https://opencollective.com/qubes-os. Links: 1. https://groups.google.com/d/msgid/qubes-users/CAF0bz4TdnXihBjPobqc%3DQ2NB8BCZMYzASPoOHNeLGEzH-toFHA%40mail.gmail.com?utm_medium=email_source=footer -- 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/1509542346.3097689.1158036408.31810878%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Trying to build a rchlinux-template, missing dependencies python-sh?
Hi, Im trying to install an archlinux template. I'm stuck on a dependencies issue with: python-sh make qubes-vm \Currently installed dependencies: git-2.9.4-1.fc25.x86_64 rpmdevtools-8.9-1.fc25.noarch rpm-build-4.13.0.1-1.fc25.x86_64 createrepo-0.10.3-10.fc25.noarch debootstrap-1.0.87-1.fc25.noarch dpkg-dev-1.17.27-1.fc25.noarch package python-sh is not installed dialog-1.3-5.20160828.fc25.x86_64 ERROR: call 'make install-deps' to install missing dependencies Makefile:199: recipe for target 'check-depend.rpm' failed make: *** [check-depend.rpm] Error 1 [user@Development qubes-builder]$ make install-deps Redirecting to '/usr/bin/dnf install -y git rpmdevtools rpm-build createrepo debootstrap dpkg-dev python-sh dialog' (see 'man yum2dnf') Last metadata expiration check: 4:03:27 ago on Wed Aug 9 21:08:11 2017. Package git-2.9.4-1.fc25.x86_64 is already installed, skipping. Package rpmdevtools-8.9-1.fc25.noarch is already installed, skipping. Package rpm-build-4.13.0.1-1.fc25.x86_64 is already installed, skipping. Package createrepo-0.10.3-10.fc25.noarch is already installed, skipping. Package debootstrap-1.0.87-1.fc25.noarch is already installed, skipping. Package dpkg-dev-1.17.27-1.fc25.noarch is already installed, skipping. Package python2-sh-1.12.14-1.fc25.noarch is already installed, skipping. Package dialog-1.3-5.20160828.fc25.x86_64 is already installed, skipping. Dependencies resolved. Nothing to do. Sending application list and icons to dom0 Complete! [user@Development qubes-builder]$ -- 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/7c9f13d5-7eea-4d7c-96c9-203dca1bc28f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Trying to Build Archlinux Template Qubes 4.0
Ive been trying to build archlinux template with make qubes-vm. This is where I get to. xen-shared-loop-losetup.patch is missing? How do I get this file??? --- ==> Starting build()... + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ./patches.qubes/xen-shared-loop-losetup.patch patch: Can't open patch file ./patches.qubes/xen-shared-loop-losetup.patch : No such file or directory ++ echo '*** patch ./patches.qubes/xen-shared-loop-losetup.patch failed ***' *** patch ./patches.qubes/xen-shared-loop-losetup.patch failed *** ==> ERROR: A failure occurred in build(). Aborting... /home/user/qubes-builder/qubes-src/builder-archlinux/Makefile.archlinux:120: recipe for target 'dist-package' failed make[2]: *** [dist-package] Error 2 Makefile.generic:156: recipe for target 'packages' failed make[1]: *** [packages] Error 1 Makefile:209: recipe for target 'vmm-xen-vm' failed make: *** [vmm-xen-vm] Error 1 [user@Development patches.qubes]$ ls libxl-disable-forced-vkb-for-HVM.patch stubdom-lwip-fix-for-dhcp.patch stubdom-linux-0004.patch stubdom-vbd-non-dom0-backend.patch stubdom-linux-0005.patch vm-0001-hotplug-do-not-attempt-to-remove-containing-xenstore.patch stubdom-linux-0006.patch xen-disable-dom0-qemu.patch stubdom-linux-config-qubes-gui.patch xen-hotplug-external-store.patch stubdom-linux-config-stubdom-mem.patch xen-hotplug-qubesdb-update.patch stubdom-linux-fix-need-memory.patch xen-libxl-qubes-minimal-stubdom.patch stubdom-linux-libxl-silence-dm_check_start.patch xen-no-downloads.patch stubdom-linux-libxl-soname.patch xen-stubdom-qubes-gui.patch stubdom-linux-libxl-suspend.patch xen-tools-qubes-vm.patch stubdom-linux-pci-add-del.patch xenconsoled-enable-logging.patch -- 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/6264c992-abb3-41ec-974d-84eb036888c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0 qubes-templates-community
On Thursday, August 3, 2017 at 1:14:32 PM UTC+12, Richard Brown wrote: > Hello Qubes community. > > I have just installed Qubes 4.0-rc1 on my laptop. > > Im trying to install whonix. > > But when trying to enable the repo is get this error; > > Failed to synchronize cache for repo 'qubes-templates-community', disabling > Last metadata expiration check: 0:17:28 ago on Thu Aug 3 00:48:06 2017. > > > What am I doing wrong?? http://yum.qubes-os.org/r4.0/ >From the looks of it, there is no community-templates atm. So I'm guessing my solution is to wait. -- 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/061c3aaa-9b88-43ae-a68c-5dd8d2e73385%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4.0 qubes-templates-community
Hello Qubes community. I have just installed Qubes 4.0-rc1 on my laptop. Im trying to install whonix. But when trying to enable the repo is get this error; Failed to synchronize cache for repo 'qubes-templates-community', disabling Last metadata expiration check: 0:17:28 ago on Thu Aug 3 00:48:06 2017. What am I doing wrong?? -- 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/70bf467f-6fd6-423d-97f7-84929046555a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2 install problem: Encryption requested for LUKS device sda2 but no encryption key specified
Confirmed. I'm having the same 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/ba41803d-7957-47cd-a485-70274d6fbc6e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: [Issue ] Qube Fallback Installer Anaconda
Has anyone has any success with the fallback installer? -- 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/00b3c37e-2d34-414d-83a8-d119b8b72146%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Installation from USB fails
Have you read? https://www.qubes-os.org/doc/uefi-troubleshooting/ Id also recommend testing usb drive on another computer to see if it works there. -- 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/f3f0425c-0852-4476-9a11-1619dfbc4530%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] [Issue ] Qube Fallback Installer Anaconda
Hello everyone, I've been trying to install Qube R3.2 on my laptop. I have an Nvidia chip. I can boot to the fallback installer when I select the troubleshooting option. How ever I can't seam to get this installer to work. Option (5) install medium. >> Select HDD >> Use all Free Space >> LUKs I get this; Generating update storage configuration storage configuration failed: autopart failed: Encryption requested for LUKS device sda2 but no encryption key specified for this device. I have tryed every type Partition Scheme available. But always seam to get this issue. Is this a BUG? I expect it to prompt for for the keys but this doesn't happen? -- 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/9ac60963-b8eb-4159-aefc-2d3e8f1ef0a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qube Install fail. due to unsupported hardware.
I have created a USB install media using DD. (Qube V 3.2) I have tested media with other older computers and it works. The Laptop I am trying to install to is a; #Acer predator G9-593-74N1 I have a "GeForce GTX 1070" Mobile chip. i'm assuming the GFX card is the issue. I can install via the TUI for some reasion. When I select HDD option (5) It doesn't prompt me for an excription key for LUKs then posts an error saying I didnt supply a key. How to I add the correct nvida drivers to the install media? Hardware via lspci; $ lspci 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1) 00:1c.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #4 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] (rev a1) 06:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 0b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10) Xorg.log [ 136.260] (WW) Failed to open protocol names file /usr/lib64/xorg/protocol.txt [ 136.260] X.Org X Server 1.18.3 Release Date: 2016-04-04 [ 136.260] X Protocol Version 11, Revision 0 [ 136.261] Build Operating System: 4.4.9-300.fc23.x86_64 [ 136.261] Current Operating System: Linux localhost 4.4.14-11.pvops.qubes.x86_64 #1 SMP Tue Jul 19 01:14:58 UTC 2016 x86_64 [ 136.261] Kernel command line: inst.stage2=hd:LABEL=Qubes-R3.2-x86_64 i915.preliminary_hw_support=1 quiet rhgb rd.live.check [ 136.261] Build Date: 30 June 2016 11:04:38PM [ 136.261] Build ID: xorg-x11-server 1.18.3-3.fc23 [ 136.261] Current version of pixman: 0.34.0 [ 136.261]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 136.261] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 136.261] (++) Log file: "/tmp/X.log", Time: Sat May 27 06:20:01 2017 [ 136.262] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 136.262] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 136.286] (==) No Layout section. Using the first Screen section. [ 136.286] (==) No screen section available. Using defaults. [ 136.286] (**) |-->Screen "Default Screen Section" (0) [ 136.286] (**) | |-->Monitor "" [ 136.292] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 136.292] (==) Automatically adding devices [ 136.292] (==) Automatically enabling devices [ 136.292] (==) Automatically adding GPU devices [ 136.292] (==) Max clients allowed: 256, resource mask: 0x1f [ 136.292] (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins [ 136.292] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 136.292] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 136.292] (II) Loader magic: 0x81ce00 [ 136.292] (II) Module ABI versions: [ 136.292]X.Org ANSI C Emulation: 0.4 [ 136.292]X.Org Video Driver: 20.0 [ 136.292]X.Org XInput driver : 22.1 [ 136.292]X.Org Server Extension : 9.0 [ 136.292] (++) using VT number 6 [ 136.292] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 136.396] (--) PCI:*(0:1:0:0) 10de:1be1:1025:1131 rev 161, Mem @ 0x6400/16777216, 0x5000/268435456, 0x6000/33554432, I/O @ 0x5000/128, BIOS @ 0x/524288 [ 136.396] (II) LoadModule: "glx" [ 136.397] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 136.426] (II) Module glx: vendor="X.Org Foundation" [ 136.426]compiled for 1.18.3, module version = 1.0.0 [ 136.426]ABI
[qubes-users] HCL - Samsung 940X3G hcl report text
--- layout: 'hcl' type: 'laptop' hvm: 'yes' iommu: 'no' slat: 'yes' tpm: 'unknown' brand: | SAMSUNG ELECTRONICS CO., LTD. model: | 940X3G/930X3G bios: | P05ACJ.128.140819.dg cpu: | Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz cpu-short: | FIXME chipset: | Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 09) chipset-short: | FIXME gpu: | Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation Wireless 7260 (rev 6b) Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) memory: | 8106 scsi: | TOSHIBA THNSNH25 Rev: N103 versions: - works: 'FIXME:yes|no|partial' qubes: | R3.2 xen: | 4.6.4 kernel: | 4.4.38-11 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK --- -- 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/e708c1aab493513c681b894601f02da9%40etstv.com. For more options, visit https://groups.google.com/d/optout. --- layout: 'hcl' type: 'laptop' hvm: 'yes' iommu: 'no' slat: 'yes' tpm: 'unknown' brand: | SAMSUNG ELECTRONICS CO., LTD. model: | 940X3G/930X3G bios: | P05ACJ.128.140819.dg cpu: | Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz cpu-short: | FIXME chipset: | Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 09) chipset-short: | FIXME gpu: | Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation Wireless 7260 (rev 6b) Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) memory: | 8106 scsi: | TOSHIBA THNSNH25 Rev: N103 versions: - works: 'FIXME:yes|no|partial' qubes: | R3.2 xen: | 4.6.4 kernel: | 4.4.38-11 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK ---
[qubes-users] HCL - Samsung 940X3G hcl report
--- layout: 'hcl' type: 'laptop' hvm: 'yes' iommu: 'no' slat: 'yes' tpm: 'unknown' brand: | SAMSUNG ELECTRONICS CO., LTD. model: | 940X3G/930X3G bios: | P05ACJ.128.140819.dg cpu: | Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz cpu-short: | FIXME chipset: | Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 09) chipset-short: | FIXME gpu: | Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation Wireless 7260 (rev 6b) Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) memory: | 8106 scsi: | TOSHIBA THNSNH25 Rev: N103 versions: - works: 'FIXME:yes|no|partial' qubes: | R3.2 xen: | 4.6.4 kernel: | 4.4.38-11 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK --- -- 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/3fdd4aa2b78e7601e820f96c604d4205%40etstv.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Samsung 940X3G
-- 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/73debf7e591a4779a772706a4c3a4e08%40etstv.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Time sync failed
My clock is not syncing and I can't figure out what the issue is. Any assistance would be greatly appreciated. I'm running Qubes 3.2 (R3.2) >From Dom0: $ qubes-pref clockvm : sys-net default-fw-netvm : sys-net default-kernel: 4.4.38-11 default-netvm : sys-firewall $ qvm-sync-clock --verbose --> Waiting for network for ClockVM. Time sync failed! - Exiting $ timedatectl status Failed to query server: Input/output error -- 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/829349fd-08ea-488c-b7f8-3a77ba6de98d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Dell Precision M6800
Hi, I am new to Qubes and have only used Linux on virtual machines before now. It is the first time I installed Linux directly. I installed Qubes 3.2 on a Dell Precision M6800 which worked with a few problems. First of all I installed Anti-Evil-Maid as I have a TPM and it caused the boot configuration file to become corrupt. I changed a grub file to fix grub and it worked fine after that. I included the fixed file as an attachment. I did multiple installs before I found the problem's solution. I ran the Grub configuration command as listed in the online documentation for multiboot sudo grub2-mkconfig -o /etc/grub.d/19_Linux_xen_tboot after fixing the file. As it changed multiboot to module which I switched back for the xen boot. And added back in --nounzip to the last module loader which anti-evil-maid removed. This only affected the AEM grub entry and it still worked with the regular boot entry even with AEM installed, but not with the AEM boot entry. Next the WiFi did not work. I downloaded and compiled the drivers for BCM4352 from broadcom.com website using a wired connection. I noticed that the kernel-devel files for Fedora don't match the version in the fedora-23 machine when upgraded to 4.4.14-38-11 as only 4.4.14-36-11 devel tools are available, but 4.4.14-11 version is still available for a downgraded kernel to build the files. I followed a post in a Qubes user group post to do the following before building the files su cp -a /lib/modules /rw/modules mount -B -rw /rw/modules /lib/modules systemctl restart systemd-udevd Notice that mount -bind with no -rw as in the user group post does not work. -rw is needed. I then created a /rw/config/rc.local file as attached to remount and remove bcma b43 and load the broadcom driver each start-up. I also built and installed the broadcom wl driver in dom0, but don't know if that is required for it to work. I also attached that file. It is basically. sudo mount -B -rw /rw/modules /lib/modules sudo rmmod b43 sudo rmmod bcma sudo modprobe wl I needed to restart the machine to get the driver working. Restarting the VM was not enough as dmesg reported kernel tait due to proprietary driver which locked the driver. I don't know how to get the Bluetooth to work. It simply does not work. I only got the wireless working. And the wired connection works with no added work. I can't build the NVIDIA drivers as the kernel-devel files that match dom0 are not available in the Fedora template, but as the duel graphics include Intel graphics I am relying on the Intel graphics for now. I'm unsure of the corresponding yumdonloader commands to use in dom0 in the documentation so I have not tired to build it in dom0. There are problems with Suspend and Hibernate and Log Out. If I log out and back in the Qubes VM Manager stops and wont start via the GUI. The check box for save session seams to have no function. Suspend saves the session to the hard drive, but when it wakes there is only a white screen and it takes over 15 minutes to recover. I it is quicker to shut down and restart the computer. Hibernate saves the session to memory and works. The screen saver works. When the laptop cover is closed it Suspends to disk with the over 15 minute delay. The Suspend and Hibernate functions are the reverse of what they should be. The laptop has rpm driver files on the Dell website under Red Hat, but they won't install. This includes the provided NVIDIA driver for Red Hat. I have all the regular VMs plus all the experimental features installed. That includes the TOR and USB VM. They seem to be working. I had no problems with USB VM so far, but restarting the TOR networking VM has had problems until restarting the machine. There were a few times it complained of a already used MAC address after restarting. Still it is still early, and I have not used it much. I'm still have not tried all the features, and besides from the above I upgraded the Fedora and Debian VMs. I am still working on configuring my machine. I have not yet installed other features such as installing Windows 7 or other templates. I hope support for Windows 10 happens soon. Richard -- 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/1603a161-a6b3-2b0d-ae91-d06b2314e387%40gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Precision_M6800-20170223-205729.yml Description: application/yaml #! /bin/sh set -e # grub-mkconfig helper script. # Copyright (C) 2006,2007,2008,2009,2010 Free Software Foundation, Inc. # # GRUB is free softwar
Re: [qubes-users] Re: Issues after in-place 3.1.17 -> 3.2 upgrade
On Sunday, November 6, 2016 at 2:07:38 PM UTC-6, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Sun, Nov 06, 2016 at 11:44:25AM -0800, Richard wrote: > > However, I noticed that the Qubes VM Manager is not reflecting the changes > > (i.e. it is still showing VMs running), even after I close and reopen it. > > This is expected (until system restart). Also, just closing the manager > window isn't enough to really restart it - if you want to, right click > on its icon and choose "exit". Then start it again from the menu. > > > I was going to use the 'shutdown now' command, but wanted to check if there > > is anything I should be doing, before I shutdown, to fix the above errors. > > Just restarting the system should be enough. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJYH42JAAoJENuP0xzK19csLdIIAIAIwf1z3m8Jj1eim8obJCUj > QHC2UrgNTqvl0rFwx0JzsfGvh33ft/SPZoVPwhO8Y9Tp0rhgvjRZVpsN1zF8NQZi > 6J2zQg8nnT7AQLrF0WntDO/N8zb8C8lVLkpbr5NHSVveSyDmB1BqrGyLVW7K46py > TMBuhdfT0aEjNuUNBC1uCVknU7uOgIGce9KnWqDp59UmyKecIUhEyPvIZC3QoXmE > BrXuceoRUTj1REoa1FG1GTTlnZms9OL0zOl90wT3fbWcmyKBlCuQLolKKoUuTQIE > UgmnZCYSPMAM7l5fFJMcYpXW30y0O5KMIFGG1/ScRlFaCXAKJIjXF8/lar6QCwU= > =joII > -END PGP SIGNATURE- Thank you Marek -- 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/38d46f47-3329-404d-a213-24fc19f07c6f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Issues after in-place 3.1.17 -> 3.2 upgrade
On Sunday, November 6, 2016 at 11:24:55 AM UTC-6, Richard wrote:
> I just finished doing an in-place upgrade to 3.2 following
> https://www.qubes-os.org/doc/upgrade-to-r3.2/
>
> However, I ran into a problem when I reached step "6. Update configuration
> files."
>
> The system will not allow me to open Konsole (I can open run command, choose
> Konsole and nothing happens).
>
> Also, now whenever I open Qubes VM Manager I receive the following message:
>
> libvirtError: internal error: client socket is closed
>
> line: if ret == -1: raise libvirtError ('virDomainlsActive() failed',
> dom=self)
> func: isActive
> line no.: 1338
> file: /usr/lib64/python2.7/site-packages/libvirt.py
> ---
> line: if libvirt_domain.isActive()
> func: get_power_state
> line no.: 876
> file: /usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py
>
> and soforth.
>
> The only VMs that are running are sys-firewall and sys-net. I've tried to
> shut down the firewall from the Qubes VM Manager and receive the following
> message:
>
> AssertionError:
> line: assert vm.is_running()
> func: action_shutdownvm_triggered
> line no: 1261
> file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
>
> I've tried to restart and shutdown my system and that is also not
> possible...nothing happens when I click on shutdown or restart.
>
> I should be grateful if anyone can provide me the steps I need to do to
> continue upgrading my system.
>
> Thanks,
> Richard
Update:
I was able to open Konsole and complete step 6
I also used 'qvm-shutdown -all' to shutdown all VMs.
However, I noticed that the Qubes VM Manager is not reflecting the changes
(i.e. it is still showing VMs running), even after I close and reopen it.
I was going to use the 'shutdown now' command, but wanted to check if there is
anything I should be doing, before I shutdown, to fix the above errors.
Thanks.
--
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/7436df3b-5662-43cd-baf1-dc901a8b0916%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Issues after in-place 3.1.17 -> 3.2 upgrade
I just finished doing an in-place upgrade to 3.2 following
https://www.qubes-os.org/doc/upgrade-to-r3.2/
However, I ran into a problem when I reached step "6. Update configuration
files."
The system will not allow me to open Konsole (I can open run command, choose
Konsole and nothing happens).
Also, now whenever I open Qubes VM Manager I receive the following message:
libvirtError: internal error: client socket is closed
line: if ret == -1: raise libvirtError ('virDomainlsActive() failed', dom=self)
func: isActive
line no.: 1338
file: /usr/lib64/python2.7/site-packages/libvirt.py
---
line: if libvirt_domain.isActive()
func: get_power_state
line no.: 876
file: /usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py
and soforth.
The only VMs that are running are sys-firewall and sys-net. I've tried to shut
down the firewall from the Qubes VM Manager and receive the following message:
AssertionError:
line: assert vm.is_running()
func: action_shutdownvm_triggered
line no: 1261
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
I've tried to restart and shutdown my system and that is also not
possible...nothing happens when I click on shutdown or restart.
I should be grateful if anyone can provide me the steps I need to do to
continue upgrading my system.
Thanks,
Richard
--
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/67b95906-a85d-4df9-ba39-20e9ef1e2efa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Trying to do an in-place upgrade from 3.1.17 to 3.2
On Sunday, October 30, 2016 at 12:00:08 PM UTC-5, Richard wrote: > I'm trying to upgrade my Qubes 3.1.17 to 3.2 I've followed the steps > outlined here: https://www.qubes-os.org/doc/upgrade-to-r3.2/ However, when I > run... > >sudo qubes-dom0-update --releasever=3.2 qubes-release > > I receive: > Loaded plugins: yum-qubes-hooks > Nothing to do > No packages downloaded > file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] > curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml" > Trying other mirror. > Nothing to do > > So of course running... sudo qubes-dom0-update --clean also provides a > similar error: > > Errno 14] curl#7 - "Failed to connect to pubmirror1.math.uh.edu port > 443: No route to host" > Trying other mirror. > No new updates available > No updates avaliable > > Is anybody able to advise me what I need to do to be able to do an in-place > upgrade to 3.2? > > Thanks, > Richard Just wondering if anyone has any ideas as I would really like to do an in-place upgrade to 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/4599dae8-a2a4-460a-a09d-9a9b0ec1a132%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Trying to do an in-place upgrade from 3.1.17 to 3.2
I'm trying to upgrade my Qubes 3.1.17 to 3.2 I've followed the steps outlined here: https://www.qubes-os.org/doc/upgrade-to-r3.2/ However, when I run... sudo qubes-dom0-update --releasever=3.2 qubes-release I receive: Loaded plugins: yum-qubes-hooks Nothing to do No packages downloaded file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml" Trying other mirror. Nothing to do So of course running... sudo qubes-dom0-update --clean also provides a similar error: Errno 14] curl#7 - "Failed to connect to pubmirror1.math.uh.edu port 443: No route to host" Trying other mirror. No new updates available No updates avaliable Is anybody able to advise me what I need to do to be able to do an in-place upgrade to 3.2? Thanks, Richard -- 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/c55fe766-d790-4f25-b54f-fa85a23f479f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [user@dom0 ~]$ sudo qubes-dom0-update --releasever=3.2 qubes-release There is no selected ClockVM, aborting. Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Running command on VM: 'sys-firewall'... (Note: dnf will complain that the yum command has been deprecated. This message is safe to ignore.) Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. Loaded plugins: yum-qubes-hooks Nothing to do No packages downloaded file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml" Trying other mirror. Nothing to do [user@dom0 ~]$ sudo qubes-dom0-update --clean There is no selected ClockVM, aborting. Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Running command on VM: 'sys-firewall'... (Note: dnf will complain that the yum command has been deprecated. This message is safe to ignore.) Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. Loaded plugins: yum-qubes-hooks Cleaning repos: fedora qubes-dom0-current qubes-templates-itl updates Cleaning up everything Checking for dom0 updates... Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. https://pubmirror1.math.uh.edu/fedora-buffet/archive/fedora/linux/releases/20/Everything/x86_64/os/repodata/0054652738782478eff37604abc430cdf327795d157634e1dfcca0fa18d8fedf-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to pubmirror1.math.uh.edu port 443: No route to host" Trying other mirror. No new updates available No updates avaliable [user@dom0 ~]$ yum info qubes-core-dom0 Installed Packages Name: qubes-core-dom0 Arch: x86_64 Version : 3.1.17 Release : 1.fc20 Size: 1.6 M Repo: installed >From repo : qubes-dom0-cached Summary : The Qubes core files (Dom0-side) URL : http://www.qubes-os.org License : GPL Description : The Qubes core files for installation on Dom0. [user@dom0 ~]$ ^C [user@dom0 ~]$
Re: [qubes-users] Remnder: Ubuntu-template anyone?
> Ah, ok. I submitted a PR and then we got bogged down with handling of > the Trolltech.conf. I havent returned to it since. > > I'll have another look and we'll get the xenial build in there That's fantastic. Thanks very much! Best regards, Richard -- 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/2260acec-9151-4092-be85-b648823c57a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Remnder: Ubuntu-template anyone?
> > > > Last night I built Xenial - I'll put in a PR today, > > Has this happened? I'd like to build a 16.04 template, but the Qubes Builder > in the offical QubesOS repository does not offer Xenial - neither does the > one in Mareks repository... I'd also be very interested in this. I have created a Vivid template and upgraded that to Wily successfully (Wily is already out of support, however), but had no luck with upgrading from Wily to Xenial. The upgrades does work and the VM boots successfully, but the Xorg install is broken so the Qubes GUI integration does not work - it complains about the ABI major version not matching. Any advice would be greatly appreciated. Best regards, Richard -- 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/5df82ce7-0041-47a9-8caa-182976b359e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R3.2 rc2 blank screen - screenlock issue?
Happened again overnight - kill -HUP xsettingsd got it useable again. -- 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/e471416e-84b1-420f-8b84-15ff6fc5c48c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R3.2 rc2 blank screen - screenlock issue?
Hi Doug That might be the clue. I waited until it happened again, did Ctrl-F2 and then restarted then xfsettingsd process with a kill -HUP. Ctrl-F1 then got me back to the login for the X without having to reboot or restart VMs. I've only tried this once ... if it's repeatable over the next few days it is at least a workaround until it's fixed in Xfce. -- Richard On Sunday, 28 August 2016 23:42:11 UTC+1, Doug Hill wrote: > > Hi, I'm having a similar issue, which I believe may be caused by a bug > in xfce. I posted about it here in a previous thread: > > https://groups.google.com/d/msg/qubes-users/qwMzj2au6uE/qd_hU6EUBQAJ > > Best of 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/45422632-e56c-43db-9588-b92381d9f1ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: R3.2 rc2 blank screen - screenlock issue?
@ Desobediente Yes I know it's seems trivial but I'm rolling it out to relatively inexperienced users and it never happened on any of my machines running R2, R3.0 or R3.1 (all on KDE). -- Richard -- 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/a466ed5d-2aa1-44d0-a6b6-4cae8c2accd5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] R3.2 rc2 blank screen - screenlock issue?
Problem description: After using the system all day (including unlocking and unlocking the screen just fine) and then leaving it overnight I come back to a blank screen. Doing a Ctrl-Alt-F2 gives me a command prompt but I can't get X to respond (with Ctrl-Alt-F1). After a reboot all is well until after some apparently random period it happens again. I've gone through the screen locker and power management settings in Xfce (turned power management off) and turned of power management in BIOS. No joy. System spec: Qubes RC2 rc2 running Xfce on Intel NUC5i5YRH with 16G ssd. Kde is also installed but I'm not using it. Has anyone got a solution? -- Richard -- 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/428b4251-0260-4ce4-81da-0c98ba71f636%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Building Archlinux Template Error
On Wednesday, August 24, 2016 at 3:15:09 PM UTC+1, Foppe de Haan wrote: > On Wednesday, August 24, 2016 at 4:14:12 PM UTC+2, Foppe de Haan wrote: > > On Thursday, August 18, 2016 at 6:40:42 PM UTC+2, Jovan Miloskovski wrote: > > > Hi, > > > I'm really learning all of this template building stuff right now but > > > I've stumbled upon an error in the Archlinux qubes template building > > > process I can't find a solution for. > > > Here is the segment of the error in my terminal output: > > > > > > -> Building vmm-xen (archlinux) for archlinux vm (logfile: > > > build-logs/vmm-xen-vm-archlinux.log) > > > --> build failed! > > > gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe > > > -fstack-protector-strong -O2 -fomit-frame-pointer -m64 > > > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes > > > -Wdeclaration-after-statement -Wno-unused-but-set-variable > > > -Wno-unused-local-typedefs -O2 -fomit-frame-pointer -m64 > > > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes > > > -Wdeclaration-after-statement -Wno-unused-but-set-variable > > > -Wno-unused-local-typedefs -D__XEN_TOOLS__ -MMD -MF .subdirs-install.d > > > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O2 -fomit-frame-pointer -m64 > > > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes > > > -Wdeclaration-after-statement -Wno-unused-but-set-variable > > > -Wno-unused-local-typedefs -D__XEN_TOOLS__ -MMD -MF > > > .subdir-install-libxl.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O2 > > > -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > > > -Wstrict-prototypes -Wdeclaration-after-statement > > > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > > > -MMD -MF .libxl_create.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > > > -Werror -Wno-format-zero-length -Wmissing-declarations > > > -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/xenstore/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > > >-Wshadow -include > > > /home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/config.h > > > -c -o libxl_create.o libxl_create.c > > > gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe > > > -fstack-protector-strong -O2 -fomit-frame-pointer -m64 > > > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes > > > -Wdeclaration-after-statement -Wno-unused-but-set-variable > > > -Wno-unused-local-typedefs -O2 -fomit-frame-pointer -m64 > > > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes > > > -Wdeclaration-after-statement -Wno-unused-but-set-variable > > > -Wno-unused-local-typedefs -D__XEN_TOOLS__ -MMD -MF .subdirs-install.d > > > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O2 -fomit-frame-pointer -m64 > > > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes > > > -Wdeclaration-after-statement -Wno-unused-but-set-variable > > > -Wno-unused-local-typedefs -D__XEN_TOOLS__ -MMD -MF > > > .subdir-install-libxl.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O2 > > > -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > > > -Wstrict-prototypes -Wdeclaration-after-statement > > > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > > > -MMD -MF .libxl_dm.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > > > -Werror -Wno-format-zero-length -Wmissing-declarations > > > -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/xenstore/include > > > > > > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > > >-Wshadow -include > > > /home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/config.h > > > -c -o libxl_dm.o libxl_dm.c > > > gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe > > > -fstack-protector-strong -O2 -fomit-frame-pointer -m64 > > > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes > > > -Wdeclaration-after-statement -Wno-unused-but-set-variable > > > -Wno-unused-local-typedefs -O2
[qubes-users] Re: Building Archlinux Template Error
On Thursday, August 18, 2016 at 5:40:42 PM UTC+1, Jovan Miloskovski wrote: > Hi, > I'm really learning all of this template building stuff right now but I've > stumbled upon an error in the Archlinux qubes template building process I > can't find a solution for. > Here is the segment of the error in my terminal output: > > -> Building vmm-xen (archlinux) for archlinux vm (logfile: > build-logs/vmm-xen-vm-archlinux.log) > --> build failed! > gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe > -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing > -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2 > -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O2 > -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > -MMD -MF .subdir-install-libxl.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > -MMD -MF .libxl_create.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -Werror -Wno-format-zero-length -Wmissing-declarations > -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/xenstore/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > -Wshadow -include > /home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/config.h > -c -o libxl_create.o libxl_create.c > gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe > -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing > -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2 > -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O2 > -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > -MMD -MF .subdir-install-libxl.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > -MMD -MF .libxl_dm.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Werror > -Wno-format-zero-length -Wmissing-declarations > -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/xenstore/include > -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include > -Wshadow -include > /home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/config.h > -c -o libxl_dm.o libxl_dm.c > gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe > -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing > -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2 > -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O2 > -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall > -Wstrict-prototypes -Wdeclaration-after-statement > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ > -MMD -MF .subdir-install-libxl.d
