[qubes-users] Re: X1C6 Undervoltong?
On Monday, February 25, 2019 at 12:43:29 PM UTC-8, dexint...@gmail.com wrote: > So I found this > > https://github.com/georgewhewell/undervolt > > How would I go about doing this in dom0? anyone? -- 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/fba5-e4e3-4805-92e2-a4e95795a70a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Lenovo Carbon X1 Gen 6 20KHCTO1WW
On Tuesday, February 26, 2019 at 3:05:50 PM UTC-8, Nick Johnson wrote: > Everything was surprisingly smooth and easy. Thanks to BIOS and kernel > upgrades, I didn't need to apply any patches to get suspend/restore working. > I made the following adjustments: > 1. Change BIOS sleep mode from Windows to Linux. > 2. Remove the Thunderbolt 3 controller from the device list for the sys-usb > Qube. > 3. Followed the DPI scaling guide at > https://github.com/Qubes-Community/Contents/blob/master/docs/customization/dpi-scaling.md > to have sane-looking fonts and UI elements. I have the WQHD display, and > found that setting the DPI to 192, while not precisely accurate, gave a good > result. In VMs, a text-scaling-factor of 1.25 seems about right; > scaling-factor appears to have no effect. > > > I did NOT enable BIOS support for Thunderbolt 3 as recommended in some other > HCL reports; doing so fixed the lockup-on-wake issue, but at the cost of > disabling all USB devices. Leaving this disabled and removing the thunderbolt > controller from the sys-usb device list fixes the issue and doesn't seem to > affect USB support at all, as far as I can tell. > > > The following peripherals are tested and functional: > - USB > - Keyboard, trackpad > - Built-in microphone > - Built-in camera > - Sound output > - Suspend and restore > > > I haven't yet tested HDMI output, but based on other reports don't anticipate > trouble. Have you performed a throttle fix on the x1 carbon yet? I haven't committed to QUBES because I don't know exactly how to undervolt the X1C6. -- 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/b92c438a-8df5-427b-b722-0e3f038ce38c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.
On Wednesday, March 27, 2019 at 8:57:42 AM UTC+5:30, Jayen Desai wrote: > On Wednesday, March 27, 2019 at 5:21:23 AM UTC+5:30, unman wrote: > > On Tue, Mar 26, 2019 at 02:00:24PM -0700, CooSee wrote: > > > snip ! > > > > > > change the default entry to smp=on in xen.cfg or BOOTX64.CFG if using > > > UEFI. > > > > > > greetings > > > > > > > Shouldn't that be "smt=on"? > > > > You should probably look at QSB#43 before doing this in any case. > > The relevant Xen advisory (273) said that for HVM and PVH guests, > > leakage can only be prevented entirely by disabling SMT/Hyper-threading. > > I don't think that advice has changed, despite the provision of patches > > now incorporated in to Qubes. > > It appears that "smt=on" is default. However I passed that as a parameter to > the kernel command line. However the problem still remains. It brings up only > 4 CPUs instead of 8 CPUs. Please help. I have gone through QSB#43 and Xen advisory 273 and I understand that only Intel core CPUs are affected by them. My laptop is Lenovo Ideapad 330 15ARR model. It is AMD Ryzen 5 2500 quadcore system. I believe it should not be impacted by the above advisories. This is to further clarify 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/94b9e5d2-4bcf-46cb-ba2b-39e722d672eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HVM + Kernel: None = distorted graphics
Hi, I've been trying to get Wireguard up and running following the instructions referenced from this issue: https://github.com/QubesOS/qubes-issues/issues/3591 I've tried installation in both Fedora 29 and Debian 9-based templates. The problem is, I can switch to HVM mode, but as soon as I set the kernel to "(none)" in either template, any attempt to bring up a terminal gives me a window with distorted graphics inside. My impression is that kernel has to be none for the kernel modules to be loaded properly? I'm not really sure why this is happening. Dom0 has a different DPI setting than the baseline templates, although that doesn't seem to cause problems usually. I would appreciate any help. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/90695bc3-2297-44af-90cc-4f04a4d7e315%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.
On Wednesday, March 27, 2019 at 5:21:23 AM UTC+5:30, unman wrote: > On Tue, Mar 26, 2019 at 02:00:24PM -0700, CooSee wrote: > > snip ! > > > > change the default entry to smp=on in xen.cfg or BOOTX64.CFG if using UEFI. > > > > greetings > > > > Shouldn't that be "smt=on"? > > You should probably look at QSB#43 before doing this in any case. > The relevant Xen advisory (273) said that for HVM and PVH guests, > leakage can only be prevented entirely by disabling SMT/Hyper-threading. > I don't think that advice has changed, despite the provision of patches > now incorporated in to Qubes. It appears that "smt=on" is default. However I passed that as a parameter to the kernel command line. However the problem still remains. It brings up only 4 CPUs instead of 8 CPUs. Please help. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/11a003d7-94ca-4d3f-ac89-9840d336dec0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't Start Network, V4
On Mon, Mar 25, 2019 at 04:20:48PM -0700, Ray Joseph wrote: > I have installed Qubes on a Toshiba laptop with wirless only. When > attempting to start sys-net from Qube Manager, an error is emitted: > Domain sys-net has failed to start: internal error: Unable to reset PCI > device 000:00:14.0: Internal error: > libxenlight failed to create new domain 'sys-net'. > > lpsci reports the Network controller correctly. > > All items in (Dom0) Editing Wi-Fi connection 1 are greyed out and > unresponsive. > > A previous message said to look at the logs in > /var/lob/libvirt/... > but when I attempt to open libvirt, I get a permission denied error. I have > tried sudo but get the same result. > > I would appreciate any suggestions, thank you. > Read www.qubes-os.org/doc/assigning-devices particularly the section on PCI passthrough issues. These features can now be accessed in the QubeManager GUI - look at the Devices tab for sys-net Settings, and the "Configure Strict Reset" 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 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/20190327005540.eecl3rpzdwptyerl%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-usb based on fedora-29-minimal >> what am I missing?
On Sat, Mar 23, 2019 at 11:20:17AM +0100, onw7two99 wrote: > Hello Qubes Community, > > I have been trying to get sys-usb working using a fedora-29-minimal template > > Unfortunately it will not work, even after installing all packages which > "should" be enough to get sys-usb working (Link > https://www.qubes-os.org/doc/templates/fedora-minimal/). > > If I use the default fedora-28 (fat template) for sys-usb, everything is > working and I can attach my external harddrive to an AppVM. > If I use my custom build template for sys-usb, other USB devices work, > but I can't attach a harddrive to another AppVM, from the GUI it looks > like the drive is attached, but it is not shown in nautilus in the > target-AppVM, where I can then click on it and mount it. > The obvious question is, IS it attached to the qube? and HOW? Check what the widget says (I assume that's what you mean by GUI), then open a konsole in dom0 and run qvm-usb. Try to attach the device at the command line. Run qvm-usb again. Then in qube, run lsusb - what do you see? Incidentally, what happens if you use qvm-block to attach partition from the harddrive ? Does the drive appear in nautilus in the qube then? -- 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/20190327004917.y6l5iyvcmutwrzgk%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: packages for conversion of pdfs to trusted pdfs
On Tue, Mar 26, 2019 at 11:33:46PM +, lik...@gmx.de wrote: > On 3/26/19 12:46 AM, 22rip-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote: > > I am not sure of why this is happening in your case but have you tried > > creating a new -dvm again? Does the issue persist? > > > What do you mean exactly by creating a new -dvm again? > > It happens every time I use the dvm based on the minimal template. If I > switch back to a dvm based on fedora-29, I can use the feature again. The > issue persists also after reboot. Is there more needed that the stated > pre-requisites? You have installed the qubes-pdf-converter package, (And all strange packages that it brings)? -- 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/20190327003550.ld22cs7526wwhbik%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] "Virtualization type: none" with Dell Latitude 5590
Claudio Chinicz wrote on 3/26/19 2:44 PM: Hi All, I've just installed Qubes 4.0.1 on a brand new Dell Latitude 5590 (Intel i5/8250U, with 16GB RAM) using the downloaded ISO burnt to a UBS stick prepared on a Windows machine with Rufus (partition scheme GPT target system UEFI). I've booted the new machine on UEFI mode and the firmware Virtualization settings all enabled (there are 3 parameters here: "Virtualization", which is I suppose is VT-x, "VT for Direct I/O", which I suppose stands for VT-d and "Trusted Execution"). When I issue lscpu command on dom0 I get "Virtualization type: none". What's wrong? Why I do not see virtualization on dom0? I run a Windows HVM, which confirms Virtualization (VT-x) is available. But what about VT-d? Isnt it available for isolation purposes? Dom0 is basically a VM running on top of Xen, so all it's reporting is the emulated CPU (to over-simplify things a bit). In order to get the actual values, ask Xen directly with "xl info". You can also run "qubes-hcl-report". -- 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/89217546-d21b-b030-acb7-e18be0eaceb9%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't Start Network, V4
Ray Joseph wrote on 3/25/19 11:20 PM: I have installed Qubes on a Toshiba laptop with wirless only. When attempting to start sys-net from Qube Manager, an error is emitted: Domain sys-net has failed to start: internal error: Unable to reset PCI device 000:00:14.0: Internal error: libxenlight failed to create new domain 'sys-net'. lpsci reports the Network controller correctly. All items in (Dom0) Editing Wi-Fi connection 1 are greyed out and unresponsive. A previous message said to look at the logs in /var/lob/libvirt/... but when I attempt to open libvirt, I get a permission denied error. I have tried sudo but get the same result. I would appreciate any suggestions, thank you. You do have to do it with sudo. In dom0, you are trying "sudo ls /var/log/libvirt/libxl"? -- 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/cb49f44f-2ca5-64fc-3a8e-8f9fb2d6c50f%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.
On Tue, Mar 26, 2019 at 02:00:24PM -0700, CooSee wrote: > snip ! > > change the default entry to smp=on in xen.cfg or BOOTX64.CFG if using UEFI. > > greetings > Shouldn't that be "smt=on"? You should probably look at QSB#43 before doing this in any case. The relevant Xen advisory (273) said that for HVM and PVH guests, leakage can only be prevented entirely by disabling SMT/Hyper-threading. I don't think that advice has changed, despite the provision of patches now incorporated in to 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/20190326235121.rgktn6g6yjr3asdp%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Compiling kernel modules
Zbigniew Łukasiak wrote on 3/24/19 4:22 PM: 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. That should be all you have to do. Might be an issue with fedora-29. Does it work with 28? -- 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/148d100f-7ca8-b0d7-9d79-8c4fd1d22428%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: packages for conversion of pdfs to trusted pdfs
On 3/26/19 12:46 AM, 22rip-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote: > I am not sure of why this is happening in your case but have you tried > creating a new -dvm again? Does the issue persist? > What do you mean exactly by creating a new -dvm again? It happens every time I use the dvm based on the minimal template. If I switch back to a dvm based on fedora-29, I can use the feature again. The issue persists also after reboot. Is there more needed that the stated pre-requisites? -- 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/d26c10a7-ad15-5146-66dc-3967a5c677f1%40gmx.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: anyone else getting fails on apt-get update debian-9 ?
On Tue, Mar 26, 2019 at 06:42:03PM +, Jon deps wrote: > On 3/26/19 4:17 AM, haaber wrote: > > > > > > On 3/26/19 2:33 PM, Jon deps wrote: > > > On 3/26/19 12:17 AM, unman wrote: > > > > On Tue, Mar 26, 2019 at 10:48:08AM +1100, haaber wrote: > > > > > On 3/26/19 10:42 AM, Jon deps wrote: > > > > > > Err:7 https://cdn-aws.deb.debian.org/debian jessie-backports Release > > > > > > 404 Not Found > > > > > > Reading package lists... Done > > > > > > E: The repository 'https://deb.debian.org/debian jessie-backports > > > > > > Release' does no longer have a Release file. > > > > > > N: Updating from such a repository can't be done securely, and is > > > > > > therefore disabled by default. > > > > > > N: See apt-secure(8) manpage for repository creation and user > > > > > > configuration details. > > > > > > > > > > > a test run inside an app vm (with direct sys-firewall access, to avoid > > > > > tor-related false errors) does confirm your observation for me. Is > > > > > this > > > > > qubes-related or debian-related ? If the second one applies, we > > > > > discuss > > > > > it in the wrong mailing list :) > > > > > > > > It's not a Qubes issue. > > > > jessie-backports was deprecated since June last year. The Release file > > > > signing expired last month and it was removed from mirrors last week. > > > > > > > > The packages can still be found at archive.debian.org, and you can > > > > change your sources list to use this, but the Release file is still > > > > expired. > > > > You can work round this by getting a new copy of the signing key (if you > > > > can) and updating with apt-key. > > > > > > > > > > > > > so do I need ? > > > deb https://deb.debian.org/debian jessie-backports main > > > > > > ( I don't even know what it is, I'm guessing it is the default > > > /etc/apt/sources.list > > > > > > so maybe I missed a memo? ) > > > > > > > > > > > > if not then just #comment it out and problem solved ? > > > > As we just learned, Unman is quite busy (thank you unman!). What I would > > do, is to try it out in an AppVM : comment it out and run apt-get update > > and then apt-get upgrade. If somethings messes, just shutdown the > > AppVM (thereby taking all the mess into nirvana) : thats a short play > > coming with no risk! If upgrading without that line works easily (I > > guess so), do the same in the template. Bernhard > > > > > > Bernhard > > > > Sorry I don't see the point of doing it in an AppVM, myself. I understand > you think it might brake the package list, but I can always just comment it > back in and apt-get update, in my case Debian-9 is not my main Template > ..though it seems from reading here recently maybe it should be ? > :) > > My question is , If this is the default /sources.list and users don't > regularly go and change their sources.list isn't this going to break > on everyone's systemsand hence some attention should be paid to it. > > > > This posting is meant for the group, not any one user , be it Mr. Unman > or anyone > > > > > My 2nd question is simply what is backports anyway , and what would be a > suggested fix if #commenting it out .. isn't a great idea ? > Debian provides a relatively long lived stable release. Unfortunately this means that the software can get somewhat dated. Backports is a way of working round this by taking packages from the next release and back porting them so that they work with stable. (Contrast this with the 9 monthly cycle of Fedora or 6 months for Ubuntu) It wont add anything, and you would not (I think) never have installed from that repository. You will lose nothing by commenting it out. That line was included in error in a build of the Debian-9 template, and has now been removed. Sorry that I missed this - I overlooked the bit where you said it was Debian-9. unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190326232426.xuwhguzwrwozc2ah%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] "Virtualization type: none" with Dell Latitude 5590
Hi All, I've just installed Qubes 4.0.1 on a brand new Dell Latitude 5590 (Intel i5/8250U, with 16GB RAM) using the downloaded ISO burnt to a UBS stick prepared on a Windows machine with Rufus (partition scheme GPT target system UEFI). I've booted the new machine on UEFI mode and the firmware Virtualization settings all enabled (there are 3 parameters here: "Virtualization", which is I suppose is VT-x, "VT for Direct I/O", which I suppose stands for VT-d and "Trusted Execution"). When I issue lscpu command on dom0 I get "Virtualization type: none". What's wrong? Why I do not see virtualization on dom0? I run a Windows HVM, which confirms Virtualization (VT-x) is available. But what about VT-d? Isnt it available for isolation purposes? Thanks in advance for any insight. Best Regards, Claudio -- 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/q7ddsc%249ne%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Announcement: Qubes Tor onion services will no longer be maintained
22...@tutamail.com: My understanding is: The -gw and -ws templates, -dvm, appvm, etc and functionality will remain...correct? The Qubes-os.org onion site is going away...right? I have been keeping pretty good track of my changes from default install(dom0 and templates) over the past few year when I originally installed 4.0, but "...have been relying on (e.g., for package repos..." might have been something I did a while ago. How would one check this? Yes the qubes onion hosting (website and repo) is gone, but the announcement from Andrew said that unman is working on hosting it again (thank you unman!) Until that's back up the only thing that needs to be changed is your update source, if you changed it to the qubes onion repo before (the whonix onion repo is still working). To check, in debian/whonix templates, look in /etc/apt/sources.list.d/qubes-r?.list (? is 4 or 3 depending on qubes version). If you have a .onion address in there it needs to be changed back to the clearnet address until the onion repo is back up. In dom0 (and i think in fedora templates too) the relevant files are in /etc/yum.repos.d/ -- Jackie -- 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/7084f490-06d7-d782-f197-2f4e165f54d4%40bitmessage.ch. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.
snip ! change the default entry to smp=on in xen.cfg or BOOTX64.CFG if using UEFI. greetings -- 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/4d98ad4f-ccea-4765-9bce-fd144861c5f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Booting Qubes 4.0 installation ISO fails with kernel panic
On Monday, March 25, 2019 at 3:41:08 AM UTC+1, thengu wrote: > 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 i assume the right format is ' noapic nolapic smp=off x2apic=off? acpi=off ' etc. << and not true or false. greetings -- 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/a2783616-5cac-4eaf-a1b9-9e39d81b5689%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
hello, i tried X11 with "Option AccelMethod=none" with newer kernel with no artifacts and login was possible, so the culprit is radeonsi_dri.so from mesa-dri package. i somehow managed to switch to FC29 and FC29 Updates and installed the newest xorg-x11-drv-amdgpu + xorg-server + mesa-dri-drivers + lightdm, but now lightdm freezes completely. here are some xorg-log errors: (WW) AMDGPU(0): gbm_create_device returned NULL, using ShadowFB [ 1802.400] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_query_sw_info) [ 1802.400] (EE) AIGLX error: unable to load driver swrast [ 1802.400] (EE) GLX: could not load software renderer [ 1802.400] (II) GLX: no usable GL providers found for screen 0 --- lightdm errors: gbm: failed to open any driver (search paths /usr/lib64/dri) gbm: Last dlopen error: /usr/lib64/dri/radeonsi_dri.so: undefined symbol: amdgpu_query_sw_info failed to load driver: radeonsi gbm: failed to open any driver (search paths /usr/lib64/dri) gbm: Last dlopen error: /usr/lib64/dri/kms_swrast_dri.so: undefined symbol: amdgpu_query_sw_info failed to load driver: kms_swrast gbm: failed to open any driver (search paths /usr/lib64/dri) gbm: Last dlopen error: /usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_query_sw_info failed to load swrast driver /bin/X: symbol lookup error: /usr/lib64/xorg/modules/drivers/amdgpu_drv.so: undefined symbol: drmModeListLessees which packages i have to install to only get X11 working ? most of packages are not upgraded, e.g python2 and python3! or can i use some important packages from qubes r4.1 repo ? this is really bugging me, because the Card is working pefect on FunToo. i could use onboard Intel-igfx, but then i had to always switch the cables to enjoy perfectly working FunToo with my new RX 590 ;-) very grateful for any help. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b779487c-83eb-4c4a-a765-f0ba4944d204%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Xorg.0.log.old Description: Binary data Xorg.1.log.old Description: Binary data shmoverride constructor running X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 Build Operating System: 4.19.9-300.fc29.x86_64 Current Operating System: Linux dom0 4.19.29-1.pvops.qubes.x86_64 #1 SMP Tue Mar 19 03:49:04 UTC 2019 x86_64 Kernel command line: root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-0dc31baf-2c25-4b70-9f0e-549a4da60935 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rhgb quiet Build Date: 26 February 2019 08:03:46PM Build ID: xorg-x11-server 1.20.4-1.fc29 Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 26 19:26:26 2019 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (II) AMDGPU(0): [KMS] Kernel modesetting enabled. gbm: failed to open any driver (search paths /usr/lib64/dri) gbm: Last dlopen error: /usr/lib64/dri/radeonsi_dri.so: undefined symbol: amdgpu_query_sw_info failed to load driver: radeonsi gbm: failed to open any driver (search paths /usr/lib64/dri) gbm: Last dlopen error: /usr/lib64/dri/kms_swrast_dri.so: undefined symbol: amdgpu_query_sw_info failed to load driver: kms_swrast gbm: failed to open any driver (search paths /usr/lib64/dri) gbm: Last dlopen error: /usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_query_sw_info failed to load swrast driver /bin/X: symbol lookup error: /usr/lib64/xorg/modules/drivers/amdgpu_drv.so: undefined symbol: drmModeListLessees
[qubes-users] Re: anyone else getting fails on apt-get update debian-9 ?
On 3/26/19 4:17 AM, haaber wrote: On 3/26/19 2:33 PM, Jon deps wrote: On 3/26/19 12:17 AM, unman wrote: On Tue, Mar 26, 2019 at 10:48:08AM +1100, haaber wrote: On 3/26/19 10:42 AM, Jon deps wrote: Err:7 https://cdn-aws.deb.debian.org/debian jessie-backports Release 404 Not Found Reading package lists... Done E: The repository 'https://deb.debian.org/debian jessie-backports Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. a test run inside an app vm (with direct sys-firewall access, to avoid tor-related false errors) does confirm your observation for me. Is this qubes-related or debian-related ? If the second one applies, we discuss it in the wrong mailing list :) It's not a Qubes issue. jessie-backports was deprecated since June last year. The Release file signing expired last month and it was removed from mirrors last week. The packages can still be found at archive.debian.org, and you can change your sources list to use this, but the Release file is still expired. You can work round this by getting a new copy of the signing key (if you can) and updating with apt-key. so do I need ? deb https://deb.debian.org/debian jessie-backports main ( I don't even know what it is, I'm guessing it is the default /etc/apt/sources.list so maybe I missed a memo? ) if not then just #comment it out and problem solved ? As we just learned, Unman is quite busy (thank you unman!). What I would do, is to try it out in an AppVM : comment it out and run apt-get update and then apt-get upgrade. If somethings messes, just shutdown the AppVM (thereby taking all the mess into nirvana) : thats a short play coming with no risk! If upgrading without that line works easily (I guess so), do the same in the template. Bernhard Bernhard Sorry I don't see the point of doing it in an AppVM, myself. I understand you think it might brake the package list, but I can always just comment it back in and apt-get update, in my case Debian-9 is not my main Template ..though it seems from reading here recently maybe it should be ? :) My question is , If this is the default /sources.list and users don't regularly go and change their sources.list isn't this going to break on everyone's systemsand hence some attention should be paid to it. This posting is meant for the group, not any one user , be it Mr. Unman or anyone My 2nd question is simply what is backports anyway , and what would be a suggested fix if #commenting it out .. isn't a great idea ? -- 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/c4692797-9a79-027c-79e2-5d9520f5085e%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Only 4 CPUs are brought up. Remaining 4 are parked.
On Tuesday, March 26, 2019 at 5:36:42 PM UTC+5:30, jayen...@gmail.com wrote: > Only 4 CPUs are brought up. Remaining 4 are parked. -- 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/c9d36778-84e4-4520-b814-6739f8466464%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Only 4 CPUs are brought up. Remaining 4 are parked.
Only 4 CPUs are brought up. Remaining 4 are parked. -- 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/d26c5f98-7c02-4aa6-a55b-3bcece56105a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
