Re: [qubes-users] Re: USB Controller passthru to HVM on Qubes 3.1
I do have a system running 3.2, but I can't keep Windows 7 running on it -- it just dies after 10 minutes or so. Does anyone have any ideas? I launched the HVM from the command line in the hopes I might see an error, but the system starts up clean -- just no device showing on Windows. -- 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/de2b2545-885c-4d2e-8076-1607ab9731d1%40googlegroups.com.
[qubes-users] Re: USB Controller passthru to HVM on Qubes 3.1
Has anyone ever gotten passthroughs to work? On Tuesday, July 30, 2019 at 9:51:45 PM UTC-6, Pete Howell wrote: > > I'm trying to passthrough a StarTech 2-Port USB 3.1 Card (#PEXUSB312A2) to > an HVM running Windows 7, and the device does not show up. The device > shows up in an lspci as: > > 01:00.0 USB controller: ASMedia Technology Inc. Device 2142 > > $ xl pci-assignable-list > :01:00.0 > :03:00.0 > $ xl pci-assignable-add 01:00.0 > libxl: warning: libxl_pci.c:636:libxl__device_pci_assignable_add: > :01:00.0 already assigned to pciback > > I have tried attaching it from the VM manager and from the command line: > > $ qvm-pci -a win7 01:00.0 > $ qvm-start win7 > (no errors) > $ qvm-pci -l win7 > ['01:00.0'] > > What I don't understand is why the device doesn't show up in the device > manager on Windows. The driver software for Windows also doesn't see the > device. > > Is there something that I'm missing to get the passthrough to work on a > Windows HVM?? > -- 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/b4273c42-e31a-436c-9d5b-26e4bacf25a7%40googlegroups.com.
[qubes-users] USB Controller passthru to HVM on Qubes 3.1
I'm trying to passthrough a StarTech 2-Port USB 3.1 Card (#PEXUSB312A2) to an HVM running Windows 7, and the device does not show up. The device shows up in an lspci as: 01:00.0 USB controller: ASMedia Technology Inc. Device 2142 $ xl pci-assignable-list :01:00.0 :03:00.0 $ xl pci-assignable-add 01:00.0 libxl: warning: libxl_pci.c:636:libxl__device_pci_assignable_add: :01:00.0 already assigned to pciback I have tried attaching it from the VM manager and from the command line: $ qvm-pci -a win7 01:00.0 $ qvm-start win7 (no errors) $ qvm-pci -l win7 ['01:00.0'] What I don't understand is why the device doesn't show up in the device manager on Windows. The driver software for Windows also doesn't see the device. Is there something that I'm missing to get the passthrough to work on a Windows HVM?? -- 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/d1f524b1-ddad-4b59-96bb-28a5a7cb8bce%40googlegroups.com.
Re: [qubes-users] Dell XPS 15 9570 UEFI Issue
Can you post the link to the instructions you followed, please. I did finally give up on this and am back to Windows 10 on my Dell laptop; but, I'd like to give it another try. I should also mention that the ISO would never boot properly from the UEFI partition on the USB stick, so I'm guessing that since the installer would only boot in legacy mode, that that may be part of the reason I get a successful Qubes install with no UEFI boot partition. Does anyone know why the Qubes 4.0.1 image does not boot in UEFI? The partition shows up to boot from, but you just get a blank screen and no installer. On Tuesday, June 4, 2019 at 6:00:37 PM UTC-6, y...@tutanota.com wrote: > Update...I tried the efi=no-rs section in the UEFI troubleshooting guide > again because I didn't try it from scratch and I got it to boot! The boot > option shows up under UEFI but it requires Legacy Options ROMs to still be > enabled in the BIOS. > > > > > Steps to install Qubes: > > 1. BIOS: Enable Legacy Options ROMs, Disable Secure Boot, SATA: AHCI mode > > 2. Boot USB drive in legacy mode - USB Storage Device. > > 3. Perform the steps in the UEFI troubleshooting section called "Installation > freezes before getting to Anaconda / disable EFI runtime services". I used a > Ubuntu liveCD to edit the xen.cfg file. When starting the installation, add > kernel parameter nouveau.modeset=0. -- 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/6e6e4d35-bf1a-4d62-9cbe-f1aa995f0d68%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Dell XPS 15 9570 UEFI Issue
I meant to say that the xen.cfg file was 0 length; not the efi file. -- 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/da465528-5450-4c5b-bf3d-3e0562a1f4eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Dell XPS 15 9570 UEFI Issue
I had a problem with v4.0.1 hanging halfway through the install, but adding "mapbs=1 noexitboot=1" seems to have fixed the issue. Unfortunately, the system does not boot -- it does not see a bootable device. I tried following the UEFI troubleshooting article to no avail. Copying /boot/efi/EFI/qubes to /boot/efi/EFI/BOOT with all the accompanying instructions did not work. I did notice that the xen-*efi file was 0 length, so I also followed the instructions on adding the entries (with the correct file versions of course), but the last instruction talks about running the efibootmgr command, which doesn't run because there is no efivars kernel module. I personally hate UEFI, but these newer systems leave you no choice -- you CANNOT boot from an internal drive without it. Does anyone know how to resolve this? I have a nice and very expensive brick that I'd like to turn into a production system. Any help would be greatly appreciated. -- 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/e595613f-507c-455f-a6a7-ca941ecb2719%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: XScreenSaver for dom0 pops up
Thanks Opal! Disabling the Compositor definitely fixes this issue.
On Monday, February 27, 2017 at 5:10:57 PM UTC-7, Opal Raava wrote:
> On Monday, February 27, 2017 at 9:41:20 PM UTC+1, ianr...@gmail.com wrote:
> > On Wednesday, October 26, 2016 at 8:43:12 AM UTC-4, John Maher wrote:
> > > I'm getting the strangest thing on my screen. I'll be working and the
> > > XScreenSaver dialog pops up (indicating the screen is locked) and the
> > > screen goes black. However, the screen is not locked. I have to move a
> > > window around to redraw my screen. This has always happened since I
> > > started using Qubes about 3 weeks ago. There appears to be no pattern
> > > that prompts this response. Bizarre! Any thoughts?
> > >
> > > Thanks.
> > >
> > > John
> >
> > I found that this happened when I had the Qubes VM Manager set to appear on
> > all desktops ("Always on Visible Worksace"). When I stopped that, it
> > stopped the problem. Tried this 5 or 6 times on 2 different machines.
> > Running v.3.2 with and without Feb. updates; no difference.
> >
> > HTH,
> >
> > --Ian
>
> Oh that's interesting, I found that disabling the compositor (Menu>System
> Tools>Window Manager Tweaks>Compositor) solves the problem for me and also
> for somebody else on the github tracker entry.
>
> I can't find the 'always on visible workspaces' settings, but I also lost the
> tray icon for the Qubes VM Manager somehow.
--
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/1471dbfd-ea56-478f-ad82-c5713abfbd0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: python3-dnf-plugins-qubes-hooks-3.2.18-1.fc23.x86_64: checksum doesn't match
I switched to the new FC25 template and now get a checksum doesn't match on xen-libs-4.6.6-29.fc25.x86_64. Anyone have any ideas? On Wednesday, August 23, 2017 at 2:35:29 PM UTC-6, Pete Howell wrote: > Running a fresh install of Qubes-R3.2, and when doing an FC23 update, all the > packages download until you get to > python3-dnf-plugins-qubes-hooks-3.2.18-1.fc23.x86_64, which fails with a > checksum doesn't match error. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/07f8231d-49c4-4d89-a7fd-f21d5d4ed31e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] python3-dnf-plugins-qubes-hooks-3.2.18-1.fc23.x86_64: checksum doesn't match
Running a fresh install of Qubes-R3.2, and when doing an FC23 update, all the packages download until you get to python3-dnf-plugins-qubes-hooks-3.2.18-1.fc23.x86_64, which fails with a checksum doesn't match error. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3e2af2c4-332c-4d40-bbb6-66bdde6338b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes Windows 10?
I tried to pull from the testing repository with the following: > qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-windows-tools It lists version 3.2.2-3 as available, but downloaded failed -- "All mirrors were tried". How can one get the test version? On Saturday, September 17, 2016 at 1:55:58 AM UTC-6, Pawel Debski wrote: > Folks, > > I have Qubes 3.2 up, updated & > running like a charm. Now the Microsoft challenge. The doc @ > https://www.qubes-os.org/doc/windows-appvms/ instructs to use > Windows 7. Do you suggest to stick with version 7 or go ahead to > 10 / 8? > > > > -- > > > > Z powazaniem / Best Regards > > Mit freundlichen Gruessen / Meilleures salutations > > Pawel Debski -- 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/497fb2ae-1927-455c-938d-bfcd31f77224%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
