[qubes-users] Troubleshooting Qubes graphical slowness
Periodically all graphics-heavy apps (Firefox, ...) in all VMs seem to slow down simultaneously. Rebooting fixes the situation. Running `sudo journalctl -f` in dom0 doesn't show anything unusual. What would you suggest as a next step towards locating the problem? -- 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/20191227073310.GA1647%40danwin1210.me.
Re: [qubes-users] sys-net interfaces
On Thu, Dec 26, 2019 at 11:47:37AM +, 'awokd' via qubes-users wrote: There's a brief discussion at https://www.qubes-os.org/doc/networking/, but there may be more detailed notes in the source code for Qubes' VM networking components. Qubes uses Xen's networking, so that might be the best place to begin research. What responsibilties does sys-net have in terms of forwarding DNS? The documentation specifies how things work for AppVMs, and it says there is no DNS server in the "network driver domain" (sys-net), but it does not say what sys-net actually has to do. Also, the docs don't appear to be entirely accurate. The documentation specifies a fairly complex set of routing tabels for the "network driver domain" (sys-net, I assume), but the actual routing table on my sys-net is fairly simple The table from the documentation: Destination Gateway Genmask Flags Metric Ref Use Iface 10.137.0.16 0.0.0.0 255.255.255.255 UH 0 0 0 vif4.0 10.137.0.7 0.0.0.0 255.255.255.255 UH 0 0 0 vif10.0 10.137.0.9 0.0.0.0 255.255.255.255 UH 0 [... many lines removed ...] 192.168.0.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 The table from my sys-net: [user@sys-net ~]$ sudo ip route [user@sys-net ~]$ sudo route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default _gateway0.0.0.0 UG60000 wls7 10.137.0.5 0.0.0.0 255.255.255.255 UH32747 00 vif5.0 192.168.0.0 0.0.0.0 255.255.255.0 U 60000 wls7 It looks like the documentation is assuming sys-net has many more virtual NICs than it actually does? -- 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/20191227070535.GA1464%40danwin1210.me.
Re: [qubes-users] Installer crash: IO-APIC + timer doesn't work (Dell XPS 7390)
On Thursday, December 26, 2019 at 5:31:50 AM UTC-8, awokd wrote: > What happens if you use an options line like the following? > > options=console=vga loglvl=all efi=no-rs > ``` (XEN) Platform timer is 23.999MHz HPET (XEN) [...] (XEN) CPU0: No irq handler for vector 40 (IRC -2147483648, LAPIC) (XEN) PCI: MCFG configuration 0: base e000 segment buses 00 - ff (XEN) PCI: Not using MCFG for segment bus 00-ff (XEN) [...] (XEN) Interrupt remapping enabled (XEN) nr_sockets: 2 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO_APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC (XEN) ...trying to set up timer (IRQ0) through 8259A ,,, (XEN) ...trying to set up timer as Virtual Wire IRQ... failed. (XEN) ...trying to set up timer as ExtINT IRQ...spurious 8259A interrupt: IRQ7. (XEN) CPU0: no irq handler for vector e7 (IRQ -8) (XEN) IRQ7 a=0001[0001,] v=60[] t=IO-APIC-edge s=0002 (XEN) failed :(. (XEN) (XEN) *** (XEN) Panic on CPU 0: (XEN) IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and send a report. Then try booting with the 'noapic' option (XEN) *** (XEN) (XEN) Reboot in five seconds... ``` I've been transcribing these logs by hand, otherwise I'd include more. I also suspect that maybe these issues could be solved by using a newer kernel for the installer? My understanding is that R4.1 will soon feature a 5.4.x kernel [1]. Are there more things to try in the meantime? Thanks! [1] https://github.com/QubesOS/qubes-issues/issues/5539#issuecomment-568863280 -- 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/f586f02e-c7cf-4143-86e8-a92258bbab9e%40googlegroups.com.
Re: [qubes-users] sys-net interfaces
On Thu, Dec 26, 2019 at 11:47:37AM +, 'awokd' via qubes-users wrote: tetrahedra via qubes-users: I haven't been able to find any documentation for what network interfaces sys-net is expected to expose internally. If I want to create my own sys-net from scratch, how does Xen/Qubes send network traffic to sys-net, to be sent onwards to my NIC? There's a brief discussion at https://www.qubes-os.org/doc/networking/, but there may be more detailed notes in the source code for Qubes' VM networking components. Qubes uses Xen's networking, so that might be the best place to begin research. Thanks, that's very helpful. -- 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/20191227061022.GA1186%40danwin1210.me.
[qubes-users] Debugging kernel suspend on Qubes - does Qubes run fsck on boot?
I'm following https://wiki.ubuntu.com/DebuggingKernelSuspend to debug a kernel suspend bug on my computer. Since there's no nvme available during suspend, I must rely on the motherboard clock for logging. The problem is that when I use the clock for logging, it loses its clock time and then the system thinks it's time to run fsck. But if the fsck takes too much time, the clock loses the logging file. To avoid the fsck, I must run tune2fs -i 0 partition, where partition is the qubes partition, which I THINK is /dev/mapper/qubes_dom0-root. The problem is that this partition already has the value 0. However when I suspend I THINK that a fsck happens, because after I input the LUKS password, the progress bar takes about an hour to complete. Since qubes shows no logging, I guess it is fsck running. So how should I prevent qubes from running fsck after doing suspend? -- 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/9df60785-ffbc-4ec2-84a3-9ad774d735a7%40googlegroups.com.
[qubes-users] how to install or use pm-suspend similar command on Qubes
I'm following https://wiki.ubuntu.com/DebuggingKernelSuspend to debug kernel suspend problems. However, on dom0 there's no pm-suspend command. How can I install SECURELY this command or how to substitute for another one? This is the command: sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" Which command does xfce use when I click the suspend button? -- 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/2af6661d-b7fd-4a3b-9fb8-6dc6ba2d6f7a%40googlegroups.com.
Re: [qubes-users] Ghost in the machine?
Thank you very much for your answers, my replies in bold below. Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, December 26, 2019 2:03 PM, 'awokd' via qubes-users qubes-users@googlegroups.com wrote: > 'Chökie Gyaltsen' via qubes-users: > > > On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users > > qubes-users@googlegroups.com wrote: > > > > In which log > > > are you seeing the above error? > > > > This message is from journalctl -ax and persisted after installation at > > everyboot until today for 3 weeks. > > Try including the -b option. I included the -b option on journalctl and the same message with 'uinput' module not being loaded and zenstored not found and being rebuiild showed up on today's boot. Thank you > > All the errors are still happening since install. I am sorry to insist, but > > the 'uinput' error is the one that worries me more, pardon my ignorance and > > thus the question: > > How can i check the signature of the module loaded? Is it possible? > > See if they persist with the above option. > > - don't top post > Mailing list etiquette: > > - trim quoted reply to only relevant portions > > - when possible, copy and paste text instead of screenshots > -- > 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/e8651f1e-cc01-502e-16e6-bc2d5709b763%40danwin1210.me. > -- 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/6Q9E7Ou6gM26SA_wQCVKsWPs98oF475sKLEY8hrcgmqkHu7SvYbZROgcNwrWygc_Wncc9XvmB2gQf6TlNPeiuks9ZnpGy8sHsCJ8s5PSAm0%3D%40pm.me. publickey - bodhisattvayana@pm.me - 0xEC5E8A90.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] How to access installer in rescue mode?
awokd: Il giorno giovedì 26 dicembre 2019 14:21:38 UTC+1, awokd ha scritto: > > Robert M: > > Claudia, > > > > Sorry for the late reply. Here are my answers: > > > >- Yes, i modified the BOOTx63.cgf file in ANACONDA. > > What were your modifications? Per > > https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer > > ? Try also > > https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer--disable-efi-runtime-services > > if you haven't. > I modified BOOTx64.cgf commenting out the mapbs and noexitboot lines. Then, following your message, I also modified the efi=attr=uc into efi=no-rs. The result does not change. > > >- The laptop has a 'VGA compatible controller: Intel Corporation UHD > >Graphics (rev 02)'. > >- No combination of keys works, even the Ctrl+Alt+canc doesn't work. > >Once the the laptop stalls the only way out is pressing the power > button. > > > > I have tried to change several things also in the UEFI setup, but either > > the screen goes blank or it get stuck with the attached message. > > I have tried to install release 4.0.1, the testing release and also the > > beta 4.1 but without any success. > > > > Merry Christmas > > > > [image: IMG_8388.JPG] > > > > > > > > Il giorno mercoledì 18 dicembre 2019 20:11:42 UTC+1, Claudia ha scritto: > >> > >> Robert M: > >>> I'm trying to install Qubes 4.0 on laptop that has UEFI firmware > >> (without the Legacy option) > >>> > >>> But I cannot get to the blue boot screen. > >>> > >>> The official "Troubleshooting UEFI related problems", requires me to > >> switch to tty2 (Ctrl+Alt+F2) . But seems that there is no combination > of > >> keys that stops the boot process before it goes to the black screen. > > This is after the first stage of the install has nearly completed, but > it sounds like you're not even getting into the first part of it. > > >>> Any hint or suggestion on how to get the installation to start would > be > >> much appreciated. > >>> > >> > >> You modified the BOOTX64.cfg file, right? And it's still freezing at a > >> black screen? > >> > >> What kind of GPU do you have? > >> > >> Is the machine still responsive, other than the screen? E.g. does the > >> caps lock key make the light come on? Or does ctrl-alt-delete reboot > it? > >> > >> I had a kind of similar problem on 4.0.2-rc2 with amdgpu graphics. > >> Adding "nomodeset" to the kernel command line fixed it. Before I > figured > >> that out, in the installer, I found I could press ctrl-alt-f2 > repeatedly > >> very early in the boot process, and about 50% of the time it would > >> switch to TTY and not freeze. No idea if it'll work for you, but it's > >> worth a try. > >> > >> - > >> This free account was provided by VFEmail.net - report spam to > >> ab...@vfemail.net > >> > >> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of > >> the NSA's hands! > >> $24.95 ONETIME Lifetime accounts with Privacy Features! > >> 15GB disk! No bandwidth quotas! > >> Commercial and Bulk Mail Options! > >> > > > > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots > -- 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/c94be158-a1ec-43bd-bd07-d0abfd887c39%40googlegroups.com.
Re: [qubes-users] kali template upgrade error
On Thu, Dec 26, 2019 at 03:01:26PM +, lik...@gmx.de wrote: > dpkg: error processing archive > /var/cache/apt/archives/kali-themes_2020.1.0_all.deb (--unpac > k): > trying to overwrite '/etc/xdg/Trolltech.conf', which is also in package > qubes-gui-agent 4.0 feels crude but worked-for-me: sudo apt-get -o Dpkg::Options::="--force-overwrite" upgrade -- 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/20191226150924.GC17393%40priv-mua.
[qubes-users] kali template upgrade error
Hi! I get the following error while upgrading a kali template which was working for at least 1 year: dpkg: error processing archive /var/cache/apt/archives/kali-themes_2020.1.0_all.deb (--unpac k): trying to overwrite '/etc/xdg/Trolltech.conf', which is also in package qubes-gui-agent 4.0 .27-1+deb10u1 Errors were encountered while processing: /var/cache/apt/archives/kali-themes_2020.1.0_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Any ideas how to solve it? Thanks in advance! -- 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/8921bdc3-091c-f8f2-4373-f639864ab732%40gmx.de.
Re: [qubes-users] UPnP in Qubes
December 23, 2019 6:09 PM, "hut7no' via qubes-users" wrote: I have a setup like this: AppVM -> FirewallVM -> NetVM -> internet and want to be able to use UPnP for the AppVM. Do any of you know how you would set this up in 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4800d296-0722-9b78-b16c-de83c5bfaffe@tt3j2x4k5ycaa5zt. nion. I don't know, but I was actually wondering about this too. You mean for automatic port forwarding, right? I would imagine you can get a UPnP daemon that allows you to set commands to be run when a client requests port forwarding, and have it run qvm-firewall or iptables/nftables accordingly. You may have to write some glue code but it should be fairly simple. See: https://www.qubes-os.org/doc/firewall/ https://qubes-core-admin-client.readthedocs.io/en/latest/manpages/qvm-firewall.html https://www.qubes-os.org/doc/networking/ https://manpages.ubuntu.com/manpages/precise/man5/upnpd.conf.5.html (Just an example. There are many implementations out there and this one may or may not be the best choice.) If you find a solution, please follow up and share what you came up with. Thanks you for the info, I'll follow up if I solve 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fefad9af-9e66-ff7c-61a2-60af4486006b%40tt3j2x4k5ycaa5zt.onion.
Re: [qubes-users] Ghost in the machine?
'Chökie Gyaltsen' via qubes-users: > On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users > qubes-users@googlegroups.com wrote: >> In which log >> are you seeing the above error? > > This message is from journalctl -ax and persisted after installation at > everyboot until today for 3 weeks. Try including the -b option. > All the errors are still happening since install. I am sorry to insist, but > the 'uinput' error is the one that worries me more, pardon my ignorance and > thus the question: > How can i check the signature of the module loaded? Is it possible? See if they persist with the above option. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/e8651f1e-cc01-502e-16e6-bc2d5709b763%40danwin1210.me.
Re: [qubes-users] Ghost in the machine?
Thank you for the answers,Below i reply in bold. Happy new year everyone! ‐‐‐ Original Message ‐‐‐ On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users qubes-users@googlegroups.com wrote: > > > > Dec 15 20:52:30 dom0 systemd-modules-load[195]: Failed to find module > > > > 'uinput' > > > > ( found info on kernel.org stating this module is for user input, is it > > > > normal that the module is not present? ) > > > > > No, it is present on mine. > > > > i do not know how to solve this, i have seen some answers on github related > > to permissions, are these permissions correct? This is the second reinstal > > of Qubes 4.0.2-preview3 > > Didn't realize you were running rc3. Have you tried 4.0.1? I installed 4.0.1 in the beginning of the month, rc3 was not available yet, and i had an even worse message on journalctl: Kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun After rc3 was made available, i installed it and the message this CPU pipe FIFO underrun was not in the logs anymore. But all the other messages are there still. > In which log > are you seeing the above error? This message is from journalctl -ax and persisted after installation at everyboot until today for 3 weeks. > > Dec 22 16:29:16 dom0 systemd-modules-load[540]: Inserted module 'uinput' > > OK, so it's working on yours too. > > > Dec 22 16:29:12 dom0 systemd[1]: Failed to start Load Kernel Modules. > > -- Subject: Unit systemd-modules-load.service has failed > > -- Defined-By: systemd > > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > > -- Unit systemd-modules-load.service has failed. > > > These messages are not so detailed on the causes on which the error > > ocurred. Is there a way to get more info, like turning on a debug mode on > > boot or something? > > Ignore this error. It does not impact Qubes functionality. Qubes is working fine, but due to the problems i had already with this machine before, after several reinstalls, including the worrying journalctl message "CPU pipe A FIFO Underrun" mentioned above; since 'uinput' is related to keyboard and mouse and it is failing, how can i be sure the version that is being loaded is not somehow tainted? Because it fails on first try, right? 'uinput' deals with keyboard and mouse and although they work fine, they seem to be perfect for logging user activity ( keyboard and mouse ). > > > > Dec 15 20:52:37 dom0 xenstored[1267]: Checking store complete. > > > > > > Dec 15 20:52:38 dom0 udisksd[1497]: Acquired the name > > > > org.freedesktop.UDisks2 on the system message bus > > > > Dec 15 20:52:38 dom0 udisksd[1497]: Error loading modules: Error > > > > opening directory '/usr/lib64/udisks2/modules': No such file or > > > > directory > > > > > Did you install something in dom0? Generally, you should not. Uninstall > > > it or reinstall Qubes and the error should go away. > > > > I did not install anything on dom0 ( how do i find what was supposedly > > installed, is there a way? ) > > This are the logs from installing the latest preview3 of 4.0.2. I installed > > it twice, the logs are the same, do you think reinstalling it will solve? > > Ignore the install logs unless you're troubleshooting an installation > issue. Instead, reference the log from a recent boot, and see if those > errors you mentioned are still present (apart from the > "systemd-modules-load.service has failed".) All the errors are still happening since install. I am sorry to insist, but the 'uinput' error is the one that worries me more, pardon my ignorance and thus the question: How can i check the signature of the module loaded? Is it possible? Thank you very much for your help. > - don't top post > Mailing list etiquette: > > - trim quoted reply to only relevant portions > > - when possible, copy and paste text instead of screenshots > > -- > > 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/72d5969d-f052-e2d4-b9bd-36cd5c962291%40danwin1210.me. > -- 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/LOHuS92AhR-_EMwHw2gpBrxSizysb3oTGiLEkP6FtE8k-t4yayuyRXmDhTLSgHnN2C-X25Bd35hqrgQ-eqOso7gPVcQ_Y0eKnCMNtTTXzKI%3D%40pm.me. publickey - bodhisattvayana@pm.me - 0xEC5E8A90.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital
Re: [qubes-users] Installer crash: IO-APIC + timer doesn't work (Dell XPS 7390)
Aaron Janse: > At this point, I got the black screen described in issue #5165 (3). > Following > the advice there, I updated my options line to the following: > ``` > options=console=vga efi=attr=uc noapic x2apic=off loglvl=all efi=no-rs > iommu=no-igfx dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan > vga=current,keep guest_loglvl=all > ``` > > With the newly verbose output, it looks like I'm back to square one: > ``` > Kernel panic - not syncing: The noapic parameter is incompatible with Xen What happens if you use an options line like the following? options=console=vga loglvl=all efi=no-rs -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/1d0eacae-6b7f-c97f-4d88-c22826a6c0f1%40danwin1210.me.
Re: [qubes-users] How to load .ISO while HVM is running
Spleen Productions: > > > I have a HVM with a bootloader .ISO loaded in the VM. > I would like to swap the cdrom and point it to another .ISO located in an > AppVM. > I cannot detach the device since i get an empty response from qubesd(see > journalctl in dom0 for details). > Is there any way to load two .ISO as --cdrom simoultaneously? > There's no easy way to do this AFAIK. You could copy the ISO into the VM, then use OS provided tools to mount it from inside. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/8375bd3f-1766-d552-24ab-a25e796548b5%40danwin1210.me.
Re: [qubes-users] How to access installer in rescue mode?
Robert M: > Claudia, > > Sorry for the late reply. Here are my answers: > >- Yes, i modified the BOOTx63.cgf file in ANACONDA. What were your modifications? Per https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer ? Try also https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer--disable-efi-runtime-services if you haven't. >- The laptop has a 'VGA compatible controller: Intel Corporation UHD >Graphics (rev 02)'. >- No combination of keys works, even the Ctrl+Alt+canc doesn't work. >Once the the laptop stalls the only way out is pressing the power button. > > I have tried to change several things also in the UEFI setup, but either > the screen goes blank or it get stuck with the attached message. > I have tried to install release 4.0.1, the testing release and also the > beta 4.1 but without any success. > > Merry Christmas > > [image: IMG_8388.JPG] > > > > Il giorno mercoledì 18 dicembre 2019 20:11:42 UTC+1, Claudia ha scritto: >> >> Robert M: >>> I'm trying to install Qubes 4.0 on laptop that has UEFI firmware >> (without the Legacy option) >>> >>> But I cannot get to the blue boot screen. >>> >>> The official "Troubleshooting UEFI related problems", requires me to >> switch to tty2 (Ctrl+Alt+F2) . But seems that there is no combination of >> keys that stops the boot process before it goes to the black screen. This is after the first stage of the install has nearly completed, but it sounds like you're not even getting into the first part of it. >>> Any hint or suggestion on how to get the installation to start would be >> much appreciated. >>> >> >> You modified the BOOTX64.cfg file, right? And it's still freezing at a >> black screen? >> >> What kind of GPU do you have? >> >> Is the machine still responsive, other than the screen? E.g. does the >> caps lock key make the light come on? Or does ctrl-alt-delete reboot it? >> >> I had a kind of similar problem on 4.0.2-rc2 with amdgpu graphics. >> Adding "nomodeset" to the kernel command line fixed it. Before I figured >> that out, in the installer, I found I could press ctrl-alt-f2 repeatedly >> very early in the boot process, and about 50% of the time it would >> switch to TTY and not freeze. No idea if it'll work for you, but it's >> worth a try. >> >> - >> This free account was provided by VFEmail.net - report spam to >> ab...@vfemail.net >> >> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of >> the NSA's hands! >> $24.95 ONETIME Lifetime accounts with Privacy Features! >> 15GB disk! No bandwidth quotas! >> Commercial and Bulk Mail Options! >> > -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/229ec7d6-e16a-4ca3-fc0e-6b940cb3e825%40danwin1210.me.
Re: [qubes-users] unsupported hardware detected with the installation of qubes 4.0.1, 4.0.2-rc2 and 4.0.2-rc3 on Dell OptiPlex 3010 Small Form Factor
rickey: > Good evening Everyone, > I have installed previously Qubes 3.2.1 on a Dell's Optiplex 3010, Small > form factor desktop pc, and I was able to use it. > When I tried to install the Qubes versions mentioned above on the same > hardware, it is showing the message into the attached screenshot - > initial.jpg. If I proceed despite it, I am finishing the installation with > the message from the attached final.jpg. After a restart, there is no > network present, and if I try to start a Disposable Fedora e.g. it doesn't > with a similar to final.jpg- message. > I have read some blog here, as well as the post in > https://github.com/QubesOS/qubes-issues/issues/3208 but no real solution > can be found there. > As Claudia has suggested, I have done an HCL- report, and attached a > screenshot - hcl.jpeg. > Please, find the link for the files > - > https://drive.google.com/drive/folders/1PP9knIZS7TbDeZlaGhESwdFK8DI6eJfm?usp=sharing. > Best, > Rickey > Have you done the steps in https://www.qubes-os.org/faq/#can-i-install-qubes-4x-on-a-system-without-vt-x-or-vt-d ? -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/b02f1e46-cc6f-2a12-18e3-56979fed3af2%40danwin1210.me.
Re: [qubes-users] Qubes/Xen doesn't comply with IOMMU grouping rules for PCI passthru
Claudia: TLDR; check bottom of https://community.amd.com/thread/241650, looks like there was a recently released related updated. Not sure if applicable to your situation. > This caused a very sneaky problem on my machine. My USB controllers are in > the same group as my > GPU, sound card, and SATA controller. So when sys-usb (or > rd.qubes.hide_all_usb) takes over those > two USB controllers, everything stops working. [4] It was quite difficult to > trace. It would have > been much easier to diagnose if grouping was enforced somewhere. I would much > rather have an error > in my logs about being unable to assign USB controllers, than have my whole > screen freeze up with > no indication why. (I got lucky that it just crashed; if something interferes > with your SATA > controller's address space it can cause disk corruption. [5]) > > I don't really know who's at fault here. Qubes? Xen? AMD? Dell? The improper grouping is probably somewhere in AGESA, which is provided to the manufacturers by AMD. It could be because of hardware related limitations, which again are supplied by AMD. Sometimes vendors take liberties (cost cutting measures) with both and break functionality, as their primary/sole concern is that Windows boots. This can especially be the case with consumer class machines such as Ryzen. Agree it would be nice if Xen handled this failure mode more gracefully. Not sure there is much Qubes can do here, though. On the other hand, my older AMD (pre-Ryzen) consumer laptop running Coreboot has correct groupings. > Intel systems > seem to just to have better grouping usually (or, are less likely to crash > when grouping rules are > violated). [6] I think that is overbroad. There are plenty of Intel systems with broken passthrough. iommu=no-igfx itself is a workaround for broken passthrough of Intel graphics. There are also plenty of AMD systems with properly implemented passthrough. > Thoughts? Is there anything Qubes can do to do avoid splitting up IOMMU > groups? Is there anything > Qubes *should* do? Should Qubes attempt to guess the IOMMU groups before > taking over devices? > Should the USB Qube option be disabled on AMD systems (you can still manually > set up sys-usb of > course)? Should we just blame Xen for not enforcing IOMMU groups in the first > place? Ultimately, it's a hardware/firmware issue. Threadripper and Epyc based AMD systems ought to be more thoroughly vetted to support passthrough. My suggestions are to disable automatic IOMMU grouping in your UEFI configuration, if possible. Otherwise, try a newer firmware version with updated AGESA code and see if it helps, or possibly add a card with additional USB controllers as that should appear in its own group. -- 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/336a9dc9-8409-3496-f0e2-9d24c06d47ab%40danwin1210.me.
Re: [qubes-users] Ghost in the machine?
'Chökie Gyaltsen' via qubes-users: > Thank you, i removed the alpha_support and with that the gtk errors i was > having vanished along with the tainted kernel messages. > Also noticed improvement of the speed of the graphics. Things appear to move > smoother and faster screen. Does that make sense? > The machine is a librem 13v3 Does make some sense if the Linux kernel used now has better support for Intel integrated graphics. Appears it must! >>> Dec 15 20:52:30 dom0 systemd-modules-load[195]: Failed to find module >>> 'uinput' >>> ( found info on kernel.org stating this module is for user input, is it >>> normal that the module is not present? ) >> > >> No, it is present on mine. > > i do not know how to solve this, i have seen some answers on github related > to permissions, are these permissions correct? This is the second reinstal of > Qubes 4.0.2-preview3 Didn't realize you were running rc3. Have you tried 4.0.1? In which log are you seeing the above error? > Dec 22 16:29:16 dom0 systemd-modules-load[540]: Inserted module 'uinput' OK, so it's working on yours too. > Dec 22 16:29:12 dom0 systemd[1]: Failed to start Load Kernel Modules. > > -- Subject: Unit systemd-modules-load.service has failed > > -- Defined-By: systemd > > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > -- > > -- Unit systemd-modules-load.service has failed. > These messages are not so detailed on the causes on which the error ocurred. > Is there a way to get more info, like turning on a debug mode on boot or > something? Ignore this error. It does not impact Qubes functionality. >>> Dec 15 20:52:37 dom0 xenstored[1267]: Checking store complete. > >>> Dec 15 20:52:38 dom0 udisksd[1497]: Acquired the name >>> org.freedesktop.UDisks2 on the system message bus >>> Dec 15 20:52:38 dom0 udisksd[1497]: Error loading modules: Error opening >>> directory '/usr/lib64/udisks2/modules': No such file or directory >> > >> Did you install something in dom0? Generally, you should not. Uninstall >> it or reinstall Qubes and the error should go away. > > I did not install anything on dom0 ( how do i find what was supposedly > installed, is there a way? ) > This are the logs from installing the latest preview3 of 4.0.2. I installed > it twice, the logs are the same, do you think reinstalling it will solve? Ignore the install logs unless you're troubleshooting an installation issue. Instead, reference the log from a recent boot, and see if those errors you mentioned are still present (apart from the "systemd-modules-load.service has failed".) -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/72d5969d-f052-e2d4-b9bd-36cd5c962291%40danwin1210.me.
Re: [qubes-users] apt update issue 111: Connection refused
Thanks, I'll check them out. On Thu, Dec 26, 2019, 1:05 PM awokd wrote: > Ondřej Šulák: > > Hello everyone, > > > > I'm pretty new to QubesOS, and I have just start experimenting. I have > > installed Qubes 3.2.1 (because of incompabilities with my HW), upgraded > > Debian Template to Debian 10 and also sys-whonix Service VM to Debian 10. > > > > When I try to run apt update in Debian Template, I got a following > errors: > > > > Err:1 https://packages.microsoft.com/debian/10/prod buster InRelease > > Could not connect to 10.137.255.254:8082 (10.137.255.254). - connect > > (111: Connection refused) > > > I'm really not sure what to do, I have spent like 3 hours trying to > solve > > this issue, but I have found nothing that was helpful. > > Qubes 3.2 is end of life, so Debian 10 and Whonix 15 have not been > tested on it. You are probably running into incompatibilities. You could > try changing /etc/qubes-rpc/policy/qubes.UpdatesProxy to use a Debian 9 > or Fedora based UpdateVM, but long term you'd want to look into getting > hardware that supports Qubes 4.x. > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots > -- 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/CAKRvif-tTFZi9kGFRFszUTt14hOBNr0%3DNyBawucT3oAHz3sbTQ%40mail.gmail.com.
Re: [qubes-users] apt update issue 111: Connection refused
Ondřej Šulák: > Hello everyone, > > I'm pretty new to QubesOS, and I have just start experimenting. I have > installed Qubes 3.2.1 (because of incompabilities with my HW), upgraded > Debian Template to Debian 10 and also sys-whonix Service VM to Debian 10. > > When I try to run apt update in Debian Template, I got a following errors: > > Err:1 https://packages.microsoft.com/debian/10/prod buster InRelease > Could not connect to 10.137.255.254:8082 (10.137.255.254). - connect > (111: Connection refused) > I'm really not sure what to do, I have spent like 3 hours trying to solve > this issue, but I have found nothing that was helpful. Qubes 3.2 is end of life, so Debian 10 and Whonix 15 have not been tested on it. You are probably running into incompatibilities. You could try changing /etc/qubes-rpc/policy/qubes.UpdatesProxy to use a Debian 9 or Fedora based UpdateVM, but long term you'd want to look into getting hardware that supports Qubes 4.x. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/f4dbe0fe-4fd2-9fc1-6f39-b9440bf111cd%40danwin1210.me.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover - Update
Ray Joseph: > I opened sys-usb settings and found the controller listed in the settings > pane (on the right). The control button/bar at the bottom entitled > "Configure strict reset for PCI devices". I clicked on the controller in > the ‘selected’ window, then clicked the strict reset button. The > controller was then highlighted. After applying the changes, I restarted > sys-usb. It worked. > > > > It was unclear that the controller did not already have the strict reset > button ‘on’. > > The newly built vm uses the usb mouse. > > It is curious that the mouse is also active in dom0. Great! I suggest changing sys-usb back to HVM. PV is not as secure. > I am using a windows laptop to take notes and work the web including this > session. While the mouse works on dom0 on the other machine and the vm, it > does not work on the windows machine (probably because it is not plugged > into it). I am excited to learn how to work in qubes – being able to jump > from dom0 to vms, take notes, post messages, email smoothly. Qubes uses the mouse in sys-usb for all VMs. This should include a Windows VM as well, but I am not following from the above if that is what you are trying to do. -- 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/6e450e25-8fb3-b707-4531-53276d995d1a%40danwin1210.me.
Re: [qubes-users] sys-net interfaces
tetrahedra via qubes-users: > I haven't been able to find any documentation for what network > interfaces sys-net is expected to expose internally. If I want to create > my own sys-net from scratch, how does Xen/Qubes send network traffic to > sys-net, to be sent onwards to my NIC? > There's a brief discussion at https://www.qubes-os.org/doc/networking/, but there may be more detailed notes in the source code for Qubes' VM networking components. Qubes uses Xen's networking, so that might be the best place to begin research. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/10c56f40-288c-16e3-d883-ea221b15798d%40danwin1210.me.
Re: [qubes-users] swap disk trim
Eva Star: > Hello, > To enable swap trim need to add "discard=once". > The string at /etc/fstab will be like this? > "*default,discard=once,x-systemd-device*" > After editing fstab need to run something? > Thanks > Yes, to the line: /dev/mapper/qubes_dom0-swap swap swap defaults,x-systemd.device-timeout=0 0 0 You would add: /dev/mapper/qubes_dom0-swap swap swap defaults,discard=once,x-systemd.device-timeout=0 0 0 Should only have to save and reboot afterwards. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/2a5b9500-d907-1236-2c23-6235b98e0d69%40danwin1210.me.
Re: [qubes-users] Startup/Shutdown thin pool trim - where to insert with systemd?
brendan.h...@gmail.com: > If fedora were still running init, I'm pretty sure I could find the right > place to do this, but with systemd, I am quite discombobulated. Perhaps that is the "do one thing, and do it well" systemd strives for. > 1. Where/how do I insert a thin_trim of the qubes_00 pool during startup > when it's available (e.g. after luks volume is mounted) but before the pool > is activated? How do I do it safely (ensuring that activation only occurs > on exit of thin_trim)? Maybe /lib/systemd/system/lvm2-pvscan@.service? I see a /lib/systemd/system/lvm2-pvscan@.service.d/30_qubes.conf too. > 2. Where/how do I insert a thin_trim of the qubes_00 pool during shutdown > after it is deactivated but before the luks volume (the VG) is dismounted? Possibly the ExecStop in the first file. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/937ef057-f876-121f-6e12-a4aafad1ea91%40danwin1210.me.
Re: [qubes-users] Newbie: Help Needed
B. Kent: > >- Created the USB installer disk and then tried to modify the >BOOTX64.cfg file (with VI), USB filesystem is Read Only > - I've read that I need to mount the Qubes ISO on my laptop, edit > BOOTX64.cfg from the ISO and then save that file...then create a new > USB > install disk > - Problem is, I'm not sure how to do that via terminal...(if someone > can detail, would appreciate it.) >- Problem #2 - Edits to the BOOTX.64.cfg file * See attached (Need help >in understanding what should be done to make it to the installer screen) Of the two options at the beginning of https://www.qubes-os.org/doc/uefi-troubleshooting/, the first is probably easier. Since you're running Linux already, I think you can do it through the Files browser. Just make sure to edit the file as root. You may not need the efi=no-rs option. In your case, I suspect it's the nvidia card causing problems. Try to disable it in UEFI config. If not possible, you probably want at least nouveau.modeset=0, or the full set of nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/23cdbe04-1dc0-afd4-d270-b7ca9d2ef59c%40danwin1210.me.
