Re: [qubes-users] coreboot on modern hardware?
Hello, schrieb am Mo., 25. März 2019, 02:15: > That was one of the first places I looked. Maybe I’m just a hardhead, but > I found it difficult to believe that there really was no support for > coreboot in any form for modern hardware. > The problem seems to be that on modern hardware it is not possible to run unsigned Firmware because of a feature on newer hardware called "boot guard" https://www.phoronix.com/scan.php?page=news_item&px=Intel-Boot-Guard-Kills-Coreboot What Intel is saying about this "feature": https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/security-technologies-4th-gen-core-retail-paper.pdf - O -- 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/CAJ3yz2sM6cnCR6stTiwj%3DNfn_cug0gvtqiFVKSdtO64h%3DE%2BZvw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4 install not seeing VT-d/VT-x
On 2019-03-24 19:09, 'awokd' via qubes-users wrote: > Gaijin wrote on 3/23/19 3:32 AM: >> While attempting to upgrade from R3.2 to R4.0.1 I get the error: >> Missing features: IOMMU/VT-d/AMD-Vi, Interrupt Remapping >> >> I have an ASRock H67DE motherboard with an Intel i7-2600 CPU which >> according to the specs supports both VT-d and VT-x, and I have both >> specifically enabled in the BIOS. However, the Qubes 4 installer >> apparently can't see them. (I wonder if this is because I can only boot >> the installation USB in Legacy mode and not AHCI mode) >> >> I'm wondering if it would be OK to proceed with the install despite this >> warning. Is there a way to check whether these BIOS settings are visible >> to Qubes, or is this warning a clear indicator that they're not? (I >> still have R3.2 working) >> > In R3.2's dom0 run qubes-hcl-report. Look for the 5 lines at the > bottom. You can proceed with the install, but if you don't really have > support it will fail when trying to set up sys-net after the initial > post-install reboot. I guess you mean the first five items instead of the last. I posted my HCL here: https://groups.google.com/forum/#!topic/qubes-users/URIPsM1VURU Looks like I do not have IOMMU or remapping available to Qubes. I wouldn't get far without sys-net. According to Intel my CPU does support VT-d and VT-x, might there be some way to try to force Qubes? I've been using this machine since R1, and would love to keep using it if possible. -- 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/588637a47165c699e89ce6e0857f6a74%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Booting Qubes 4.0 installation ISO fails with kernel panic
Hi, I'd appreciate it if someone can help me debug an issue with the qubes installer. I am not able to enable legacy booting on my bios, so I am only booting the installation ISO using UEFI. My hardware is https://www.gigabyte.com/Mini-PcBarebone/GB-BLCE-4105-rev-10#sp, and it is running F1 version of the firmware. When I boot from the ISO I see the following: -- APIC boot state is 'xapic' ACPI: 32/64X FACS address mismatch in FADT - 79807080/, using 32 IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-119 Enabling APIC mode: Flat. Using 1 I/O APICs mapped APIC to 82cfb000 (fee0) mapped IOAPIC to 82cfa000 (fec0) Switched to APIC driver x2apic_cluster xstate: size: 0x440 and states: 0x1b Using scheduler: SMP Credit Scheduler (credit) Platform timer is 19.200MHz HPET Detected 1497.650 MHz processor. Initing memory sharing. CPU0: Noirq handler for vector 7c (IRQ -2147483648, LAPIC) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB Intel VT-d Snoop Control not enabled. Intel VT-d Dom0 DMA Passthrough not enabled. Intel VT-d Queued Invalidation enabled. Intel VT-d Interrupt Remapping enabled. Intel VT-d Posted Interrupt not enabled. Intel VT-d Shared EPT tables enabled. I/O virtualisation enabled - Dom0 mode: Relaxed Interrupt remapping enabled Getting VERSION: 1060014 Getting VERSION: 1060014 Enabled directed EOI with ioapic_ack_old on! Getting ID: 0 Getting LVT0: 700 Getting LVT1: 400 Suppress EOI broadcast on CPU#0 enabled ExtINT on CPU#0 ENABLING IO_APIC IRQs -> Using old ACK method ..MP-BIOS bug: 8254 timer not connected to IO-APIC CPU0: No irq handler for vector e7 (IRQ -8) IRQ7 a=0001[0001,] v=60[] t=IO-APIC-edge s=0002 failed :(. Panic on CPU 0: IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and send a report. Then try booting with the 'noapic' option When I add the `noapic` option to the options=... portion of BOOTX64.cfg (under [qubes-verbose] heading), and also add the `noapic` option to the kernel command line, I see the following: -- APIC boot state is 'xapic' ACPI: 32/64X FACS address mismatch in FADT - 79807080/, using 32 Found and enabled local APIC! mapped APIC to 82cfb000 (fee0) Switched to APIC driver x2apic_cluster. -- Following this line is a crash dump of the CPU registers and Xen stack trace. Additionally, it prints the Xen call trace: init_bsp_APIC, init_IRQ, __start_xen and the panic message is Panic on CPU 0: GENERAL PROTECTION FAULT [error_code=] I ommitted the stack trace and register contents since I'm manually transcribing the logs from my monitor onto another computer. I also tried booting with the "noexitboot=1" and "mapbs=1" lines commented, which didn't help. Finally, I tried various combinations of adding more xen options to the "options=..." line: - nolapic=true - nosmp=true - x2apic=false - apci=false Booting with all of those options together didn't help, but I only tried a couple random combinations of booting with less than all of them together. Does anyone have any suggestions? At some point I might try updating the motherboard firmware, but I'm not sure if that would help with this kind of issue... The one benefit of updating the firmware is that it may allow me to boot in legacy mode, which could possibly yield a different result? I'm not sure if the boot mode has anything to do with this APIC stuff... Thank you -- 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/vU8m1AwJPKyP-wL2mWDgK2iHSsPpfw_8yfhtvtdG1S7yzMjDYO1R5AfgoTmzo9IesI1WRNQ-YwxrBPRROc--2MeaYktXdJQ0GkBMbYd8WUQ%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Announcement: Qubes Tor onion services will no longer be maintained
This is seriously bad news. If you and Whonix are that resource strapped, it does not bode well for the future of either team. I have done my part and contributed what I could to both. -- 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/0dc40ab1-30fe-4a43-8c2f-4c6d111bd4e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Fedora-29 Template (Qubes 4.0.1) keeps asking to upgrade
On Tuesday, March 19, 2019 at 5:18:30 PM UTC, Claudio Chinicz wrote: > Hi All, > > I've already upgrade a few times through the GUI and command line but > still shows in the GUI as if required. > > Has anyone experienced this? Any insights how tpo get rid of the GUI > update reminder? > > Thanks, > > Claudio Chinicz I've had the same thing happen, but it only happened in the last day on Fedora 29 and debian-9-minimal. Like I said, this didn't occur at all until just the last couple of days. -- 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/01675aeb-86c9-456f-9632-f2c192cf23db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] coreboot on modern hardware?
That was one of the first places I looked. Maybe I’m just a hardhead, but I found it difficult to believe that there really was no support for coreboot in any form for modern hardware. -- 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/3a38bc37-68b3-4a8e-b3a0-932742ced5d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Announcement: Qubes Tor onion services will no longer be maintained
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 24/03/2019 7.54 PM, haaber wrote: >> Dear Qubes Community, >> >> We regret to announce that the Qubes Tor onion services will no >> longer be maintained due to lack of resources. This includes all >> Qubes onion services, including the Qubes website onion mirror >> and the onion package repos. >> >> We would like to thank the Whonix Project for generously >> maintaining these services for over a year. [1] Maintaining the >> Tor onion services requires labor, servers, and bandwidth. >> Unfortunately, none of these resources are available to the Qubes >> OS or Whonix projects in sufficient quantities to allow us to >> continue offering these services. >> >> We recommend that users who currently rely on any Qubes onion >> addresses transition to the corresponding clearnet addresses >> immediately. >> > Maybe you could have added two lines how to do this. Is is correct > / sufficient for this transition to choose sys-firewall as > UpdateVM in qubesManager->GlobalSettings ? > It is not necessary to switch from sys-whonix to sys-firewall. Whonix VMs will still continue to work as before. This announcement just means that you should switch from any Qubes Tor onion service domains (ending in ".onion") that you may have been relying on (e.g., for package repos or the Qubes website) to instead use the corresponding clearnet domain (usually qubes-os.org). Note that you can still use Tor with clearnet domains. If you were not using any Qubes Tor onion services, then this announcement does not affect you. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlyYKt8ACgkQ203TvDlQ MDCg1A//VYXaL6NyHnaO8gQCwI2emTi17D2y8ZKXvBUQg4djJAF3WxI6lG6tF1zn sUgBP9Qx40KI68IjikAgmk3nACpCpA+95d+UjP7Nss5Q1PuZtLrHvupys786EMmC AzE3ttwiOz6rf2ljjxLY4+a6YHoi2euHx1wuf0/un62znO/F5Pl67YmAkiarIuiP p6QA5Yhj9Yhg8tTrU+pkFKZUH8eNCSt5GRMdcOZ9oHDlXZHDhnAIYqvhHIZRA98y Ird9c8fWoxHrA70PhGzROhLEc03zN03xT62XYEULDnbRzlkHlMJe7wE0lsfZwrmh whWbWZLoJMU2EUmRDqR714IGomj/GonHQp1yviyI24GJfyIxjJoCaX1f2qxTNlFu wRPiuVusGLOyYzlkx6rgkL7tAOZe72gPwL1p9Nzl33rJvVxPv0bIQ8ICCeZY4VE5 BkzKb22ps7Gux9o+aNuxV4B65KmCVWXyLOE9Zaegkoa9dAXZyk7dpwWvSSa0reaZ +sQyDy6U0J4U2399pPnjCGuuPDrnka9K1A28s33cQBekDgpos/C+xJ27IPpA5Rn9 +2ihZqm2I1SZfufWCH26buiCVJ/dYZ2hTgiHf1JCCjm9RSPETkPNFIN34Mb0S6/s Xj+gD2ZI1CCH6nmaMRwiWcx7wKr9iwyJS+UxMJg1A/HhWTC2Gpw= =HBQ9 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/93420b3d-d2c9-29e8-9518-4192a84990ca%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Announcement: Qubes Tor onion services will no longer be maintained
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Qubes Community, We regret to announce that the Qubes Tor onion services will no longer be maintained due to lack of resources. This includes all Qubes onion services, including the Qubes website onion mirror and the onion package repos. We would like to thank the Whonix Project for generously maintaining these services for over a year. [1] Maintaining the Tor onion services requires labor, servers, and bandwidth. Unfortunately, none of these resources are available to the Qubes OS or Whonix projects in sufficient quantities to allow us to continue offering these services. We recommend that users who currently rely on any Qubes onion addresses transition to the corresponding clearnet addresses immediately. Maybe you could have added two lines how to do this. Is is correct / sufficient for this transition to choose sys-firewall as UpdateVM in qubesManager->GlobalSettings ? -- 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/06e0a884-9ca6-2870-5d36-493b9ea5cdb5%40web.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora-29 Template (Qubes 4.0.1) keeps asking to upgrade
Just had this happen again on fedora 28. -vv showed metadata issues. sudo dnf clean all or metadata didn't work this time. But enabling testing repo in /etc/yum.repos.d/qubes-r4.repo and then updating fixed 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/62e61f14-a697-4bc3-b9ca-1dd1175f3506%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Announcement: Qubes Tor onion services will no longer be maintained
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Qubes Community, We regret to announce that the Qubes Tor onion services will no longer be maintained due to lack of resources. This includes all Qubes onion services, including the Qubes website onion mirror and the onion package repos. We would like to thank the Whonix Project for generously maintaining these services for over a year. [1] Maintaining the Tor onion services requires labor, servers, and bandwidth. Unfortunately, none of these resources are available to the Qubes OS or Whonix projects in sufficient quantities to allow us to continue offering these services. We recommend that users who currently rely on any Qubes onion addresses transition to the corresponding clearnet addresses immediately. [1] https://www.qubes-os.org/news/2018/01/23/qubes-whonix-next-gen-tor-onion-services/ This announcement is also available on the Qubes website: https://www.qubes-os.org/news/2019/03/24/tor-onion-services-no-longer-maintained/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlyYIQ8ACgkQ203TvDlQ MDDCfg/9F9Y4TMWeUVKHXyRhs3S2mqG1t7zeOD9XnxUzk6XG85H003JMRM590G6i 6ZRBvSv62hiy9SLbDhfgG7OeCZ5fBdD/BEIKdfuO08EIxFaNoyPeRTz0aY15YlrO 2guA3HlQmx2+1Bn4UEAPFleRhquhDbCT04qBWIRsvNkEEU+lwr8Mb5P7Nhrh8Mjk dzKu/EfEMPrCl16fdrtYN7tv5D300HQ51TcFYYKyLlBZHsq7Qol5+RVY4MPW1SAJ 9l1uYQBAmUsEikG9Xp4VgHoaNQOg5IulASkgWqfoONs5o9V2cy+tDeVH4H9+Io0o FWtJU1yP97LnPMrr8huzJoQlWDRuKK1DSE4URDYCtSJNSDARUUZ7r3ACX+qXltM3 WdGtp8x7UVAm6KErcComrd3rSZuDXytUUnT7D6Io4QxZajjQLa3zLLAxHdnxzuh8 1Lxs7bi8ebvt5ILLnoi89k+p0WRSf2NMzE3IGlxEZ7zA/9SNYgS+6VfgATGLQl4I Kfpm579r2HtsJw7G8gI5xJqN8+l2eB7mtxwSTCvy1i2tARUhLKEJsPWnaql8kxpb OcxuQE6zY525sM3D5zY3a8WPMgrrS2GJlO9sJDU6mcK8ILRDuwyb1m3Xw4knD/t6 Pa3b1msNtiSMUMdoJ07eRWwho7JPz78NnK7FIhl/YujB2MdXlMY= =K1j1 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4cb2a29b-729c-cb72-4174-f313f19cd930%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Blank Screen Trying To Install
Yushatak wrote on 3/24/19 9:39 PM: On Sunday, March 24, 2019 at 3:36:10 PM UTC-4, awokd wrote: I think the issue is he edited grub.cfg but has no legacy mode, which means grub won't be used. Yushatak, try using that same procedure to edit xen.cfg instead. It will be somewhere under boot/efi/EFI/qubes. There is no such path, the closest I'm aware of is EFI/BOOT, which contains BOOTX64.cfg, which I already modified with nouveau.modeset=0 on each option to no avail. To my understanding this is the conf that should apply since this is the EFI boot folder, so I don't think that setting is the culprit. That said, it's not Xen.cfg, but I did 'ls -R | grep Xen.cfg' which resulted in nothing, then did 'ls -R | grep xen' which returned packages as well as xen.gz, then 'ls -R | grep Xen' which returned nothing, so I'm not sure there is such a config. You're right, not xen.cfg but BOOTX64.cfg. I was thinking of post-install path & filename. -- 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/bde0ab7a-0ce5-9f76-a50b-243758a39338%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Mounting a second hard drive -- I can't figure out how to make qvm-block see it....
billol...@gmail.com wrote on 3/24/19 8:48 PM: I am sure this is a silly issue, but I've been searching in the archives and can't see the answer. I have a laptop with 1 SSD and 1 SATA drive. I installed Qubes on the SSD, and have a couple of data partitions on the SATA drive. I want to make one of those partitions available to my work vm or its template. I was able to mount it on dom0 by putting it in the fstab. The /etc/fstab line is: UUID= /big ext4 defaults,discard,xsystemd.device-timeout=0 1 1 in dom0, it shows up as /dev/sda3. The df -h command, gives: FilesystemSizeUsed Avail Use% Mounted on /dev/sda3 903G 154G 703G 18%/big I can't figure out how to make this disk available to my template or user vms. Most flexible way to use the secondary drive would be to backup the data somewhere else, then https://www.qubes-os.org/doc/secondary-storage/. If you want to assign sda3 to a VM, you'd have to unmount it from dom0 first, then use qvm-block to attach it to a single VM at a 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/a4fe75b6-3efc-bfb2-216b-064cff60502c%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Blank Screen Trying To Install
On Sun, 24 Mar 2019 14:39:12 -0700 (PDT) Yushatak wrote: > On Sunday, March 24, 2019 at 3:36:10 PM UTC-4, awokd wrote: > > Mike Keehan wrote on 3/24/19 3:36 PM: > > > On Sun, 24 Mar 2019 02:07:10 -0400 > > > Yushatak wrote: > > > > > >> Machine has no legacy mode. > > >> > > >> On Sat, Mar 23, 2019, 11:32 PM Gaijin wrote: > > >> > > >>> On 2019-03-24 02:41, Yushatak wrote: > > On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak > > wrote: > > > When I boot the Qubes installation media (I dd'd it to a USB > > > stick per > > >>> the instructions on the site) it initializes Xen, then the > > >>> kernel starts booting (Linux penguins, etc.), and then it goes > > >>> to a black screen and there's no activity. F1 does nothing. My > > >>> hardware is a laptop with an i7 8700K and an Nvidia 1060, so it > > >>> smelled like nouveau driver problems to me. However, normally > > >>> one works around that by editing the kernel line in grub with > > >>> nouveau.modeset=0 and I have no grub! I decided to try editing > > >>> the grub.conf in the isolinux directory of the ISO by > > >>> extracting the iso, editing, then regenerating the ISO. Someone > > >>> on IRC was nice enough to provide me a log from the official > > >>> build of the ISO so I used the proper switches/etc.. I booted > > >>> that in a VM to make sure it was OK as a sanity check, then > > >>> wrote that to the USB stick (which takes like 26 minutes, it's > > >>> USB 2.. not fun) and it stopped booting after attaching the USB > > >>> stick as a SCSI device, not even quite getting to the black > > >>> screen. AFAIK my hardware requires a 4.18 kernel and from what > > >>> they said on IRC there's nothing newer than 4.14 in Qubes > > >>> anyway, but since it tries to boot I don't know. I throw myself > > >>> upon your mercy, Qubes community/developers. > > > > Nobody has a single thought? > > >>> > > >>> Might the solution be putting your BIOS into Legacy mode? > > >>> https://groups.google.com/forum/#!topic/qubes-users/Vy5wpWbOYxU > > >>> > > >>> In my case switching the HDD from AHCI mode to IDE mode seemed > > >>> to get past this blank screen and got me to the install screen. > > >>> > > >> > > > > > > I had exactly this problem when I installed Qubes. Searching > > > this mail list found the answer. (You have to edit the > > > installation image, or mount the image, edit it and build a new > > > image for installation.) > > I think the issue is he edited grub.cfg but has no legacy mode, > > which means grub won't be used. Yushatak, try using that same > > procedure to edit xen.cfg instead. It will be somewhere under > > boot/efi/EFI/qubes. > > There is no such path, the closest I'm aware of is EFI/BOOT, which > contains BOOTX64.cfg, which I already modified with nouveau.modeset=0 > on each option to no avail. To my understanding this is the conf that > should apply since this is the EFI boot folder, so I don't think that > setting is the culprit. That said, it's not Xen.cfg, but I did 'ls -R > | grep Xen.cfg' which resulted in nothing, then did 'ls -R | grep > xen' which returned packages as well as xen.gz, then 'ls -R | grep > Xen' which returned nothing, so I'm not sure there is such a config. > Have you looked at this page? https://www.qubes-os.org/doc/uefi-troubleshooting/ -- 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/20190324221654.69e7724c.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: i3 support?
On Sunday, March 24, 2019 at 12:30:50 PM UTC-5, Stumpy wrote: > On 3/23/19 8:32 PM, Yethal wrote: > > W dniu sobota, 23 marca 2019 21:11:49 UTC+1 użytkownik Stumpy napisał: > >> I have been considering looking into i3 on my qubes box but was > >> wondering about support in the future. As there appears to be a bit of a > >> learning curve i wanted to check before diving in. > >> > >> w/ v3 i was using kde then, as support seemed to wan, i switched over to > >> xfce which is admittedly lighter but doest seem to be as feature rich. > >> > >> is there any "official" stance on i3 now and going on into the future? > > > > There is an i3 package in main Qubes repo and it does work fine. I use i3 > > as my daily DE in Qubes and couldn't be happier with it. > > > > Thanks, thats good to know. Do you have a multi-monitor setup? I jsut > ask because I am hoping for better MM support than XFCE offers. > > As for the package availability, I beleive there is still a kde package > as well - what I am hoping to learn (maybe I should ask on the dev list? > really dont want to distract them though) is the "long term > availability" of i3. It seems like kde might not be offered in the > future and while i am guessing it should be possible to install whatever > win manager one might want, I prefer to go with what the community is > supporting as I wouldn't trust myself to properly securely install > another winman myself. > > thanks! Yes, i3 works very well with multiple monitors. I use my notebook in three different configurations, standalone, dual (with a large external monitor) and clone (hdmi same as screen). i3 does layout to use the whole screen, partitioning as necessary. In my dual configuration, each screen is managed separately. You can pair screens independently, one on the notebook and one on the external display. You can reconfigure between the two using xrandr. Jon -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9a5f9050-5431-4faa-9236-bc098a9e8c0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kernel 4.20 Can’t find
On Sunday, March 24, 2019 at 1:36:42 AM UTC+1, Aly Abdellatif wrote: > Hi, > > With qubes-dom0-update , I can’t find the kernel 4.20 version with the > current or current testing or even the unstable. The further I can go is the > 4.19. > > Is there something wrong in what I’m doing? > > Best Regards > Aly Abdellatif kernel-4.20 is obsolete, but there's a package on current Qubes Package repository - download and install if you must. https://yum.qubes-os.org/r4.0/current/dom0/fc25/rpm/ kernel-4.19 is the current stable longterm one - better use this. or you can try 5.0.2 from testing with: qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel-latest kernel-latest-qubes-vm goog 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/ec79783e-ff75-419f-bc4a-557a56efdc8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Blank Screen Trying To Install
On Sunday, March 24, 2019 at 3:36:10 PM UTC-4, awokd wrote: > Mike Keehan wrote on 3/24/19 3:36 PM: > > On Sun, 24 Mar 2019 02:07:10 -0400 > > Yushatak wrote: > > > >> Machine has no legacy mode. > >> > >> On Sat, Mar 23, 2019, 11:32 PM Gaijin wrote: > >> > >>> On 2019-03-24 02:41, Yushatak wrote: > On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak wrote: > > When I boot the Qubes installation media (I dd'd it to a USB > > stick per > >>> the instructions on the site) it initializes Xen, then the kernel > >>> starts booting (Linux penguins, etc.), and then it goes to a black > >>> screen and there's no activity. F1 does nothing. My hardware is a > >>> laptop with an i7 8700K and an Nvidia 1060, so it smelled like > >>> nouveau driver problems to me. However, normally one works around > >>> that by editing the kernel line in grub with nouveau.modeset=0 and > >>> I have no grub! I decided to try editing the grub.conf in the > >>> isolinux directory of the ISO by extracting the iso, editing, then > >>> regenerating the ISO. Someone on IRC was nice enough to provide me > >>> a log from the official build of the ISO so I used the proper > >>> switches/etc.. I booted that in a VM to make sure it was OK as a > >>> sanity check, then wrote that to the USB stick (which takes like 26 > >>> minutes, it's USB 2.. not fun) and it stopped booting after > >>> attaching the USB stick as a SCSI device, not even quite getting to > >>> the black screen. AFAIK my hardware requires a 4.18 kernel and from > >>> what they said on IRC there's nothing newer than 4.14 in Qubes > >>> anyway, but since it tries to boot I don't know. I throw myself > >>> upon your mercy, Qubes community/developers. > > Nobody has a single thought? > >>> > >>> Might the solution be putting your BIOS into Legacy mode? > >>> https://groups.google.com/forum/#!topic/qubes-users/Vy5wpWbOYxU > >>> > >>> In my case switching the HDD from AHCI mode to IDE mode seemed to > >>> get past this blank screen and got me to the install screen. > >>> > >> > > > > I had exactly this problem when I installed Qubes. Searching this mail > > list found the answer. (You have to edit the installation image, or > > mount the image, edit it and build a new image for installation.) > > > I think the issue is he edited grub.cfg but has no legacy mode, which > means grub won't be used. Yushatak, try using that same procedure to > edit xen.cfg instead. It will be somewhere under boot/efi/EFI/qubes. There is no such path, the closest I'm aware of is EFI/BOOT, which contains BOOTX64.cfg, which I already modified with nouveau.modeset=0 on each option to no avail. To my understanding this is the conf that should apply since this is the EFI boot folder, so I don't think that setting is the culprit. That said, it's not Xen.cfg, but I did 'ls -R | grep Xen.cfg' which resulted in nothing, then did 'ls -R | grep xen' which returned packages as well as xen.gz, then 'ls -R | grep Xen' which returned nothing, so I'm not sure there is such a config. -- 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/57022df6-359b-4318-940c-cc8e57aa67ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590
On Sunday, March 24, 2019 at 8:31:12 PM UTC+1, awokd wrote: > CooSee wrote on 3/22/19 11:41 PM: > > On Friday, March 22, 2019 at 11:56:14 PM UTC+1, Foppe de Haan wrote: > >> what's ~/.local/share/xorg/Xorg.0.log telling you? > > > > there' no log in this specified directory. > > Try looking for it in /var/log? ok, here's the one from working 4.14.103 kernel using a debian-vm -see attachment. All the other Xorg.logs are from dom0 with newer kernels. AMD_IOMMUV2 >> is not the problem, because testing a compiled kernel without > same problem > no login possible > crashing back to login and as i said, with newer kernel after 4.14 the login background is scrambled with glitches, but this happens only with newer kernel. With 4.14.103 no problems at all - no glitches and even direct rendering's working fine with the amdgpu : --- glxinfo | grep rendering direct rendering: Yes --- @John Mitchell thx for the video, but i already managed the Firmware problem in Qubes with using the linux-firmware package from FC31, so it's current! the error with: --- [62.958] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage [62.958] (WW) glamor: Failed to allocate 22x22 FBO due to GL_OUT_OF_MEMORY. [62.958] (WW) glamor: Expect reduced performance. --- was already addressed in newer versions of xorg-server, please see: https://gitlab.freedesktop.org/xorg/xserver/commits/master?utf8=%E2%9C%93&search=glamor On my Funtoo System with a manually build kernel, i never got this kind of problems at all - no glitches etc. and everything working fine with RX590. After installing the RX590 i had to boot with amdgpu.dpm=0 at first, but after recompiling the kernel and also with a better firmware for the Card, i never have to use the boot option anymore. Now, how to switch or install a newer Version of Xorg-Server and Mesa on Qubes FC25 - the problem is that this packages depends on newer Version of Openssl-1.1 and Glibc-2.26 or higher and Mesa depends on LLVM 7 ? With FunToo this is so easy :-) It would be great if there's a solution for this annoying problem, so i can also use newer kernels without booting amdgpu.dpm=0 boot Option. thx -- 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/9fcf3279-f7a0-4989-801d-38b39b59c83d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Xorg.0.log_working_4.14.103_kernel Description: Binary data
[qubes-users] Mounting a second hard drive -- I can't figure out how to make qvm-block see it....
I am sure this is a silly issue, but I've been searching in the archives and can't see the answer. I have a laptop with 1 SSD and 1 SATA drive. I installed Qubes on the SSD, and have a couple of data partitions on the SATA drive. I want to make one of those partitions available to my work vm or its template. I was able to mount it on dom0 by putting it in the fstab. The /etc/fstab line is: UUID= /big ext4 defaults,discard,xsystemd.device-timeout=0 1 1 in dom0, it shows up as /dev/sda3. The df -h command, gives: FilesystemSizeUsed Avail Use% Mounted on /dev/sda3 903G 154G 703G 18%/big I can't figure out how to make this disk available to my template or user vms. In dom0, qvm-block l gives: dom0:nvme0n1p4 () dom0:nvme0n1p5 () dom0:sda1 WDC_WD10SPZX-60Z1TO () dom0:sda2 WDC_WD10SPZX-60Z1TO () I have rebooted a few times, and it has not autmagically shown up. I'm sure this is simple, but I'd like to mount it on my debian vm, and let all the user vms from that see it. I can't find the howto page for this. Thanks! billo -- 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/641afe83-dd44-4b06-8f55-c0e987f69cba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using "Installed" AppImages on AppVMs?
Stumpy wrote on 3/24/19 5:20 PM: I have read a doc or two that says to "install" an appimage onto a template and then use it in the appvm. Problem is as far as i know appvms are self contained and not installed per se so I have tried to just put an appvm in my template then run it from an appvm but nada. Is there a way to put an appimage on a template and then have it useable on the appvms that are based on that template? Put them anywhere on the template except "/rw (includes /home, /usr/local and bind-dirs)" and they will be available to the appvms based on it. -- 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/c99b8ff5-d914-f6b7-ccdc-f188ef0c6d3c%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Blank Screen Trying To Install
Mike Keehan wrote on 3/24/19 3:36 PM: On Sun, 24 Mar 2019 02:07:10 -0400 Yushatak wrote: Machine has no legacy mode. On Sat, Mar 23, 2019, 11:32 PM Gaijin wrote: On 2019-03-24 02:41, Yushatak wrote: On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak wrote: When I boot the Qubes installation media (I dd'd it to a USB stick per the instructions on the site) it initializes Xen, then the kernel starts booting (Linux penguins, etc.), and then it goes to a black screen and there's no activity. F1 does nothing. My hardware is a laptop with an i7 8700K and an Nvidia 1060, so it smelled like nouveau driver problems to me. However, normally one works around that by editing the kernel line in grub with nouveau.modeset=0 and I have no grub! I decided to try editing the grub.conf in the isolinux directory of the ISO by extracting the iso, editing, then regenerating the ISO. Someone on IRC was nice enough to provide me a log from the official build of the ISO so I used the proper switches/etc.. I booted that in a VM to make sure it was OK as a sanity check, then wrote that to the USB stick (which takes like 26 minutes, it's USB 2.. not fun) and it stopped booting after attaching the USB stick as a SCSI device, not even quite getting to the black screen. AFAIK my hardware requires a 4.18 kernel and from what they said on IRC there's nothing newer than 4.14 in Qubes anyway, but since it tries to boot I don't know. I throw myself upon your mercy, Qubes community/developers. Nobody has a single thought? Might the solution be putting your BIOS into Legacy mode? https://groups.google.com/forum/#!topic/qubes-users/Vy5wpWbOYxU In my case switching the HDD from AHCI mode to IDE mode seemed to get past this blank screen and got me to the install screen. I had exactly this problem when I installed Qubes. Searching this mail list found the answer. (You have to edit the installation image, or mount the image, edit it and build a new image for installation.) I think the issue is he edited grub.cfg but has no legacy mode, which means grub won't be used. Yushatak, try using that same procedure to edit xen.cfg instead. It will be somewhere under boot/efi/EFI/qubes. -- 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/b7cb65c1-3894-be9c-1fba-084ef3d543af%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590
CooSee wrote on 3/22/19 11:41 PM: On Friday, March 22, 2019 at 11:56:14 PM UTC+1, Foppe de Haan wrote: what's ~/.local/share/xorg/Xorg.0.log telling you? there' no log in this specified directory. Try looking for it in /var/log? -- 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/3ee50576-78fc-2640-0e6f-008153431cc9%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Installing software..
22...@tutamail.com wrote on 3/23/19 11:22 PM: What would be the commands to install lets say: LibraOffice into a Debian template? I have used Protonmail bridge on whonix and debian and have only been able to get it to install by giving full access temporarily to the template... Libreoffice is in Debian's repos so all you'd need to run in the template is: sudo apt install libreoffice You might be thinking of software that's not available from Debian repos. For those, it's usually best to see if there's something else that will work and available. If not, it's better to download the package in a qube already internet connected, then qvm-copy it to the template. That way you can avoid touching the Internet from your template. -- 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/3cc1eb8b-9ed3-af09-0b59-963005e116c9%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4 install not seeing VT-d/VT-x
Gaijin wrote on 3/23/19 3:32 AM: While attempting to upgrade from R3.2 to R4.0.1 I get the error: Missing features: IOMMU/VT-d/AMD-Vi, Interrupt Remapping I have an ASRock H67DE motherboard with an Intel i7-2600 CPU which according to the specs supports both VT-d and VT-x, and I have both specifically enabled in the BIOS. However, the Qubes 4 installer apparently can't see them. (I wonder if this is because I can only boot the installation USB in Legacy mode and not AHCI mode) I'm wondering if it would be OK to proceed with the install despite this warning. Is there a way to check whether these BIOS settings are visible to Qubes, or is this warning a clear indicator that they're not? (I still have R3.2 working) In R3.2's dom0 run qubes-hcl-report. Look for the 5 lines at the bottom. You can proceed with the install, but if you don't really have support it will fail when trying to set up sys-net after the initial post-install reboot. -- 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/2f6737ef-14ce-7476-46bb-6d2959435750%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HVM from previous filesystem in the form of .img
luse...@gmail.com wrote on 3/22/19 10:54 AM: I have dumped my previous Linux daily driver's filesystem on an .img file. I'm trying to create an HVM with the option --root-copy-from. The HVM fails to boot at all cases. Either I get the grimmy 4 liner, or it's running background jobs and then notes that the booting failed or I get a kernel panic. The image file contains my root previous working tree and the boot partition included in it under /boot. Any ideas? The default HVM disk size is likely smaller than your .img file. Create the HVM first, size the disk and RAM (2GB+ at first) appropriately, then cp name.img /dev/mapper/qubes_dom0-vm--[VMNAME]--root. -- 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/d26dfea3-66fe-bb60-b28a-52df27bbc890%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Torsocks and dnf no longer work in Fedora 29 -- Any Ideas?
I utilize torsocks dnf to perform updates over tor inside of HVM linux installs (so not in templates obviously which would use qubes normal update mechanism). Since upgrading to Fedora 29 torsocks is not working with DNF. It throws an exception message. This is not directly related to qubes, but I imagine others have had this issue. Does anyone know how to use torsocks with dnf now. For example: sudo torsocks --isolate dnf update Running the above used to work perfectly. Now, it will work until it reaches a random error which is unrelated to networking. It is the following: terminate called after throwing an instance of 'libdnf::File::CloseException' what(): Cannot close file: /var/cache/dnf/fedora-modular-[random letters]/repodata/[random letters]]-modules.yaml.gz Aborted So, it seems related to closing a file and for some reason this causes a termination, but only when using torsocks. When not using torsocks it works normally. I have run dnf clean all and all of that. -- 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/Lakw7aL--3-1%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: i3 support?
On 3/23/19 8:32 PM, Yethal wrote: W dniu sobota, 23 marca 2019 21:11:49 UTC+1 użytkownik Stumpy napisał: I have been considering looking into i3 on my qubes box but was wondering about support in the future. As there appears to be a bit of a learning curve i wanted to check before diving in. w/ v3 i was using kde then, as support seemed to wan, i switched over to xfce which is admittedly lighter but doest seem to be as feature rich. is there any "official" stance on i3 now and going on into the future? There is an i3 package in main Qubes repo and it does work fine. I use i3 as my daily DE in Qubes and couldn't be happier with it. Thanks, thats good to know. Do you have a multi-monitor setup? I jsut ask because I am hoping for better MM support than XFCE offers. As for the package availability, I beleive there is still a kde package as well - what I am hoping to learn (maybe I should ask on the dev list? really dont want to distract them though) is the "long term availability" of i3. It seems like kde might not be offered in the future and while i am guessing it should be possible to install whatever win manager one might want, I prefer to go with what the community is supporting as I wouldn't trust myself to properly securely install another winman myself. 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/1f5172ca-8a86-a1d1-07a3-b73d413c0252%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Using "Installed" AppImages on AppVMs?
I have read a doc or two that says to "install" an appimage onto a template and then use it in the appvm. Problem is as far as i know appvms are self contained and not installed per se so I have tried to just put an appvm in my template then run it from an appvm but nada. Is there a way to put an appimage on a template and then have it useable on the appvms that are based on that template? -- 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/274254b2-d6e9-5009-c910-35b97b2cb837%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Compiling kernel modules
OK - so it looks that it does not work like that in QubesOS - i.e. by default the modules directory is read only. I found some instructions on installing custom kernels in: www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm. I don't really need a new kernel - I just want to be able to compile the modules - but this looks like a possible way out for me. So I did cloned the fedora-29 template and: qvm-prefs virt_mode hvm qvm-prefs kernel '' unfortunately now the cloned template does not start - so I cannot continue with the instructions at the doc linked above. When I change the kernel back to '4.14.103-1' it works fine. -- ZL -- 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/CAGL_UUvA65K__3Kg1mNexjdMidvOJEsT%2BOYDyJUzBH7aR3AayQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Blank Screen Trying To Install
On Sun, 24 Mar 2019 02:07:10 -0400 Yushatak wrote: > Machine has no legacy mode. > > On Sat, Mar 23, 2019, 11:32 PM Gaijin wrote: > > > On 2019-03-24 02:41, Yushatak wrote: > > > On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak wrote: > > >> When I boot the Qubes installation media (I dd'd it to a USB > > >> stick per > > the instructions on the site) it initializes Xen, then the kernel > > starts booting (Linux penguins, etc.), and then it goes to a black > > screen and there's no activity. F1 does nothing. My hardware is a > > laptop with an i7 8700K and an Nvidia 1060, so it smelled like > > nouveau driver problems to me. However, normally one works around > > that by editing the kernel line in grub with nouveau.modeset=0 and > > I have no grub! I decided to try editing the grub.conf in the > > isolinux directory of the ISO by extracting the iso, editing, then > > regenerating the ISO. Someone on IRC was nice enough to provide me > > a log from the official build of the ISO so I used the proper > > switches/etc.. I booted that in a VM to make sure it was OK as a > > sanity check, then wrote that to the USB stick (which takes like 26 > > minutes, it's USB 2.. not fun) and it stopped booting after > > attaching the USB stick as a SCSI device, not even quite getting to > > the black screen. AFAIK my hardware requires a 4.18 kernel and from > > what they said on IRC there's nothing newer than 4.14 in Qubes > > anyway, but since it tries to boot I don't know. I throw myself > > upon your mercy, Qubes community/developers. > > > > > > Nobody has a single thought? > > > > Might the solution be putting your BIOS into Legacy mode? > > https://groups.google.com/forum/#!topic/qubes-users/Vy5wpWbOYxU > > > > In my case switching the HDD from AHCI mode to IDE mode seemed to > > get past this blank screen and got me to the install screen. > > > I had exactly this problem when I installed Qubes. Searching this mail list found the answer. (You have to edit the installation image, or mount the image, edit it and build a new image for installation.) Mike. -- 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/20190324153605.69690b17.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - GB-BSi3-6100
--- layout: 'hcl' type: 'desktop' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'no' remap: 'yes' brand: | GIGABYTE model: | GB-BSi3-6100 bios: | F3 cpu: | Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz cpu-short: | Intel x64 i3 chipset: | Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08) chipset-short: | FIXME gpu: | Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) gpu-short: | FIXME network: | Intel Corporation Ethernet Connection I219-V (rev 21) Intel Corporation Wireless 3165 (rev 81) memory: | 16299 scsi: | Samsung SSD 850 Rev: 1B6Q usb: | 1 versions: - works: yes qubes: | R4.0 xen: | 4.8.5 kernel: | 4.14.103-1 remark: | Graphical glitches and freezes. Minor text rendering issues to Firefox freezing on tabs and unable to re-render new tabs without being restart. credit: | FIXME 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/CAPX9O0_oADQ6NXR1UWj%3DJOHxuFThJh%3DzxHK7eZAG-g%2BW8%2BW3VA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-GIGABYTE-GB_BSi3_6100-20190315-125343.yml Description: application/yaml
[qubes-users] HCL ASRock H67DE motherboard
Works great with 3.2. Apparent lack of IOMMU is stopping R4 installation although the i7-2600 has support for VT-d and VT-x. -- 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/24056a9940d0eb2409289a5885f333a6%40riseup.net. For more options, visit https://groups.google.com/d/optout. --- layout: 'hcl' type: 'desktop' hvm: 'yes' iommu: 'no' slat: 'yes' tpm: 'unknown' remap: 'no' brand: | THIRDWAVE CORPORATION model: | Prime Series bios: | L1.43Y cpu: | Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz cpu-short: | i7-2600 chipset: | Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0100] (rev 09) chipset-short: | Intel 8086 rev 09 gpu: | Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) gpu-short: | nVidia GeForce GTX 560 Ti network: | Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) memory: | 32676 scsi: | Samsung SSD 850 Rev: 2B6Q TOSHIBA DT01ACA3 Rev: ABB0 DVDRAM GH24NS70 Rev: GN03 ST8000DM004-2CX1 Rev: 0001 HDCR-U Rev: USB Flash Disk Rev: 1.00 usb: | 4 versions: - works: yes qubes: | R3.2 xen: | 4.6.6 kernel: | 4.14.103-1 remark: | Works great in R3.2, but apparent lack of IOMMU seems to be a problem with R4. credit: | Gaijin link: | FIXLINK ---
Re: [qubes-users] Dom0 Update breaks sys-usb widget
I had to use --best --allowerasing to update qubes-desktop-linux-manager. USB widget now works better than before, but VM widget seems broken. -- 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/4036163a-3d84-4dbe-9063-73a6702342be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590
I don't know if this will be helpful since I am using Xubuntu 18.10 with kernel 5.0.1 with a RX590 card. So the problem is likely with the kernel build since the older kernels do not properly reset the RX590. Here is a video walking through getting everything to work with Xubuntu, perhaps you can extrapolate some useful information. https://www.youtube.com/watch?v=qK5ra2eed7w -- 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/aeb264d2-5ead-4fc2-9929-92d735b7a52e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Shrinking a private volume
On 3/24/19 4:15 AM, 799 wrote: Hello Unman, unman mailto:un...@thirdeyesecurity.org>> schrieb am So., 24. März 2019, 03:17: [...] We're all working on the assumption that you have Qubes 4.0 - can you confirm that? Yes, of course - sorry for not mentioning this, but I don't see why someone would run Q3.2, I have switched to 4.0 shortly after the release and never looked back. You can see what size is actually used on disk by using s flag to ls: so 'ls -lsS' will show you the apparent size and the actual size. Thanks, I wasn't aware of this command option and will review the man page for ls, to see it there are more interesting options In 3.2, to attach a private.img try: qvm-block -A dom0:/var/. That's 3.x specific. One way to do it in 4.0 (losetup assigns a device to the img file then prints the device name): $ sudo losetup -f /var/lib/qubes/...img loop0 $ qvm-block attach newvm dom0:loop0 As for backup and restore, you can do this just fine between non-lvm and lvm systems. If you do create a backup you may want to copy it to a third device so there is an extra copy, then do a verify on the extra copy just in case. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9374f0ab-b020-ca92-d08d-dc0b2663c6a3%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] coreboot on modern hardware?
Hello, schrieb am So., 24. März 2019, 10:11: > On 2019-03-23 19:03, jrsmi...@gmail.com wrote: > > Spent several hours yesterday trying to track down what I would need > > to do to install coreboot on all of my computers, starting with my > > Qubes box: a Levnovo Thinkpad T480. [...] > I'd suggest visiting https://coreboot.org/status/board-status.html to > see if your box is compatible with coreboot. From what I can see, the > T480 is not coreboot friendly. > The provided link is the right place to see, I have also invested some time for the research before flashing my X230 with Coreboot and again when I tried to flash my W540. It seems that everything after the X230/T430/W530 is not corebootable. On the other hand the ?30-Series offers enough performance for most workloads. Newer hardware will (very likely) not work with Coreboot (if you look into Lenovo) and NOT buying Lenovo and talk about it why you are not buying it, might be the only way to convince companies to change (even when this is very (!) unlikely). - O -- 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/CAJ3yz2tbvSzCisSdbdKS4fvNe1Lf0yofGdQN_deNt4xzbtST%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] coreboot on modern hardware?
On 2019-03-23 19:03, jrsmi...@gmail.com wrote: > Spent several hours yesterday trying to track down what I would need > to do to install coreboot on all of my computers, starting with my > Qubes box: a Levnovo Thinkpad T480. > > The bottom line from what I can tell is that if you have an Intel CPU > made since 2008 (any that have Boot Guard) or an AMD CPU made since > 2013 (any that have PSP), you are out of luck. Libreboot spells this > out in their docs. I'm not sure if that is because of coreboot itself > or something specific to Libreboot. I was stuck by how they seemed > perfectly fine walling themselves off from the present and the future. > > I could find nothing indicating that anyone had even tried, much less > succeeded, in installing coreboot on a T480 and everything I did find > was for much older hardware. > > I read through the coreboot docs where they just wave their hands at > the end of the build process and say "now go flash". I also read > through the heads docs, which say more or less the same thing. > > Hackaday has an article on the horrors of installing coreboot on a > Toshiba laptop. Not only do they neglect to say which model they > used, at the end of the article they had it working. > > The gist is that the information that's out there is out of date, > incomplete, misleading, and sometimes just incompetent. > > I'm hoping that someone here has first-hand knowledge and can advise > me (and others who read this). > > Thanks, > John Smiley I'd suggest visiting https://coreboot.org/status/board-status.html to see if your box is compatible with coreboot. From what I can see, the T480 is not coreboot friendly. The coreboot web site generally is a very good starting point in establishing the how, what and when procedures for installing coreboot successfully. -- 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/e4e04ba6dbc7a03a192e8ef1f724cd59%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Shrinking a private volume
Hello Unman, unman schrieb am So., 24. März 2019, 03:17: > [...] > We're all working on the assumption that you have Qubes 4.0 - can you > confirm that? > Yes, of course - sorry for not mentioning this, but I don't see why someone would run Q3.2, I have switched to 4.0 shortly after the release and never looked back. You can see what size is actually used on disk by using s flag to ls: > so 'ls -lsS' will show you the apparent size and the actual size. > Thanks, I wasn't aware of this command option and will review the man page for ls, to see it there are more interesting options In 3.2, to attach a private.img try: > qvm-block -A dom0:/var/. > Will this also work under Qubes 4, as you are mentioning 3.2 specifically. What are the command to do so in 4.0? - O > -- 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/CAJ3yz2uqMgniDVmMQidau0ij2a1z0BkxTED_UeNLg1CQNXF0tA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
